How to Implement Infor CloudSuite Fashion for Garment & Apparel Business (2026 Guide)

1Who Infor CloudSuite Fashion fits

Infor CloudSuite Fashion fits large and upper mid-market apparel, footwear, accessories and home-textile companies that want an industry suite with native style, colour and size handling and are ready for a partner-led, multi-module project. Infor describes it as a SaaS suite for "apparel, footwear, accessories, and home/textile companies", and its fashion documentation describes an industry process catalogue targeted at cut and sew manufacturers.

Infor CloudSuite Fashion is Infor's fashion industry suite, built on the Infor M3 ERP (the documentation for the suite sits under Infor's M3 documentation). Infor's fashion page lists the parts of the suite: a fashion and apparel ERP, Fashion PLM, configure-price-quote (CPQ), fashion demand forecasting, the Infor Nexus supply chain network, a warehouse management system, sustainability and compliance, e-commerce (Infor Rhythm for Commerce) and the cloud technology platform.

Signs Infor CloudSuite Fashion is a good choice

Infor tends to fit when the business is large enough to use the suite and has the people to run a long project.

• The company runs several sites, brands or channels and wants one fashion-aware ERP across them.
• Style counts per season are in the hundreds or thousands, and the size and colour matrix is a daily tool.
• The company also wants PLM, a supplier network (Infor Nexus) or a WMS from the same vendor.
• A partner with M3 fashion experience is available, and the company can release key users for months.

Signs to slow down

Slow down when the size of the suite is larger than the problem.

• The factory is a single-site CMT unit with a few hundred operators. The suite is heavy for that, in our judgement; a smaller ERP plus an operations layer often fits better (see the Odoo chapter or apparel-specific ERPs).
• The main pain is sampling, T&A and the floor, not the ledger or the supply chain.
• Nobody has checked which suite modules are in the contract, and the plan assumes all of 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. Infor has gone further than most general ERPs by adding a fashion layer to M3, with styles, SKUs, a matrix and style-level structures, yet the development, approval and floor work still sits before or beside the transactions M3 records. The same wall applies to brands and buying agents: their development, sampling and follow-up across many factories happen before any purchase order exists.

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. 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 33 shows it in full.

3The recommended architecture, in short

Agree before discovery which system owns which part of the business. Our recommendation: Infor keeps the books, and an operations system built for apparel runs the work from the style to the shipment. With CloudSuite Fashion, this also means deciding which suite modules you actually need, because the suite offers some of the same ground.

MerchandiserOS is built for the operations side: style and tech pack, quotations and costing, buyer orders, procurement, planning, production, the shop floor (on its own floor screens or through its Garment.io integration), quality and logistics. Infor keeps accounts, payables and receivables, invoicing, payments, stock value, tax and e-invoicing. The rest of this chapter still explains how to configure M3 for garment production, because some companies choose that, and a consultant needs to know what each choice costs. Section 32 shows the split in full.

4Business types, and what each needs from Infor

The business type decides who owns the material, what is invoiced and which parts of the Infor suite carry weight. Settle it in the first discovery meeting, because many companies run two types at once.

5Who should be on an Infor fashion project team?

An Infor fashion project needs one decision owner for every design question, and most of those owners sit in merchandising, production, stores, quality and finance, not in IT. The partner configures; the business decides how styles, units, lots, costs and inspections work.

Keep a decision log with the date, the owner, the option chosen and the options rejected. With a suite this size, the log is the only place where a decision made in month two can still be found in month nine.

6What should discovery workshops cover for an Infor fashion project?

Run one workshop per department, each walking a real, recent order from start to finish, and map every finding to a fit-gap line. Use the company's own orders, not Infor's demo data. The methodology page lists the full question sets (ERP-agnostic method); the questions below are the ones that matter most on M3.

Merchandising and product

• Which axes does each product family use: colour and size only, or also fit, inseam or cup? This decides the X, Y and Z feature groups.
• How are seasons named, and does a carry-over style keep its number?
• How do buyers order: by matrix, by ratio pack, by delivery drop?
• Where do tech packs, approvals and the T&A calendar live today, and will Fashion PLM or an operations layer own them?

Stores and purchasing

• Which materials are bought in kg and used in metres? What is measured per roll at receipt?
• Which attributes must travel with a lot: shade group, GSM, width, shrinkage, country of origin?
• Which import charges (freight, clearing, bank charges, duty) must reach the material cost?

Production, quality and finance

• At what level is production controlled: style, style-colour, SKU, delivery or cut?
• Which processes go outside, and how are pieces counted out and back?
• Which inspections run, and which buyers set their own AQL?
• Which currencies, prepayments, letters of credit and chargebacks does finance handle, and which e-invoicing rules apply?

7The apparel fit-gap checklist for Infor CloudSuite Fashion: 52 lines

A fit-gap checklist records, requirement by requirement, whether the ERP meets it as standard, with configuration, with custom work, or better outside the ERP. The 52 lines below are our assessment of Infor CloudSuite Fashion on M3 for a typical full-package garment factory, based on Infor's documentation where we found it. Lines marked "check" were not found in the documentation we reviewed; confirm them with Infor or your partner before you sign a scope.

Key: Standard documented as delivered · Configure settings or setup work · Custom build an extension or third-party tool · Operations layer better run in an apparel operations system and passed to Infor

Counted from this table, 9 of the 52 lines are standard, 25 need configuration, 9 need custom work and 9 are better run outside Infor. That count is our assessment for a typical full-package factory, not a survey. Compared with a general ERP, M3 scores better on the product lines (1, 11, 14, 23, 41) because of its fashion layer, and about the same on sampling, T&A, floor capture and AQL.

8Which Infor suite modules and which deployment should you choose?

Choose modules and deployment after the fit-gap: the suite lists ERP, PLM, CPQ, demand forecasting, Infor Nexus, WMS, sustainability, e-commerce and the cloud platform, and a garment manufacturer rarely needs all of them on day one. Infor sells CloudSuite Fashion as a cloud subscription; we do not quote prices because they depend on the contract.

Single-tenant or multi-tenant?

Infor's own pages describe both, so confirm which one your contract gives you. The fashion industry page says the suite is "available in a multi-tenant cloud", while the CloudSuite Fashion documentation overview describes delivery on AWS in a single-tenant, subscription model. The answer matters because it shapes what extensions, upgrades and integrations the partner may build (section 24).

Questions to settle before signing

• Which suite modules are in the subscription, and which are only on the product page?
• Single-tenant or multi-tenant, and what does that allow for extensions?
• Which M3 fashion features (matrix plug-ins, Planning Workbench, QMS) are licensed?
• Is ION API Gateway access included for the integrations the design needs?

9Infor CloudSuite Fashion vs SAP S/4HANA for fashion: which should a manufacturer choose?

Both are enterprise ERPs with a native fashion model and both suit large, multi-site businesses; the choice usually comes down to the partner, the existing landscape and which suite modules the business needs. SAP S/4HANA for fashion and vertical business models a style as a generic article with variants from characteristics and adds segmentation; Infor M3 models a style with SKUs on X, Y and Z feature groups and keeps structures at style level.

For the SAP side in detail, read the SAP S/4HANA Fashion chapter. Neither product covers sampling rounds, the T&A calendar, line-level floor capture or ISO 2859-1 AQL as standard, so both projects face the same decision about an operations layer. The comparison page sets all the ERPs in this guide side by side.

10How should item types and materials be set up in Infor M3 for apparel?

Set up M3 item types by how each material is bought, stocked, costed and tracked: fabric, yarn, trims, packaging, subcontract services and finished styles each get their own item type, because the type drives numbering, costing and which attributes apply. M3's style settings document item types (CRS040) and the "Settings - Create Items" program (CRS760) as part of style setup.

Put lot control on fabric and yarn, with the attributes the stores head listed in discovery. Most trims do not need lots. Buttons bought by the gross and issued by the piece convert through an alternate unit on the item (section 12).

With operations on top: the style, its bill of materials by category and its consumption are built in the operations layer. M3 still needs the item types and lot rules, because it holds stock value and payables.

11How does Infor M3 handle style, colour and size?

Infor M3 treats a style as the parent and each colour-size combination as an SKU, generated through the M3 Product Configurator on feature groups X, Y and Z. Infor's documentation defines a style as "a comprehensive term for a number of similar items" and an SKU as "the item(s) connected to a certain style".

The style and SKU setup documented by Infor uses these programs:

Infor's example SKU code is VHF013-18-40-CO: the style code followed by size, colour and material, separated by hyphens. For order entry, the M3 Fashion Matrix plug-ins show SKUs with the X and Y dimensions in a grid, let the user change the Z option, and show line, column and grand totals. The customer-order plug-in works with Customer Order. Open (OIS100), Open Line (OIS101) and the toolbox (OIS300); a customer order header must exist in OIS100 first. A matching plug-in exists for distribution orders.

A style/colour/size matrix is a grid with colours on one axis and sizes on the other, into which the quantity for each combination is entered.

With operations on top: styles, colourways and size breakdowns live in the operations layer, and M3 holds the SKUs that are actually ordered, stocked and invoiced.

12How do you convert kilograms to metres for fabric in Infor M3?

M3 converts between units with an alternate unit of measure and a conversion factor per item, set in Item. Connect Alternate U/M (MMS015), so kg-to-metre works as standard only as one fixed factor per fabric item. Knit fabric is bought by weight and cut by length, and the true factor depends on each roll's GSM and width.

GSM means grams per square metre: the weight of one square metre of fabric.

M3 also documents catch weight management, where a transaction carries an actual weight beside the quantity, with the alternate cost unit set in MMS015. Whether catch weight suits fabric rolls, holding metres as the quantity and the actual kilograms as the catch weight, is a design to test with your partner; we found no Infor document that describes it for fabric.

Three workable designs

13Can Infor M3 track fabric dye lots and shade?

Yes. M3 lets a collection of attributes be stored when a lot or balance ID is created in stock, and Infor's fashion documentation names shade among them, so each dye lot can be an M3 lot carrying its shade, GSM and width. A dye lot is a batch of fabric dyed together; fabric from two dye lots can differ in shade, so one garment must never mix them.

Attributes are created in Attribute. Open (ATS010) and assigned a category that controls their value type. An attribute kept at lot-master level holds one value per lot; an attribute kept at balance-ID level can differ within a lot. For dye lots, keep shade group at lot level and roll length or actual width at balance-ID level if rolls are tracked separately. M3 also documents viewing inventory by attribute and tracing lots.

A shade band is a set of approved shade references for one fabric colour, used to judge each new lot. M3 holds the result as an attribute; the judgement against the band happens at inspection.

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. M3 still holds the lot on receipts and issues.

14Can Infor M3 hold one bill of materials for a whole style?

Yes. Infor's fashion documentation says product structures (bill of materials and bill of operations) can be maintained from style level, with exceptions at style-colour or SKU level where needed. That suits apparel well: one structure for the polo, colour exceptions for thread and buttons, and SKU exceptions for fabric that grows with size.

Marker efficiency is the share of fabric in a cutting marker that ends up in garment pieces. Shrinkage is fabric lost in washing or finishing. Keep them apart in the source table, even if M3 receives one combined quantity per SKU.

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 M3.

15How do you model cutting, sewing and finishing in Infor M3, and where does line planning live?

Model cutting, sewing, finishing and packing as work centers with operations and times on the style's bill of operations; plan capacity with the M3 Planning and Scheduling Workbench if it is licensed. A work center is a place where operations run, with its own capacity and rate.

Infor documents two planning tools for fashion. The Planning Workbench works at facility level over a medium horizon (Infor's documentation says 3 to 4 months), showing capacity and loading across work centers and facilities, and lists moving orders to or from subcontractors among the planning decisions. The Scheduling Workbench is a decision-support tool for scheduling manufacturing orders against finite capacity and material flow. Neither is documented as operator-level line balancing or hourly output capture.

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.

16Where do sampling, approvals and the T&A calendar live in an Infor project?

We found no M3 object for sample rounds, buyer verdicts or a T&A calendar; the options are Infor Fashion PLM if it covers your process (check with Infor), an extension, or an operations layer. A PP (pre-production) sample is a garment in bulk fabric and trims that the buyer approves as the reference for production. A T&A (time and action) calendar lists an order's milestones with planned dates worked back from ex-factory, actual dates and owners.

Whatever holds sampling must record each round (sent date, courier, pieces, comments, verdict), link the approved round to the spec version it approved, and block the next step until the approval exists.

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 live in the operations layer.

17Does Infor M3 support subcontracting for CMT, embroidery or washing?

Yes, in M3 core: a subcontract order is a purchase order for an operation done by a subcontractor, either tied to a manufacturing order or run without one. Infor's documentation says a subcontract operation runs on a work center with resource type 2, and creating the manufacturing order creates a planned purchase order for the operation in Planned Purchase Order. Open (PPS170). How CloudSuite Fashion configures this for multi-step garment chains was not documented in what we reviewed; demo it.

The "without manufacturing order" variant is documented for companies without in-house production that manage operation chains with material bought directly or sent from their own stock, which also suits a brand sending fabric to a CMT unit.

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. M3 receives the subcontract purchase order and the payable.

18How does Infor M3 handle garment costing and landed cost on imported fabric?

M3 costs purchased items with a costing model built from costing elements, and lets charges such as freight be added to a purchase order and matched against supplier or third-party invoices in Supplier Invoice Match GR Line (APS360). Whether and how those charges flow into each fabric item's stock value in your setup is a question to confirm with the partner. The garment costing sheet used to quote a buyer comes before any SKU exists, so it usually lives outside M3.

A landed cost is every cost of bringing goods to the factory beyond the supplier's price: freight, insurance, duty, clearing and bank charges. In M3, each charge is a costing element; for each element that represents a charge, up to five object types (for example warehouse, delivery method and country) can select a different rate.

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. M3 holds the charges that actually hit the purchase orders.

19Does Infor M3 support AQL inspection for garments?

M3's Quality Management System (QMS) creates quality inspection (QI) requests per item and lot, with tests and specifications (QMS200), for received purchased goods, manufacturing and returns; we did not find ISO 2859-1 sampling tables in its documentation, so AQL sample sizes and acceptance numbers need an extension or a separate system. AQL (acceptance quality limit) inspection checks a random sample from a lot and accepts or rejects the lot on the number of defects found.

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 run in the operations layer. M3 sees the delivery once it is cleared.

20How do you handle cartons and shipping documents with Infor?

Packing and dispatch run in M3 (and in the suite WMS if licensed), while buyer-specific carton rules, labels and packing-list layouts usually need design per buyer. Infor documents creating packing instructions and making them available to suppliers, which helps a brand; confirm the factory-side carton flow in a demo.

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

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

Multi-currency is expected of an enterprise ERP like M3, but we did not verify the fashion suite's handling of prepayments, letters of credit or chargeback reason codes in Infor's documentation; confirm each with the partner and test it with the scenarios in section 27. A letter of credit is a bank's promise to pay the exporter when documents matching its terms are presented; under ICC's UCP 600, documents are presented within 21 calendar days after shipment unless the credit says otherwise.

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

22Does Infor CloudSuite Fashion support e-invoicing in garment-exporting countries?

We did not verify Infor's localisation coverage for garment-exporting countries in this guide, so check your country with Infor and the partner before signing. Egypt, Turkey, Pakistan, Bangladesh, India, Vietnam and Morocco each have their own e-invoicing, VAT and export rules, and free-zone or temporary-admission factories often report material import and re-export to customs in a local format. Test a real e-invoice end to end in the test tenant before go-live.

23In what order should Infor M3 be configured for a garment business?

Configure from the ledger outward: company, currencies and accounts; then units, item types, features and options; then attributes and lot rules; then costing and purchase charges; then work centers, subcontracting and quality; and only then styles and SKUs. The program codes below are those named in Infor's documentation; confirm each on your tenant.

24Which extensions does an Infor apparel implementation usually need?

An apparel M3 project that keeps operations inside Infor usually needs extensions for per-lot fabric conversion, cut control, AQL, quantity tolerance, letters of credit and buyer documents; the extension tools allowed depend on your tenant, so agree them with Infor and the partner first. Infor's own Fashion Matrix plug-in documentation uses a personalisation script on OIS300, which shows that personalisation is one route; what else a single-tenant or multi-tenant subscription allows is a question to settle before design.

Every extension must survive Infor's cloud upgrades, so keep the list short.

25Which systems does an Infor apparel implementation integrate with?

An Infor apparel project typically connects to PLM, a shop-floor system, EDI with retailers, banks and an operations layer, most often through Infor ION and the ION API Gateway. Each connection needs one writer per field, links stored on permanent keys, and receivers that are safe to call twice.

Where the disagreement is between two systems, show it to a person on a review list. Never overwrite silently.

26How do you migrate apparel data into Infor M3?

Migrate only open and active data (active styles and SKUs, open orders, open purchase orders, stock by lot with attributes) in dependency order, and have each department head sign the loaded totals. Loads usually run through M3 API programs or the load tools your partner uses; confirm which tools your subscription includes.

Map old size labels to M3 options one scale at a time, merge duplicate materials, and give every roll in stock its lot and shade before the count. A cut-off rule states the exact moment after which every transaction is entered in Infor.

27How should you test an Infor apparel implementation end to end?

Test with end-to-end scenarios that follow one real order from the buyer's PO to cash, run by key users on migrated data, each step with an expected result written before the test starts.

Test script: short shipment within tolerance

Scenario T6: the buyer allows ±3% and the factory ships 2,940 pieces, 60 short (2.0%).

28How should training, cut-over and hypercare run on an Infor go-live?

Train each role only on the programs and scenarios it will use, rehearse the cut-over once in full, go live between seasons, and keep the partner in close support until the first month-end close in Infor is done. Hypercare is the period after go-live when the project team fixes issues daily.

• Cut-over. Freeze master data a week ahead, stop receipts in the old system at a set time, count fabric by lot and roll, load, and let the sponsor decide go or no-go on signed totals.
• Timing. Avoid shipment peaks, financial year-end and audits.
• Hypercare. Practitioners commonly plan four to eight weeks; that range is judgement, not a standard. Nobody leaves before the first month-end close is done.

29What are the most common mistakes when implementing Infor for apparel?

The most common mistakes are buying more suite than the business can absorb, fixing feature groups too late, relying on the style-level structure without SKU exceptions for fabric, one conversion factor per fabric, and two masters for the style (PLM and an operations tool). The list comes from implementation practice and from the general failure modes in the methodology.

1. Suite bought, not scoped.Modules on the order form with no owner and no fit-gap line.
2. Feature groups changed after go-live.Adding fit or inseam later means new SKUs for every affected style.
3. Style-level fabric only.No SKU exceptions, so large sizes run short (Example 9).
4. One conversion factor per fabric.Stock value looks right while the cutting room runs short (Example 7).
5. Shade as an optional attribute.Lots received without shade cannot be controlled at cutting.
6. Two style masters.Fashion PLM and an operations layer both editing the spec.
7. Planning Workbench mistaken for line balancing.Medium-horizon facility planning is not hourly floor control.
8. Tenancy assumed.Extensions designed for single-tenant freedoms on a multi-tenant subscription, or the reverse.
9. Linking on editable text.Integrations that match on descriptions or buyer references break when someone edits them.

The general failure modes, mapped to Infor

30What must be decided before an Infor apparel go-live?

Decide the suite modules, the tenancy, the feature groups per product family, the lot attributes, the fabric unit design, the costing elements, and which system owns style, sampling, T&A, floor capture and AQL, because each is expensive to change once transactions exist.

• Which suite modules are licensed and who owns each.
• Single-tenant or multi-tenant, and the extension tools that allow.
• Feature groups X, Y, Z per product family, and SKU numbering.
• Lot and balance-ID attributes, and which are mandatory at receipt.
• The fabric unit design and how kg converts to metres.
• Costing elements for import charges and how they reach stock value.
• Where style and tech pack live: Fashion PLM or the operations layer.
• Where sampling, T&A, floor capture and AQL live.
• How buyer-supplied fabric stays out of stock value.
• The quantity tolerance rule and who may approve outside it.
• Which ION API Gateway access the integrations need.

31How do you integrate with Infor CloudSuite Fashion through the ION API Gateway?

Integrate through the Infor ION API Gateway, which authenticates callers with OAuth 2.0 and forwards REST requests to M3's API programs; a backend service logs in with a service account under the resource owner grant, using the client ID and secret Infor issues in an .ionapi file. Infor describes the gateway as a reverse proxy that accepts HTTP requests and passes them to the target application.

The Infor documentation we checked does not list the client-credentials grant; confirm with Infor which grants your tenant offers. Infor publishes sample code in the ion-api-sdk repository on GitHub.

• API programs. M3 exposes MI programs such as PPS200MI, Infor's purchase order information interface for headers, lines, transactions, addresses and texts. Community material shows the REST path as m3api-rest/execute/<program>/<transaction>; take the exact path from your tenant's ION API catalogue.
• Identifiers. Store M3's own keys (company plus order or item number), never a description or a buyer reference a user can edit. Check that purchase order numbers come from an M3 number series and are never typed by hand.
• Push and pull. ION also moves business documents between applications. Which events your tenant can publish to an outside system is not something we verified; polling for changes stays the dependable baseline, so make the receiving side safe to call twice.
• Limits. We found no published rate limit for the gateway; ask Infor for the limits on your tenant and batch loads accordingly.

POST /api/v1/erp/po-status
Idempotency-Key: m3-100-4000457-released

{"rows": [{"request_ref": "PR-1042",
           "erp_po_id": "100/4000457",
           "erp_po_number": "4000457",
           "status": "released",
           "date": "2026-10-21"}]}

32Is Infor CloudSuite Fashion good for a clothing brand, a buying agent or an own-label retailer?

Infor CloudSuite Fashion fits large clothing brands and own-label retailers well on the commercial side, because the suite pairs the M3 ERP with Fashion PLM, the Infor Nexus supply chain network, a WMS, demand forecasting and e-commerce; a buying agent needs far less of it. What none of them get as standard is the daily follow-up of development, samples, T&A and inspections across many outside factories.

Who they are

• A brand or wholesaler designs and sells, while factories make for it on FOB or CMT terms.
• A buying agent or buying house sources for buyers on commission and holds no stock.
• An own-label retailer develops its own label and buys it from factories, usually as private label sourcing.

What they need from Infor, and what to skip

As an ERP for fashion brands, Infor should carry the money and the goods flow, not the factory floor.

Skip the manufacturing modules: work centers, manufacturing orders, the Planning and Scheduling Workbench and shop-floor extensions. A brand that runs no factory does not need them, and a buying agent needs little beyond accounts and commission invoicing. As buying house ERP or sourcing agent software, the full suite is heavy, in our judgement.

What Infor handles poorly for them

• Development and sampling with many factories, round by round, with the buyer's verdicts.
• T&A across factories, with one critical path per order.
• Following production that happens outside, in factories that do not run the brand's ERP.
• Inspections at the vendor, with AQL at the buyer's level.
• One status per order across many factories and many buyers.

The MerchandiserOS model for brands and agents

MerchandiserOS runs development, samples and approvals, the T&A, the orders placed with factories, sourcing, the planning view across subcontracted factories, quality inspections and shipping follow-up. Infor keeps the books. Its workspace set-ups include "Brand" and "Buying agent". Retail back-office work (stores, POS, allocation, open-to-buy) is outside MerchandiserOS's scope; for that, a brand or retailer uses Infor's retail and e-commerce modules or another retail system.

For a lighter ERP around the same model, see the NetSuite chapter or apparel-specific ERPs.

·Glossary of apparel and Infor terms

Short definitions of the terms used in this chapter. The full list is on the guide glossary.

AQL

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

Balance ID

In M3, an identity for stock at a location, which can carry its own attributes within a lot.

CMT

Cut, make and trim: a factory model where the buyer supplies fabric and the factory charges for making.

Costing element

In M3, one component of cost, such as freight or a discount, combined into a costing model.

Dye lot

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

Feature group

In M3, one axis (X, Y or Z) of the fashion matrix, such as colour, size or fit.

FOB

Free on board: the price of goods loaded at the port of shipment, the usual garment quote.

GSM

Grams per square metre: the weight of fabric.

Infor Nexus

Infor's supply chain network for trading partners, listed as part of CloudSuite Fashion.

ION API Gateway

Infor's gateway that authenticates API callers with OAuth 2.0 and forwards requests to Infor applications.

.ionapi file

The credentials file Infor issues when an application is registered in the ION API Gateway.

Landed cost

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

MI program

An M3 API program, such as PPS200MI for purchase order information.

PP sample

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

QI request

Quality inspection request: M3's record of the tests on an item and lot.

SKU

In M3, the item connected to a style for one combination of options, such as navy, size L.

Style

In M3, a comprehensive term for a number of similar items, the parent of its SKUs.

Style/colour/size matrix

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

T&A calendar

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

·Checklists: an Infor apparel implementation on one page

Discovery

• Business type settled per buyer: CMT, full package, brand, agent or own label.
• One owner per decision; one workshop per department on a real order.
• All 52 fit-gap lines answered with evidence, decision and owner.
• Suite modules, tenancy and ION API access confirmed.

Design

• Feature groups X, Y, Z per product family; SKU numbering agreed.
• Lot attributes (shade, GSM, width) mandatory at receipt.
• Fabric unit design; SKU-level fabric exceptions generated from CAD.
• Costing elements for import charges; subcontract operations per processor.
• Where sampling, T&A, floor capture and AQL live.

Build, data, testing and go-live

• Configuration in dependency order; extensions listed with owners.
• Integrations link on M3 keys, one writer per field.
• Migration loaded in order with signed totals.
• All 13 scenarios passed by key users; cut-over rehearsed.
• Go-live between seasons; hypercare to the first month-end close.

·Sources

Infor pages were checked on 26 September 2026. M3 program codes are taken from Infor's M3 documentation (docs.infor.com); confirm them on your tenant's version.

1. Infor, Fashion industry page (suite components, target segments, multi-tenant cloud) · infor.com
2. Infor CloudSuite Fashion documentation, overview (single-tenant, AWS, subscription) · docs.infor.com
3. Infor CloudSuite Fashion, M3 Product Data Management (style-level structures, lot attributes incl. shade) · docs.infor.com
4. Infor M3 Fashion, Industry Process Catalog (cut and sew manufacturers) · docs.infor.com
5. Infor M3, Settings for Style and Stock Keeping Unit (CRS582, PDS055, PDS050, PDS056, CRS040, MMS024, CRS759, CRS760, CRS912) · docs.infor.com
6. Infor M3, Fashion Matrix plug-ins for customer order · docs.infor.com · for distribution order · docs.infor.com
7. Infor M3, Define Alternate Unit of Measure (MMS015) · docs.infor.com · Catch weight settings · docs.infor.com
8. Infor M3, Attribute control and attributes (ATS010) · docs.infor.com · View inventory by attribute · docs.infor.com
9. Infor M3, Subcontract order and subcontract operation (resource type 2, PPS170) · docs.infor.com · docs.infor.com
10. Infor M3 Planning Workbench for fashion · docs.infor.com · Planning and Scheduling Workbench for Fashion · docs.infor.com
11. Infor M3, Costing purchased items and the costing model (costing elements, charges, APS360) · docs.infor.com · docs.infor.com
12. Infor M3, Quality Management System (QI requests, QMS200) · docs.infor.com · docs.infor.com
13. Infor M3, Purchase order settings (PPS096) and PPS200MI · docs.infor.com · docs.infor.com
14. Infor M3, Create packing instruction and make available for supplier · docs.infor.com
15. Infor OS 2024.x, ION API Gateway: choosing a grant type · docs.infor.com
16. Infor Developer Portal, API interface for M3 · developer.infor.com · ION API SDK · github.com
17. Community material on the m3api-rest path (not Infor documentation) · m3ideas.org
18. ISO 2859-1, sampling procedures for inspection by attributes · iso.org · AQL tables · qima.com
19. UCP 600, documentary credits · tradefinanceglobal.com

Corrections. Infor updates its cloud suite several times a year, and program names, suite composition and deployment options can change. If a statement here contradicts your tenant, report a correction with the version and the page you checked; we correct the chapter and note the change and its date here. We re-check the Infor facts in this chapter at least once a year.

Infor, Infor CloudSuite, Infor M3, Infor ION, Infor Nexus and Infor Ming.le are trademarks of Infor, used here only to name the products. This guide is not endorsed by Infor. SAP and S/4HANA are trademarks of SAP SE. Garment.io is named because MerchandiserOS integrates with it; this guide is not endorsed by Garment.io.