How to Implement Dynamics 365 Finance & Supply Chain Management for Garment & Apparel Business (2026 Guide)

1Who Dynamics 365 Finance & Supply Chain Management fits

Microsoft Dynamics 365 Finance and Dynamics 365 Supply Chain Management (together F&SCM, formerly Finance and Operations) fit textile and apparel groups with several legal entities, several countries or a vertical chain that runs from yarn or fabric through dyeing to garments. The deciding capability for many of them is process manufacturing: batch orders on formulas with co-products and by-products, which suit a dye house or a finishing plant.

F&SCM is a large ERP. It carries a product master with five product dimensions, batch tracking with batch attributes and disposition codes, discrete and process manufacturing in one system, intercompany trade, a landed cost module, quality orders with acceptance sampling, and an extension model in X++. It asks in return for a partner with manufacturing experience, a real project budget and a factory ready to work in a structured way. A single cut-and-sew factory with one company and a small office team usually does not need that much system; Business Central is the Microsoft product built for it.

Signs F&SCM is a good choice

F&SCM tends to work when the group's structure needs it: several companies, process manufacturing or its own retail.

• The group has several legal entities trading with each other, for example a knitting and dyeing company selling fabric to a garment company in the same group (section 23).
• Part of the business is process manufacturing: dyeing, washing, finishing, yarn dyeing or chemical recipes, where a formula yields a main product plus co-products or by-products (section 16).
• The group sells through its own stores or online as well as wholesale, and wants one product master shared with Dynamics 365 Commerce.
• There is budget for a partner, a support team and continuous updates, and someone owns the extension code.

Signs to slow down

Slow down when the expectations placed on F&SCM belong to a planning, floor or development system.

• The factory expects the ERP to balance sewing lines hour by hour and track bundles. Production orders and the production floor execution interface report jobs, not bundles moving between operators (section 15).
• The owners want tech packs, lab dips and PP samples inside the ERP. F&SCM has no object for them.
• The group is one company with one factory, and nobody can say which F&SCM capability Business Central lacks for it (section 9).
• 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 Dynamics 365 weakness. F&SCM's product dimensions are among the strongest variant models in any general ERP, and it still has no home for a lab dip round or a size-graded marker, which is why fashion ISV solutions exist on Microsoft AppSource, and why even they leave much of the work outside. The same wall stands in front of fashion brands, buying agents and own-label retailers that make nothing themselves, because the work they follow happens in factories their ERP cannot see (section 39).

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. In F&SCM that customisation is X++ extension code, which every continuous update must carry. 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 40 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: F&SCM keeps the books and the legal record of stock, and an operations system built for apparel runs everything from the style to the shipment.

For a vertical group there is a second line to draw. Dyeing and finishing are process manufacturing with formulas, batch genealogy and co-products, and F&SCM's batch orders handle them as standard. A group may choose to run its dye house in F&SCM and its garment operations on top. Section 16 explains the trade-off. With the split above, the F&SCM project stays close to standard: less X++, cleaner continuous updates and a shorter project. The rest of this guide still explains how to bend F&SCM toward garment production, because some groups choose to do that, and a consultant needs to know what each choice costs. Section 40 describes the model in full, department by department.

4Business types, and what each needs from F&SCM

"Apparel manufacturer" covers very different businesses, and a group that chooses F&SCM often contains several of them in different legal entities. The business type decides who owns the material, what is invoiced and which parts of F&SCM carry weight. Settle it per entity in the first discovery meeting.

The list above is general implementation practice. Treat it as a starting point for the discovery questions in section 6, not as a scope.

5Who should be on a Dynamics 365 apparel project team?

A Dynamics 365 apparel project needs one decision owner for every design question, and most of those owners sit in the factory or the group's head office, not in IT. The partner configures and builds; the business decides how styles, dimensions, batches, costs and inspections work, and in a group it also decides which entity owns what.

The table lists the roles we see on projects that go well. One person can hold several roles in a small entity. 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. Five rules prevent them, and the fifth matters most in a group.

• 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.
• The sponsor settles scope, not configuration. The sponsor decides whether T&A lives in F&SCM 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.
• Shared data has one owner across the group. Product masters, colours, sizes and units are shared across legal entities; released products are per entity. Decide who may create a product master, or each entity will invent its own.

6What should discovery workshops for an apparel group cover?

Discovery for an apparel group is one workshop per department and per entity type, 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 group's own orders, not the Contoso demo 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 group'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 does the group keep its own?

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, batches 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?
• Will the warehouse run advanced warehouse management with license plates and a mobile app, or basic inventory?

Dyeing, finishing and the mill

Process questions matter only if the group dyes, washes, knits or finishes in-house, and they decide whether batch orders are in scope.

• How is a dye recipe written today: per kg of fabric, per batch, per machine? Who approves a recipe change?
• What does one batch yield besides first-quality fabric: seconds, remnants, recoverable chemicals, waste?
• Which attributes are measured per batch before release: shade against the standard, GSM, width, shrinkage, fastness?
• Does the dye house sell to the group's garment company, to outside buyers, or both?

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) 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 entities, currencies, payment terms, import costing and tax.

• Which legal entities exist, which trade with each other, and at what transfer prices?
• 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?
• Is any site in a free zone or under a temporary-admission regime, and what reports does that require?
• Which e-invoicing and tax reporting rules apply in each country?

7The apparel fit-gap checklist for Dynamics 365 F&SCM: 52 lines

A fit-gap checklist lists every requirement an apparel business has and records, line by line, whether Dynamics 365 Finance and Supply Chain Management meets it as standard, meets it with configuration, needs X++ or an ISV, or is better handled outside the ERP. The 52 lines below cover product, BOM and costing, materials, production, quality, sales and shipping, and finance.

The answers are our assessment of Supply Chain Management 10.0.45 and later for a typical full-package garment entity, checked against Microsoft Learn. Where a line depends on a feature flag or a newer release, the note says so. Confirm each line in a sandbox on your version before you sign a scope.

Key: Standard works as delivered · Configure setup, parameters, attributes or light personalisation · Custom build X++ extension or an ISV solution · Operations layer better run in an apparel operations system and passed to F&SCM

Counted from this table, 10 of the 52 lines are standard, 24 need configuration, 10 need X++ or an ISV and 8 are better run outside F&SCM. That count is our assessment for a typical full-package garment entity, not a survey. It is a better score than most general ERPs reach, mainly because of batch attributes, disposition codes, acceptance sampling and letters of credit. A dye house or mill entity scores better still. A CMT entity drops most of the costing and material lines.

8Which Dynamics 365 apps does an apparel group need, and where does it run?

An apparel group implementing F&SCM usually licenses Dynamics 365 Finance and Dynamics 365 Supply Chain Management, and adds Dynamics 365 Commerce only if it runs its own stores or online shop. Microsoft sells these as separate apps on one platform; confirm current licensing, minimums and prices with Microsoft or a partner, because they change and we do not repeat them here.

Where does F&SCM run, and how are environments managed?

F&SCM runs as a cloud service that Microsoft operates, and its environments are now managed in the Power Platform admin center, where a finance and operations environment is an application inside a Power Platform environment. Microsoft is moving management capabilities from Lifecycle Services (LCS) to the Power Platform admin center, and developers work in a Unified Developer Environment (UDE), a sandbox provisioned for X++ development that replaces the cloud-hosted developer virtual machines deployed through LCS. Section 27 covers what that means for an apparel project.

Microsoft's documentation on service protection limits also refers to on-premises environments. If a group needs to run F&SCM on its own servers, check with Microsoft which deployment options are currently offered and what they exclude.

What drives the cost of an F&SCM apparel project?

The cost is driven by users per app, the partner's work, and above all the amount of X++ the fit-gap calls for; licences are usually the more predictable part. The table lists the drivers.

The fastest way to lower the total is to shrink the custom-build column. Every line moved to standard F&SCM or to an operations system is X++ nobody has to regression-test.

9F&SCM vs Business Central: which one for a textile group?

Choose between Dynamics 365 F&SCM and Dynamics 365 Business Central on process type and entity complexity, not on revenue. If any part of the group dyes, washes, finishes or mixes recipes and needs formulas with co-products or by-products, F&SCM has batch orders for it and Business Central has no documented equivalent. If the group is one or a few cut-and-sew companies doing discrete production, Business Central is usually enough and far lighter to run.

Which one should a textile group choose?

From practice, three questions decide it. Does any entity run process manufacturing where a formula yields co-products or by-products? Do several legal entities trade with each other every week? Will the group sell through its own stores on the same product master? Two or three yes answers point to F&SCM. None points to Business Central, and a group that picks F&SCM anyway pays for capability it will not use. One yes is a real decision; weigh it against the cost of the project and the team to run it. Our Business Central chapter covers the other side, and the comparison page sets both against other ERPs.

10How should products and materials be set up in Dynamics 365 for apparel?

Set up apparel products in F&SCM by how each material is bought, stocked, costed and tracked: fabrics, yarns, trims, packaging, subcontract services and finished garments each get their own item group, item model group and dimension groups, because those groups carry the ledger postings, the inventory model and whether batches are tracked. 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 F&SCM setup must follow them.

What each group carries in F&SCM

Four groups on the released product do most of the work. The item model group sets the inventory model; Microsoft lists FIFO, LIFO, moving average, periodic weighted average and standard cost as the supported costing methods, and the same group decides whether a service is a stocked product, which matters for subcontracting (section 18). The item group drives ledger postings. The tracking dimension group decides whether batch numbers and serial numbers are active. The storage dimension group decides site, warehouse, location and whether warehouse management processes and license plates are used.

Decide these before the first product is released. Microsoft's documentation on inventory dimension groups states that the storage and tracking dimension groups of a product with transactions cannot simply be changed; Supply Chain Management offers a tool to change the storage dimension group for items only as part of the warehouse-management upgrade path. Treat every group choice as permanent.

With operations on top: the style, its bill of materials by category and its consumption are built in the operations layer. F&SCM still needs the groups above, because it holds stock value, batches and the payables.

11How do you set up size and colour variants in Dynamics 365 Supply Chain Management?

Model the style as a product master and give it a product dimension group that switches on the dimensions the style varies by, usually Colour and Size; each valid combination becomes a product variant. Microsoft documents five product dimensions (Colour, Configuration, Size, Style and Version), combined in dimension groups that are assigned to product masters. A product master needs at least one active dimension.

Dimension values are created under Product information management ‣ Setup ‣ Dimension and variant groups, on the Sizes, Colors and Styles pages, and maintained per product master from its Product dimensions action. Size, colour and style also have groups (size group, colour group, style group), so a product can take all the sizes of one scale in one step. The Version dimension has no group; versions are added as the product changes.

Which configuration technology should a garment style use?

Use predefined variants for bulk garments. Microsoft documents three configuration technologies: predefined variants, where each valid combination of Colour, Style and Size is a distinct variant; dimension-based configuration, where the Configuration dimension selects BOM lines from one shared "global" BOM; and constraint-based configuration, where a product configuration model describes every possible variant. Microsoft states that a product cannot be converted from one model to another after implementation, so this choice is permanent per product master.

Shared products and released products

A product master is shared across the group; it is then released to each legal entity that buys, makes or sells it, and each released product carries that entity's settings. In a group this is the right shape: the dye house and the garment company share the jersey product master, and each releases it with its own warehouses and costing. It also means someone must own product creation for the whole group (section 5).

Microsoft's own example is a pair of jeans in three colours and six sizes where only nine of the eighteen combinations are made. With predefined variants you create only the combinations that exist. Do that on purpose: generate variants when a colourway is confirmed, not every combination on day one.

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

12How do you convert kilograms to metres for fabric in Dynamics 365 Supply Chain Management?

F&SCM can convert kilograms to metres with an inter-class conversion defined for a specific product, and from the Unit of measure conversions for product variants feature also for a specific variant; it cannot hold a different conversion per batch, which is what knit fabric really needs. Kilograms are in the mass unit class and metres in the length unit class, and standard conversions work only inside a class.

GSM means grams per square metre: the weight of one square metre of the fabric. The conversion depends on the fabric's GSM and its width, so it differs for every fabric and often for every roll.

Units are managed under Organization administration ‣ Setup ‣ Units ‣ Units. Each unit has a unit class; its Unit conversions page has three tabs: standard conversions for all products, intra-class conversions for one product, and inter-class conversions for one product across classes. With the variant feature on, a product master's Enable unit of measure conversions option lets a conversion be set per variant, with the product master's conversion as the fallback. Microsoft notes the variant feature is not available for catch-weight products.

Is catch weight the answer for knit fabric?

Usually not, for a garment factory. Catch weight lets an item carry two units, a catch-weight unit and an inventory unit such as kg, with a nominal conversion and minimum and maximum weights. Microsoft's catch weight documentation lists restrictions that matter here: with warehouse management, only formula processing is supported for catch-weight products, not bills of materials; kanbans are not supported; and the Landed cost module does not support purchase orders with catch-weight items. A garment BOM and an imported-fabric voyage would both be affected. Catch weight can suit a mill entity that works on formulas; test it there before assuming it.

Three workable designs

There are three workable ways to hold knit fabric in a garment entity, 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. F&SCM can stay in the purchase unit, kilograms, for stock value and payables.

13How do you track dye lots and fabric rolls in Dynamics 365?

Track fabric by batch in F&SCM and treat each batch number as one dye lot: give the fabric a tracking dimension group with the batch number active, record shade, GSM and width as batch attributes, and use batch disposition codes to hold a lot until quality releases it. 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.

Batch attributes

Microsoft describes batch attributes as characteristics of raw materials and finished products that make up inventory batches. They are assigned per product, and optionally per product and customer; an Integer or Fraction attribute can carry a minimum, a maximum and a target value, with a warning or an error when a value falls outside the range. The product must have the batch dimension active in its tracking dimension group. When batches are reserved for a sales order or picked for a production order, users can search on batch attributes to find a batch that fits.

For fabric this is a strong fit, though Microsoft's own examples are cheese and steel: shade group, GSM, width and shrinkage per dye lot, with the buyer's tolerance as the range. A customer-specific attribute lets one buyer's tighter GSM tolerance apply only to that buyer's orders.

Batch disposition codes

A batch disposition code marks a batch as available or unavailable. Codes are set up under Inventory management ‣ Setup ‣ Batch ‣ Batch disposition master; an Unavailable code blocks master planning, reservation, picking and shipping by default, and each block can be relaxed per order type (sales, transfer, production). Codes are assigned to batches from Warehouse management ‣ Setup ‣ Inventory ‣ Batches with Reset batch disposition code. Microsoft notes that for items with a reservation hierarchy where batch is below location, the codes are enforced at reservation only in warehouse-management warehouses or with the advanced batch reservation policy.

Rolls and shade bands

Tracking each roll is a design choice: a serial number per roll gives roll-level issue and return; under warehouse management a license plate per roll keeps the batch as the unit and gives each roll a scannable identity. 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. F&SCM has no shade band object; the shade group is a batch attribute and the band itself is a physical reference 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. F&SCM still holds the batch on receipts and issues, so stock value and traceability stay correct.

14How do you handle size-dependent fabric consumption in Dynamics 365 BOMs?

To give a garment size its own fabric quantity in F&SCM, create a BOM version for that variant: Microsoft documents that relating a BOM to a product variant requires a BOM version, and that a version's validity can be constrained by period, quantity, site and specific product dimensions. With five sizes and three colours that is up to fifteen BOM versions per style, so generate them from a consumption table rather than typing them.

The alternative is dimension-based configuration, where one global BOM holds every line and the Configuration dimension selects the lines valid for a configuration. It suits products configured to order; for a bulk garment with a predefined Colour-Size variant it means an extra dimension to carry, and the configuration technology cannot be changed later (section 11). Most garment projects use BOM versions per variant, generated by a script or an extension.

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. A BOM line holds one quantity, so the split is kept in the consumption table or the operations layer.

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 F&SCM. F&SCM does not need BOM versions per size at all.

15How do you model cutting, sewing and finishing with Dynamics 365 routes?

Model cutting, sewing, finishing and packing as resources and resource groups, list the garment's operations with their times on a route, and use production orders to make each variant; this gives jobs, scheduling against capacity and a labour cost, but it does not balance a sewing line or track bundles. A production order in F&SCM is based on a BOM and a route and makes a product or product variant in a given quantity on a date.

Microsoft's production process overview names the order types that can be mixed in one end-to-end process: production orders, batch orders, kanbans and manufacturing projects. It lists the life cycle stages: created, estimated, scheduled, released, prepared or picked, started, progress reported, reported as finished, quality assessment, put away, ended, and period closure. Scheduling can be operations scheduling, a rough long-term plan, or job scheduling, where operations break into jobs assigned to resources, with finite capacity where it is used and a Gantt chart to adjust the plan.

What an operation 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. List each as a route operation, or group them into a few operations per department. Grouping keeps jobs manageable; listing every operation gives a detailed cost but floods the job list.

The production floor execution interface

F&SCM's production floor execution interface lets workers clock in and out, start jobs, report progress on production and batch orders (including co-products and by-products), see the materials a job needs and register batch and serial numbers of tracked components. It is a genuine shop-floor screen. In a garment factory it works well at the level of a job per operation; it does not capture pieces per operator per hour or bundle movement without extension.

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. F&SCM receives material issues for stock value and does not need garment production orders at all.

16Can Dynamics 365 run a dye house or finishing plant with batch orders?

Yes. F&SCM's batch order is built for processes where manufacturing conversion is based on a formula, or where co-products and by-products are end products alongside or instead of the main product, and batch orders use Formula-type BOMs and routes. This is the capability that most often decides F&SCM against Business Central for a textile group, because dyeing, washing, finishing and yarn dyeing are formula processes.

A formula defines the ingredients and outcomes of a process. Its lines can be items, formula items, catch-weight items, purchased items, co-products or by-products, and a line can be of type Vendor where a subcontractor does the work. Every formula has at least one version; versions are approved before use, and the production control parameters can block editing of approved formulas and require an electronic signature at approval. Step consumption suits chemicals whose quantity rises in steps with batch size rather than in proportion.

Decide how cost is shared between the main product and co-products with finance, and check the co-product cost settings in your version. Recipe development, lab dips and shade approval still happen before any formula is approved, and they are outside F&SCM.

With operations on top: MerchandiserOS does not run dye recipes. In a vertical group, the dye house can run its batch orders in F&SCM or in its own system; the garment operations in MerchandiserOS see the dyed fabric as a receipt with its measured lot record and incoming inspection, judged against the shade band.

17Where do sampling, approvals and the T&A calendar live in a Dynamics 365 project?

F&SCM has no object for garment samples, buyer approvals or a T&A calendar, so a Dynamics 365 project must build them in X++, buy an ISV solution, borrow Dataverse and Power Apps, 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.

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. The typical failure is bulk fabric ordered, or cutting released, on the strength of an approval nobody can find.

What a sampling solution must hold, wherever it is built

If the project builds sampling in X++ or in a Power App on Dataverse, the minimum design is the same.

• A sample request per style and colourway, 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 spec version it approved, so a later revision cannot silently replace it.
• A block on the next step: the dye formula waits for the lab dip, the cutting production order waits for the PP sample.
• T&A milestones that take their actual dates from the rounds instead of from someone typing them.

A Power App on Dataverse avoids X++, and virtual entities can show F&SCM data inside it. It is still an application someone must own, secure and keep in step with F&SCM releases.

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. F&SCM needs none of it.

18How does subcontracting work in Dynamics 365 Supply Chain Management?

F&SCM documents two ways to subcontract production work: subcontracted route operations on production or batch orders, and activity-based subcontracting in lean production flows. The first suits a garment factory sending panels out for embroidery or printing; the second suits steady, repetitive outsourcing such as a CMT unit that sews every week against a purchase agreement.

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

In the route-operation model the service sits on a BOM line of type Vendor, allocated to the route operation, whose resource is a resource of type Vendor linked to the vendor account. The purchase order acts as the anchor for the subcontracted operation, and the Subcontracted work list page in Production control ships material and semi-finished goods to the vendor and receives them back. For production and batch orders, semi-finished goods move to the vendor only through the picking list journal on that page, which creates a delivery note. Receiving the purchase order line completes the operation.

Three documented rules shape the garment design. A production order can have many operations, each with a different vendor, so one order can trigger several purchase orders: printer, sewing unit and washer in one chain. There is no explicit concept of semi-finished products, so printed panels are tracked in WIP, not as stock. And a production route cannot cross sites, so the vendor-managed warehouse that holds material at the subcontractor must be in the same site as the internal resources.

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. F&SCM shows the subcontracted work, the purchase order and the vendor-managed warehouse. The allowance, the reject reasons and the balance per order are 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. F&SCM receives the subcontractor's purchase order and the payable.

19How do you cost a garment in Dynamics 365, and where does the costing sheet live?

F&SCM costs stock through the inventory model on the item model group, calculates standard costs for manufactured items from BOMs and routes in a costing version, adds indirect costs through costing sheets, and brings freight and duty into stock through the Landed cost module. The garment costing sheet used to quote a buyer is built before any product master exists and usually lives outside F&SCM.

• Inventory models. Microsoft supports actual cost methods (FIFO, LIFO, moving average, periodic weighted average) and standard cost.
• Costing versions. A costing version of type Standard cost holds cost records for items, cost categories and calculation formulas for indirect costs. Variances to standard can be kept per cost group, so purchase price and production variances show by cost element.
• Costing sheets. A costing sheet defines the cost breakdown format and the basis for indirect costs, with surcharges and routing costs.
• Landed cost. Voyages, containers and folios, cost types such as duty, freight and insurance, apportioned by quantity, volume, weight or amount (below).

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. Pre-costing a style is done before a product master exists, so it tends to live outside F&SCM.

How do you configure landed costs in Dynamics 365 for imported fabric and customs duties?

Use the Landed cost module: create a voyage for the shipment, add the purchase order lines to a shipping container, add costs (from auto costs or by hand) at the voyage, container, item or order level, and let the apportionment rules spread each cost by quantity, volume, weight or amount. 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.

Microsoft's overview describes the flow. Estimated landed costs are posted with the purchase order invoice, and actual costs when the vendor invoice journal is posted, through clearing accounts per cost type; for moving average and standard cost items, purchase price variance accounts take the difference. Goods-in-transit orders are optional and let the business take ownership at the port of loading. The module does not support project purchase orders, purchase orders with catch-weight items, service or non-stocked items, or non-deductible tax as a voyage cost.

Choose the apportionment per cost type. Sea freight follows weight or volume; clearing and bank charges usually follow amount; 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 reporting rules 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. F&SCM holds the landed cost that actually hit the receipts, for stock value.

20Can Dynamics 365 run AQL inspection for garments?

Yes, from Supply Chain Management 10.0.45. The acceptance sampling feature adds a sampling code letter chart and an AQL chart to quality orders, can load both from a template that Microsoft says aligns with ANSI/ASQ Z1.4 or ISO 2859-1, and marks each test on the quality order with its sample size, acceptance number and rejection number. The feature is on by default from 10.0.49. Only single sampling is supported.

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. In F&SCM the pieces fit together like this.

Advanced quality management (10.0.44 and later) adds CAPA cases, flexible sampling plans with skip-lot testing, electronic signatures, customer-specific certificates of analysis and quick results entry. A skipped test is excluded from AQL calculations, and the decision to skip is kept for the audit trail.

Quality control at cutting, sewing, 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 at a dye house or printer, so those checks land on the receipt, or on the batch order where the dye house belongs to the group.

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. F&SCM's acceptance sampling remains useful for a dye house or mill entity that keeps its production in F&SCM.

21How do you handle cartons, packing lists and shipping documents in Dynamics 365?

F&SCM packs goods into containers under warehouse management, posts a packing slip for the shipment and prints delivery documents; assorted and ratio cartons, buyer carton labels and pack-level packing lists usually need an extension or ISV. Over-delivery and under-delivery percentages on the product or the order line control how far a shipment may differ from the ordered quantity.

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. F&SCM receives the dispatch, posts the packing slip and raises the customer invoice.

22How does Dynamics 365 Finance handle multi-currency, letters of credit, prepayments and chargebacks?

Dynamics 365 Finance handles foreign currencies, customer prepayment invoices and export and import letters of credit as standard; buyer chargebacks can use the deduction workbench where rebate or trade allowance agreements exist, and otherwise reason-coded write-offs. Garment exporters usually sell in USD or EUR, buy some materials abroad and pay wages locally, so every order touches at least two currencies.

Customer prepayments

Microsoft distinguishes a customer prepayment invoice, a billing document tied to a sales order for a percentage or fixed amount that the final invoice later accounts for, from a customer prepayment, a payment received with no invoice to settle against. For a buyer who pays 30% of the order in advance, the prepayment invoice is the closer fit.

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. Dynamics 365 Finance has export letters of credit and import letters of credit and import collections in Cash and bank management, set up with bank facilities and posting profiles. On a sales order the bank document type is set to Letter of credit, and the credit carries the bank document number, the expiration date, the issuing and advising banks and the shipments fetched from the order. After invoicing, each shipment line shows as documents submitted, then payment received.

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. F&SCM's deduction workbench (Sales and marketing ‣ Trade allowances ‣ Deductions ‣ Deduction workbench) settles short payments against claims, but it requires deduction management setup and a customer rebate or trade allowance agreement. Garment chargebacks are usually penalties, not rebates, so many projects register the short payment and write the difference off to a chargeback account with a financial dimension for the reason.

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

23How does Dynamics 365 handle a group of textile companies and intercompany trade?

Each company in the group is a legal entity in one F&SCM environment, identified in data entities by its dataAreaId; product masters are shared across the group and released to each entity, and intercompany trade relationships let a purchase order in one entity create the matching sales order in another as an order chain. This is the second reason, after batch orders, that vertical groups choose F&SCM.

Intercompany trade is set up between a vendor account in one entity and a customer account in another, with parameters for Accounts payable, Accounts receivable, procurement and sales. When a sales order or purchase order is created for one of the parties, the order chain creates the other order in the right entity. Planning Optimization documents intercompany planning, so demand in the garment company can drive supply in the dye house.

If the group sells through its own stores or online, Dynamics 365 Commerce works on the same product masters and variants: a new colourway released for wholesale is the same variant the store sells. That is a real advantage over running a separate retail system, as long as the product master design in section 11 is right for both. Note that Commerce channel apps do not support the Version dimension.

24Does Dynamics 365 Finance support e-invoicing in garment-exporting countries?

Microsoft publishes an electronic invoicing coverage list for Dynamics 365 Finance. At the time of checking it lists Egypt (generation and direct submission to the Egyptian Tax Authority) and India (submission to the Invoice Registration Portal) as available, Türkiye as a public preview, and Indonesia and Malaysia as available. For every other country, check the list and a local partner before assuming compliance.

E-invoicing rules change often, so treat any statement older than the current tax year with care. Factories in free zones or under temporary admission often report the import and re-export of materials to customs. F&SCM stock movements carry the quantities, but the report format is local and usually custom.

25In what order should you configure Dynamics 365 F&SCM for an apparel group?

Configure F&SCM for an apparel group from the ledger outward: legal entities, currencies and financial dimensions first, then units and product dimensions, then dimension groups and item model groups, then batches, quality and landed cost, then production and subcontracting, and only then the products. Each step depends on the one before it, and several choices (dimension groups, configuration technology) cannot be changed once transactions exist.

Menu paths below are given only where Microsoft Learn states them. Labels move between releases; check each on the version you deploy.

26What X++ extensions and ISV solutions does an apparel implementation usually need?

An apparel F&SCM implementation that keeps operations inside the ERP usually needs extensions or ISV solutions for size consumption, per-batch fabric conversion, cutting control, packs, sampling, T&A, colour-by-size order entry and buyer documents. Extensibility is the only customisation model: overlayering is not supported, and since release 8.0 Microsoft's models are sealed so customisation happens only through extensions.

An extension adds new model elements, extends existing ones and extends source code through class extensions and event handlers, which keeps Microsoft's code intact across updates. Three documented details matter for apparel projects. OData actions added through extensions are not currently supported, so an integration that needs custom behaviour exposes it through a custom service or a custom data entity. Extensions that reference inventory dimensions must also handle the Version dimension once it is on. And where an extension needs a hook Microsoft has not provided, partners file an extensibility request with Microsoft and wait for it.

From practice: an ISV fashion solution can cover several rows at once, and it is still code that must be tested with every Microsoft service update, on the ISV's timetable. Ask each ISV which F&SCM releases it supports today and how quickly it certified the last two.

27How are Dynamics 365 F&SCM environments set up for an apparel project?

Plan at least a development environment, a test sandbox and production, and usually separate sandboxes for data migration rehearsal and for training. Environments are now administered in the Power Platform admin center, where finance and operations apps run inside a Power Platform environment with a Dataverse database, and development moves to Unified Developer Environments provisioned for X++ with the Power Platform CLI and Visual Studio.

Data events need the Microsoft Power Platform integration enabled on the environment, so decide early whether the integration design in section 36 relies on them. Microsoft documents copying a Lifecycle Services environment to a unified environment for projects that started under LCS.

28Which systems does a Dynamics 365 apparel implementation integrate with?

A Dynamics 365 apparel implementation typically connects to a PLM or tech-pack system, a shop-floor system, EDI with retailers, banks, Dataverse apps and an operations layer; each connection needs one owner per field, keys that never change and a throttling priority. The table shows the usual source of truth for each kind of record, based on general practice.

Rules for every connection

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

• Link on F&SCM's keys, including the legal entity. A data entity record is identified by its full entity key, and the same order number can exist in two legal entities; store the dataAreaId with every link.
• Hold product dimensions as structured fields. Colour, size and style travel as separate values, never as a code someone has to parse.
• 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.
• Handle 429 responses and set a throttling priority. The integration's Entra app gets Low, Medium or High priority, and the client retries after the interval the service gives.

29How do you migrate apparel data into Dynamics 365 F&SCM?

Migrate only open and active apparel data (active styles, open orders, open purchase orders and stock by batch) through the Data management framework: data entities grouped in data projects, run as data jobs from data packages, loaded in dependency order and signed off by each department head. History stays in the old system or an archive.

A data entity is a conceptual abstraction of one or more tables, such as Customers or Vendors. A data project holds configured entities with their mapping; a data job is one run of it with its files and schedule; a data package is a single compressed file with the project manifest and data files. For repeated loads and rehearsals, the package REST API and the recurring integrations API automate import and export with OAuth 2.0. Microsoft lists the Data Import/Export Framework and recurring integrations among the services exempt from service protection API limits.

Load order

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

The cut-off rule

A cut-off rule states the exact moment after which every transaction is entered in F&SCM 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, a batch half dyed, 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. In a group, each legal entity can have its own cut-off, but an intercompany chain that spans two entities must not straddle two systems.

Cleansing

Clean data before it is loaded, never after.

• Merge duplicate vendors and materials ("Navy Jersey 180", "Jersey 180 NVY").
• Retire styles with no order in two seasons.
• Give every fabric one inventory unit, and every roll in stock its batch number and measured attributes.
• Map old size labels to the new size groups, one scale at a time.
• Split any "open" order line that is already partly delivered into delivered and open quantities.

dataAreaId,ProductNumber,Color,Size,SalesPrice
gar,P-2041,NVY,S,4.26
gar,P-2041,NVY,M,4.26
gar,P-2041,NVY,L,4.26
gar,P-2041,NVY,XL,4.26
gar,P-2041,NVY,XXL,4.26

dataAreaId,SalesOrder,Item,Color,Size,Qty,UnitPrice,LineAmount
gar,SO-P2041,P-2041,NVY,S,300,4.26,1278.00
gar,SO-P2041,P-2041,NVY,M,750,4.26,3195.00
gar,SO-P2041,P-2041,NVY,L,900,4.26,3834.00
gar,SO-P2041,P-2041,NVY,XL,750,4.26,3195.00
gar,SO-P2041,P-2041,NVY,XXL,300,4.26,1278.00

Open PO:  gar / PO-000457, navy jersey 180 GSM, 925 kg ordered, 0 kg received
Stock:    gar, buttons 15 mm NVY, 9,504 pcs, warehouse FAB-TRIMS, no batch

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.

30How should you test a Dynamics 365 apparel implementation end to end?

Test a Dynamics 365 apparel implementation with end-to-end scenarios that follow one real order from the buyer's PO to cash, run by the group's key users on migrated data in a sandbox, each step with an expected result written down before the test starts. Testing screens 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, at least T1, T4 and T5, after every Microsoft service update that touches production, inventory or quality.

Test script: subcontract embroidery with loss

Scenario T5 proves that fronts sent out, fronts returned and fronts lost add up, using the route operation from Example 15.

Test script: short shipment within tolerance

Scenario T6 proves that a short shipment inside the buyer's tolerance is invoiced on what shipped. The sales lines carry a 3% under-delivery percentage; the factory ships 2,940 pieces, 30 short in M and 30 short in L.

31How should you train a garment group's staff on Dynamics 365?

Train each role only on the workspaces and scenarios it will use, in the local language, on the group's own styles and orders, and have key users teach their colleagues. A merchandiser does not need the general ledger, and a floor supervisor needs one screen that works, not an introduction to Dynamics 365.

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. Use the training sandbox, not production, and keep it stable during training weeks.

Floor operators and supervisors are trained on whatever captures floor output. If that is the production floor execution interface or a kiosk, the training is minutes, not hours; if it is F&SCM's office forms, expect the data never to arrive.

32What does a Dynamics 365 cut-over plan look like for a garment factory?

A Dynamics 365 cut-over plan is a day-by-day list of the steps that move a legal entity from the old system to F&SCM: freeze, final data packages, stock count by batch, opening balances, checks and the first live transactions, each with an owner and a go or no-go point. Rehearse it once in full in the migration sandbox before the real weekend.

33When should a garment group go live on Dynamics 365, 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 F&SCM. In a group, go live entity by entity, and put the entity whose intercompany chains are simplest first. 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 week of a scheduled Microsoft service update.
• 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 F&SCM is complete.
• 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, integrations run without throttling errors, and key users handle first-line questions without the partner.

34What are the most common mistakes when implementing Dynamics 365 F&SCM for apparel?

The most common mistakes in apparel F&SCM projects are the wrong configuration technology or dimension groups (both permanent), every colour-size combination created on day one, catch weight used for garment fabric, one kg-to-metre factor for every roll, batches not enforced at picking, and more X++ than the team can carry through updates. The list below comes from implementation practice, not from Microsoft's documentation.

1. The wrong configuration technology.A product master cannot be converted from one technology to another after implementation.
2. Dimension groups chosen in a hurry.Storage and tracking groups cannot simply be changed once a product has transactions; fabric released without batch tracking stays without it.
3. Every colour and size released on day one.Thousands of variants nobody sells; create predefined variants when a colourway is confirmed.
4. Style dimension confused with the garment style.The garment style is the product master; the Style dimension is an axis such as inseam.
5. Catch weight for garment fabric.Formula-only with warehouse management, and not supported by the Landed cost module.
6. One conversion factor for all rolls.Stock in metres looks right while the cutting room runs short.
7. One BOM version for all sizes.Large sizes run short and small sizes leave surplus.
8. Batches recorded but not enforced.Disposition codes and attribute ranges exist, but nobody set them, so any batch can be picked.
9. Subcontract purchases outside the production order.Embroidery bought on a plain purchase line; WIP and cost lose the link to the operation.
10. Landed cost by manual journal.Freight and clearing posted to expense; fabric cost understated.
11. Seasons in free text.Use attributes or categories, or no report will ever group by season.
12. No throttling budget for integrations.A bulk sync and the operations layer share one Entra app with no priority, and both get 429 responses at month-end.
13. X++ the team cannot carry.Every extension is retested at every service update; unowned code blocks updates.

The 15 general failure modes, and how each shows up in F&SCM

Apparel ERP projects fail in the same fifteen ways whatever the ERP. The table maps each one to where it appears in an F&SCM project and how to prevent it.

35What must be decided before a Dynamics 365 apparel go-live?

Decide the configuration technology, the dimension groups for every material and style, the batch attributes and disposition codes, the inventory model per item model group, the legal entity and intercompany design, and which system owns sampling, T&A and floor capture before go-live, because each is expensive or impossible to change once transactions exist. The full list:

• The configuration technology per product master (predefined variant for bulk garments).
• The product dimension group per category, and the size group per size scale.
• Product master per style, or per style-colour where each colour costs and prices on its own.
• Tracking dimension groups: batch active for fabric and yarn; serial or license plate for rolls.
• Storage dimension groups: warehouse management processes on or off, per warehouse.
• Batch attributes, their ranges, and the disposition codes with who may change them.
• The unit design for every fabric and yarn, and whether per-batch conversion is built.
• Item model groups: inventory model per material and garment; which services are stocked.
• Legal entities, intercompany relationships and transfer prices.
• Which entity, if any, uses formulas and batch orders, and how co-products are costed.
• Which system owns sampling, T&A, planning, floor capture and quality: F&SCM with X++, an ISV, or an operations layer.
• How buyer-supplied fabric is held so it never enters stock value.
• Over-delivery and under-delivery percentages, and who may approve a shipment outside them.
• Financial dimensions for order profitability and chargeback reasons.
• The integration app registrations, their throttling priorities and whether data events are used.

36Which Dynamics 365 F&SCM API should an apparel integration use?

Use OData data entities for record-level reads and writes, data events or business events for push notifications, and the Data management framework's package or recurring integrations APIs for bulk files; authenticate with a registered Microsoft Entra application and give it a throttling priority. Dual-write is for synchronising with Dataverse and Dynamics 365 customer engagement apps, not a general API for third-party systems.

Identifiers and legal entities

By default OData returns data from the caller's default company only. To read across companies, add ?cross-company=true; to read one company, filter on dataAreaId, for example $filter=dataAreaId eq 'gar'&cross-company=true. An apparel integration should therefore store every link as legal entity plus the entity's key (for a purchase order, dataAreaId and the purchase order number), never the number alone. Hold colour, size and style as separate fields on every variant reference.

Throttling

F&SCM applies resource-based service protection limits: when web server resources are under pressure, OData and custom service requests get a 429 Too Many Requests response, and the client retries after the interval the service gives. User-based limits (6,000 requests, 1,200 seconds of execution time and 52 concurrent requests per five-minute window) were made optional and, from 10.0.36, are disabled. Under System administration ‣ Setup ‣ Throttling priority mapping, an administrator assigns each integration's Entra application or user a Low, Medium or High priority, so a nightly bulk sync is throttled before the operations layer's purchase-order feed.

Push and pull

Use a data event on the purchase order entity to learn that something changed, then read the record by its key. Keep a scheduled pull as the dependable baseline, because events can arrive out of order, and make every receiver safe to call twice.

POST /api/v1/erp/po-status
Idempotency-Key: d365-gar-PO-000457-confirmed

{"rows": [{"request_ref": "PR-1042",
           "erp_po_id": "gar:PO-000457",
           "erp_po_number": "PO-000457",
           "status": "Confirmed",
           "date": "2026-10-21"}]}

37Is Dynamics 365 F&SCM a good ERP for fashion brands that outsource production?

Dynamics 365 Finance and Supply Chain Management can be a strong ERP for fashion brands and clothing brands that outsource production, when the brand has several legal entities, imports through voyages with goods in transit, pays by letter of credit or runs its own stores on Dynamics 365 Commerce. It should be implemented without its manufacturing modules. For a single-entity brand, Business Central is usually the lighter choice.

Three kinds of apparel business make nothing themselves, and each needs a different slice of F&SCM.

What a brand needs from F&SCM

A brand needs the procurement, import, finance and sales halves of F&SCM, and none of production control.

• Purchase orders to factories on FOB or CMT terms, on the same product masters and variants the brand sells. Vendor collaboration lets factories without EDI see purchase orders sent for review and accept, reject or accept them with changes, and a vendor's confirmation can confirm the order automatically.
• Landed cost and duty through voyages, containers and folios, with goods-in-transit orders so ownership can pass at the port of loading, as most FOB terms require.
• Vendor payments and import letters of credit in Cash and bank management.
• Wholesale sales orders to retailers, with over- and under-delivery percentages, and chargebacks handled through the deduction workbench or reason-coded write-offs.
• EDI 850, 856 and 810 with retailers through an EDI provider or ISV; F&SCM has no EDI translator of its own.
• Multi-currency and intercompany, for a group with a sourcing office in the producing country and a sales company in the market.
• Dynamics 365 Commerce on the same product masters, for a brand or own-label retailer with stores or an online shop.

What a brand should not buy or configure

Skip production control, routes, resources, formulas and batch orders, the production floor execution interface and manufacturing master planning. A brand's "production" happens in someone else's factory, and none of these screens can see inside it. Keep batch tracking only if the brand must trace dye lots or production lots to cartons for recalls or buyer claims, and keep quality orders for inspections done at its own warehouse on arrival.

38Can Dynamics 365 handle a buying agent's commission accounting?

Yes. A buying agent that takes no title to goods invoices its commission to the buyer with a free text invoice, which Dynamics 365 Finance creates under Accounts receivable ‣ Invoices ‣ All free text invoices, with a main account and financial dimensions per line and optional templates or recurring invoices. It needs no inventory, no goods payables and no goods receivables.

Buying house ERP and sourcing agent software are often discussed together, but the accounting differs by model.

F&SCM also has a sales commission feature, where commission groups and sales representatives earn a percentage of the sales order's net amount. It is built for paying the business's own sales reps, not for an agent's income from a buyer, so use free text invoices for the agent. Whether a buying commission belongs in the customs value of the goods is a question for the customs broker in each importing country.

39What does Dynamics 365 handle poorly for brands and agents, and what runs on top?

F&SCM records the purchase order, the voyage and the invoice, but it does not follow the work that happens inside other companies' factories: development and sampling across many factories, T&A across factories, the progress of production it does not run, inspections at the vendor, and one status per order across many factories and buyers. The same wall stops manufacturers in section 2, and it stands taller for a brand, because every step it cares about happens somewhere its ERP cannot see.

The MerchandiserOS model for brands and agents

MerchandiserOS runs the private label sourcing work: development, samples and approvals, T&A, the orders placed with factories, sourcing, the planning view across subcontracted factories, quality inspections and shipping follow-up. Dynamics 365 keeps the books: purchase orders as the financial record, landed cost, payables, receivables, letters of credit, commission invoices, tax and e-invoicing. MerchandiserOS's workspace set-ups include "Brand" and "Buying agent". Retail back-office work (stores, point of sale, allocation and open-to-buy) is outside MerchandiserOS's scope; for an own-label retailer that stays in Dynamics 365 Commerce or a retail planning system.

·Glossary of apparel and Dynamics 365 terms

Short definitions of the apparel and Dynamics 365 terms used in this guide.

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.

Acceptance sampling

The Supply Chain Management feature (10.0.45 and later) that applies code letter and AQL charts to quality orders.

Batch attribute

A characteristic recorded per inventory batch, such as GSM, width or shade group, with an optional minimum, maximum and target.

Batch disposition code

A code that marks a batch as available or unavailable for master planning, reservation, picking and shipping.

Batch order

A production order type for formula-based processes, able to produce co-products and by-products.

BOM version

A version of a bill of materials whose validity can be limited by date, quantity, site and product dimensions; the way to give one variant its own BOM.

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.

Co-product, by-product

Outputs of a batch order besides the main product; in dyeing, second-quality fabric is a typical co-product.

Costing version

A set of cost records for items and manufacturing processes; a Standard cost version holds standard costs.

Cut-over

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

dataAreaId

The field identifying the legal entity a record belongs to in F&SCM data entities.

Data entity

An abstraction over one or more tables, used for OData, data events and the Data management framework.

Dual-write

Near-real-time, bidirectional synchronisation between F&SCM and Dataverse.

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.

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.

Formula

The ingredients, quantities and outcomes of a process-manufacturing step, used by batch orders.

Free text invoice

A customer invoice in Dynamics 365 Finance not tied to a sales order, posted to a main account; suits commission invoicing.

GSM

Grams per square metre: the weight of fabric.

Hypercare

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

Item model group

The group on a released product that sets the inventory model (FIFO, moving average, standard cost and others) and stocking policy.

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 beyond the supplier's price: freight, insurance, duty, clearing, bank charges. Also the name of the F&SCM module that handles it.

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.

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.

Predefined variant

The configuration technology where each valid combination of colour, size and style is a distinct product variant.

Product dimension

One of the five characteristics that identify a product variant: Colour, Configuration, Size, Style, Version.

Product master, variant

In F&SCM, the product master is the style; each variant is one combination of dimension values, such as navy, size L.

Quality association

A rule that creates a quality order automatically on an event such as product receipt or production output.

Ratio pack

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

Released product

A shared product released to a specific legal entity, where it gets that entity's settings.

Shade band

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

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.

Tracking dimension group

The group that switches batch and serial number tracking on or off for a product.

UCP 600

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

Voyage

In the Landed cost module, a movement of goods from an outbound location to an inbound warehouse, carrying containers, folios and costs.

X++

The programming language of Dynamics 365 F&SCM, used to write extensions.

·Checklists: a Dynamics 365 F&SCM 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 legal entity and buyer: CMT, full package, mill, brand or agent.
• One decision owner named for each area, and one owner for shared product data across the group.
• One workshop per department, walking a real recent order.
• All 52 fit-gap lines answered with evidence, decision and owner, plus process lines for any mill or dye house.
• F&SCM or Business Central decided on process type and entity complexity.
• Architecture decided: what F&SCM owns, what runs in an operations layer.

Design

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

• Configuration technology and product dimension groups per category; size groups per scale.
• Tracking and storage dimension groups for every material; batch attributes and disposition codes.
• Unit design per fabric and yarn; whether per-batch conversion is built; catch weight ruled in or out.
• BOM versions per variant, or consumption kept outside.
• Routes, resources and what stays in planning outside F&SCM.
• Formulas and batch orders for any process entity; co-product costing agreed.
• Subcontracting model per outside process.
• Quality associations, acceptance sampling charts and override rights.
• Carton rules and buyer documents per buyer.
• Currencies, prepayments, letters of credit, chargeback reasons, intercompany, 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, in a sandbox on the go-live version.
• Extensions and ISVs listed with owners and an update-testing plan.
• Integrations on registered Entra apps with throttling priorities, linked on legal entity plus key, one writer per field.
• Data packages rehearsed, with a cut-off rule and signed totals.
• All 13 end-to-end scenarios passed by key users.

Go-live

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

• Training done per role, on the group's own orders.
• Cut-over rehearsed once in full.
• Go-live date between seasons, away from year-end, audits and service updates.
• Go or no-go point and fall-back defined, per legal entity.
• Hypercare runs at least until the first month-end close in F&SCM.

·Sources

Microsoft Learn pages were checked on 26 September 2026. Dynamics 365 Supply Chain Management feature versions are named where Microsoft states them.

1. Product dimensions — learn.microsoft.com
2. Product information overview (product masters, configuration technologies, released products) — learn.microsoft.com
3. Create a product master — learn.microsoft.com
4. Manage units of measure — learn.microsoft.com
5. Unit of measure conversion per product variant — learn.microsoft.com
6. Catch weight product processing with warehouse management — learn.microsoft.com
7. Batch attributes — learn.microsoft.com
8. Batch disposition codes — learn.microsoft.com
9. Inventory dimension groups (changing groups with transactions) — learn.microsoft.com · warehouse management upgrade — learn.microsoft.com
10. Bills of materials and formulas (BOM versions per variant) — learn.microsoft.com
11. Dimension-based product configuration — learn.microsoft.com
12. Production process overview (production orders, batch orders, kanbans) — learn.microsoft.com
13. Formulas and formula versions — learn.microsoft.com
14. Production floor execution interface — learn.microsoft.com
15. Manage subcontracting work in production — learn.microsoft.com · activity-based subcontracting — learn.microsoft.com
16. Costing versions — learn.microsoft.com · costing sheets — learn.microsoft.com
17. Landed cost module overview — learn.microsoft.com
18. Acceptance sampling — learn.microsoft.com
19. Advanced quality management overview — learn.microsoft.com · quality associations — learn.microsoft.com
20. Over-delivery and under-delivery percentages at shipment — learn.microsoft.com
21. Export letter of credit — learn.microsoft.com · letters of credit and import collections — learn.microsoft.com
22. Customer prepayment invoices — learn.microsoft.com · customer prepayments — learn.microsoft.com
23. Deduction workbench — learn.microsoft.com
24. Free text invoices — learn.microsoft.com · sales commission rules — learn.microsoft.com
25. Vendor collaboration with external vendors — learn.microsoft.com
26. Intercompany trade set-up — learn.microsoft.com · intercompany planning — learn.microsoft.com
27. Electronic invoicing coverage — learn.microsoft.com · Egypt — learn.microsoft.com
28. Customise through extension and overlayering — learn.microsoft.com
29. Unified admin experience for finance and operations apps — learn.microsoft.com · unified developer experience — learn.microsoft.com
30. Data management overview — learn.microsoft.com · package REST API — learn.microsoft.com · recurring integrations — learn.microsoft.com
31. Open Data Protocol (OData) — learn.microsoft.com
32. Data events — learn.microsoft.com · business event endpoints — learn.microsoft.com
33. Dual-write overview — learn.microsoft.com · virtual entities — learn.microsoft.com
34. Service protection API limits — learn.microsoft.com · throttling prioritization — learn.microsoft.com
35. Business Central item variants — learn.microsoft.com · Business Central subcontracting (2026 release wave 1) — learn.microsoft.com · Business Central API webhooks — learn.microsoft.com
36. PORINI 365 ERP for fashion, luxury and textile, listed on Microsoft AppSource — appsource.microsoft.com
37. ISO 2859-1, Sampling procedures for inspection by attributes — iso.org
38. AQL tables and acceptance numbers — qima.com · inspection levels: qualityinspection.org
39. UCP 600, documentary credits — uscib.org · tradefinanceglobal.com
40. EDI transaction sets — 1edisource.com · celigo.com

Corrections. Dynamics 365 changes with every service update, and a menu path, a feature flag or a limit can move in a single release. 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 Dynamics 365 facts in this chapter at least once a year and after major Microsoft releases. Related chapters: Dynamics 365 Business Central · SAP S/4HANA Fashion · NetSuite · the method behind this guide · full glossary.

Microsoft, Dynamics 365, Dataverse, Power Platform, Power Automate and Microsoft Entra are trademarks of the Microsoft group of companies, used here only to name the products. This guide is not endorsed by Microsoft. PORINI is a trademark of its owner. Garment.io is named because MerchandiserOS integrates with it; this guide is not endorsed by Garment.io.