How to Implement Sage X3 for Garment & Apparel Business (2026 Guide)

1Which Sage product fits an apparel business?

For a garment manufacturer, Sage X3 is the Sage product to consider: it is Sage's mid-market ERP with multi-level BOMs, work orders, routings, subcontracting, lot and sub-lot management and quality statuses as standard. Sage 300 is a finance and distribution system, used in apparel with a third-party style, colour and size add-on; Sage 200 is a finance and stock system for which we found no verifiable apparel add-on.

No Sage product has a style/colour/size matrix as standard. In Sage X3 the matrix comes from partners: Greytrix describes colour and size matrix entry for stock, sales and purchasing, and "Sage X3 Wear" is a partner-delivered fashion vertical for purchasing groups, clothing stores and chains. For Sage 300, Acute Data sells Sage 300 Apparel with a style, colour and size grid. That makes the partner the most important choice in any Sage apparel project.

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 Sage weakness; SAP, NetSuite, Dynamics 365 and Odoo meet the same wall. In Sage X3 it shows first as the missing colour-size matrix, which is why the fashion capability of a Sage project is only as good as its partner. The same wall applies to brands and buying agents, whose sampling, T&A and inspections happen at factories the ERP never sees.

3The recommended architecture, in short

Agree before discovery which system owns which part of the business. Our recommendation is that Sage keeps the books and an apparel operations system runs everything from the style to the shipment.

The split has a particular benefit in Sage: it takes the colour-size matrix off the critical path. If the matrix lives in the operations layer, Sage needs only the SKUs that are sold and invoiced, and the project depends far less on a fashion add-on surviving each Sage upgrade.

4Business types, and what each needs from Sage

The business type decides who owns the material, what is invoiced and which Sage modules carry weight. Settle it in the first meeting, because one company often runs two types.

5Who should be on a Sage apparel project, and what should discovery cover?

A Sage apparel project needs one decision owner per design question, and in Sage one extra owner: someone accountable for the fashion add-on, its licence, its code and its upgrade path. The merchandising head decides products and the matrix, the stores head units, lots and statuses, the CAD lead consumption, the IE manager minutes, the quality manager inspections, the finance head costing, currencies and legislation.

Run one workshop per department on a real recent order. The questions that matter most for Sage:

• Merchandising. How are sizes and colours entered today; how many SKUs per season; do buyers order ratio packs; what tolerance per order?
• Development. Which sample types does each buyer require; where do tech packs and revisions live?
• Stores. Which unit is each material bought, stocked and issued in; what is measured at receipt; which lots are put on hold, and who releases them?
• Production. Work orders per size or per style-colour; which processes go outside and how pieces are counted out and back?
• Quality. Which inspections run; which buyers set their own AQL; who may release a rejected lot?
• Finance. Currencies; LC, prepayment or open account; chargebacks; import costing; free-zone reports; which X3 legislation applies?
• The add-on. Which partner, which Sage versions it supports today, and how quickly it followed the last two releases?

6The apparel fit-gap checklist for Sage X3: 52 lines

A fit-gap checklist records, line by line, whether Sage X3 meets an apparel requirement as standard, with configuration, with custom code or a partner add-on, or better outside it. The answers are our assessment of Sage X3 2025 R2 and 2026 R1 without a fashion add-on, for a typical full-package garment factory. A partner add-on moves several "Custom build" lines to "Standard" for as long as the add-on is maintained; confirm each line in a demo.

Key: Standard works as delivered · Configure parameters, user fields or set-up · Custom build specific development or a partner add-on · Operations layer better run in an apparel operations system and passed to Sage

Counted from this table, 6 of the 52 lines are standard, 23 need configuration, 14 need custom code or a partner add-on and 9 are better run outside Sage X3. That is our assessment for a full-package factory, not a survey. The standard lines cluster in production and stores; the custom lines cluster in the matrix, which is why a partner add-on changes the picture more in Sage than in most ERPs.

7Product, partner, licensing and hosting: what should a Sage apparel project decide first?

Decide the partner and the fashion add-on first, then the product and hosting, because in Sage the apparel capability travels with the partner. Sage X3 is sold and implemented through partners; prices are quoted by Sage or the partner, and we do not repeat them here.

Sage X3 ships releases named by year: 2025 R2 is version 12.0.38 and 2026 R1 is version 12.0.39, and Sage has stated that with 2026 R1 the 2024 R1 release left support. A partner add-on has to follow those releases. Ask for evidence that it did.

8Sage X3 vs Acumatica for apparel

Sage X3 has deeper standard stores and production features for a manufacturer (lots and sub-lots, A/Q/R status, subcontract orders), while Acumatica has the colour-size matrix and grid entry in its core and licenses by resources rather than users. Both leave sampling, T&A, cut plans and AQL outside. See the Acumatica chapter for its side.

From practice: a manufacturer that values stores and quality control and has a strong X3 partner leans to Sage X3; a business that needs the matrix in core and many light users leans to Acumatica. The comparison page covers the other systems.

9How should product categories and materials be set up in Sage X3 for apparel?

Set up Sage X3 product categories by how each material is bought, stocked, costed and tracked (knit fabric, woven fabric, yarn, trims, packaging, subcontracted services, finished garments), because the category supplies the defaults for units, lot management, stock management rules and costing that every product in it inherits.

Sage's help notes that a product's lot management mode can only be changed while the product has no stock. Decide it before the first receipt.

10How does Sage X3 handle style, colour and size?

Standard Sage X3 has no colour-size matrix: each colour-size combination is its own product record, and a style exists only as a naming pattern or a statistical group. Colour and size grids for stock, sales and purchasing come from partner add-ons, such as those Greytrix describes and the Sage X3 Wear vertical, which a partner article describes as adding season, family and brand statistics and size and colour handling for purchasing groups, stores and chains.

That leaves three designs, and the choice decides how much of the project depends on the partner.

With operations on top: styles, colourways and size breakdowns live in the operations layer, and X3 needs only the products that are sold and invoiced.

11How do you convert kilograms to metres for fabric in Sage X3?

Sage X3 gives each product a stock unit and lets purchase, sales and packing units convert to it by a coefficient held on the product; that coefficient is fixed per product, while knit fabric's metres per kilogram changes with each roll. Sage's help states that purchase and sales units can only be used on receipts into stock if they are also defined as packing units for the product.

12How do you track dye lots, rolls and quarantine in Sage X3?

Use Sage X3's "lot and sub-lot" management mode: the lot is the dye lot, the sub-lot is the roll, and every fabric receipt enters stock in status Q until quality releases it to A. A dye lot is a batch of fabric dyed together; a garment must never mix two.

• Lots and sub-lots. In "lot and sub-lot" mode the sub-lot divides the lot; sub-lot numbers are free (five characters by default, starting at 00001 on receipt) and each is a separate stock line. Stock inquiries show quantity by lot, sub-lot, location, warehouse and status.
• Lot characteristics. X3 has a lot characteristics change function and lot user fields; check which fields your version offers for GSM, width and shade group.
• Status A, Q, R. Stock is accepted (A), in quality control (Q) or rejected (R). Putting a lot in status Q creates an analysis request with a planned end date from the quality control lead time.
• A trap. X3's renumbering and mixing function can move part of a lot into another lot. For dye lots, restrict who may use it; mixing two shades in the system is the first step to mixing them on the cutting table.

13How do you handle size-dependent fabric consumption in Sage X3 BOMs?

A Sage X3 bill of materials belongs to a product, and each colour-size is its own product, so each size has its own BOM and size-graded consumption falls out as a different fabric quantity per BOM. Generate the BOMs by import from a consumption table. X3 supports multi-level BOMs and multi-level planning, so a sub-assembly such as an embroidered front can have its own BOM.

With operations on top: the consumption engine (marker efficiency, shrinkage, woven construction) and net-to-buy across the order book run in the operations layer, which sends the purchase quantity to X3.

14How do you model cutting, sewing and finishing in Sage X3?

Model cutting, sewing and finishing as work centres and list the garment's operations on a routing with their minutes; work orders then carry planned labour and collect actuals through production tracking, which Sage also documents as a mobile flow. The routing costs the garment; it does not balance a sewing line.

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.

15Where do sampling, approvals and the T&A calendar live in a Sage project?

Sage X3 has no object for garment samples, buyer approvals or a T&A calendar, so the project builds them, borrows another record type, or keeps them in an operations system. 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 worked back from ex-factory. For the polo, lab dips approved on 17 October release bulk dyeing, the PP sample approved on 14 November releases cutting on 17 November, and the final AQL on 12 December releases the 15 December ex-factory. Only the receipt and the delivery are X3 transactions.

16How does Sage X3 subcontracting work for embroidery, printing, washing and CMT?

Sage X3 subcontracts in two documented ways: a routing operation on a subcontract work centre, which is automatically subcontracted and scheduled on the subcontracted product's lead time, and subcontract orders, which plan and order the service and the materials the subcontractor needs from a BOM. This covers embroidery, printing and washing steps, and a CMT unit sewing cut panels, as standard; a chain of processors needs an operation or product per step.

CMT (cut, make, trim) describes a factory that sews from supplied fabric and charges for labour; in subcontracting it also means sending cut panels to another unit to be sewn.

17How do you cost a garment in Sage X3, and how do landed costs work?

Sage X3 costs work orders against standard and collects landed costs on purchases in two ways: a landed cost coefficient or fixed cost per unit on the product (global costs), or a cost structure that details each charge at the time of purchase. A cost structure can be defined at product category, product or product-site level, and the landed cost amount appears on its own line in the stock journal.

18Can Sage X3 run quality control and AQL inspection for garments?

Sage X3 has quality control as standard: stock statuses A, Q and R, analysis requests when stock goes into Q, and a status change function to put suspect stock on hold. We did not find ISO 2859-1 sampling plans documented, so final AQL at the buyer's level needs a check with your partner, custom work or another system. AQL (acceptance quality limit) inspection checks a random sample and accepts or rejects the lot on the defects found.

19How do you handle cartons and shipping documents in Sage X3?

X3 packing units handle cartons as a unit of a product; assorted and ratio cartons, buyer carton labels, SSCC numbers and pack-level packing lists need custom work, and we found no documented over- or under-shipment tolerance on the sales order.

20How does Sage X3 handle multi-currency, prepayments, letters of credit and chargebacks?

Sage X3 handles multi-currency and exchange differences as standard, and analytical dimensions let finance tag every document to an order; customer prepayments exist, but check how they attach to sales orders in your version and legislation. There is no letter-of-credit object, so LC terms and document checks need custom fields or a partner module. Under ICC's UCP 600, documents are presented within 21 days after shipment unless the credit says otherwise, and never after expiry.

21Does Sage X3 support e-invoicing and localisation in garment-exporting countries?

Sage X3 is organised by legislation (country packs), maintained by Sage for its core markets and by partners elsewhere; check your country. We have not verified coverage for Egypt, Bangladesh, Pakistan, India, Vietnam, Turkey or Morocco in this guide. Ask the partner which statutory reports and e-invoicing connections it has delivered, and test an e-invoice end to end before go-live. Free-zone and temporary-admission reports are usually custom.

22In what order should you configure Sage X3 for a garment factory?

Configure X3 from the ledger outward: company, sites, legislation and currencies; then units and stock statuses; then product categories with lot modes and stock management rules; then cost structures; then work centres and routings; then products and BOMs. The function names below appear in Sage X3's version 12 online help; menu locations differ by set-up, so we do not give paths.

23How do partners and customisation work in a Sage X3 apparel project?

Sage X3 apparel projects rely on two kinds of extension: partner verticals such as a colour-size matrix or Sage X3 Wear, and specific development by the implementing partner. Sage publishes developer documentation for X3 on its developer portal. Every extension must be carried through each release, and a partner vertical adds a second party whose release cycle you depend on.

24Which systems does a Sage apparel implementation integrate with?

A Sage apparel project connects a PLM or tech-pack system, a floor system, EDI, banks and an operations layer; each connection needs one writer per field and links on permanent keys. Link on the document's key, never on a free-text reference; keep one writer per field; show disagreements to a person instead of overwriting them; make every receiver safe to call twice.

25How do you migrate apparel data into Sage X3?

Migrate only open and active data (active products, open orders, open purchase orders, stock by lot and sub-lot) in dependency order using X3's import templates, and have each owner sign the loaded totals. Load categories before products, products before BOMs, and stock with its lot, sub-lot and status. Remember that a product's lot mode cannot change once it holds stock.

Product,Description,Category,StockUnit,StatGroup
P2041-NVY-S,Men's piqué polo navy S,FG,UN,P2041
P2041-NVY-M,Men's piqué polo navy M,FG,UN,P2041
P2041-NVY-L,Men's piqué polo navy L,FG,UN,P2041
P2041-NVY-XL,Men's piqué polo navy XL,FG,UN,P2041
P2041-NVY-XXL,Men's piqué polo navy XXL,FG,UN,P2041

Order,Customer,Product,Qty,Price
SO-P2041,BUYER01,P2041-NVY-S,300,4.26
SO-P2041,BUYER01,P2041-NVY-M,750,4.26
SO-P2041,BUYER01,P2041-NVY-L,900,4.26
SO-P2041,BUYER01,P2041-NVY-XL,750,4.26
SO-P2041,BUYER01,P2041-NVY-XXL,300,4.26

26How should you test a Sage X3 apparel implementation end to end?

Test with end-to-end scenarios that follow one real order from buyer PO to cash, run by key users on migrated data, with the add-on installed on the go-live release. The 13 scenarios are: T1 FOB order to payment; T2 CMT with buyer fabric; T3 prepack order; T4 shade split in cutting; T5 subcontract embroidery with loss; T6 short shipment within tolerance; T7 over-shipment; T8 seconds sale; T9 LC discrepancy; T10 chargeback; T11 mid-season spec revision; T12 cancelled order with committed materials; T13 FX at month-end.

Test script: short shipment within tolerance

Scenario T6: the buyer allows ±3% and the factory ships 2,940 pieces, 2.0% short. The expected invoice is 2,940 × 4.26 = USD 12,524.40 less the 3,834.00 prepayment, 8,690.40 due, with no open balance left on the order. Repeat with 2,900 pieces (3.3% short): delivery should need a named approval. Because we found no documented tolerance field in X3, step two needs the partner's add-on or custom work.

27How should a garment factory train, go live and run hypercare on Sage X3?

Train each role only on the functions it uses, on the factory's own products, and go live between seasons with a rehearsed cut-over; keep the partner close until the first month-end close. Stores and quality need extra time, because X3's lot, sub-lot and status rules are stricter than most factories' current habits.

• Cut-over. Freeze master data a week ahead; stop receipts in the old system at a set time; count fabric by lot and roll and load it with lot, sub-lot and status; sign totals; go or no-go at a fixed hour.
• Timing. Avoid shipment windows, year-end, audits and the weeks when the add-on partner is upgrading.
• Hypercare. Practitioners commonly plan four to eight weeks; that range is judgement. Nobody leaves before the first month-end close.

28What are the most common mistakes when implementing Sage for apparel?

The most common Sage apparel mistakes come from partner dependence: a fashion add-on that falls behind Sage releases, a matrix that only one partner can maintain, and a vertical built for retailers sold to a manufacturer. The list is from implementation practice and the partner-dependence pattern in the research behind this guide.

1. The add-on is a release behind.The whole system waits for the partner at every upgrade.
2. A retail vertical sold to a factory.Sage X3 Wear is described for purchasing groups, stores and chains; check its fit for manufacturing.
3. Sage 200 chosen for a factory.No verified apparel add-on, and production then lives in spreadsheets.
4. Coefficient conversion for knit fabric.Stock metres the cutting room cannot find.
5. Lot mode decided after the first receipt.It cannot change while the product holds stock.
6. Lot mixing left open.The renumbering and mixing function can merge shades in the system.
7. A fixed landed cost coefficient.Every shipment is slightly wrong (Example 13).
8. One BOM copied to all sizes.Large sizes short of fabric (Example 9).

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

29What must be decided before a Sage apparel go-live?

Decide the product and partner, the matrix design, the unit and lot mode for every fabric, the receipt statuses, the landed cost method, and which system owns sampling, T&A and floor capture, because each is expensive to change once stock exists.

• Sage X3, Sage 300 or Sage 200, and why.
• Matrix: partner add-on, standard products, or an operations layer.
• The add-on's supported releases, code ownership and exit plan.
• Stock unit and coefficients for every fabric and yarn.
• Lot mode (lot, or lot and sub-lot) per category, before any receipt.
• Which categories arrive in status Q, and who releases them.
• Who may use lot renumbering and mixing.
• Landed cost by coefficient or by cost structure.
• Tolerance, cartons, LC records and chargeback reasons.
• Which system owns sampling, T&A, planning, floor capture and final AQL.

30Is Sage a good ERP for fashion brands, buying agents and own-label retailers?

Sage X3 is a reasonable ERP for fashion brands and clothing brands that outsource production, and it is the Sage product with a fashion vertical aimed at them: Sage X3 Wear, which a partner describes as covering purchasing, distribution and wholesale or retail sales for purchasing groups, clothing stores and chains. A buying house needs far less, often only Sage's finance. None of them should buy X3's manufacturing functions.

Who they are

• A brand or wholesaler designs and sells; factories make for it on FOB or CMT terms, and it owns the stock once the goods ship.
• A buying agent or buying house sources for buyers on commission, places and follows orders across factories, and holds no stock.
• A retailer developing its own label runs private label sourcing like a brand and sells through its stores.

What they need from Sage, and what to skip

What not to buy or configure. Skip BOMs, routings, work centres, work orders and subcontract orders; a brand buys finished garments, and its colour-size products carry only purchase and sales data. A buying agent needs Sage's financials, customers per buyer and a commission service, and no stock management at all. For an agent, Sage 200's finance may be enough.

What Sage handles poorly for them

• Development and sampling across many factories: no object for proto, fit, lab dip and PP rounds.
• T&A across factories: a purchase order has a date, not a critical path.
• Following production that happens outside: Sage sees the PO and the receipt, nothing between.
• Inspections at the vendor: final AQL at the factory is not a Sage transaction; X3's Q status starts only when goods arrive.
• One status per order across factories and buyers: an agent with 40 orders at 12 factories needs one board, and the orders are not even in its Sage.

The MerchandiserOS model for brands and agents

For a brand or buying house, MerchandiserOS is the sourcing agent software and Sage is the ledger. MerchandiserOS runs development, samples and approvals, the T&A, the orders placed with factories, sourcing, the planning view across subcontracted factories, quality inspections at the vendor and shipping follow-up. Sage keeps the books. MerchandiserOS offers workspace set-ups for a Brand and for a Buying agent. Retail back-office work (stores, point of sale, allocation and open-to-buy) is outside MerchandiserOS's scope; a chain keeps that in Sage X3 Wear or its retail systems.

Related: the apparel-specific ERP chapter covers systems built for brands, and the NetSuite chapter covers a common alternative ERP for fashion brands.

31Which Sage API should an apparel integration use?

For Sage X3, build new integrations on the GraphQL API, available from X3 2021 R2 (V12), which authenticates with a JWT issued through a Connected Application; keep the older REST web services (V7 and later, JSON over /api1/x3/erp/<endpoint>/<class>?representation=…) for set-ups that already use them. Sage 300 has a Web API based on OData with JSON, and Sage 200 has an API authenticated with OAuth 2.0 through Sage ID.

None of these is documented as pushing events by webhook, so plan to poll: read changed purchase orders on a schedule and make the receiving side safe to call twice.

• Identifiers. X3 identifies a purchase order by its document number, the record key allocated by a sequence counter. Store it with the company and site, confirm with the partner that numbers cannot be reused, and never key on a free-text reference.
• Integration user. A dedicated user or connected application with only the rights the integration needs.
• Add-on data. If a partner matrix add-on holds the style and grid, check that its tables are reachable through the API before designing on them.

POST /api/v1/erp/po-status
Idempotency-Key: x3-FAB01-POE-2610-00457-open

{"rows": [{"request_ref": "PR-1042",
           "erp_po_id": "FAB01:POE-2610-00457",
           "erp_po_number": "POE-2610-00457",
           "status": "Open",
           "date": "2026-10-21"}]}

·Glossary of apparel and Sage terms

A/Q/R status

Sage X3's stock statuses: accepted, in quality control, rejected.

Analysis request

The Sage X3 quality control record created when stock is placed in status Q.

AQL

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

CM, CMT

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

Coefficient

In Sage X3, the fixed factor between a product's purchase, sales or packing unit and its stock unit; also the landed cost coefficient on a product.

Connected Application

The Sage X3 set-up that issues the credentials used to sign JWTs for the GraphQL API.

Cost structure

In Sage X3, a detailed list of landed cost charges applied at purchase.

Dye lot

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

FOB

Free on board: the price of goods loaded at the port; the usual quoted price per garment.

GSM

Grams per square metre: the weight of fabric.

Landed cost

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

Legislation

In Sage X3, the country pack that sets tax, accounting and statutory rules.

PP sample

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

Sage X3 Wear

A partner-delivered fashion vertical on Sage X3 for purchasing groups, stores and chains.

Size/colour matrix

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

Sub-lot

In Sage X3, a subdivision of a lot, such as one roll within a dye lot.

Subcontract work centre

A Sage X3 work centre whose operations are performed by a supplier.

T&A calendar

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

·Checklists: a Sage apparel implementation on one page

Discovery

• Business type per buyer; Sage product chosen with reasons.
• Partner and add-on vetted: releases supported, code ownership, garment references.
• All 52 fit-gap lines answered with evidence, decision and owner.
• Architecture decided: what Sage owns, what runs in an operations layer.

Design

• Matrix design: add-on, standard products or operations layer.
• Stock units and coefficients per fabric; lot mode per category.
• Receipt statuses and release rights; lot mixing restricted.
• Cost structures for imports; subcontract work centres.
• Cartons, tolerance, LC records, chargeback reasons, legislation.

Build, data and go-live

• Configuration in dependency order on the go-live release, add-on included.
• Integrations keyed on document keys, one writer per field, polling safe to repeat.
• Data loaded with lot, sub-lot and status; owners sign totals.
• All 13 scenarios passed; go-live between seasons; hypercare to first close.

Related chapters: Acumatica · Infor · SAP Business One · apparel-specific ERPs · the ERP-neutral methodology and glossary.

·Sources

Pages checked on 26 September 2026. Sage X3 online help pages are for version 12 unless stated. Partner and third-party sources are marked as such.

1. Sage X3 online help, Products (GESITM) — online-help.sagex3.com · Product categories (GESITG) — online-help.sagex3.com
2. Sage X3 online help, Stock statuses (GESTST) — online-help.sagex3.com · Quality control — online-help.sagex3.com · Stock management rules — online-help.sagex3.com
3. Sage X3 online help, Lot management — online-help.sagex3.com · Field help LOTMGTCOD (lot and sub-lot mode, version 11) — online-help.sagex3.com · Lot modification — online-help.sagex3.com · Lot characteristics change — online-help.sagex3.com · Stock by lot — online-help.sagex3.com
4. Sage X3 online help, Work order (GESMFG) — online-help.sagex3.com · Routing management (GESROU) — online-help.sagex3.com · Subcontract orders (GESSCO) — online-help.sagex3.com · Multi-level planning — online-help.sagex3.com · Work order production tracking (mobile) — online-help.sagex3.com
5. Sage X3 online help, Landed costs by site — online-help.sagex3.com · Cost loading upon order receipt — online-help.sagex3.com · Sage City, what is a cost structure — sagecity.com
6. Sage X3 online help, REST API get query — online-help.sagex3.com · Sage City, using REST web services — sagecity.na.sage.com
7. Sage Developer, GraphQL API for X3 — developer.sage.com · Create a connected application — developer.sage.com · GraphQL guide — developer.sage.com (the portal returned HTTP 403 to our automated check; facts cross-checked with third-party summaries)
8. Sage X3 releases: Sage Community Hub, 2025 R2 (12.0.38) available — communityhub.sage.com · 2026 R1 (12.0.39) and end of support for 2024 R1, partner summary — nextecgroup.com
9. Partner source: Greytrix, Sage X3 for textile and apparel (colour and size matrix) — medium.com · sub-lot set-up — greytrix.com
10. Partner source: Sage X3 Wear for purchasing groups, stores and chains — linkedin.com
11. Third-party add-on: Acute Data, Sage 300 Apparel — acutedata.com
12. Sage 300 Web API: Sage 300 SDK samples — github.com · Web API endpoint reference (hosted by Acute Data) — acutedata.com
13. Sage 200 API authentication — developer.sage.com · developer.sage.com
14. ISO 2859-1 — iso.org · inspection levels — qualityinspection.org
15. UCP 600 — uscib.org · tradefinanceglobal.com

Corrections. Sage X3 ships two releases a year, and partner add-ons change on their own cycle. If you find a statement here that your version or add-on contradicts, report a correction with the version and the page you checked; we correct the guide and note the change and its date here. We re-check this chapter at least once a year and after each Sage X3 release.

Sage, Sage X3, Sage 300 and Sage 200 are trademarks of The Sage Group plc or its licensors, used here only to name the products. This guide is not endorsed by Sage. Sage X3 Wear, Greytrix and Acute Data are named as partner or third-party sources; their products are theirs. Acumatica and NetSuite are trademarks of their owners. Garment.io is named because MerchandiserOS integrates with it; this guide is not endorsed by Garment.io.