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

1Who Acumatica fits in apparel

Acumatica fits mid-size apparel brands, wholesalers and factories that want a cloud ERP with strong distribution and finance, a real manufacturing module, and pricing that does not charge per user. Acumatica Cloud ERP is a mid-market cloud ERP sold in industry editions; the Manufacturing Edition adds bills of material, routings, production orders, MRP, estimating and engineering change control.

For apparel, its best features are template items with matrix items for style, colour and size, grid entry on sales and purchase orders, lot and serial tracking, landed cost documents that can come from several vendors, and an open integration surface: a versioned REST API, OData for reporting, and push notifications to webhooks. Its main apparel weakness is that a bill of material belongs to one item, so every size and colour of a style needs its own BOM.

Signs Acumatica is a good choice

Acumatica tends to work when the business is growing, has many occasional users and wants one cloud ledger.

• Many people need to look at stock, orders and approvals, but few enter transactions all day, so user-based licensing would be expensive.
• The business sells wholesale or online as well as making, so distribution and commerce matter as much as the shop floor.
• A partner with Manufacturing Edition experience is available, or the factory has a .NET developer for extensions.
• Style counts are in the hundreds per season, so a matrix item per colour and size stays manageable.

Signs to slow down

Slow down when the requirements belong to a floor, planning or development system.

• The owner expects the ERP to plan sewing lines hour by hour and track bundles.
• Most of the work is sampling and development, which happens before any Acumatica item exists.
• The factory is mainly CMT and expects outside processing to model its own sewing for buyers without testing it first (section 16).
• Local e-invoicing has no known Acumatica solution in the country (section 21).

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 an Acumatica weakness. SAP, NetSuite, Dynamics 365 and Odoo meet the same wall; in Acumatica it shows most clearly as a BOM that belongs to one matrix item, when the factory thinks in styles. The same wall applies to brands and buying agents, whose sampling, T&A and inspections happen at factories the ERP never sees.

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

3The recommended architecture, in short

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

With this split the Acumatica project stays close to standard, and the Manufacturing Edition becomes optional rather than central. The rest of this guide still explains how to bend Acumatica toward garment production, because some factories choose to, and a consultant needs to know what each choice costs.

4Business types, and what each needs from Acumatica

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

5Who should be on an Acumatica apparel project, and what should discovery cover?

An Acumatica apparel project needs one decision owner per design question, and most owners sit in the factory: the merchandising head for items and matrices, the stores head for units and lots, the CAD lead for consumption, the IE manager for minutes, the quality manager for inspections and the finance head for costing and currencies. The partner configures; the factory decides.

Run one workshop per department, walking a real recent order from buyer PO to cash. Each workshop produces the flow as it really runs (spreadsheets included), findings mapped to fit-gap lines, and decisions with an owner. The questions that matter most for Acumatica are these.

• Merchandising. How are sizes and colours broken down; do buyers order ratio packs; what quantity tolerance applies per line and per order; how many deliveries per order?
• Development. Which sample types does each buyer require; where do tech packs and revisions live; who builds the quote cost?
• Stores. In which unit is each material bought, stocked and issued; what is measured at receipt (GSM, width, shade, shrinkage); can every roll of one dye lot be found today?
• Production. At what level is production controlled: per size, per style-colour, per cut? Which processes go outside, and how are pieces counted out and back?
• IE and planning. Where do operation minutes come from; how is line capacity planned across the season, including subcontractors?
• Quality. Which inspections run; which buyers set their own AQL; who may release a failed lot?
• Shipping. Solid or assorted cartons; buyer labels; ASN; LC documents?
• Finance. Currencies; LC, prepayment or open account; chargebacks; how import charges are costed; free-zone reporting; e-invoicing?

A decision log with date, owner, option chosen and options rejected keeps the project moving. "Merchandising and finance will agree" produces no decision; write one name against each fit-gap line.

6The apparel fit-gap checklist for Acumatica: 52 lines

A fit-gap checklist records, line by line, whether Acumatica meets an apparel requirement as standard, with configuration, with custom code or an ISV add-on, or better outside it. The answers are our assessment of Acumatica 2025 R2 and 2026 R1 with the Manufacturing Edition, for a typical full-package garment factory; confirm each line in a demo on your version.

Key: Standard works as delivered · Configure settings, attributes, classes or imports · Custom build a customisation project or ISV add-on · Operations layer better run in an apparel operations system and passed to Acumatica

Counted from this table, 8 of the 52 lines are standard, 24 need configuration, 12 need custom code or an ISV add-on and 8 are better run outside Acumatica. That count is our assessment for a full-package factory, not a survey. Acumatica scores more "Configure" than most ERPs because a BOM per matrix item turns size and colour rules into master data rather than code; the cost moves from development to data maintenance.

7Which Acumatica edition, licence and hosting does an apparel project need?

A garment factory that makes in-house needs the Manufacturing Edition, because BOMs, routings, production orders and MRP come with it; a brand or wholesaler that buys finished goods can often start without it. If the recommended architecture is used, even a factory may keep Acumatica to finance, purchasing, stock and sales, and leave production to the operations layer.

How much does Acumatica cost for a garment factory?

Acumatica prices by the applications you use, the resources and transaction volume you expect, and how you deploy, not by the number of users. Acumatica calls this unlimited-user licensing; you choose a resource tier, and it sets limits such as concurrent API requests and requests per minute. We do not quote prices, because they depend on the tier and the region; Acumatica and its partners quote them.

For a garment factory the model has a clear upside: merchandisers, supervisors, quality staff and managers can all log in to look at orders and stock without a licence each. The side to watch is the API. Every integration, e-commerce connector and scheduled import shares the tier's request limits, so size the tier with the integrations in mind (section 31).

Questions to settle with the partner

• Which edition and which applications does the fit-gap need, and which resource tier?
• Which customisations and ISV add-ons are planned, who owns them, and who retests them at each release?
• Is there a sandbox or test tenant for trying each release against real data?
• Acumatica ships two releases a year (2026 R1 in spring; 2026 R2 announced for 1 October 2026). Which one goes live, and when is the next upgrade?

8Acumatica vs NetSuite for apparel

Acumatica and NetSuite both model a style as a parent with generated children for colour and size, both allow grid entry, and both are cloud ERPs sold mostly through partners; the clearest differences are licensing (resources in Acumatica, users in NetSuite) and how manufacturing and subcontracting are packaged. Neither covers sampling, T&A, cut plans or AQL out of the box. See the NetSuite chapter for its side in full.

From practice: a business with many light users and a strong wholesale side often prefers Acumatica's licensing; a brand that wants a prepackaged apparel starting point often looks at NetSuite's edition. In both, the parts marked custom build or operations layer in the fit-gap stay that way. Compare other systems on the comparison page.

9How should item classes and materials be set up in Acumatica for apparel?

Set up Acumatica item classes by how each material is bought, stocked, costed and tracked: knit fabric, woven fabric, yarn, trims, packaging, outside-process services and finished garments each get a class, because the class carries the default units, the lot/serial class, the valuation method and the posting accounts. An item class in Acumatica is a template of defaults that every item in it inherits; defaults can be overridden per item.

Outside-process services such as embroidery are non-stock items, which is how Acumatica's outside processing expects them (section 16). Landed-cost charges are not items at all; they are landed cost codes (section 17).

With operations on top: the style, its classified bill of materials and its consumption live in the operations layer. Acumatica still needs item classes, because it holds stock value and payables.

10How do template items and matrix items handle style, colour and size in Acumatica?

In Acumatica the style is a template item and each colour-size combination is a matrix item, a real stock item generated from the template's Variant attributes. A template item holds attributes of the Variant category with a combo control, and a pattern that builds each matrix item's ID and description from the template ID, attribute values, constants or numbers.

Because each matrix item is a full stock item, it can have its own units, price, vendor details and BOM. That is Acumatica's strength for distribution and its cost for manufacturing: one style in 5 sizes and 3 colours is 15 stock items and, in production, 15 BOMs.

• Grid entry. On sales and purchase orders, adding matrix items opens a matrix view where quantities are typed per colour and size. Acumatica's help documents buying and selling matrix items, including importing orders that contain them.
• Non-variant attributes. Season, buyer style number and fit notes can be attributes that do not generate items.
• ID pattern. Agree it before the first import, for example P2041-NVY-L. Users should not edit it later, and integrations must not rely on it (section 31).
• Create only what sells. Matrix items are generated when you choose to create them, so a merchandiser can create the combinations the buyer ordered rather than the full grid.

With operations on top: styles, colourways and size breakdowns live in the operations layer, and Acumatica needs only the matrix items that are actually sold and invoiced, without BOMs.

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

Acumatica lets you define item-specific unit conversions on the Stock Items form (IN202500), so a knit fabric can have a base unit and a purchase unit in different measures with a factor between them; the factor is fixed per item, while the real metres per kilogram changes with each roll. Units can also be defined system-wide on the Units of Measure form (CS203500) and per item class on the Item Classes form (IN201000).

GSM is the weight of one square metre of fabric in grams. The conversion from weight to length depends on it and on width:

Acumatica's help describes conversions between units measuring the same thing in different quantities; it does not discuss weight-to-length pairs. Test a kg-to-metre item-specific conversion in your version before relying on it. The safer designs are below.

Count units work cleanly: a button bought by the gross (144) and issued by the piece is an ordinary conversion, and a pair unit for socks is another count conversion.

With operations on top: the operations layer records a measured lot record per receipt (GSM, width, shrinkage) and works consumption in the cutting room's unit. Acumatica stays in kilograms for stock value and payables.

12How do you track dye lots and fabric rolls in Acumatica?

Give fabric a lot/serial class that tracks lot numbers assigned when received, treat each lot as one dye lot, and make the lot mandatory on every issue to cutting. A dye lot is a batch of fabric dyed together; two dye lots can differ slightly in shade, so one garment must never mix them.

Tracking rules live on the Lot/Serial Classes form (IN207000) and reach items through the item class (IN201000) and the stock item (IN202500). A class sets the tracking method (not tracked, lot numbers or serial numbers), the assignment method (when received, or when used) and, for items assigned when received, the issue method: FIFO, LIFO, sequential, expiration or user-enterable. The class also sets automatic numbering, which suits internal lot numbers; a mill's own dye lot number is usually typed or scanned at receipt instead.

Rolls are a design choice. A serial number per roll gives roll-level issue and return; a lot per roll keeps one number per roll but loses the dye lot unless it is held in a field. Shade group, measured width and measured GSM are not standard lot fields and need custom fields.

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

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

In the Acumatica Manufacturing Edition a bill of material belongs to one item, so each matrix item (each colour and size) carries its own BOM, and size-graded consumption falls out naturally as a different fabric quantity on each size's BOM. The work is in creating and maintaining those BOMs; generate them by import from a consumption table instead of typing them.

Acumatica documents multi-level BOMs by item or site, cost rolls from lower levels to the top, phantoms and backflushing, BOM compare, and BOM revisions under engineering change control. Community answers from Acumatica staff confirm that a matrix is a collection of stock items and each can have its own BOM; there is no single BOM on the template with per-size rules.

Marker efficiency is the share of fabric in a marker that ends up in garment pieces; shrinkage is what the garment loses in washing or finishing. Keep them apart in the consumption table even if the BOM holds only the result.

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 Acumatica. No per-size BOMs are needed there.

14How do you model cutting, sewing and finishing with Acumatica work centres?

Model cutting, sewing, finishing and packing as work centres, and give each BOM a routing of operations with their minutes and labour rates; production orders then carry estimated labour and collect actuals, but the routing does not balance a sewing line. Acumatica's production management schedules work centres to finite or infinite capacity and compares estimated, planned or standard cost with actual cost per production order.

SMV (standard minute value) is the time a trained operator needs for one operation at a normal pace. A polo has 15 to 25 sewing operations; group them into a few routing operations per department, or the operation list becomes unreadable. 2026 R1 added seconds-level time tracking on operations, which helps short, repetitive garment operations.

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. Acumatica receives material issues for stock value.

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

Acumatica has no object for garment samples, buyer approvals or a T&A calendar, so the project builds them as a customisation, borrows project or case records, 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, with actual dates and owners.

Each sample round has a sent date, a courier and tracking number, the buyer's comments and a verdict, and each approval unlocks the next step: bulk dyeing waits for the lab dip, cutting waits for the PP sample. A custom build needs sample requests per style and colourway, rounds under each, a link from the approved round to the spec version, a block on the next step, and T&A dates that come from the rounds.

With operations on top: dev approvals (lab dip, strike-off, sample, shipping mark) with rounds, courier details and verdicts, the T&A with its critical path, and the PP approval that locks the style version for the order live in the operations layer.

16Does Acumatica outside processing work for embroidery, printing, washing and CMT?

Acumatica Manufacturing Edition handles outside processing: an operation on a BOM is marked as an outside process with a preferred vendor, a non-stock service item represents the vendor's work, a purchase order is created for it, and receiving it moves the work back into WIP. It fits a single step such as embroidery well; whether it fits a CMT unit sewing your cut panels, or a chain of processors, is something to test in a demo, because Acumatica's material describes heat treating, painting, coating and assembly rather than garments.

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. Practitioners on Acumatica's community describe the setup: a non-stock item for the process with its vendor and price, added to the operation as material of type subcontract, with the outside-process flag and preferred vendor on the operation, and a process that creates purchase orders from production orders. One reported snag is that the PO takes the non-stock item's default vendor rather than the vendor on the BOM operation; check this in your version.

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 lines. Acumatica receives the subcontractor's purchase order and the payable.

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

Acumatica values stock by the item's valuation method, rolls BOM costs up from lower levels, and compares estimated or standard production cost with actual; landed costs (freight, duty, clearing, bank charges) are added to purchase receipts through landed cost documents. The garment costing sheet used to quote a buyer comes before the item exists and usually lives outside, though the Manufacturing Edition's Estimating can cost a new item and convert the estimate into a BOM.

How do you set up landed costs in Acumatica for imported fabric?

Create a landed cost code for each import charge with its allocation method, then enter a landed cost document that lists the charges and the purchase receipt lines they apply to; charges can come from vendors other than the fabric vendor, such as the forwarder and the bank. Purchase receipts are entered on the Purchase Receipts form (PO302000).

Acumatica documents these allocation methods:

By Weight and By Volume read the Packaging tab of each stock item. If the weight per base unit is blank, the item gets no share. Fill it during data migration.

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. Acumatica holds the landed cost that actually hit the receipts.

18Can Acumatica run quality control and AQL inspection for garments?

Core Acumatica does not include a quality management module with ISO 2859-1 sampling tables; quality inspection comes from ISV suites built on the Acumatica platform, such as eWorkplace Apps' Quality Management Suite, or from custom work or a separate system. AQL (acceptance quality limit) inspection checks a random sample from a lot and accepts or rejects the whole lot on the number of defects found.

Without an ISV, the standard tools are a hold location for fabric waiting for inspection, lot tracking so a failed lot can be found, and attachments for lab reports. If you evaluate an ISV suite, ask it to show the ISO 2859-1 lookup from lot size and inspection level to sample size and acceptance numbers, and a logged override.

With operations on top: typed inspections (incoming, cutting, PP, DUPRO, final AQL, pre-shipment, measurement), the AQL engine at the buyer's level, CAPA, needle and metal control and quality grades run in the operations layer. Acumatica sees the shipment once it is cleared.

19How do you handle cartons, tolerance and shipping documents in Acumatica?

Acumatica shipments hold packages, and sales order lines carry undership and overship thresholds that decide whether a short or over shipment completes the line; ratio cartons, buyer carton labels and pack-level packing lists need custom work. The thresholds are percentages per line, so a buyer tolerance on the order total needs a check across the five size lines.

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

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

Acumatica handles foreign currencies, exchange differences and customer prepayments as standard, including prepayments created on the sales order and reserved for it; letters of credit and reason-coded chargebacks need design. Prepayments are entered on the Payments and Applications form (AR302000) or directly on the Sales Orders form (SO301000).

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 must be presented within 21 days after shipment unless the credit says otherwise, and never after expiry. Acumatica has no LC object; the credit number, amount, latest shipment date, expiry and document list need custom fields or a custom screen.

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

Check your country. Acumatica is sold in a limited set of regions with local editions and partner localisations, and we have not verified e-invoicing coverage for Egypt, Bangladesh, Pakistan, India, Vietnam, Turkey or Morocco in this guide. Before selecting Acumatica for a factory in these countries, ask the partner which statutory reports and e-invoicing connections they have delivered, and test an e-invoice end to end in the sandbox.

Free-zone and temporary-admission factories report the import and re-export of materials to customs. Acumatica holds the quantities by lot; the report format is local and usually a custom report.

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

Configure Acumatica from the ledger outward: features, company and currencies first, then units, attributes and lot/serial classes, then item classes, then warehouses and locations, then landed cost codes, then manufacturing, and only then the items themselves. Loading items before classes and units are final means reloading them.

Screen IDs below are the ones we confirmed in Acumatica's help or its user forums; labels can move between releases, so check them on your version.

23How is Acumatica customised for apparel, and what usually gets built?

Acumatica is extended through customisation projects built on the Acumatica Framework: added fields, screens, business logic and web service endpoints, packaged as a project that can be exported as a file and published to another tenant. ISV solutions on the Acumatica Marketplace use the same framework. Every customisation must be retested at each twice-yearly release.

24Which systems does an Acumatica apparel implementation integrate with?

An Acumatica apparel project typically connects a PLM or tech-pack system, a floor system, EDI, banks, e-commerce and an operations layer; each connection needs one writer per field and links stored on permanent ids. Four rules prevent most faults.

• Link on Acumatica's record GUID, the id the REST API returns, never on an order number or inventory ID a user can change.
• One writer per field. If two systems can change a quantity, one of them is wrong without knowing it.
• Show disagreements to a person instead of overwriting silently.
• Make receivers safe to call twice, so a retried message never creates a second purchase order.

25How do you migrate apparel data into Acumatica?

Migrate only open and active data (active styles, open orders, open purchase orders, stock by lot), load it in dependency order with import scenarios, and have each owner sign off the loaded totals. An import scenario maps a data provider, which describes the source file's structure, to an Acumatica form, and runs on the Import by Scenario form (SM206036). Acumatica's help and community document importing template and matrix items and orders containing matrix items through scenarios.

Load order: accounts and currencies; units, attributes and lot classes; item classes; customers and vendors; materials; template items and their matrix items; work centres and BOMs; stock by lot and location, counted at cut-off; open purchase orders; open sales orders; open receivables and payables. Fill each fabric's weight on the Packaging tab before the first landed cost.

Template,Color,Size,InventoryID,Description,BaseUnit,ItemClass
P2041,NVY,S,P2041-NVY-S,Men's piqué polo navy S,PCS,FG
P2041,NVY,M,P2041-NVY-M,Men's piqué polo navy M,PCS,FG
P2041,NVY,L,P2041-NVY-L,Men's piqué polo navy L,PCS,FG
P2041,NVY,XL,P2041-NVY-XL,Men's piqué polo navy XL,PCS,FG
P2041,NVY,XXL,P2041-NVY-XXL,Men's piqué polo navy XXL,PCS,FG

OrderType,OrderNbr,Customer,InventoryID,Qty,UnitPrice
SO,SO-P2041,BUYER01,P2041-NVY-S,300,4.26
SO,SO-P2041,BUYER01,P2041-NVY-M,750,4.26
SO,SO-P2041,BUYER01,P2041-NVY-L,900,4.26
SO,SO-P2041,BUYER01,P2041-NVY-XL,750,4.26
SO,SO-P2041,BUYER01,P2041-NVY-XXL,300,4.26

Open PO:  navy jersey 180 GSM, 925 KG ordered, 0 received
Stock:    buttons 15 mm navy, 9,504 PCS (66 gross), no lot

Clean before loading: merge duplicate materials, retire styles with no order in two seasons, give every roll in stock its lot, and split partly delivered order lines into delivered and open quantities.

26How should you test an Acumatica 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 in a sandbox, each step with its expected result written down first. These 13 scenarios cover the flows where apparel projects break.

Test script: shade split at cutting

Scenario T4 proves that lots stay apart when sizes span two lots. Issue lot A to the XXL and XL production orders and 87 pieces' worth to size S; issue lot B to L and the other 213 pieces of S; issue lot C to 727 pieces of M, and lot A to 23. Return the remainder per lot: A 23.4 m, B 0.3 m, C 0.2 m. The expected result is that every issue names its lot and the leftover per lot matches the cut plan. Refusing a second lot on one cut needs the cut-control customisation or an operations layer; Acumatica does not enforce one lot per cut.

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

Train each role only on the screens it uses, on the factory's own styles, and go live between seasons with a rehearsed cut-over; keep the partner close until at least the first month-end close. Hypercare is the period right 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, reconcile and sign; the sponsor gives go or no-go at a fixed hour.
• Timing. Avoid shipment windows, the financial year-end, audits and, in practice, the weeks around an Acumatica release upgrade.
• Hypercare. Practitioners commonly plan four to eight weeks; that range is judgement, not a standard. Nobody leaves before the first month-end close in Acumatica is complete.
• Floor. If operators record output in Acumatica, the 2026 R1 Shop Floor Kiosk is the screen to train on; if they use a floor system, Acumatica training stops at the office.

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

The most common Acumatica-specific mistakes are copying one size's BOM to every matrix item, a fixed kg-to-metre factor, FIFO issue on dye-lotted fabric, blank weights that break landed cost by weight, and integrations that exhaust the licence's API limits. The list is from implementation practice.

1. One BOM copied to every size.MRP under-buys fabric for large sizes (Example 8).
2. Full-grid matrix creation.Thousands of stock items and BOMs nobody uses.
3. A fixed kg-to-metre conversion.Stock shows metres the cutting table cannot find (Example 6).
4. FIFO issue on dye lots.The system picks a lot the cutting master did not choose.
5. Blank weights on the Packaging tab.Freight allocated by weight skips those items.
6. Outside processing assumed to fit CMT.Test panels, vendors and per-size counts before designing on it.
7. Production orders per size, planned as if per style.Five orders to release, issue and close for one polo colour.
8. API limits ignored.An e-commerce connector and an operations integration share the tier's concurrent requests and requests per minute.
9. Customisations not retested at release.Two releases a year means two regression cycles.

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

29What must be decided before an Acumatica apparel go-live?

Decide the template level, the unit design for every fabric, the lot class and issue method, how BOMs per matrix item are generated, and which system owns sampling, T&A and floor capture before go-live, because each is expensive to change once transactions exist.

• Template per style or per style-colour; Variant attributes and ID pattern.
• Create full grids or only ordered combinations.
• Unit design for every fabric and yarn; whether any item-specific kg-to-metre conversion is used.
• Lot/serial classes, assignment and issue methods; roll design.
• How BOMs per matrix item are generated and revised.
• Production order level, and how five sizes are released and closed together.
• Outside processing tested for each subcontract type.
• Landed cost codes, allocation methods and item weights.
• Line thresholds and the order-total tolerance check.
• How buyer-supplied fabric stays out of stock value.
• Which system owns sampling, T&A, planning, floor capture and quality.
• API resource tier sized for every integration.

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

Yes, for the books and the trade flows: a clothing brand, a buying house or an own-label retailer can run vendor purchase orders with matrix entry, landed cost and duty, vendor payments, wholesale sales orders and multi-currency in Acumatica without the Manufacturing Edition. What Acumatica does not do for them is the work in between, following development, samples, T&A and inspections at factories they do not own.

Who they are

Three kinds of apparel business never sew a garment themselves, and each uses an ERP differently.

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

What they need from Acumatica

A brand needs the purchasing, landed cost, payables, sales and finance side of Acumatica, and none of the production side.

What not to buy or configure. Skip the Manufacturing Edition, BOMs, routings, work centres, outside processing and MRP. A brand does not need a BOM per matrix item, because it buys finished garments; the matrix items carry only purchase and sales data. A buying agent needs even less: Acumatica's financials, a customer per buyer, a service item for commission, and no inventory at all. The resource-based licence suits both, because merchandisers and quality staff who only look at orders do not each need a seat.

What Acumatica handles poorly for them

The hard part of a brand's or agent's job happens at factories, and Acumatica only sees the purchase order and the receipt.

• Development and sampling across many factories. Proto, fit, lab dip and PP rounds with several vendors per style have no object in Acumatica.
• T&A across factories. A purchase order has a promised date, not a critical path of fabric booking, approvals, cutting and inspection.
• Following production that happens outside. Acumatica has no view of a vendor's cutting, sewing or packing progress.
• Inspections at the vendor. Final AQL at the factory, before the goods ship, is not an Acumatica transaction.
• One status per order across factories and buyers. An agent following 40 buyer orders at 12 factories needs one board, and Acumatica does not hold the agent's orders at all.

The MerchandiserOS model for brands and agents

For a brand or buying house, MerchandiserOS is the sourcing agent software and Acumatica 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. Acumatica keeps the books: the purchase orders as financial commitments, landed cost, payables and receivables, commission invoices and tax. 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; an own-label retailer keeps that in its retail systems.

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

31Which Acumatica API should an apparel integration use?

Use the contract-based REST API for reading and writing records, OData for reporting reads from generic inquiries, and push notifications to a webhook for near-real-time events; authenticate with OAuth 2.0 through a connected application. The contract-based API exposes business objects that map to Acumatica screens, so validations and workflow rules apply to API writes.

What are Acumatica's API limits?

Each licence sets a maximum number of concurrent web service API requests and a maximum per minute; above half the per-minute limit Acumatica starts delaying requests, and it declines a request when more than 20 are queued or one waits more than 10 minutes. The license also caps concurrent API user sessions. Limits vary by tier and are shown in the License Monitoring Console (SM604000). Design integrations to batch, back off and sign out.

• Identifiers. Store the record's id GUID; show the order number, never key on it.
• Push and pull. A push notification on a generic inquiry of purchase orders tells the operations layer something changed; a REST read by id confirms it. Keep a scheduled pull as a safety net.
• Version pinning. Keep the endpoint version fixed until you retest after an upgrade.

POST /api/v1/erp/po-status
Idempotency-Key: acu-po-8f1c2b7e-open

{"rows": [{"request_ref": "PR-1042",
           "erp_po_id": "8f1c2b7e-4d3a-4c1e-9b0a-2e5f6a7b8c9d",
           "erp_po_number": "PO000457",
           "status": "Open",
           "date": "2026-10-21"}]}

·Glossary of apparel and Acumatica terms

AQL

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

Allocation method

In Acumatica, the rule a landed cost code uses to spread a charge: by quantity, cost, weight, volume, or none.

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.

Connected application

In Acumatica, a registered OAuth 2.0 or OpenID Connect client allowed to call the web services.

Contract-based REST API

Acumatica's versioned web service that exposes business objects mapped to its screens.

Dye lot

A batch of fabric dyed together; pieces from different dye lots 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; the usual quoted price per garment.

Generic inquiry

An Acumatica query screen whose results can be exposed through OData or used to trigger push notifications.

GSM

Grams per square metre: the weight of fabric.

Item class

In Acumatica, a template of defaults (units, lot class, valuation, accounts) inherited by items.

Landed cost

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

Lot/serial class

In Acumatica, the rules for tracking, assigning and issuing lot or serial numbers.

Matrix item

In Acumatica, a stock item generated from a template item for one combination of Variant attribute values.

Outside processing

In the Acumatica Manufacturing Edition, a BOM operation performed by a vendor on a purchase order.

PP sample

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

Push notification

An Acumatica message sent to a webhook, queue or hub when data behind an inquiry changes.

Size/colour matrix

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

SMV

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

T&A calendar

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

Template item

In Acumatica, the style record whose Variant attributes generate matrix items.

·Checklists: an Acumatica apparel implementation on one page

Discovery

• Business type settled per buyer; one owner per area.
• All 52 fit-gap lines answered with evidence, decision and owner.
• Architecture decided: what Acumatica owns, what runs in an operations layer.
• Edition, applications and resource tier confirmed, including API limits.

Design

• Template level, Variant attributes and ID pattern locked.
• Unit design per fabric; lot classes and issue methods.
• BOM generation per matrix item, or none if operations run outside.
• Outside processing tested; landed cost codes and item weights set.
• Thresholds, cartons, LC records, chargeback reasons, e-invoicing.

Build, data and testing

• Configuration in dependency order on the go-live release.
• Customisations and ISV add-ons listed with owners and a retest plan per release.
• Integrations keyed on record GUIDs, one writer per field.
• Import scenarios run in order, with a cut-off and signed totals.
• All 13 scenarios passed by key users.

Go-live

• Role training on the factory's own orders; cut-over rehearsed.
• Go-live between seasons, away from year-end and release upgrades.
• Hypercare until the first month-end close.

Related chapters: NetSuite · Dynamics 365 Business Central · Odoo · Sage · the ERP-neutral methodology and glossary.

·Sources

Pages checked on 26 September 2026. Acumatica's help portal does not always state a version on each page; where it does, it is named.

1. Acumatica, Manufacturing Edition datasheet (version 210915) — acumatica.com
2. Acumatica, Manufacturing management overview — acumatica.com · Bill of materials and routing — acumatica.com · Production management — acumatica.com
3. Acumatica 2026 R1 release — acumatica.com · 2026 R1 for manufacturers, distributors and retailers — acumatica.com · 2026 R2 launch event — acumatica.com
4. Acumatica, Apparel ERP software article — acumatica.com
5. Acumatica help, Allocating Landed Costs (2024 R2) — help-2024r2.acumatica.com
6. Acumatica help, Units of Measure: General Information — help.acumatica.com · Stock Items: Units of Measure — help.acumatica.com
7. Acumatica help, Items with Lot and Serial Numbers: Tracking Settings — help.acumatica.com · Lot/Serial Classes — help.acumatica.com
8. Acumatica help, Matrix Items: To Purchase Matrix Items — help.acumatica.com · Selling Matrix Items: Import of Orders with Matrix Items — help.acumatica.com
9. Acumatica Community, template and matrix items; matrix items and BOMs — community.acumatica.com · community.acumatica.com · importing matrix items — community.acumatica.com
10. Acumatica Community, outside processing setup and purchase orders — community.acumatica.com · community.acumatica.com
11. Acumatica help, Line-Level Shipping Rules (2024 R2) — help-2024r2.acumatica.com
12. Acumatica help, prepayments in Accounts Receivable and on sales orders — help.acumatica.com · help.acumatica.com
13. Acumatica Marketplace, Quality Management Suite (eWorkplace Apps) — acumatica.com
14. Acumatica, web services, REST API, OData and integration best practices — acumatica.com
15. Acumatica help, Push Notifications: Destinations — help.acumatica.com · Business Events: Subscribers (2024 R2) — help-2024r2.acumatica.com
16. Acumatica help, Generic Inquiries and OData: General Information — help.acumatica.com
17. Acumatica help, Connected Applications — help.acumatica.com · Getting Started with OAuth 2.0 and OpenID Connect — help.acumatica.com
18. Acumatica help, License Restrictions for API Users — help.acumatica.com
19. Acumatica pricing — acumatica.com · unlimited-user licensing — acumatica.com · Licensing Guide, April 2025 — acumatica.com
20. Import scenarios and data providers (SM206015, SM206025, SM206036), user-group examples — augforums.com
21. NetSuite facts: Oracle NetSuite help, matrix items — docs.oracle.com · Grid Order Management — docs.oracle.com · Outsourced Manufacturing — docs.oracle.com · apparel and footwear — netsuite.com
22. ISO 2859-1 — iso.org · inspection levels — qualityinspection.org
23. UCP 600 — uscib.org · tradefinanceglobal.com

Corrections. Acumatica ships two releases a year, and a form ID, a feature boundary or a limit can move in one of them. 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 here. We re-check this chapter at least once a year and after each Acumatica release.

Acumatica is a trademark of Acumatica, Inc., used here only to name the product. This guide is not endorsed by Acumatica, Inc. NetSuite is a trademark of Oracle. Garment.io is named because MerchandiserOS integrates with it; this guide is not endorsed by Garment.io.