How to Implement Epicor Kinetic or SYSPRO for Garment & Apparel Business (2026 Guide)

1Who Epicor Kinetic and SYSPRO fit in apparel

Epicor Kinetic and SYSPRO fit mid-market manufacturers that make more than garments, or that make textiles or technical products where lots, routings, subcontract operations and job costing matter more than a size and colour matrix. Neither vendor offers an apparel edition that we could find, and neither documents a native style, colour and size matrix, so a garment business must model each size and colour as its own part or stock code, or extend the product.

Epicor Kinetic is Epicor's manufacturing ERP for make-to-order and mixed-mode manufacturers. SYSPRO is an ERP for mid-market discrete and process manufacturers and distributors. Epicor also sells Prophet 21, a distribution ERP for wholesalers and distributors, which is outside the scope of this chapter.

When these ERPs make sense for a textile or garment business

• A multi-product manufacturer also makes textiles or garments: workwear, technical textiles, home textiles, uniforms, medical textiles.
• A textile mill or finishing plant needs lots, process routings and job costing more than a size grid.
• The company already runs Epicor or SYSPRO in another division and wants one ledger.
• Style counts are small and size ranges are narrow (uniform programmes, fixed catalogues).

When to look elsewhere

• Fashion ranges with hundreds of styles per season, many colours and wide size runs; see Infor CloudSuite Fashion or apparel-specific ERPs.
• Buyers who order by size grid every day and expect matrix entry on every document.
• A brand whose main work is development and vendor follow-up (section 32).

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. Epicor Kinetic and SYSPRO go one step further from apparel than most, because their item is a part or stock code with no parent style, so even the style itself has no home. The same wall applies to brands and buying agents: their development, sampling and follow-up across many factories happen before any purchase order exists.

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, and in full section 33).

3The recommended architecture, in short

Let Epicor Kinetic or SYSPRO keep the books and the stock value, and run apparel operations from the style to the shipment in a system built for them. For these two ERPs the case is stronger than for fashion ERPs, because the style itself has no home in the ERP.

MerchandiserOS runs 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. The ERP keeps accounts, payables and receivables, invoicing, payments, stock value, tax and e-invoicing.

4Business types, and what each needs from Epicor Kinetic or SYSPRO

The business type decides who owns the material, what is invoiced and how much of the ERP carries weight. Settle it first, because a company often runs two types at once.

5Who should be on the project team?

Name one decision owner for every design question, and put the part-numbering decision with the merchandising head, not with IT, because it decides how every garment is counted for years. The partner configures; the business decides.

6What should discovery workshops cover for a garment line on Epicor or SYSPRO?

Walk a real, recent order through each department and map every finding to a fit-gap line; spend extra time on how many parts the range will create and who will keep their BOMs. The full question sets are on the methodology page; these are the ones that decide an Epicor or SYSPRO design.

• How many styles, colours and sizes per season, and how many of those combinations actually sell?
• Do buyers order by grid, by ratio pack or line by line?
• Which materials are bought in kg and used in metres, and what is measured per roll?
• Which attributes must travel with a lot: shade group, GSM, width, shrinkage?
• Which processes go outside, and how are pieces counted out and back?
• Which inspections run, and which buyers set their own AQL?
• Which import charges must reach material cost, and which e-invoicing rules apply?

7The apparel fit-gap checklist for Epicor Kinetic and SYSPRO: 52 lines

This fit-gap records, line by line, whether Epicor Kinetic and SYSPRO meet each apparel requirement as standard, with configuration, with custom work, or better outside the ERP. It is our assessment for a typical full-package garment factory, based on the vendors' documentation where we found it; where the two products differ, the note says so. Confirm every line with your partner before signing 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 the ERP

Counted from this table, 8 of the 52 lines are standard, 24 need configuration, 11 need custom work and 9 are better run outside the ERP. This is our assessment, not a survey. The pattern is clear: these ERPs are strong on the manufacturing and costing lines and weak on the product lines a fashion ERP covers natively.

8Which modules and licences does a garment project need?

License the manufacturing core and only the modules the fit-gap needs; for apparel the ones to check first are lot tracking, landed cost, quality and, in Epicor, Advanced Unit of Measure. We do not quote prices or deployment options, because both vendors sell through partners and the terms change; confirm cloud or on-premise and the module list in writing.

9Epicor Kinetic vs SYSPRO vs Acumatica for a garment line

For apparel the three are close on manufacturing depth; the difference is how each holds size and colour. Acumatica has template and matrix items (one SKU per combination), Epicor Kinetic has attribute-based inventory through Advanced Unit of Measure, and SYSPRO has neither, so it relies on stock codes per combination or its Product Configurator.

If a size grid is central to the business, read the Acumatica chapter before choosing. If one ledger across several divisions matters more, Epicor or SYSPRO plus an operations layer is a sound design.

10How should parts and materials be classified for apparel?

Classify parts by how they are bought, stocked, costed and tracked: fabric, yarn, trims, packaging, subcontract services and finished garments each get their own class or product group, with lot tracking on fabric and yarn. In a part-per-SKU design, add a class or user field that links each garment part back to its style and colour, because the ERP has no parent to do it.

Buttons: 3 per polo is 9,000 pieces; with a 5% allowance 9,450, which is 9,450 ÷ 144 = 65.6 gross, so the PO says 66 gross (9,504 pieces). Gross to pieces is a fixed factor, so an alternate unit handles it in either ERP.

11How do you handle sizes and colours in Epicor Kinetic or SYSPRO without a matrix?

Neither Epicor Kinetic nor SYSPRO documents a native style, colour and size matrix that we could find, so the usual design is one part (Epicor) or stock code (SYSPRO) per style, colour and size, with a numbering convention and a field that links it back to the style. A style/colour/size matrix is a grid with colours on one axis and sizes on the other, used to enter or show quantities for each combination.

There are three ways to hold size and colour:

Epicor describes Advanced Unit of Measure as letting a business track inventory by attribute under a single part number and plan inventory at the attribute level. Epicor's own examples are engineering attributes such as hardness, strength and density; partners describe using it for size and colour, so test it on a real polo range before relying on it.

With operations on top: styles, colourways and size breakdowns live in the operations layer, and the ERP holds only the parts that are actually stocked and invoiced.

12How do you convert kilograms to metres for fabric in Epicor Kinetic or SYSPRO?

SYSPRO converts between a stocking unit and an alternate or other unit with a conversion factor per stock code, and Epicor offers the same kind of factor plus Advanced Unit of Measure, whose dynamic attributes Epicor says help convert, for example, pounds or grams to feet or metres. A fixed factor is wrong for knit fabric, because the real factor changes with every roll's GSM and width.

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

SYSPRO's help notes that changing a conversion factor does not change outstanding sales or purchase orders already entered in the alternate unit, so a factor corrected mid-season leaves old orders on the old factor. In Epicor, stock status can show availability by attribute in both units; whether the conversion can be driven by a measured GSM and width per receipt is the question to demo.

With operations on top: a measured lot record per receipt (GSM, width, shrinkage) drives consumption in the operations layer, and the ERP can stay in kilograms for stock value and payables.

13Can Epicor Kinetic or SYSPRO track fabric by dye lot?

Yes. Both track lots: Epicor lists serial and lot processing with barcode scanning at every stage, and SYSPRO's Lot Traceability module tracks materials by lot from receipt through manufacture, inspection and distribution. Use each lot as one dye lot and make it mandatory on receipt and on every issue to cutting. A dye lot is a batch of fabric dyed together; two lots can differ in shade and must not meet in one garment.

Shade group, GSM and width per lot need a user field or, in Epicor, a dynamic attribute. Neither product documents a shade band or a rule that stops one cut from mixing lots, so that control belongs in an extension or the operations layer.

14How do you handle size-dependent fabric consumption in Epicor or SYSPRO BOMs?

In a part-per-SKU design, size consumption is simple: each size part has its own BOM with its own fabric quantity. The risk moves from the model to the maintenance, because new sizes are usually created by copying an existing BOM, and a copied fabric quantity is wrong for every other size. Generate BOMs from a consumption table instead.

Marker efficiency is the share of fabric in a marker that ends up in garment pieces; shrinkage is fabric lost in washing or finishing. Keep them apart in the source table.

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

15How do you model cutting, sewing and finishing as operations?

Model cutting, sewing, finishing and packing as operations on the part's routing, with times and labour rates; both ERPs then cost labour on the job. Neither is documented as a sewing-line balancing or hourly output tool.

With operations on top: the 52-week heat-map of lines and subcontractors, 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?

Neither ERP has an object for garment sample rounds, buyer verdicts or a T&A calendar that we could find, so they live in 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 calendar lists an order's milestones with planned dates worked back from ex-factory.

With operations on top: dev approvals (lab dip, strike-off, sample, shipping mark) with rounds, courier details and buyer 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.

17How do Epicor Kinetic and SYSPRO handle subcontracting for CMT, embroidery or washing?

Both handle subcontracted operations as standard. In Epicor Kinetic, subcontract purchase orders are tied to job operations and shipments to the supplier are recorded against the subcontract operation. In SYSPRO, WIP Subcontract Operations Management records a dispatch when job-issued material is sent to a subcontract supplier, with quantity, lot and serial details for traceability and reconciliation.

CMT means cut, make and trim: in subcontracting, a unit that sews cut panels for the factory and charges for the labour.

With operations on top: subcontract steps sit on the production order in the operations layer, with subcontractors on the planning heat-map. The ERP receives the subcontract PO and the payable.

18How do you cost a garment and its imported fabric in Epicor or SYSPRO?

Job costing in both ERPs collects material, labour, subcontract and overhead per job, and both handle landed cost on imports: Epicor allocates additional costs to received materials, and SYSPRO's Landed Cost Tracking module tracks freight, duties, insurance and handling per shipment. The quotation cost build comes before any part exists, so it usually lives outside the ERP.

A landed cost is every cost of bringing goods to the factory beyond the supplier's price: freight, insurance, duty, clearing and bank charges.

With operations on top: the cost engine to FOB with landed cost and dated FX, the standard cost sheet and quotations with approval gates run in the operations layer. The ERP holds the landed cost that actually hit the receipts.

19Can Epicor Kinetic or SYSPRO run AQL inspection for garments?

Both run inspections, but we did not find ISO 2859-1 AQL tables in either product's documentation, so AQL sample sizes and acceptance numbers need an extension or a separate system. Epicor Kinetic has an Inspection Workbench where failed parts go to discrepant material report (DMR) processing, nonconformance records, and Epicor QMS for CAPA. SYSPRO receives inspection-flagged items into inspection first, then accepts, rejects or scraps them in Purchase Order Inspection, and its Quality Management module adds an Inspection Engine and non-conformance reports.

AQL (acceptance quality limit) inspection checks a random sample from a lot and accepts or rejects the lot on the defects found.

With operations on top: typed inspections, 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.

20How do you handle cartons and shipping documents?

Shipping and packing run in the ERP (Epicor lists master packs in Kinetic Warehouse), while buyer carton rules, labels and packing-list layouts need design per buyer.

21How do these ERPs handle currencies, letters of credit, advances and chargebacks?

Multi-currency is expected in both ERPs, but we did not verify deposit invoicing, letter-of-credit handling or chargeback reason codes in the vendors' documentation for this guide; confirm each with the partner and test it (section 27). A letter of credit is a bank's promise to pay when documents matching its terms are presented; under UCP 600 they are presented within 21 days after shipment unless the credit says otherwise.

22Do Epicor Kinetic and SYSPRO support e-invoicing in garment-exporting countries?

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

23In what order should Epicor Kinetic or SYSPRO be configured for a garment line?

Configure from the ledger outward: company, currencies and accounts; units and conversion factors; part classes and numbering; lot tracking; landed cost; work centers, operations and subcontract setup; quality; and only then the parts and BOMs, loaded from a generated file. The screen names below are those used in the vendors' documentation; menu locations vary by version, so find them through search in your version.

24Which extensions does an apparel project on Epicor or SYSPRO usually need?

Expect extensions for a style layer (grid entry and part generation), BOM generation and mass change, per-lot fabric conversion, cut control, AQL and quantity tolerance, unless those move to an operations layer. Epicor Kinetic offers Epicor Functions and BPM for business logic, reachable through its REST API; SYSPRO extends through e.net business objects. The list below is from implementation practice.

25Which systems does the ERP integrate with in a garment business?

A garment business on Epicor or SYSPRO typically connects a style or PLM tool, a floor system, EDI with retailers, banks and an operations layer. Keep one writer per field, link on the ERP's own keys, show disagreements to a person on a review list, and make every receiver safe to call twice.

26How do you migrate apparel data into Epicor Kinetic or SYSPRO?

Migrate only open and active data, in dependency order, with generated part and BOM files rather than hand-keyed ones, and have each owner sign the loaded totals. Epicor users widely load data with Epicor's Data Management Tool (DMT) per the Epicor user community; confirm it is in your licence. SYSPRO offers import programs (for example Purchase Order Receipts Import, which posts through the PORTOR business object) and e.net business objects for loads.

A cut-off rule states the exact moment after which every transaction is entered in the new ERP. For the polo order, the check is simple: 1,278 + 3,195 + 3,834 + 3,195 + 1,278 = 12,780.00 = 3,000 × 4.26, across five part lines.

27How should you test a garment 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, with expected results written first. The 13 scenarios are the same for every ERP in this guide.

Test script: short shipment within tolerance

28How should training, cut-over and hypercare run?

Train each role on its own screens and scenarios using the factory's own parts, rehearse the cut-over once in full, go live between seasons, and keep the partner close until the first month-end close is done. Hypercare is the period after go-live when the project team fixes issues daily.

• Merchandisers learn to enter the polo as five part lines, or the grid in the operations layer that creates them.
• Stores learn receipts into inspection with lots, and issues that always name the lot.
• Planners learn jobs, subcontract operations and the embroidery PO.
• Quality learns inspection, nonconformance and release.
• Finance learns landed cost, job costing, advances and currency.

Practitioners commonly plan four to eight weeks of hypercare; that is judgement, not a standard. Nobody leaves before the first month-end close.

29What are the most common mistakes when using Epicor or SYSPRO for apparel?

The most common mistakes are part explosion, BOMs copied from one size, no link from part to style, one conversion factor per fabric, and expecting a manufacturing ERP to do a merchandiser's job. The list comes from implementation practice and from the general failure modes in the methodology.

1. Part explosion.Every possible combination created up front (Examples 6 and 7).
2. BOMs copied from size M.Large sizes run short (Example 10).
3. No style link.Reports cannot add up a style across its parts.
4. One conversion factor.Stock says metres the cutting table does not have (Example 8).
5. Lots optional at issue.Shade mixing found at final inspection.
6. Attributes assumed to drive BOMs.Epicor dynamic attributes chosen without a demo of size-dependent consumption.
7. A job per size per order without thought.Five times the jobs and subcontract POs for every order.
8. Grid-thinking users on line-entry screens.Merchandisers keep their spreadsheets.

30What must be decided before go-live?

Decide the part model, the numbering, the style link, the fabric unit design, the lot rules, the job level and which system owns style, sampling, T&A, floor capture and AQL, because each is expensive to change once transactions exist.

• Part per SKU, Epicor dynamic attributes, SYSPRO configurator, or an operations layer.
• Part numbering and when a part is created.
• How BOMs are generated and mass-changed.
• Fabric units and kg-to-metre conversion.
• Lot as dye lot; which lot fields are mandatory.
• Job per size, per style-colour or per delivery.
• Landed cost allocation methods.
• Where sampling, T&A, floor capture and AQL live.
• How buyer-supplied fabric stays out of stock value.
• Which API the integration uses and which service account it logs in with.

31Which API should an integration use with Epicor Kinetic or SYSPRO?

Use the Epicor Kinetic REST API v2, built on OData v4, where every request carries an API key plus Basic authentication or a bearer token. For SYSPRO, write through e.net business objects, which run on WCF services with HTTP REST and SOAP endpoints, and read through the SYSPRO OData service, which is read-only.

Epicor Kinetic

• Endpoint. Services sit under https://<server>/<instance>/api/v2/odata/<company>/, with business objects, BAQs (Epicor's saved queries) and Epicor Functions exposed as services, per Epicor and third-party documentation. Kinetic's built-in REST help lets you browse services and try calls.
• Auth. An API key on every request, plus Basic credentials or a bearer token. REST v2 appeared in Epicor 10.2.700, per third-party documentation; check your version.
• Identifiers. Link on the company plus the PO number Epicor assigns, never on a reference a user types.

SYSPRO

• e.net business objects carry SYSPRO's own business logic for queries and postings; for example, PORTOR posts purchase order receipts. Calls run under a SYSPRO operator; check the e.net guide for your release.
• SYSPRO OData is a standalone OData 4.0 service that exposes SYSPRO tables for reading only, with Basic authentication using SQL credentials; SYSPRO lists it from SYSPRO 8 2021 R2.
• SYSPRO Harmony API queries and posts to the Harmony database; it is not the route for ERP transactions.

We found no documented webhooks for either ERP in what we reviewed, so polling for changes is the baseline. Make the receiving side safe to call twice.

POST /api/v1/erp/po-status
Idempotency-Key: epicor-MAIN-10457-approved

{"rows": [{"request_ref": "PR-1042",
           "erp_po_id": "MAIN/10457",
           "erp_po_number": "10457",
           "status": "approved",
           "date": "2026-10-21"}]}

32Are Epicor Kinetic or SYSPRO good for a clothing brand, buying agent or own-label retailer?

Usually not as a first choice. Both are built for manufacturers, and a clothing brand, a buying house or an own-label retailer uses little of their manufacturing depth while missing the style, matrix and retail features a fashion or distribution ERP offers. They can work when a brand sits inside a group that already runs Epicor or SYSPRO for its 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 through private label sourcing.

What they need, and what to skip

Skip the manufacturing modules: jobs, routings, work centers, MRP for production and shop-floor tools. As buying house ERP or sourcing agent software, a manufacturing ERP is more system than the work needs; as an ERP for clothing brands, it lacks the style and grid. Compare with NetSuite and Dynamics 365 Business Central.

What these ERPs handle poorly for them

• Development and sampling with many factories.
• T&A across factories.
• Following production that happens outside.
• Inspections at the vendor with AQL.
• One status per order across many factories and 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. The ERP 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.

·Glossary of apparel, Epicor and SYSPRO terms

Short definitions of the terms used here. The full list is on the guide glossary.

Advanced Unit of Measure

Epicor Kinetic functionality for tracking inventory by dynamic attributes under one part number, with conversions between units.

AQL

Acceptance quality limit: a sampling inspection that accepts or rejects a lot on the defects found, using ISO 2859-1 tables.

BAQ

Business Activity Query: a saved query in Epicor, callable through the REST API.

CMT

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

DMR

Discrepant material report: Epicor's record for failed material awaiting a decision.

Dye lot

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

e.net business object

A SYSPRO service that queries or posts a transaction using SYSPRO's own business logic.

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.

Landed cost

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

Part-per-SKU

A design where each style-colour-size combination is its own part or stock code.

PP sample

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

Stock code

SYSPRO's identifier for an inventory item.

Style/colour/size matrix

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

Subcontract operation

A routing step done by an outside supplier, bought on a purchase order tied to the job.

T&A calendar

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

·Checklists: Epicor Kinetic or SYSPRO for apparel on one page

Discovery and design

• Business type settled: CMT, full package, multi-product, mill, brand, agent or own label.
• Range size counted: styles × colours × sizes actually sold.
• Part model chosen and demonstrated on a real range.
• BOM generation and mass change planned.
• Fabric unit design, lots as dye lots, lot fields mandatory.
• Where style, sampling, T&A, floor capture and AQL live.

Build, data, testing and go-live

• Modules licensed: lots, landed cost, quality, units.
• Integration on Epicor REST v2 or SYSPRO e.net, linked on ERP keys.
• Parts and BOMs loaded from generated files; totals signed.
• All 13 scenarios passed by key users; cut-over rehearsed.
• Go-live between seasons; hypercare to the first month-end close.

·Sources

Pages were checked on 26 September 2026. Some epicor.com pages refuse automated fetches; for those, claims rest on the page as indexed by search engines and are marked as vendor pages.

1. Epicor, Kinetic Open REST API (vendor page) · epicor.com
2. Epicor Kinetic REST API v2: API key plus Basic or bearer, OData v4, endpoints (third party) · knowledgelib.io
3. Epicor, Advanced Unit of Measure (vendor page) · epicor.com · ebook · epicor.com
4. Epicor, Kinetic Supply Chain Management (landed cost, container tracking, lot and serial) · epicor.com · Kinetic Warehouse · epicor.com
5. Epicor, Kinetic Production Management and Epicor QMS · epicor.com · epicor.com
6. Epicor Prophet 21 (distribution ERP) · epicor.com
7. Epicor user community on DMT loads · epiusers.help
8. SYSPRO e.net Solutions · developer.syspro.com
9. SYSPRO OData service (read-only, OData 4.0, Basic with SQL credentials) · help.syspro.com
10. SYSPRO 8 Harmony API Service · help.syspro.com
11. SYSPRO PORTOR business object · help.syspro.com
12. SYSPRO Stock Code Maintenance (units and factors) · help.syspro.com
13. SYSPRO Product Configurator · help.syspro.com
14. SYSPRO WIP Subcontract Operations Management (2026 R1 guide) · help.syspro.com
15. SYSPRO Landed Cost Tracking · syspro.com · Lot Traceability · syspro.com
16. SYSPRO Purchase Order Inspection, Non Conformance Report Maintenance, Inspection Engine · help.syspro.com · help.syspro.com · help.syspro.com
17. SYSPRO overview (third party) · erpresearch.com
18. Acumatica matrix items and landed cost (see the Acumatica chapter) · acumatica.com
19. ISO 2859-1 · iso.org · AQL tables · qima.com · UCP 600 · tradefinanceglobal.com

Corrections. Both vendors release often, and module names, API versions and options change. If a statement here contradicts your version, 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 these facts at least once a year.

Epicor, Epicor Kinetic and Prophet 21 are trademarks of Epicor Software Corporation. SYSPRO is a trademark of SYSPRO. Acumatica is a trademark of Acumatica, Inc. Names are used only to identify the products; this guide is not endorsed by any of them. Garment.io is named because MerchandiserOS integrates with it; this guide is not endorsed by Garment.io.