Cutting and Marker

Between a released Production Order and a Batch that's stitching garments sits the cutting room. The cutting pipeline turns a plan into bundles: someone draws a Marker (the cutting layout), someone spreads fabric and runs the Cutting Order, and the resulting cut bundles get handed to a Batch to start stitching.

Two doctypes drive it: Marker Order and Cutting Order.

How they fit together

Marker Order declares the layout: this pattern, these sizes, this many pieces per ply, this much fabric per length.

Cutting Order does the work: spread N plies on the table, cut to the marker, handle the rolls, record what came out.

Most cuts go through both. A few cases (re-cuts, sample runs) use a shortened flow.

The pipeline at a glance

For a typical batch:

1. A Production Batch is created against a Released Production Order.
2. A Marker Order is created for the Batch, declaring the marker the cutting room will use.
3. A Cutting Order is created against the Marker Order, declaring the lay plan.
4. The Cutting Order moves through workflow states: Pending → Marked → Spread → Cut → Handed Over.
5. When Handed Over, the cut quantities post to the Production Batch and stitching can start.

Getting there

Awesome bar: Cmd/Ctrl + K → type cutting order or marker order → pick the relevant list.

Click path: Desk → GarmentFlow → Production → Cutting & Marker card.

The pages

• Marker Order — the marker spec: pattern, pieces, lay limit, fabric width, on-X/Y shrinkage, yield, total pieces.
• Cutting Order — the physical cut: fabric, items, roll audit, results, defects, and the workflow that drives Pending → Handed Over.
• Cutting App — how the cutting room actually works: markers, roll scanning, ply confirmation, defects and handover, on a phone.
• Cutting Control — every open cut in the factory on one Kanban board, for whoever sets the cutting room's priorities.

Both records are normally created for you. The cutting wizard on the Production Order builds the markers, batches and cutting orders for a whole plan in one pass, and the cut calendar schedules them.

Why this isn't one doctype

You might wonder why cutting isn't a single document. The separation matters because:

• A marker is reusable. The same marker can be cut more than once for a re-cut, a top-up, or a second variant on the same pattern. Keeping the marker as its own record makes that obvious.
• Spreading and cutting are physically separate. Different people, different shifts, different mistakes to track. Two records is two places to audit.
• Yields are pattern-and-fabric data, not order data. A marker yield tells you something about the pattern that's worth knowing across orders. A Cutting Order yield tells you about this particular cut.

Keep them separate, and the data stays useful long after the order has shipped.

What to do next

Open Marker Order to understand the spec, then Cutting Order for how the actual cut happens — and Cutting App for how the room works it.