Cutting Order

A Cutting Order is the physical cut. It tracks the lay being spread, the fabric rolls being used, the cut output, and the handover to stitching. Where a Marker Order describes what will be cut, a Cutting Order tracks the act of cutting it.

Cutting Orders move through a workflow with real consequences — every state transition reflects something physical happening on the cutting floor.

Getting there

Awesome bar: Cmd/Ctrl + K → type cutting order → pick Cutting Order List

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

A Cutting Order is created against a Marker Order. The Marker Order's spec carries over to the Cutting Order header.

The sections

Order section. Posting date, Production Batch, linked Marker Order, Production Unit (which cutting line), spreader, cutter, supervisor. This is the "who and when" of the cut.

Fabric section. The fabric being cut, with usable width, and (once the cut happens) the actual length spread.

Items section. The output items the cut will produce — one row per size × variant being cut.

Roll Audit section. The Cutting Order Roll Audit child table — one row per fabric roll consumed in this cut. Each row captures the roll number, planned length, actual length consumed, and any shortfall. This is the data that lets you reconcile actual fabric use against planned consumption.

Results section. What came off the table: number of plies spread, total cut pieces (per size), pieces handed over to stitching, any pieces in Quality Hold or Reject.

The workflow

Cutting Orders move through these states:

• Pending — the order exists but cutting hasn't started.
• Marked — the marker has been placed on the table; spreading is about to start.
• Spread — fabric is spread to the planned number of plies.
• Cut — the cut has been made and pieces are counted.
• Handed Over — bundles have been transferred to stitching; cut quantities post to the linked Production Batch.

Plus two off-flow states:

• Hold — paused at any point. Reason captured.
• On Hold — a longer-form pause, typically from Spread or Cut state.

And a terminal:

• Rejected — the cut was bad enough that the order is killed and a new one will be raised.

Transitions move forward with Approve actions and pause with Hold actions. The role permissions on each transition determine who can advance the order; most factories set it so spreaders can move Pending → Spread, cutters can move Spread → Cut, and a supervisor signs off Cut → Handed Over.

The handover moment

The single most important transition is Cut → Handed Over. That's the moment the floor commits that this cut is done, the count is correct, and the bundles are ready to leave the cutting room.

Once Handed Over:

• The cut quantities are recognized on the linked Production Batch.
• The Batch's Operation Ledger sees a Handoff entry for the Cutting operation.
• Stitching is unblocked.

If the quantity reported at Handover diverges from the planned quantity, the Material Reconciliation dashboard will catch it. Don't try to fudge the number to match the plan — GarmentFlow handles divergence honestly, and so should the floor.

Image: A Cutting Order open on Results, showing total cut pieces by size, pieces handed over, and any in Quality Hold.

What to do next

Once a Cutting Order is Handed Over, the Production Batch carries the work forward. For tracking the day-to-day movements that follow, see Daily execution.