Garment ERP Explained: Style BOM, Size-Colour Matrix and Cut-to-Ship

Ask any apparel factory owner where their real costing and delivery risk lives, and the answer is rarely finance. It lives on the shop floor, buried inside one deceptively simple object: the style. A single style becomes dozens of size and colour combinations, each consuming slightly different fabric, each moving through cutting, stitching and finishing at a different pace. Generic business software was never designed for this, which is why so many manufacturers still run on spreadsheets held together by memory. This is exactly the gap that garment ERP software is built to close.

In this guide we break down the three concepts every apparel manufacturer must get right in their systems: the style BOM, the size-colour matrix, and cut-to-ship tracking. Understand these and you understand why a purpose-built garment ERP is not a luxury but the backbone of a profitable garment business.

What a garment ERP actually is

A garment ERP is enterprise resource planning software shaped around apparel manufacturing rather than generic distribution or discrete assembly. It connects sampling, order confirmation, material planning, cutting, stitching, job-work, quality, finishing and dispatch into one flow, with the style at the centre. Everything downstream, from fabric procurement to buyer packing lists, is derived from how the style is defined.

The difference matters because apparel has combinatorial complexity that ordinary ERPs flatten and lose. In a garments ERP, one confirmed order for a style automatically knows its sizes, colours, fabric consumption, trims and operations. In a generic ERP, the same order becomes a pile of unrelated part numbers that nobody can reconcile back to the buyer PO. If you manufacture in textile and apparel manufacturing, that structural fit is the whole point.

The style BOM: costing an apparel product properly

The bill of materials, or BOM, is the recipe for a garment. A style BOM in a garment ERP records every input a style consumes: the main fabric and its consumption per size, lining, interlining, threads, buttons, zippers, labels, hang-tags, poly bags and cartons, plus the sequence of operations and any job-work sent outside. Defined once per style, it becomes the single source of truth for costing, purchasing and production.

Why an apparel BOM is different

Consumption is not constant. A 3XL shirt eats more fabric than a small, so a flat per-piece figure quietly destroys your margin on larger sizes. A proper style BOM stores consumption by size, so when an order arrives with a real size ratio the ERP explodes exact fabric and trim requirements rather than a rough average. That single capability is often the difference between a costing you can defend to a buyer and one you discover was wrong only after the fabric is cut.

A good style BOM also separates standard cost from actual cost. You quote from the standard BOM; the ERP then captures real issues, real wastage and real job-work rates as production runs, so post-order costing tells you the truth about which styles actually made money. Over many seasons this history becomes the most valuable planning asset a factory owns.

The size-colour matrix: one style, many SKUs

Take a single polo shirt. Offer it in five sizes and four colours and you instantly have twenty sellable combinations. Add a second fabric or a contrast collar and the count multiplies again. This grid of sizes against colours is the size-colour matrix, and how your software handles it determines whether your data stays sane.

Weak systems shatter the matrix into twenty disconnected SKUs. Suddenly nobody can answer a basic question: how many pieces of this style, across all sizes and colours, are still pending? A capable garment ERP keeps the matrix as one linked structure. You order, plan, cut, track WIP and dispatch against the matrix, then drill into any single size-colour cell when you need to. Buyer order sheets, cut plans and packing lists all speak the same language because they all reference the same matrix.

The matrix is also where size ratios live. Buyers rarely order equal quantities per size; they order to a curve. Holding that ratio inside the ERP means cut plans, marker planning and fabric booking all respect real demand instead of an assumed even split, which is how factories quietly avoid ending a season with unsellable size runs.

Cut-to-ship: tracking an order across the floor

Cut-to-ship is the heartbeat of garment production: the journey of an order from fabric cutting all the way to the shipped carton. The reason it deserves its own discipline is that quantities change shape at every stage. You cut a bundle, some pieces fail quality, some are re-cut, stitching runs at a different pace than finishing, and packing happens in ratio cartons. Without tracking, the gap between what you cut and what you can ship stays invisible until it is a crisis.

The stages a garment ERP tracks

• Cutting: fabric laid, markers used, bundles created and pieces cut per size-colour cell.
• Stitching and job-work: bundles issued to lines or external units, with pieces received back and rejections captured.
• Finishing: washing, pressing, checking and repair, with pass and reject quantities per stage.
• Packing: pieces packed into ratio or solid cartons against the buyer packing plan.
• Dispatch: cartons shipped against the order, closing the loop back to the buyer PO.

With live cut-to-ship visibility you can answer the questions that actually decide whether a shipment lands on time: How many pieces are still on the cutting table? How many are stuck at an external stitching unit? Which colour is lagging and will hold up the whole order? A modern garment ERP turns those answers into a dashboard instead of a phone-around.

Checklist: what a garment ERP should tie together

If you are evaluating systems, use this as a quick test of whether the software genuinely understands apparel:

• Style-level master with the full size-colour matrix as one linked object
• Style BOM with fabric and trim consumption stored per size
• Automatic BOM explosion and material requirement on order confirmation
• Standard versus actual costing per style and per order
• Cut-to-ship tracking with quantities at cutting, stitching, finishing, packing and dispatch
• Job-work management for operations sent to external units
• Buyer-ready order sheets, packing lists and dispatch documents from the same data

Where Pixel ERP fits

Pixel ERP is a ready, AI-native ERP product that already models styles, the size-colour matrix, style BOMs and cut-to-ship tracking out of the box. It is not a custom, build-from-scratch project. Instead it adapts to the way your factory already works through no-code configuration, so your process shapes the software rather than the other way around. That is how apparel manufacturers go live in weeks and start trusting their costing again.

To go deeper on the buying decision, read our guide to the best ERP for garment and apparel manufacturers, and to understand production control specifically, see how to manage job-work, seasons and WIP in a garment ERP. When you are ready to see it against your own styles, explore the full garment ERP software overview or book a demo with our team.

Frequently asked questions