How to Implement Dynamics 365 Business Central for Garment & Apparel Business (2026 Guide)

1Who Business Central fits

Microsoft Dynamics 365 Business Central fits small and mid-size apparel brands, wholesalers and garment factories with one or a few legal entities that make discrete products in-house or through subcontractors. It handles colour and size through item variants, has production BOMs, routings and work centers in its Premium licence, tracks lots and packages, and adds import costs to stock with item charges.

Microsoft Dynamics 365 Business Central is Microsoft's cloud ERP for small and mid-size businesses, sold through partners in the Cloud Solution Provider (CSP) programme, with an on-premises option. It is extended with AL, Microsoft's language for Business Central extensions, and with apps published on Microsoft AppSource.

It suits a factory that wants a Microsoft-based system for finance, purchasing, inventory and sales, and a partner who writes AL. It suits a factory less well if the owner expects the ERP to replace the merchandisers' tracking sheets, the IE department's minute studies and the quality team's inspection reports in one move. Microsoft's own manufacturing documentation says Business Central "doesn't support detailed shop floor control", and the parts of this guide that describe the floor, sampling and quality are where Business Central needs the most design work, AL code or a separate system.

Signs Business Central is a good choice

Business Central tends to work when the business is Microsoft-based, runs discrete production and has a partner who writes AL.

• The business runs on Microsoft 365 and wants its ERP in the same identity and security model (Microsoft Entra ID).
• Production is discrete: cut, sew, finish and pack, in-house or at CMT units, washers, printers and embroiderers.
• The business has one or a few companies. Business Central allows up to 300 companies in one environment, per Microsoft's operational limits.
• A partner with manufacturing experience is available, or the factory has developers who can maintain AL extensions through Microsoft's twice-yearly major updates.
• The country has a Microsoft or partner localisation (section 22).

Signs to slow down, or to look at another product

Slow down when the work expected of Business Central belongs to a process ERP, a planning tool or a floor system.

• The business dyes or finishes fabric in-house and needs formula BOMs with co-products and by-products. Business Central has no documented formula or co-product model; Dynamics 365 Supply Chain Management does, with batch orders. See our chapter on Dynamics 365 Finance and Supply Chain Management.
• The group has many legal entities in many countries with shared warehouses and intercompany flows at scale. Choose on process type and entity complexity, not on revenue.
• The factory expects Business Central to plan sewing lines hour by hour, balance operators or track bundles.
• Buyers require EDI, compliance labels and portal uploads, and nobody has scoped them.
• The go-live date falls inside peak season.

2Why no ERP fits apparel on its own

No general ERP fits apparel out of the box, because an ERP is built around a known item with one bill of materials, while a garment order starts as a style that is quoted, sampled and approved before any item exists. This is not a Business Central weakness. SAP, NetSuite, Odoo and every general ERP meet the same wall, which is why Business Central's AppSource lists fashion add-ons, and why even they leave much of the work outside. The same wall stands in front of brands, buying agents and own-label retailers who never cut a garment themselves: their orders also begin as styles and samples, only at someone else's factory.

An ERP is built around the transaction: a known item, a fixed bill of materials, a price, a receipt, an invoice. It is right to be strict about that, because strictness keeps the books correct. A garment order does not start there.

Forcing an ERP to do all of this means heavy customisation in the one system that most needs to stay standard. Every update gets harder, the ledger fills with data finance never reads, and the merchandisers keep their spreadsheets anyway. The durable answer is to give the ERP the books and give the operations to a system built for them. Section 3 summarises that model and section 38 shows it in full.

3The recommended architecture, in short

Before discovery starts, agree which system owns which part of the business. Our recommendation is a split along the line in Example 1: Business Central keeps the books, and an operations system built for apparel runs everything from the style to the shipment.

With this split, the Business Central project stays close to standard: fewer AL extensions, cleaner updates, possibly no need for the Premium licence, and a shorter project. The rest of this guide still explains how to bend Business Central toward garment production, because some factories choose to do that, and because a consultant needs to know what each choice costs. Where an area moves out of Business Central under the recommended model, the section ends with a short note. Section 38 describes the model in full, department by department.

4Business types, and what each needs from Business Central

"Apparel manufacturer" covers very different businesses. The business type decides who owns the material, what is invoiced, and which parts of Business Central carry weight. Settle it in the first discovery meeting, because a factory often runs two types at once, for example full package for one buyer and CMT for another.

The list above is general implementation practice. Treat it as a starting point for the discovery questions in section 6, not as a scope. If the business does not manufacture at all, read Part 10 before Parts 3 and 4: much of the manufacturing design can be skipped.

5Who should be on a Business Central apparel project team?

A Business Central apparel project needs one decision owner for every design question, and most of those owners sit in the factory, not in IT. The partner configures and writes AL; the factory decides how styles, variants, units, lots, costs and inspections work.

The table lists the roles we see on projects that go well. One person can hold several roles in a small factory. What matters is that every question in the fit-gap has a named person who can say yes.

Rules that keep decisions moving

Most delays in apparel projects come from decisions nobody owns. Four rules prevent them.

• One owner per decision. "Merchandising and finance will agree" produces no decision. Write one name against each fit-gap line.
• Decide in writing. Keep a decision log with the date, the owner, the option chosen and the options rejected. Discovery findings, design choices and change requests all go in it.
• The sponsor settles scope, not configuration. The sponsor decides whether T&A lives in Business Central or elsewhere. The merchandising head decides how it works.
• Key users are released from part of their day. A key user who is also running peak-season orders will not test properly.

6What should discovery workshops for an apparel factory cover?

Discovery for an apparel factory is one workshop per department, each walking a real, recent order from start to finish and asking where the data comes from, who changes it and what goes wrong. Use the factory's own orders, not the Cronus demonstration company. The polo order in this guide is the kind of order to bring.

Each workshop produces three things: the current flow as it really runs (including the spreadsheets), a list of findings mapped to the fit-gap lines in section 7, and a list of decisions with an owner. The question lists below are a starting set; add the factory's own.

Merchandising

Merchandising questions establish how orders arrive, change and are tracked.

• How does an order arrive: buyer PO by email, portal, EDI? What fields does it carry, and how often is it amended after confirmation?
• How are sizes and colours broken down, and do buyers order in ratio packs?
• What quantity tolerance do buyers allow, and how is a short or over shipment agreed?
• Is one buyer order split into several deliveries, each with its own date and destination?
• Where is the T&A calendar kept, who updates it, and who looks at it each morning?
• Which season and style numbering does each buyer use, and which codes must appear on the buyer's documents? (This decides the item references in section 11.)

Development and sampling

Development questions establish what happens before an order exists.

• Which sample types does each buyer require, and in what order?
• How are sample rounds recorded: sent date, courier, comments, verdict?
• Where do tech packs live, and how is a revision after PP approval handled?
• Who prepares the quotation cost, from what inputs, and how many versions does a quote go through?

Purchasing and stores

Stores questions establish units, lots and what is measured at receipt.

• In which unit is each material bought, stocked and issued? Which suppliers invoice in a different unit from the one they deliver in?
• What is checked at receipt: weight, width, GSM, shade, shrinkage, four-point inspection? Who records it and where?
• How are dye lots and rolls labelled, and can the store find every roll of one lot today?
• Which materials are nominated by the buyer or supplied by the buyer?
• Does the warehouse use bins, and does it need picks and put-aways, or simple receipts and shipments?
• What happens to leftover fabric and trims after an order ships?

Cutting, production and subcontracting

Production questions establish the level of control and how output is counted.

• At what level is production controlled: per order, per style-colour, per delivery, per cut?
• How is the cut plan made per dye lot, and who checks that lots are not mixed?
• How is output counted today: per line per hour, per operator, at end of line?
• Which processes go outside (print, embroidery, wash, CMT), in what sequence, and how are pieces counted out and back?
• How are rejects, repairs and second-quality pieces recorded?

Industrial engineering and planning

IE questions establish where minutes and capacity come from.

• Are operation minutes (SMV) studied per style, taken from a library, or estimated?
• How is line capacity planned across the season, including subcontractors?
• What efficiency figure is used for planning, and how is actual efficiency measured?

Quality

Quality questions establish inspections, buyer standards and who may release a failed lot.

• Which inspections run: incoming fabric, cutting, inline, end of line, pre-final, final, measurement?
• Which buyers set their own AQL levels, and where are their quality manuals kept?
• Who may release a lot that failed inspection, and is that decision logged?
• Which lab tests and certificates are required per order?

Shipping

Shipping questions establish packing rules and documents per buyer.

• How are cartons packed: solid size, assorted, ratio? What carton labels does each buyer require?
• Which export documents are prepared per shipment, and who checks them against the letter of credit?
• Does any buyer require an advance shipping notice?

Finance

Finance questions establish currencies, payment terms, import costing and tax.

• Which currencies are used for sales, purchases and wages? How are exchange differences booked today?
• How are buyers paid: letter of credit, prepayment, open account? Which buyers deduct chargebacks?
• How is imported material costed: are freight, duty and clearing added to the material cost?
• Which dimensions does finance want on every entry (buyer, season, order, department)?
• Is the factory in a free zone or under a temporary-admission regime, and what reports does that require?
• Which e-invoicing and tax reporting rules apply, and which partner localisation covers them?

7The apparel fit-gap checklist for Business Central: 52 lines

A fit-gap checklist lists every requirement an apparel business has and records, line by line, whether Business Central meets it as standard, meets it with configuration, needs an AL extension or an AppSource app, or is better handled outside Business Central. The 52 lines below cover product, BOM and costing, materials, production, quality, sales and shipping, and finance.

The answers are our assessment of Business Central 2026 release wave 1 (version 28) with the Premium licence and Microsoft's Subcontracting and Quality Management apps, for a typical full-package garment factory. Confirm each line against your version, your localisation and your partner's apps before you sign a scope.

Key: Standard works as delivered · Configure setup, templates, personalisation or discipline · Custom build an AL extension or an AppSource app · Operations layer better run in an apparel operations system and passed to Business Central

Counted from this table, 7 of the 52 lines are standard, 23 need configuration, 14 need an AL extension or an app, and 8 are better run outside Business Central. That count is our assessment for a typical full-package factory, not a survey. A CMT factory drops most of the costing and material lines; a mill adds process lines this list does not cover.

8Business Central Essentials vs Premium for manufacturing, and where to run it

Manufacturing in Business Central, meaning production BOMs, routings, work centers and production orders, is part of the Premium experience, and Microsoft states that "users with an Essentials license can't sign in to a company that uses the Premium experience". A garment factory that runs production in Business Central therefore needs Premium for every full user of that company. Choose the licence after the fit-gap, because the recommended architecture may not need manufacturing in Business Central at all.

Business Central licences can only be bought through Microsoft's Cloud Solution Provider programme. Microsoft lists Essentials, Premium, Team Member and External Accountant licences, plus read access through Microsoft 365 licences and a Device licence for shared devices such as a shop-floor or warehouse terminal. Rights and prices are in the Dynamics 365 Licensing Guide and on Microsoft's pricing page; we do not repeat prices because they change.

Business Central online or on-premises?

Business Central online suits most apparel projects, because AL extensions run there and Microsoft handles updates, backups and scaling; on-premises suits a business with a firm reason to host its own servers.

Online, Microsoft ships two major releases a year and monthly updates in between; version 28 (2026 release wave 1) has received updates 28.1 to 28.5 at the time of checking. Every AL extension must keep compiling and working against each new version, so budget for testing each release in a sandbox.

What does Business Central cost for a garment factory?

The cost of Business Central for a garment factory depends on the licence tier and user count, the partner's implementation work, the AL extensions and AppSource apps the fit-gap calls for, and their upkeep through each release; licence fees are usually the smaller and more predictable part.

Questions to settle with the partner

Settle these with the partner before signing, because each changes the cost and the update path.

• Does the design need the Premium experience, and for how many users?
• Which AppSource apps are planned, who publishes them, and do they support the go-live version and the country localisation?
• Which AL extensions are planned, who owns the code, and who fixes them after each release?
• How is each release tested in a sandbox before it reaches production?
• Is the Subcontracting app part of the scope, and does the go-live version include it?

9Business Central vs NetSuite for apparel

Business Central and Oracle NetSuite are the two cloud ERPs most often compared by mid-size apparel businesses. Business Central models a style as an item with a flat list of variants and needs an add-on for grid entry, while NetSuite models a style as a matrix item with child items per option combination (up to 2,000) and offers grid entry through the Grid Order Management SuiteApp. Neither covers sampling, T&A, size-graded consumption or AQL out of the box.

Which should an apparel business choose?

Choose on the fit-gap, the partner, the licence model and local compliance, not on the product name. From practice, Business Central tends to suit a business already on Microsoft 365 with a partner who writes AL, and one that wants the option of on-premises; NetSuite tends to suit a brand or wholesaler that wants grid entry and matrix items with little development. In both, the parts of this guide marked custom build stay custom build. See our NetSuite chapter and the comparison table.

NetSuite facts from Oracle's documentation (see sources).

10How should item categories and materials be set up in Business Central for apparel?

Set up Business Central items by how each material is bought, stocked, costed and tracked: fabrics, yarns, trims, packaging, subcontract services and finished garments each get their own item category, inventory posting group and general product posting group, because those groups decide the G/L accounts. The costing method and the item tracking code sit on each item, so put them into item templates per category and let new items inherit them.

Apparel is not one product type. The garment category decides the size system, the main material, the unit it is bought in and the processes it goes through.

Materials, and how each is bought and used

Each material has its own purchase unit, usage unit and receipt checks, and the Business Central item setup must follow them.

What each item carries in Business Central

In Business Central, the costing method, base unit of measure and item tracking code sit on the item card, and the posting groups decide the accounts. Three documented rules shape the item design for apparel:

• The costing method cannot change once item ledger entries exist. Microsoft's costing documentation says so directly. Business Central supports FIFO, LIFO, Average, Specific and Standard. Decide per material family before the first receipt.
• Standard cost rolls up only through Standard items. To calculate the unit cost of a production BOM, Microsoft notes that the parent item and its components must use Standard. A factory that wants a rolled-up standard cost for the polo sets fabric and trims to Standard too, and accepts purchase variances.
• Item charges behave differently on Standard items. On a Standard item, an item charge does not change the unit cost; Business Central posts it as a purchase variance (section 18).

With operations on top: the style, its bill of materials by category and its consumption are built in the operations layer. Business Central still needs the item categories, posting groups and costing methods above, because it holds stock value and the payables.

11How do you set up size and colour variants in Business Central?

In Business Central, a colour-size combination is an item variant: one variant code per combination, listed on the item's Item Variants page, with no size grid in standard. The key design decision is where to split. Either the style is the item and every colour-size is a variant, or the style-colour is the item and each size is a variant. Most apparel projects choose the second.

Microsoft's own example is item 1200 with variant BLUE-L: the code carries both colour and size. The Item Variant table defines the code as Code[10], so every variant code, whatever it encodes, must fit in ten characters. Variants can be blocked separately for sales and for purchasing, and from the 2026 release wave 1 (general availability 1 April 2026) each variant can carry its own item attribute values, inherited from the item and editable per variant, with an Update Variant Attributes action to resynchronise them. Variant attributes are descriptive: they help search and filtering, and they do not change stock, cost or planning.

From practice, design B wins for most factories and brands, because the buyer's price, the fabric and the dye lot usually differ by colour, and because a size-only variant code leaves room for a second size axis such as inseam.

Variant Mandatory if Exists

Turn on Variant Mandatory if Exists on the Inventory Setup page. With it on, a user cannot post an entry for an item that has variants without naming the variant, which stops "polo, no size" from reaching stock. The setting can be overridden per item with Default, No or Yes, and it does not affect items without variants.

Item references for buyer codes

Item references map a customer's or vendor's own code to your item and variant. Microsoft's example maps the customer's BLU-LG-POLO to item 1200, variant BLUE-L, and item references can also carry a variant-specific unit of measure. For apparel, this is where the buyer's style number and colour code live, so the buyer's documents can show their codes while stock stays on yours.

Stockkeeping units for planning and per-size BOMs

A stockkeeping unit (SKU) in Business Central links an item, a location and optionally a variant into one planning identity with its own replenishment method, lead time, reorder point, vendor and even production BOM. The planning and requisition worksheets then make a separate proposal per location-variant combination. This is the standard way to give each size its own BOM (section 14).

Naming and codes

Agree a code convention before the first import and write it down: fixed positions, fixed abbreviations and no free text. Integrations and reports will parse these codes, and a variant called Navy L on one item and NVY-L on another breaks both. Keep the buyer's codes in item references, not in the variant code. Add item and variant translations where buyers need their own language on documents; a variant-specific translation takes priority over the item's.

When a fashion add-on earns its place

Standard Business Central has no size scale, no colour-by-size grid for order entry and no way to create a style's variants from a template. AppSource lists apps that add these. One example, named for illustration and not as an endorsement, is CS Fashion Central Premium from Central Solutions, which describes itself as adding functionality for businesses that sell items in colours and sizes, with templates to create items and variants. Evaluate any such app against your version, your localisation and your partner's support before relying on it (section 25).

With operations on top: styles, colourways and size breakdowns live in the operations layer, and Business Central only needs the finished-goods items and variants that are actually sold and invoiced. The variant count in Business Central drops to what ships.

12How do you convert kilograms to metres for fabric in Business Central?

Business Central converts between an item's units with one fixed Qty. per Unit of Measure per unit, so it can hold kilograms and metres on the same fabric item, but it cannot change the factor from roll to roll or lot to lot. Knitted fabric is usually bought by weight and cut by length, and the true factor depends on each roll's weight per square metre (GSM) and width.

GSM means grams per square metre: the weight of one square metre of the fabric. A 180 GSM jersey weighs 180 g per square metre.

An item has one base unit of measure, which is how it is stored, with a Qty. per Unit of Measure of 1. Alternative units on the Item Units of Measure page state how many base units they contain, and the item card names a default purchase unit and sales unit. A Quantity Rounding Precision per unit stops fractions such as 4.99998 pieces. Because the base unit decides how every ledger entry is stored, choose it before the item is used.

Three workable designs

There are three workable ways to hold knit fabric in Business Central, each with a trade-off.

With operations on top: the operations layer records a measured lot record per receipt (GSM, width, shrinkage) and works consumption in the unit the cutting room uses. Business Central can stay in kilograms for stock value and payables.

13How do you track dye lots and fabric rolls in Business Central?

Give every fabric an item tracking code that requires a lot number on inbound and outbound entries, and use each lot as one dye lot. A dye lot is a batch of fabric dyed together; fabric from two dye lots can differ slightly in shade, so pieces cut from two lots show a colour difference once sewn into one garment. Cutting must stay within one lot.

Business Central tracks serial numbers, lot numbers and package numbers on the Item Tracking Lines page of any inbound or outbound document, and the posted tracking lands on the item ledger entries. Lot numbers can be assigned from a number series or typed from the mill's own labels, and the Item Tracking Lines page shows availability per lot so the same lot is not promised twice. The Business Central mobile app can scan lot and package barcodes into these pages.

Tracking each roll is a design choice: a package number per roll keeps the lot as the dye lot and the package as the physical roll; a serial number per roll gives the same roll-level issue and return but treats every roll as a unit of one.

A lot information card can hold a short description, comments and a Blocked flag that excludes the lot from transactions. It has no fields for measured GSM, width, shrinkage or shade group; those need a table extension in AL. The Blocked flag is useful as a quality hold (section 19).

A shade band is a set of approved shade references for one fabric colour, used to judge whether a new lot is close enough to the standard. Buyers often allow shade groups within the band (for example A, B and C), and a garment must stay within one group. Business Central has no shade band object; it is a field added by extension or a record in another system.

With operations on top: shade bands per fabric, the measured lot record and the incoming inspection that carries the dye lot sit in the operations layer. Business Central still holds the lot on receipts and consumption, so stock value and traceability stay correct.

14How do you handle size-dependent fabric consumption in Business Central BOMs?

Give each size its own production BOM through a stockkeeping unit per variant: the SKU for P2041-NVY, variant XL, names a BOM with 1.02 m of body fabric, and the SKU for variant S names one with 0.82 m. Microsoft's Contoso "Variants" walkthrough uses exactly this pattern for colours, with SKUs created per location and variant and a different Production BOM No. on each.

Business Central has two kinds of BOM, and apparel uses both.

On a production BOM line, Quantity per holds the consumption, Scrap % adds a fixed percentage for material scrapped when picking, and a Routing Link Code ties the component to the operation that consumes it. A Calculation Formula (Length, Length × Width, Weight and others) can compute a quantity from dimensions. BOM versions with a starting date let the next season's construction replace the current one without editing an open order's BOM, and the Production BOM Version Comparison page shows quantities per version side by side.

Marker efficiency is the share of the fabric in a cutting marker that ends up in garment pieces; the rest is waste between the pieces. Shrinkage is the fabric the garment loses in washing or finishing, planned into the pattern. Keep the two apart: they come from different people (CAD and lab), change for different reasons, and are argued about with different suppliers. Business Central's single Scrap % per line cannot hold both.

With operations on top: the consumption engine (marker efficiency, shrinkage, woven construction) and the net-to-buy across the order book run in the operations layer, which passes the purchase quantity to Business Central. Business Central does not need per-size BOMs.

15How do you model cutting, sewing and finishing with Business Central work centers and routings?

Model cutting, sewing, finishing and packing as Business Central work centers, and list the garment's operations with their minutes on a routing attached to the item; this gives production orders a schedule and a labour cost, but it does not balance a sewing line. A work center in Business Central is a production resource with a shop calendar, a capacity, an efficiency percentage and a unit cost; machine centers can sit under it.

Microsoft's documentation describes the hierarchy as work center groups, work centers and machine centers, with availability stored in calendar entries built from shop calendars. On the work center card, Unit of Measure Code sets the time unit (minutes suit garments), Direct Unit Cost is the labour rate per time unit, Indirect Cost % and Overhead Rate add overhead, Unit Cost Calculation chooses time or units, Capacity is how many people or machines work at once, and Efficiency is the share of standard output actually achieved.

On a routing line, Run Time is per unit and Setup Time is per production order; Wait Time and Move Time lengthen the lead time without using capacity. Microsoft states that the allocated run time ignores efficiency and capacity, while the duration is Run Time ÷ Efficiency ÷ Capacity. A Send-Ahead Quantity lets the next operation start on a partial lot, which is how bundles flow from cutting to sewing. Routings have versions with a starting date, and parallel routings are possible with the Next Operation No. field.

Scheduling is infinite by default. Work centers can be set up as capacity constrained resources with a critical load percentage, and Microsoft says plainly that Business Central "doesn't support detailed shop floor control": it plans a feasible rough-cut schedule, not an hour-by-hour line plan.

What an operation's run time means in a garment factory

SMV (standard minute value) is the time a trained operator needs for one operation at a normal pace, including allowances. A polo has 15 to 25 sewing operations. You can list each one as a routing line, or group them into a few lines per department. Grouping keeps production order routings manageable; listing every operation gives a detailed cost but floods the capacity ledger with entries nobody reads.

With operations on top: the planning heat-map (lines and subcontractors, 52 weeks), production orders with job cards per department and the WIP board run in the operations layer. Business Central receives material issues for stock value and does not need routings at all.

16Where do sampling, approvals and the T&A calendar live in a Business Central project?

Business Central has no object for garment samples, buyer approvals or a T&A calendar, so a Business Central project must build them in AL, borrow another area such as projects or tasks for them, or keep them in an operations system. Before a single bulk garment is cut, the buyer approves the product in stages. Each stage can take several rounds, and each approval unlocks the next step of the order. Miss one, and the factory is ordering fabric or cutting on a spec the buyer has not agreed.

A PP (pre-production) sample is a garment made in the actual bulk fabric and trims, which the buyer approves as the reference that bulk production must match. A T&A (time and action) calendar is the list of an order's milestones, each with a planned date worked back from the ex-factory date, an actual date and an owner.

Every round has a sent date, a courier and tracking number, the pieces sent, the buyer's comments and a verdict: approved, approved with comments, or rejected. The T&A calendar hangs on these dates.

Business Central has no object for this. Teams stretch projects, tasks, notes or item attributes to hold it, and more often it lives in email. Business Central's production BOM and routing versions record what the construction is from a date, but not that a buyer approved it, on which round, for which order. The typical failure is bulk fabric ordered, or cutting started, on the strength of an approval nobody can find.

What an AL sampling extension must hold

If the project builds sampling inside Business Central, the extension needs a small set of tables that link to the item, the variant and the sales order. The list below is the minimum we would design.

• A sample request per item and variant, with its type (lab dip, strike-off, fit, size set, PP, TOP, shipment).
• Rounds under each request: sent date, courier, tracking number, pieces sent, buyer comments, verdict, verdict date, who recorded it.
• A link from the approved round to the production BOM version it approved, so a later version cannot silently replace it on the order.
• A block on the next step: purchase orders for bulk dyeing wait for the lab dip, release of the production order waits for the PP sample.
• T&A milestones that take their actual dates from the rounds instead of from someone typing them.

With operations on top: dev approvals (lab dip, strike-off, sample, shipping mark) with rounds, courier details and the buyer's verdict, the T&A calendar with its critical path, and the PP approval that locks the style version for the order all live in the operations layer. Business Central needs none of it.

17How does Business Central subcontracting work for CMT, washing, printing and embroidery?

Business Central subcontracts a routing operation: a work center linked to a vendor sits on the garment's routing, and a purchase order for that operation is created from the released production order. Which version you run decides how much of the rest is standard. From 8 July 2026, Microsoft's Subcontracting app adds component transfers to the subcontractor, returns, subcontractor prices and item charges on subcontract receipts; before it, only the basic tools existed and sending panels out was a manual transfer.

CMT (cut, make, trim) means the factory sews garments from fabric the buyer supplies and charges only for the labour; in subcontracting, the same term describes a factory that sends cut panels to another unit to be sewn. Job work is the South Asian term for the same arrangement.

Which version do you need?

Name the Business Central version in the design document, because the subcontracting design depends on it.

How the Subcontracting app handles components

Each production BOM line that goes to a subcontractor carries the routing link code of the subcontract operation and a Component Supply Method.

Four documented rules matter on the factory floor:

• Receiving posts capacity, not always output. Posting the subcontracting receipt posts a capacity ledger entry; it posts output automatically only when the subcontract operation is the last one on the routing. Microsoft warns this can post the wrong quantity and suggests adding a final in-house operation.
• Invoice from the order. Subcontracting purchase orders must be invoiced from the order itself, not with Get Receipt Lines on a separate invoice.
• Returns are capped. The return quantity is the lesser of what is physically at the subcontractor and what the outstanding purchase quantity still needs; once the purchase line is fully received, the proposed return is zero even if spare pieces remain there.
• Only work centers. Routing lines for subcontracting must use a work center, not a machine center.

Components sent to a subcontractor are usually set to Backward flushing on the stockkeeping unit for the subcontractor's location, so they are consumed there when output is posted. Garments often visit several processors in sequence. In Business Central each visit is its own subcontract operation on one routing, which keeps the whole chain on one production order.

Subcontractor tracking a factory expects

A factory expects to see, per processor, what went out, what came back, what was lost and whether the loss is inside the agreed allowance. With the Subcontracting app, the Subcontracting Transfer Entries action on the production order lists the posted transfers, and stock at the subcontractor's location is visible. The loss allowance per processor, the reject reasons and a balance per order remain design work or a report to build.

With operations on top: subcontract steps sit on the production order in the operations layer, and subcontractors appear on the planning heat-map beside the factory's own lines. Business Central receives the subcontractor's purchase order and the payable.

18How do you cost a garment in Business Central, and where does the garment costing sheet live?

Business Central values stock by the costing method on each item (FIFO, LIFO, Average, Specific or Standard), adds freight and duty to receipts with item charges, and can roll up a standard cost from production BOMs and routings; the garment costing sheet used to quote a buyer is built before any item exists and usually lives outside Business Central. A garment costing sheet lists fabric, trims, making, washing, testing, freight, finance cost and margin per piece, and adds up to the price quoted to the buyer.

• Costing method is set per item and cannot change once item ledger entries exist. Average can be calculated per item or per item, location and variant.
• Standard cost rolls up with Calc. Production Std. Cost on the item or the Standard Cost Worksheet, but only when the parent and its components use Standard.
• Adjust Cost - Item Entries forwards later cost changes, such as an item charge posted after the goods were used, into consumption and cost of goods sold.
• Multi-currency and prepayments are standard (section 21).

Pre-costing a style for a quote (fabric, trims, CM, washing, testing, freight, finance cost, commission, margin) is usually done before a Business Central item exists, so it tends to live outside Business Central.

How do you add landed cost to imported fabric with item charges?

Create one item charge per kind of import cost (freight, clearing, bank charges, duty), put it on the purchase invoice as a line of type Charge (Item), and assign it to the fabric receipt lines with Suggest Item Charge Assignment. A landed cost is any cost of bringing goods to the factory beyond the supplier's price: freight, insurance, customs duty, clearing and bank charges.

Each item charge number carries a general product posting group and tax groups, which decide its G/L account. The assignment can be made on the same invoice as the goods, or later from a separate invoice with Get Receipt Lines against the posted receipt. Microsoft documents four distribution options: Equally, By Amount, By Weight and By Volume; By Weight and By Volume read the Net Weight and Unit Volume fields on the item card, so those must be filled in. The charge is posted as a value entry on the original receipt's item ledger entry, and the Item Charges - Specification and Cost Shares Breakdown reports show it afterwards.

Choose the distribution per charge. Sea freight follows weight or volume; clearing and bank charges usually follow value; a duty charged per kilogram follows weight. For a factory in a free zone or under temporary admission, duty may be zero or suspended, and the rules for what must be reported are local. Agree them with the customs broker and finance before configuring.

With operations on top: the cost engine (fabric, trims, decoration, CMT, overhead, margin to FOB, with landed cost and dated exchange rates), the standard cost sheet and quotations with approval thresholds run in the operations layer. Business Central holds the item charges that actually hit the receipts, for stock value.

19Can Business Central run quality control and AQL inspection for garments?

Business Central's Quality Management app, introduced in the 2026 release wave 1, creates inspections from templates on purchase receipts, production and assembly output, transfers, sales returns and warehouse movements, and can block lots on the result; it takes a sample as a fixed amount or a percentage, and it has no ISO 2859-1 tables, so AQL inspection still needs AL or a separate system. AQL (acceptance quality limit) inspection checks a random sample drawn from a lot and accepts or rejects the whole lot according to how many defects the sample contains.

Quality Management is a Microsoft-published extension, preinstalled on new environments and installable on existing ones from Extension Management. Microsoft documents quality tests with value types (decimal, integer, Boolean, text, option, lookup), pass and fail conditions per test, templates that group tests, and inspection generation rules that decide when an inspection is created: for example when a purchase order is received, or when production output is posted. The template's Sample Source sets a Sample Amount or a Sample %. Three permission sets separate quality administrators, inspectors and auditors; only a Quality Admin & Supervisor may reopen a finished inspection or change its quantities. The app can block lots, move non-compliant stock to quarantine bins, and print a Certificate of Analysis. Microsoft notes the Premium experience is required for its production capabilities.

Quality control at cutting, stitching, dyeing and printing

A garment factory inspects at each stage where a defect is cheaper to catch than at the end. Dyeing and printing usually happen outside the factory, so those checks land on the receipt of the goods coming back.

A Sample % of 4.17 gives about the same number of pieces as the final sample in Example 18 for this one lot size. It is not an AQL plan: under ISO 2859-1 the sample size comes from the lot-size band and the inspection level, and the lot is accepted or rejected against fixed acceptance numbers, which change with the lot size and the AQL.

Acceptance numbers as published in ISO 2859-1 Table II-A, reproduced in common AQL references (see sources).

With operations on top: typed inspections (incoming, cutting, PP, DUPRO, final AQL, pre-shipment, measurement), the AQL engine on ISO 2859-1 at the buyer's level, CAPA, needle and metal control and quality grades (only first-quality pieces count as shippable) run in the operations layer. Business Central sees the shipment only once it is cleared.

20How do you handle cartons, packing lists and shipping documents in Business Central?

Business Central posts sales shipments and prints shipment documents, and its package numbers can record which carton a lot or quantity went into, but assorted and ratio cartons, buyer carton labels with SSCC numbers and buyer-format packing lists need AL, report layouts or an AppSource app. A carton is not a native object in the W1 application; the package number is the closest standard hook.

Documents a garment shipment needs

An export shipment of garments carries a standard set of documents, and a letter of credit may require each to match exactly.

With operations on top: shipments per delivery, packing and cartonisation, and ship clearance against the buyer's terms run in the operations layer. Business Central receives the shipment and raises the customer invoice.

21How does Business Central handle multi-currency, letters of credit, prepayments and chargebacks?

Business Central handles foreign currencies, exchange rate adjustments and prepayments as standard; letters of credit and reason-coded chargebacks need design, because the W1 application has no letter-of-credit object. Garment exporters usually sell in USD or EUR, buy some materials abroad and pay wages locally, so every order touches at least two currencies.

Multi-currency and exchange differences

Each currency has a code, exchange rates by starting date and, on the Currencies page, accounts for realised and unrealised gains and losses. The Adjust Exchange Rates batch job revalues open customer, vendor and bank entries at period end and posts unrealised gains or losses; when the payment arrives, the unrealised amount is reversed and the realised gain or loss is posted. A currency exchange rate service can update rates automatically, but it does not adjust entries that are already posted. The adjustment can be previewed before posting.

Prepayments

A prepayment in Business Central is an invoice posted against a sales or purchase order before the final invoice, and deducted from it. Default prepayment percentages can be set per customer, vendor and item, and the amount can be changed on the order. Additional prepayment invoices can be issued if the order grows, and a prepayment credit memo is needed before deleting a line that was prepaid.

Letters of credit

A letter of credit is a bank's promise to pay the exporter when documents that match the credit's terms are presented. Under ICC's UCP 600 rules, which most credits follow, documents must be presented within 21 calendar days after the shipment date unless the credit says otherwise, and never after the credit expires. Business Central has no LC object: the credit number, amount, latest shipment date, expiry, presentation period and required documents need an AL table or an AppSource app, and a check before shipment that the documents will match.

Chargebacks

A chargeback is an amount a buyer deducts from a payment for a claimed failure: a late shipment, a wrong carton label, a missing or wrong advance shipping notice. It arrives as a short payment. Post the shortfall to a chargeback G/L account per reason, with a reason code on the journal line, and attach the buyer's deduction notice. Without reason codes, nobody can tell whether the factory loses money to labels or to lateness.

With operations on top: finance stays in Business Central in full. The operations layer sends the orders, shipments and purchase requests that the invoices and payables are built on; no money amounts travel through its ERP API.

22Does Business Central support e-invoicing and localisation for garment-exporting countries?

For most garment-exporting countries, Business Central's localisation comes from a partner, not from Microsoft: Microsoft's country list shows Egypt, Bangladesh, Pakistan, Vietnam, Türkiye, Morocco, Tunisia, Sri Lanka and Cambodia as partner-localised on the worldwide (W1) base, and India as localised by Microsoft. E-invoicing and statutory reports therefore depend on the partner's apps; check your country and test an e-invoice end to end before go-live.

Microsoft explains that where it does not deliver a localisation, partners publish translation and localisation apps on Microsoft Marketplace, built on the W1 version, and that availability in its list concerns Business Central online, not the partner apps themselves. Some countries have more than one partner app.

Language needs checking too. Microsoft's supported-languages table lists Vietnamese and Turkish as partner-provided application translations; Arabic does not appear in that table at the time of checking, so an Egyptian or Moroccan factory that wants an Arabic interface should ask partners what they provide. English is built in.

Factories in free zones or under temporary admission often report the import and re-export of materials to customs. Business Central's item ledger entries carry the quantities, but the report format is local and usually custom.

23In what order should you configure Business Central for a garment factory?

Configure Business Central for a garment factory from the ledger outward: the company and its experience, the chart of accounts, posting groups and dimensions first, then currencies, units of measure, item tracking codes and inventory setup, then locations and item templates, then manufacturing, subcontracting and quality, and only then the items, variants and BOMs themselves. Each step depends on the one before it; items loaded before their tracking codes and base units are final must be reloaded or corrected with journals.

Business Central is navigated by page name through its search (Alt+Q), so the table names the page to open rather than a menu path. Page names below are from Microsoft Learn for version 28; check each on the version you deploy.

Two item-level settings complete the setup. A garment made in the factory needs Prod. Order as its replenishment system and a routing and production BOM (or SKUs carrying them), and a fabric needs its item tracking code and base unit. Both are easier to set in the item template or the configuration package than by hand.

24Which AL extensions does a Business Central apparel implementation usually need?

A Business Central apparel implementation that keeps operations inside Business Central usually needs between a handful and a dozen AL extensions, covering fabric units, lot attributes, cut control, packs and cartons, sampling, AQL, quantity tolerance, letters of credit and buyer documents. AL is the language for Business Central extensions; an extension adds tables, fields, pages, reports and event subscribers to Microsoft's application without editing Microsoft's own code, which is what keeps updates possible.

Extensions reach a tenant in two ways: as a per-tenant extension written for one customer, or as an app published on Microsoft AppSource for many customers. The list below is from implementation practice; the names are descriptive, not real packages. Look on AppSource before writing your own, and check each app against your version and localisation.

Every extension in the table is code someone must test against each major Business Central release and each monthly update. That is the real cost of keeping operations inside Business Central, and it recurs twice a year at least.

Rules for AL work on an apparel project

Four rules keep extensions from becoming the reason a factory falls behind on updates. They come from practice.

• Keep a register. Every extension, its owner, the fit-gap lines it serves and the business process it touches.
• Test each release in a sandbox before it reaches production, with the 13 scenarios in section 28.
• Prefer adding to changing. A new table and a page extension survive updates better than logic that depends on the order in which Microsoft's events fire.
• Retire extensions Microsoft replaces. The Subcontracting and Quality Management apps arrived in 2026; an older custom subcontract or inspection extension should be reviewed against them.

25Should you use an AppSource fashion app or build in AL?

Use an AppSource app for the parts every apparel business needs in the same way, such as size scales, variant generation and grid entry, and write AL only for what is specific to the factory or its buyers. An app spreads its update cost across many customers; a per-tenant extension carries it alone.

AppSource lists Business Central apps aimed at businesses that sell items in colours and sizes. As one example, and not as an endorsement, CS Fashion Central Premium from Central Solutions describes itself as adding functionality for the apparel and fashion industry, with templates for creating items and variants in collections. Apps change their scope and pricing; read the current listing and ask the publisher for a demonstration on your own styles.

26Which systems does a Business Central apparel implementation integrate with?

A Business Central apparel implementation typically connects to a PLM or tech-pack system, a shop-floor system, EDI with retailers, banks, e-invoicing, and an operations layer; each connection needs one owner per field and links stored on Business Central's permanent id. The table shows the usual source of truth for each kind of record, based on general practice.

Rules for every connection

Four rules prevent most integration faults. They apply whether the other side is a PLM, a floor system or an operations layer.

• Link on the record's id (a GUID), which the API documents as non-editable, never on the document number or item number a user can change.
• One writer per field. If two systems can change the same quantity, one of them is wrong without knowing it.
• Show disagreements to a person. When the other system says something different, put it on a review list; never overwrite silently.
• Make receivers safe to call twice, so a retried message does not create a second purchase order.

Microsoft's own Power Automate connector for Business Central is triggered by webhooks, and Microsoft notes it cannot process "collection" notifications, so a flow does not fire when more than 1,000 records change within the 30-second delay. For anything with volume, build on the API directly (section 34).

27How do you migrate apparel data into Business Central?

Migrate only open and active apparel data into Business Central (active items and variants, open orders, open purchase orders and stock by lot), load it in dependency order with configuration packages, post opening stock through item journals with item tracking, and have each department head sign off the loaded figures. History stays in the old system or an archive.

A configuration package is Business Central's tool for moving setup and master data: you choose tables and fields, export them to Excel, fill them in, import, validate and apply. Configuration templates add default values to imported records, and a configuration worksheet groups tables into areas. Microsoft's documentation sets three limits that shape an apparel migration: you cannot import into tables that hold posted entries, such as item or customer ledger entries, so opening balances are posted through journals; the importing user needs direct insert and modify permissions; and source and target should share the same schema and version. Edit in Excel on any list is a lighter tool for small fixes.

Load order

Each object depends on the ones above it. Load and check each level before starting the next.

For opening stock with lots, Microsoft documents a journal batch setting, Item Tracking on Lines, that lets the lot, serial and package numbers be entered straight on item journal lines, including through Edit in Excel. That is the practical way to load several hundred rolls by lot.

The cut-off rule

A cut-off rule states the exact moment after which every transaction is entered in Business Central and not in the old system. Write it as a date and time, name what happens to documents in flight (a truck at the gate, an inspection half done), and stop receiving into the old system at that moment. Stock is counted at the cut-off and loaded as it was counted, not as the old system said.

Cleansing

Clean data before it is loaded, never after. The usual work in an apparel migration is listed below.

• Merge duplicate vendors and materials ("Navy Jersey 180", "Jersey 180 NVY").
• Retire styles with no order in two seasons.
• Give every fabric one base unit, and every roll in stock its lot.
• Map old size labels to the new variant codes, one item at a time, inside the 10-character limit.
• Split any "open" order line that is already partly delivered into delivered and open quantities.

Item No.,Code,Description
P2041-NVY,S,Men's piqué polo navy S
P2041-NVY,M,Men's piqué polo navy M
P2041-NVY,L,Men's piqué polo navy L
P2041-NVY,XL,Men's piqué polo navy XL
P2041-NVY,XXL,Men's piqué polo navy XXL

Document No.,Type,No.,Variant Code,Quantity,Unit Price,Line Amount
SO-P2041,Item,P2041-NVY,S,300,4.26,1278.00
SO-P2041,Item,P2041-NVY,M,750,4.26,3195.00
SO-P2041,Item,P2041-NVY,L,900,4.26,3834.00
SO-P2041,Item,P2041-NVY,XL,750,4.26,3195.00
SO-P2041,Item,P2041-NVY,XXL,300,4.26,1278.00

Open PO:  PO-10457, navy jersey 180 GSM, 925 KG ordered, 0 received
Journal:  item journal, button 15 mm navy, 9,504 PCS, location MAIN, no lot

Sign-off

Each owner signs a one-page check of their data: record counts against the old system, totals (stock value, open order value, open payables) and five records picked at random and checked on screen. A migration with no signatures is a migration nobody owns when the first figure is wrong.

28How should you test a Business Central apparel implementation end to end?

Test a Business Central apparel implementation with end-to-end scenarios that follow one real order from the buyer's PO to cash, run by the factory's key users in a sandbox with migrated data, each step with an expected result written down before the test starts. Testing pages one by one proves the configuration works; only end-to-end scenarios prove the business works.

The 13 scenarios below cover the flows where apparel projects usually break. Run each at least twice: once by the partner to find faults, once by the key users to accept the result. Run them again in a sandbox before each major release reaches production.

Test script: subcontract embroidery with loss

Scenario T5 proves that fronts sent out, fronts returned and fronts lost add up, using the Subcontracting app. The polo's chest logo is embroidered outside at operation 20; the cut-front BOM line has Scrap % 1, routing link code EMB and Component Supply Method Transfer to Vendor.

Test script: short shipment within tolerance

Scenario T6 proves that a short shipment inside the buyer's tolerance is invoiced on what shipped. The buyer allows ±3%; the factory ships 2,940 pieces, 30 short in M and 30 short in L.

Step 1 and step 4 need the quantity-tolerance extension from section 24; standard Business Central has no quantity-tolerance field on a sales order. For step 3, check how your version deducts a prepayment when the invoiced quantity is below the ordered quantity, and prove the full 3,834.00 is deducted.

29How should you train a garment factory's staff on Business Central?

Train each role only on the pages and scenarios it will use, on the factory's own styles and orders, with role centers and personalised pages that hide what the role does not need, and have key users teach their colleagues. A merchandiser does not need the accounting pages, and a floor supervisor needs one screen that works, not an introduction to Business Central.

Train close to go-live, so that what people learn is still fresh, but not so close that there is no time to repeat a session. Keep each session short and practical: people learn by entering an order they recognise. Microsoft publishes free Business Central e-learning modules on Microsoft Learn, which key users can take before the project's own sessions.

Floor operators and supervisors are trained on whatever captures floor output. If that is a kiosk or scanner screen, the training is minutes, not hours; if it is Business Central's output journal, expect the data never to arrive.

30What does a Business Central cut-over plan look like for a garment factory?

A Business Central cut-over plan is a day-by-day list of the steps that move the factory from the old system to Business Central: freeze, final configuration packages, stock count, opening balances through journals, checks and the first live transactions, each with an owner and a go or no-go point. Rehearse it once in full in a sandbox copied from production before the real weekend.

31When should a garment factory go live on Business Central, and how long is hypercare?

Go live between seasons, in the lowest-volume weeks and before a new wave of cutting starts, and keep the partner in close support until at least the first month-end close is done in Business Central. Hypercare is the period right after go-live when the project team stays on hand to fix issues daily.

• Timing. Avoid the weeks before a main shipment window, the month-end of the financial year, any audit, and the window when the tenant takes a major update. A go-live in peak season turns every small fault into a missed shipment.
• Parallel running. A short, bounded parallel run of the books can help finance compare figures. Running the whole factory in two systems rarely works, because people keep using the one they trust.
• Duration. Practitioners commonly plan hypercare of four to eight weeks. That range is judgement, not a measured standard; the rule that matters is that nobody leaves before the first month-end close in Business Central is complete, including Adjust Cost - Item Entries and the exchange rate adjustment.
• Issue log. Keep one list: date, who, what happened, severity, owner, status. Review it daily in the first two weeks.
• Exit criteria. Hypercare ends when the month-end closes on time, no issue blocks shipping or invoicing, and key users handle first-line questions without the partner.

32What are the most common mistakes when implementing Business Central for apparel?

The most common mistakes in Business Central apparel projects are every colour and size created as variants on day one, one item per SKU, inconsistent variant codes, one fabric consumption for all sizes, dye lots not tracked from receipt, a fixed kg-to-metre factor, subcontract work bought as plain purchase lines, and landed cost posted by hand in the general ledger. The list below comes from implementation practice, not from Microsoft's documentation.

1. Every colour and size created on day one.Unused combinations sit in lists, price lists and counts for years. Create variants when an order needs them.
2. One item per SKU.Style-level reporting is lost, and 3,000 items do the job of 200 items with variants.
3. Inconsistent variant codes.Integrations and reports end up parsing free text. Fix a convention that fits in ten characters.
4. One fabric consumption for all sizes.Large sizes run short and small sizes leave surplus.
5. Dye lots not tracked from receipt.The item tracking code is added later, and the stock already on hand has no lot to trace.
6. A fixed kg-to-metre factor for every fabric.Stock value looks right while the cutting room runs short.
7. Subcontract work bought as plain purchase lines outside the production order.The cost and the work-in-progress are disconnected, and nobody knows what is at the embroiderer.
8. Landed cost posted as manual journals.Freight never reaches the item cost; use item charges assigned to the receipt.
9. Seasons held in free text.Reports by season depend on spelling. Use an item category, attribute or dimension.
10. No budget for API limits.A season load or a nightly sync from one integration user hits the per-user rate limit and returns 429.
11. Premium discovered late.Manufacturing is switched on and Essentials users can no longer sign in to the company.
12. The subcontract operation left last on the routing.Each subcontract receipt posts output automatically, sometimes with the wrong quantity.

The 15 general failure modes, and how each shows up in Business Central

Apparel ERP projects fail in the same fifteen ways whatever the ERP. The table maps each one to where it appears in a Business Central project and how to prevent it.

33What must be decided before a Business Central apparel go-live?

Decide the item-versus-variant split and the variant code convention, the base unit and costing method of every item, the item tracking codes, the licence experience, the subcontracting model and version, and which system owns sampling, T&A and floor capture before go-live, because each is expensive to change once item ledger entries exist. The full list:

• Style as item or style-colour as item, and the variant code convention within ten characters.
• Variant Mandatory if Exists: on globally, and any item-level exceptions.
• Base unit of measure for every fabric and yarn, and how kg-to-metre is converted.
• Costing method per item family; it cannot change once item ledger entries exist.
• Item tracking codes: lot for dye lots, package or serial for rolls, required inbound and outbound.
• Which item charges exist and how each is distributed.
• Essentials or Premium, for which company and which users.
• Subcontracting: basic tools or the Subcontracting app, and the version that includes it; component supply method per component.
• Whether Quality Management runs receipt inspections, and who holds the Quality Admin & Supervisor role.
• Number series for items, orders and lots.
• Chart of accounts, dimensions and posting groups.
• Which system owns sampling, T&A, planning, floor capture and final AQL: Business Central, AL extensions or an operations layer.
• How buyer-supplied fabric is held so it never enters inventory value.
• The quantity tolerance rule and who may approve a shipment outside it.
• How profitability per order is tagged (a dimension).
• Which AppSource apps and partner localisation apps are in scope, and their support for the go-live version.
• The integration users, their permission sets and their share of the API limits.

34Which Business Central API should an apparel integration use?

Build integrations on Business Central API v2.0, an OData v4 REST API, authenticated with OAuth 2.0 through Microsoft Entra ID using the client credentials flow, and add custom API pages in AL for anything the standard pages do not expose. Microsoft states that extending the standard APIs with extra fields "isn't currently possible"; you copy the AL of the API page and publish your own, for which Microsoft's ALAppExtensions repository on GitHub holds the source of the standard pages.

Standard resources are addressed per company, for example https://api.businesscentral.dynamics.com/v2.0/{environment}/api/v2.0/companies({id})/purchaseOrders. Resources an apparel integration uses include:

Authentication

Register an application in Microsoft Entra ID, give it the API.ReadWrite.All application permission for Dynamics 365 Business Central, and set it up in Business Central on the Microsoft Entra applications page with its Client ID, state Enabled and only the permission sets it needs. Microsoft notes that applications cannot be assigned the SUPER permission set. Tokens are requested from https://login.microsoftonline.com/{tenantId}/oauth2/v2.0/token with scope https://api.businesscentral.dynamics.com/.default. Service-to-service authentication has been available for API v2.0 online since version 18.3.

Limits

Microsoft applies operational limits to OData and API requests, now counted per user, and a service-to-service app counts as a user.

Microsoft's guidance is to handle 429 with a retry and a cool-off period, to use webhooks, filters on lastModifiedDateTime, $expand and deep inserts to cut the number of calls, and, where one integration user is the bottleneck, to spread work across several users or service principals. The API Terms of Use apply.

Webhooks

Business Central pushes a change notification to your endpoint when a subscribed resource changes; the notification says only what changed, so the receiver then reads the record. A subscription is created with POST /api/v2.0/subscriptions carrying notificationUrl, resource and an optional clientState; Business Central calls the URL with a validationToken, which the receiver must return in the body with status 200.

• Subscriptions expire after three days unless renewed with a PATCH, which repeats the handshake.
• Notifications are delayed and batched. Business Central waits 30 seconds after the first change; if more than 1,000 records change in that time, one collection notification with a filter replaces the individual ones.
• Retries last 36 hours if the receiver answers 408, 429 or any 5xx. Any other error code deletes the subscription with no retry, so monitor subscriptions and re-create them.
• Not every resource is covered. Microsoft's list includes salesOrders, items, customers and vendors; it does not include purchaseOrders or itemVariants. For those, poll on lastModifiedDateTime or publish a custom API page, which is webhook-enabled when it meets Microsoft's conditions.

Identifiers

Store every link on the record's id, a GUID that the API documents as non-editable. The document number, the item number and the variant code are display values a user can change or a number series can reuse. Hold the variant as a structured field (itemVariantId), never as text parsed from a description.

POST /api/v1/erp/po-status
Idempotency-Key: bc-po-9b1f3c2a-open

{"rows": [{"request_ref": "PR-1042",
           "erp_po_id": "9b1f3c2a-6d4e-4f7a-8c21-3e5d0a7b4c19",
           "erp_po_number": "PO-10457",
           "status": "Open",
           "date": "2026-10-21"}]}

Where the customer does not want an API connection at all, a file exchange (CSV in, CSV out, on a schedule) does the same job with no programming on the Business Central side beyond a configuration package or an import, and the MerchandiserOS ERP API offers that path too.

35Is Business Central a good ERP for fashion brands, buying agents and own-label retailers?

Yes for the books, and only partly for the work. Business Central is a sound ERP for fashion brands and clothing brands that outsource production, for a buying house and for an own-label retailer's sourcing team: purchase orders with variants, item charges for freight and duty, vendor payments in foreign currency, wholesale sales orders and prepayments are all standard, and none of it needs the Premium experience. What it does not do is follow samples, T&A, production and inspections at factories the business does not own.

Three kinds of business source garments without making them:

For all three, the wall described in section 2 still stands: their orders also start as styles, tech packs and samples, only at somebody else's factory. The difference is that none of it happens on their own floor, so the gap is follow-up across many factories rather than production control.

36What should a brand or buying agent use in Business Central, and what should it skip?

A brand should use Business Central for purchase orders to factories, landed cost through item charges, vendor payments and letters of credit, wholesale sales with prepayments, and EDI through an app where it sells to retailers; a buying agent should use it for commission invoicing and multi-currency accounting, with no stock at all. Both should skip the manufacturing area, which means Essentials is normally enough. Used this way, Business Central works as an ERP for clothing brands without any of the garment-production design in Parts 3 and 4.

What to skip

Skip what only a maker uses. It saves licence cost and configuration time.

• The Premium experience. Without production orders, routings and work centers, Essentials covers purchasing, item charges, sales and finance. Check the apps you plan to use do not require Premium.
• Production BOMs, routings, work centers and SKU BOMs per size. Consumption is the factory's problem; the brand buys finished garments by variant.
• Lot tracking on finished goods, unless a retailer demands traceability by production batch.
• For an agent, items and inventory altogether. A buying house that never takes title has no stock, no goods payables and no goods receivables; its Business Central is a services company.

37Where does Business Central fall short for brands and buying agents, and what runs on top?

Business Central falls short on the work that fills a brand's or an agent's day: development and sampling with many factories, the T&A calendar across factories, following production that happens outside, inspections at the vendor, and one status per order across many factories and buyers. None of these is a transaction in the buyer's books, so no standard object holds them, and sourcing agent software or buying house ERP tools exist for this reason.

The MerchandiserOS model for brands and agents

MerchandiserOS runs the work and Business Central keeps the books. MerchandiserOS has workspace set-ups for a Brand and for a Buying agent, and in them it runs:

• development, samples and approvals: lab dips, strike-offs, samples and shipping marks, round by round, with courier details and the buyer's verdict;
• the T&A calendar with its critical path;
• the orders placed with factories, with size-by-colour breakdowns, tolerance bands and per-shipment deliveries;
• sourcing: suppliers with qualification, purchase requests and purchase orders;
• the planning view across subcontracted factories on the planning heat-map;
• quality inspections, including final AQL on ISO 2859-1 at the buyer's level;
• shipping follow-up: shipments per delivery, packing and ship clearance against the buyer's terms.

Business Central keeps the purchase orders as financial records, the payables, the item charges, the stock value, the sales invoices, the commission invoices and the tax. Retail back-office work (stores, POS, allocation, open-to-buy) is outside MerchandiserOS's scope; an own-label retailer keeps those in its retail systems.

·Glossary of apparel and Business Central terms

Short definitions of the apparel and Business Central terms used in this guide.

AL

The programming language for Business Central extensions.

API v2.0

Business Central's standard REST API over OData v4, addressed per company.

AppSource

Microsoft's marketplace for business apps, including Business Central extensions from other publishers.

AQL

Acceptance quality limit: an inspection method that checks a random sample from a lot and accepts or rejects the lot on the number of defects found, using ISO 2859-1 tables.

Assembly BOM

In Business Central, a BOM for items put together from other items in a simple process, used for packs and sets.

CM, CMT

Cut and make, or cut, make and trim: the labour charge for making a garment, and a factory model where the buyer supplies the fabric and the factory charges only for making.

Colourway

One colour version of a style, with its own fabric shade and trims.

Component Supply Method

In the Subcontracting app, how a component reaches the subcontractor: Vendor-Supplied, Consignment at Vendor or Transfer to Vendor.

Configuration package

Business Central's tool for exporting, filling in, importing and applying setup and master data.

Cut-over

The planned switch from the old system to Business Central, around a fixed cut-off moment.

DUPRO

During-production inspection, done once part of the order is packed.

Dye lot

A batch of fabric dyed together; pieces from different dye lots can differ in shade and must not be mixed in one garment.

Essentials, Premium

Business Central's two main licence tiers and experiences; Premium adds Manufacturing and Service Management.

Ex-factory

The date goods leave the factory for shipment.

FOB

Free on board: the price of goods loaded at the port of shipment; in garment trade, the usual quoted price per piece.

GSM

Grams per square metre: the weight of fabric.

Hypercare

The period after go-live when the project team fixes issues daily.

Item charge

In Business Central, a cost such as freight or duty assigned to posted receipt or shipment lines to build landed cost.

Item reference

In Business Central, a mapping from a customer's or vendor's own code to your item and variant.

Item tracking code

In Business Central, the setting on an item that decides whether serial, lot or package numbers are required.

Item variant

In Business Central, one version of an item, such as a colour or size, identified by a code of up to 10 characters.

Lab dip

A small dyed fabric sample sent to the buyer to approve a shade before bulk dyeing.

Landed cost

Every cost of bringing goods to the factory or warehouse beyond the supplier's price: freight, insurance, duty, clearing, bank charges.

Letter of credit (LC)

A bank's promise to pay an exporter when documents matching the credit's terms are presented.

Marker efficiency

The share of fabric in a cutting marker that ends up in garment pieces.

Package number

In Business Central, an item tracking number for a physical package, usable for a fabric roll or a carton.

POM

Points of measure: the garment measurements in a tech pack, with a tolerance per size.

PP sample

Pre-production sample: a garment in bulk fabric and trims that the buyer approves as the reference for production.

Prepayment

In Business Central, an invoice posted against an order before the final invoice and deducted from it.

Production BOM

In Business Central, the certified list of components for a produced item, with versions by starting date.

Ratio pack

A pack or carton holding sizes in a fixed ratio, for example 1 S, 2 M, 2 L, 1 XL.

Routing link code

In Business Central, a code that ties a BOM component to the routing operation that consumes it.

Shade band

A set of approved shade references for a fabric colour, used to judge each new lot.

SKU

In Business Central, a stockkeeping unit: an item at a location, optionally for one variant, with its own planning and BOM settings.

SMV

Standard minute value: the time a trained operator needs for one operation at a normal pace.

Size/colour matrix

A grid of colours by sizes used to enter or show order quantities for each combination.

Strike-off

A sample of a print or embroidery on the actual fabric, approved before bulk.

T&A calendar

Time and action calendar: an order's milestones with planned dates worked back from ex-factory, actual dates and owners.

TOP sample

Top of production: the first bulk pieces, checked against the PP sample.

UCP 600

The ICC's rules for documentary credits, which most letters of credit follow.

Webhook

A notification Business Central sends to a registered URL when a subscribed resource changes.

Work center

In Business Central, a production resource with a shop calendar, capacity, efficiency and unit cost.

·Checklists: a Business Central apparel implementation on one page

The checklists below repeat the decisions and checks from each part of this guide, in project order.

Discovery

Discovery is complete when every item below is ticked.

• Business type settled for each buyer: CMT, full package, brand, agent, or a mix.
• One decision owner named for each area.
• One workshop per department, walking a real recent order.
• All 52 fit-gap lines answered with evidence, decision and owner.
• Architecture decided: what Business Central owns, what runs in an operations layer.
• Licence experience (Essentials or Premium), localisation and AppSource apps confirmed against the fit-gap.

Design

Design is complete when every item below is decided and written down.

• Item categories, posting groups, item templates and costing method per item family.
• Style-colour as item, size as variant; code convention inside 10 characters; Variant Mandatory if Exists on.
• Base unit per fabric and yarn, and the kg-to-metre design.
• Item tracking codes: lot as dye lot, package or serial per roll.
• Size consumption source decided: SKU BOMs or outside.
• Work centers, routings and minutes; what stays in planning outside Business Central.
• Subcontracting model and version; component supply method per component.
• Inspection points, Quality Management templates, AQL source and release rights.
• Carton rules, package numbers and buyer documents per buyer.
• Currencies, prepayments, LC records, chargeback reasons, e-invoicing.

Build, data and testing

Build, migration and testing are complete when every item below is proven on the go-live version.

• Configuration done in dependency order, on the go-live version.
• AL extensions and AppSource apps listed with owners and a release-testing plan.
• Integrations link on Business Central's id, with one writer per field and a share of the API limits.
• Migration loaded with configuration packages and journals, with a cut-off rule and signed totals.
• All 13 end-to-end scenarios passed by key users in a sandbox.

Go-live

Go-live is ready when every item below is in place.

• Training done per role, on the factory's own orders.
• Cut-over rehearsed once in full in a sandbox.
• Go-live date between seasons, away from year-end, audits and a major update.
• Go or no-go point and fall-back defined.
• Hypercare runs at least until the first month-end close in Business Central.

·Sources

Microsoft Learn pages were checked on 26 September 2026 against Business Central 2026 release wave 1 (version 28). Page names are from the English (US) documentation. Other chapters in this series: NetSuite, Dynamics 365 Finance and Supply Chain Management, Odoo, and the ERP-agnostic method and glossary.

1. Microsoft Learn, Manage product variants (Variant Mandatory if Exists, item references per variant, translations, SKUs, variant attributes) — learn.microsoft.com
2. Microsoft Learn, Table "Item Variant" (Code[10], Sales Blocked, Purchasing Blocked) — learn.microsoft.com
3. Microsoft Learn release plan, Define item attributes for item variants (GA 1 April 2026) — learn.microsoft.com
4. Microsoft Learn, Contoso Coffee walkthrough: Variants (SKU per variant with its own production BOM) — learn.microsoft.com
5. Microsoft Learn, Set up item units of measure — learn.microsoft.com
6. Microsoft Learn, Track items with serial, lot and package numbers (lot information cards, Item Tracking on Lines) — learn.microsoft.com
7. Microsoft Learn, Work with bills of material (assembly vs production BOMs) — learn.microsoft.com
8. Microsoft Learn, Create production BOMs (versions, Scrap %, routing link codes, calculation formula, phantom BOMs) — learn.microsoft.com
9. Microsoft Learn, Create routings (run, setup, wait and move time; send-ahead quantity; routing scrap) — learn.microsoft.com
10. Microsoft Learn, Set up work centers and machine centers (capacity, efficiency, "doesn't support detailed shop floor control") — learn.microsoft.com
11. Microsoft Learn, About production orders (simulated, planned, firm planned, released, finished) — learn.microsoft.com · Create production orders — learn.microsoft.com
12. Microsoft Learn, Subcontracting overview — learn.microsoft.com · Set up subcontracting — learn.microsoft.com · Order subcontracting — learn.microsoft.com · Manage components in subcontracting — learn.microsoft.com · Subcontract purchase provisions — learn.microsoft.com
13. Microsoft Learn release plan, Use subcontracting capabilities in production processes (GA 8 July 2026; Italian localisation deprecation) — learn.microsoft.com
14. Microsoft Learn, Update 28.3 for Business Central 2026 release wave 1 — learn.microsoft.com · What's new overview — learn.microsoft.com
15. Microsoft Learn, Use item charges to account for extra trade costs — learn.microsoft.com · Extending item charges in AL — learn.microsoft.com
16. Microsoft Learn, Design details: costing methods — learn.microsoft.com
17. Microsoft Learn, Quality management overview — learn.microsoft.com · Setup and configuration — learn.microsoft.com · Quality inspection templates — learn.microsoft.com
18. Microsoft Learn, Update currency exchange rates (Adjust Exchange Rates) — learn.microsoft.com
19. Microsoft Learn, Invoice prepayments — learn.microsoft.com
20. Microsoft Learn, Enable Premium features (Essentials vs Premium experience) — learn.microsoft.com · Licensing in Business Central — learn.microsoft.com
21. Microsoft Learn, Country/regional availability and supported languages — learn.microsoft.com
22. Microsoft Learn, Set up company configuration packages — learn.microsoft.com
23. Microsoft Learn, API (v2.0) for Business Central (extending APIs) — learn.microsoft.com · ALAppExtensions, APIV2 pages — github.com
24. Microsoft Learn, purchaseOrder resource — learn.microsoft.com · purchaseOrderLine — learn.microsoft.com · salesOrder — learn.microsoft.com · itemVariant — learn.microsoft.com
25. Microsoft Learn, Working with webhooks — learn.microsoft.com
26. Microsoft Learn, Working with API limits — learn.microsoft.com · Operational limits for Business Central online — learn.microsoft.com
27. Microsoft Learn, Using service-to-service authentication — learn.microsoft.com
28. Microsoft APIs Terms of Use — learn.microsoft.com
29. Microsoft AppSource, CS Fashion Central Premium (Central Solutions) — appsource.microsoft.com
30. Oracle NetSuite documentation: matrix items — docs.oracle.com · Grid Order Management — docs.oracle.com · Outsourced Manufacturing — docs.oracle.com · costing methods — docs.oracle.com · concurrency governance — docs.oracle.com
31. ISO 2859-1, Sampling procedures for inspection by attributes — iso.org
32. AQL tables and acceptance numbers — qima.com · tetrainspection.com · inspection levels: qualityinspection.org
33. UCP 600, documentary credits — uscib.org · tradefinanceglobal.com
34. EDI transaction sets — 1edisource.com · celigo.com

Corrections. Business Central changes every month, and a page name, a limit or a feature boundary can move in a single update; Microsoft has also said it stops publishing release plans from September 2026, so new features will appear on its AI at Work roadmap instead. If you find a statement here that your version contradicts, report a correction with the version and the page you checked; we correct the guide and note the change and its date at the top of this section. We re-check the Business Central facts in this chapter at least once a year and after each major release.

Microsoft, Dynamics 365, Business Central, Microsoft Entra, Power Automate and AppSource are trademarks of the Microsoft group of companies, used here only to name the products. This guide is not endorsed by Microsoft. Oracle and NetSuite are trademarks of Oracle and its affiliates. CS Fashion Central Premium is a product of Central Solutions and is named only as an example. Garment.io is named because MerchandiserOS integrates with it; this guide is not endorsed by Garment.io.