What Is a Cut Ticket and Why It Belongs in the ERP, Not a Spreadsheet

A production manager at a $22M contemporary womenswear brand emails a cut ticket to her Vietnam factory on a Tuesday. It is an Excel file, tab three of a workbook that also holds the tech pack tab and a BOM tab. On Thursday the factory replies: fabric consumption is 2.4 yards, not 2.1, and the interlining trim is out of stock at the nominated mill. She updates tab three. She forgets to update the PO in QuickBooks, and she never updates the size ratio in the planning sheet the merchandiser uses. Six weeks later the goods land 800 units short of what allocation was promised, and nobody can reconstruct where the number moved.

That is the workflow this post is about. Not the definition of a cut ticket in the abstract, but the specific reason a cut ticket apparel ERP workflow beats the spreadsheet version for any brand doing more than one or two production runs a season.

What is a cut ticket in apparel production?

A cut ticket is the production work order a brand issues to a cutting room or contract factory. It authorises the factory to cut and sew a specific quantity of a specific style, in a specific colorway breakdown and size ratio, from a specific fabric and trim list, against a specific delivery window. It is the operational instruction that sits downstream of the tech pack (which describes how to make the garment) and downstream of the purchase order (which commits the money). The cut ticket is what actually moves fabric off the roll.

A complete cut ticket carries the style number and season, the colorway and size ratio (for example, 2-3-4-3-2 across XS to XL), the total unit count, the fabric SKU with required yardage and allowance, the trim BOM with quantities per unit, the cutting instructions (marker efficiency target, lay height, shrinkage allowance), the delivery date, the ship-to warehouse or 3PL, and the labelling and packing requirements per retailer. In a spreadsheet, roughly half of those fields are usually missing or stale.

Why do brands still run cut tickets in Excel?

Because it worked at $3M. When you are running one factory, four styles, and a founder who remembers every conversation, a spreadsheet is faster than any system. The tech pack is a PDF, the cut ticket is a tab, and the production manager sends everything by email. There is no reconciliation problem because there is only one person doing the reconciling, in her head.

The workflow stops working somewhere between $10M and $20M in revenue. That is the predictable breakpoint zone, and Breakpoint 2 of the 6 Breakpoints framework, production and supply execution drifting from the plan, is where the cut ticket sits. Across the comparison conversations I have run this quarter, the pattern is remarkably consistent: the brand has grown into three or four factories, two seasons overlapping in production, and a merchandiser who needs to see live WIP to commit to a wholesale buyer. The spreadsheet cannot answer any of the questions leadership now asks weekly.

The questions that break the spreadsheet are not exotic. They are: how many units of style 4471 in navy are actually cut versus sewn versus in finishing? Which POs have slipped their factory ex-date, and by how many days? What is the fabric consumption variance against the original cut plan across the last four seasons? A spreadsheet answers none of these without a human rebuilding the data.

What does the cut ticket look like when it lives in the ERP?

In a cut ticket apparel ERP workflow, the ticket is not a document. It is a record linked to other records. The style record holds the tech pack, the size chart, and the BOM. The PO holds the commercial terms with the factory. The cut ticket references both, inherits the fabric and trim requirements from the BOM, and adds the production-specific fields (size ratio for this run, delivery date for this run, allocation of this run to warehouses or retailers).

When the factory reports progress, the WIP status updates against the ticket, not against a status column in a shared sheet. When fabric consumption comes back higher than planned, the variance is captured against the BOM, which means next season’s cut plan starts from a more accurate number. When the goods ship, the ASN references the ticket, the PO, and the inbound receipt at the 3PL, so the warehouse knows what to expect and the finance team knows what to accrue.

This is what people mean when they say production, inventory, orders, warehouse, and reporting need to run in one connected system. Not that everything is on one screen, but that a change to the cut ticket updates the seven downstream places that also need to know.

Which fields actually break in the spreadsheet version?

When I am sitting across from a buyer comparing vendors, I usually ask them to open the cut ticket for their last problem PO and count the fields that disagree with the PO or the tech pack. It is almost never zero. The recurring offenders:

• Size ratio. The merchandiser updates the planning sheet after a late wholesale order lands, and the cut ticket never gets refreshed.
• Fabric consumption. The factory revises upward after the marker is made, and the new number lives in an email thread instead of the BOM.
• Trim BOM. A trim is substituted mid-production because the original is out of stock, and the substitution is verbal.
• Delivery date. The factory verbally slips a week, and the merchandiser is still telling the sales team the original date.
• Ship-to. Allocation between two warehouses changes after the goods are already cut, and the packing list does not reflect it.

Each of these looks small in isolation. Together, they are the reason a $15M brand loses 6 to 9 hours a week reconciling inventory across Shopify, the 3PL, and wholesale, and why oversell rates run 2 to 3 percent at peak. The cut ticket is upstream of both problems. If the ticket is wrong, the receipt is wrong, and if the receipt is wrong, ATS is wrong.

What is the actual cost of the spreadsheet cut ticket?

At the $15M revenue mark, the direct cost is one FTE effectively doing data plumbing. That FTE is nominally a production coordinator or an operations analyst, but the actual job is reconciling what the cut ticket said, what the factory delivered, what the 3PL received, and what Shopify and the wholesale system think is available. The indirect costs are larger. Chargebacks from wholesale accounts when ship windows slip. Cancelled DTC orders when oversell hits at drop. Fabric write-offs when consumption variance is not caught until end-of-season.

The uncomfortable version of this: if your factory ex-dates are slipping by more than five business days on average, your cut ticket process is the problem, not your factory. The factory works from what you send them. If what you send them is a spreadsheet that disagrees with the PO and the tech pack, they will build to whichever version they opened last, and the slip is baked in before the fabric is cut.

How does a cut ticket in the ERP connect to inventory truth?

Breakpoint 3, inventory truth getting weaker, is the breakpoint operators feel first because it shows up at the customer. But it is downstream of Breakpoint 2. The cut ticket is the origin document for inbound inventory. If the ticket says 1,200 units in a 2-3-4-3-2 ratio across five sizes, the system can pre-post the expected receipt, the allocation engine can commit units against wholesale POs before the goods physically land, and the DTC channel can hold back the correct ATS.

When the ticket is a spreadsheet, none of this happens. The 3PL receives the goods, counts them, and posts a receipt against the PO. If the size ratio delivered does not match what allocation assumed, the wholesale team finds out at pack-out, three days before the ship window, when the pick sheet comes up short in medium.

The rule I would push on: returns should post to inventory in days, not weeks, and inbound receipts should reconcile to the cut ticket the same day they land. Neither is possible when the ticket is an email attachment.

What does an operator actually gain by moving the ticket into production software?

Three things worth naming specifically. First, variance reporting. Because the ticket, the BOM, and the receipt are linked records, the system can produce a fabric consumption variance report across seasons without a human rebuilding the data. Next season’s cut plan starts from a real number, not an optimistic one. Second, live WIP. The factory updates status against the ticket (cut, sewn, finished, packed), and the merchandiser sees it without asking. Wholesale commitments get made against a real production position, not a planning-sheet position. Third, audit trail. When a delivery slips or a size ratio changes, the change is timestamped and attributed. Nobody has to reconstruct who told the factory what.

Those three are what people are actually paying for when they replace three to five tools plus spreadsheets with a connected production, inventory, and order system. The cut ticket is one of the more visible pieces of that replacement, but the value is not in the ticket. It is in the fact that the ticket is no longer the last place a number was correct.

When does the spreadsheet cut ticket actually stop working?

A specific threshold is more useful than a general one. The spreadsheet stops working when any of the following becomes true: you are running more than one production season concurrently, you are working with more than two factories, you have a wholesale channel that commits units before the goods land, or you have a 3PL that is not physically colocated with your production coordinator. Any one of those makes the reconciliation cost jump. Two or more, and you are inside the $10M to $20M breakpoint zone whether or not your revenue has crossed it yet.

Brands that wait past that point do not get worse spreadsheets. They add headcount. The production coordinator gets an assistant, the operations analyst gets a junior, and the reconciliation job spreads across two or three people instead of one. That works for a while, and then it stops, usually at a drop where the oversell rate on DTC and the short-ship rate on wholesale hit in the same week.

What this means for an apparel operations team

The cut ticket is not a document to redesign. It is a workflow to relocate. Moving it from Excel into the ERP is not about the ticket looking prettier. It is about the ticket being the same record the PO, the receipt, the WIP status, and the ATS calculation all read from. That is the difference between production drift getting caught at the cutting table and production drift getting caught at pack-out.

If your production coordinator can tell you, on any Tuesday, the exact WIP position of every open cut ticket across every factory, without opening a spreadsheet or emailing a factory, your Breakpoint 2 is closed. If she cannot, the cost is quantifiable, and it compounds every season the workflow stays where it is. That is the diagnosis worth acting on before the next buy is placed.