A garment order is never one item. A single buyer PO is a style, in four colourways, across six sizes, with a ratio per pack — 24 SKU-equivalents that the merchandiser thinks about as one line and that Business Central insists on treating as 24 unrelated items. Teams work around it: item numbers built by string convention, a spreadsheet holding the real size ratio, cut plans and bundle cards written by hand on the cutting floor, and export paperwork retyped from the sales order into Word. The cost of that workaround shows up at the end of the season, when nobody can say what a style actually cost to make, because the fabric issue, the trim consumption, the CMT charge and the freight all landed in different places.

Business Central out of the box has the pieces but not the shape. Item Variants exist, but they are a single flat dimension — there is no native concept of a size axis crossed with a colour axis, no size ratio, and no way to enter a buyer PO as a matrix. Production BOMs and Routings are solid for discrete manufacturing but assume a bill per item, not a bill per style with size-dependent fabric consumption. Item Tracking handles lots and serials, not cut bundles moving between cutting, stitching, finishing and packing. And the export side — commercial invoice, packing list with carton-level size breakdown, certificate of origin — has no home in the standard document set. Every one of those gaps is a place where the truth leaves the system.

What we build is an AL extension that adds the garment model to Business Central rather than beside it. A Style master carries the size and colour axes as real records, with a size ratio, and a matrix entry page that lets a merchandiser key a buyer PO in one screen and generate the underlying sales order lines against variant-tracked items. A cut plan is a first-class document: it takes the order matrix, applies marker efficiency and fabric width to compute lay length and fabric requirement, and issues numbered bundles with a size, colour, layer count and destination line. Bundle movement is posted through codeunits that write to standard item ledger and capacity ledger entries, so line-wise output and WIP stay reconcilable in the native ledgers instead of a parallel table. Order costing rolls fabric issue, trim consumption, CMT and outsourced processes back to the style and to the buyer PO, using the standard cost object structure so your existing Business Central reports keep working. Export documents are report objects driven from the shipment, producing a commercial invoice and a packing list that shows cartons with the actual size breakdown inside them, plus a declaration set matched to your destination markets. Integration follows the platform rules: table and page extensions rather than modified base objects, event subscribers instead of forked code, API pages on REST API v2.0 / OData v4 so your CAD, marker-making or buyer EDI systems can read the style and cut plan without a file drop, job queue entries for nightly costing rollups, and named permission sets for merchandising, cutting-floor and costing roles. It targets current Business Central release waves on SaaS and runs on-premises where you need it, delivered as a per-tenant extension or shaped for AppSource validation if you intend to publish.

This is build-to-order, not a download. There is no AppSource listing to install today. We start with a scoping call, walk your actual buyer POs, size charts, cut-plan practice and export destinations, and write a specification that names the tables, pages, codeunits and reports we will add and — just as importantly — what we will not add in version one. Typical delivery is one working week from confirmed scope, longer if you need buyer-specific EDI or a multi-unit subcontracting model. You get the AL source, a signed extension built against your Business Central version, deployment on a sandbox for UAT before anything touches production, a rollback plan, documentation, a training session for merchandisers and costing staff, and a support window after go-live. The repository is handed to you, so nothing about your production model is locked behind us.