Item classes, released products and the shared-product boundary

Separate the defaulting, reporting and posting intent bundled into Acumatica item classes, decide what becomes a product master with variants, and load released products in a legal-entity structure the source never had.

What you will be able to do

Introduction

Product data is where an Acumatica migration first meets a structural difference that has nothing to do with accounting: the target separates the product from the released product, and the source does not.

Product, released product, and the boundary between them

Read that table alongside the legal-entity design and two questions follow immediately.

Taking item class apart

The concept mapping rates the item class translation medium confidence and classifies it as product-and-posting design. The medium rating is honest: how a given tenant uses item class depends on its module footprint and its customisation estate.

Product dimensions: the variant decision

Acumatica estates commonly hold each sellable combination as its own item: a garment in four sizes and three colours is twelve item records. The target can express that as one product master with size and colour product dimensions, producing twelve variants under one product.

Units of measure

Units are unglamorous and they gate everything. The playbook puts unit of measure loading in wave zero alongside currencies and calendars, because item loading, inventory balances, order migration, costing and every quantity-bearing integration depend on them.

Non-stock, service and kit patterns

Every estate has items that are not really items, and each pattern needs an individual decision.

Deciding what not to migrate

Item volume is the easiest master set to over-migrate. Catalogues accumulate discontinued products, one-off specials, superseded revisions, test records and items created by an integration that has since been switched off.

Sequencing

Wave zero — units of measure, currencies, calendars. Waves one and two — chart, dimensions, and customer and vendor grouping, because the posting crosswalk that determines item groups depends on them.

Knowledge check

Summary

The source holds items inside a tenant; the target defines a product once and releases it into each legal entity that transacts on it. That boundary is the first structural difference, and it resolves duplication the source tolerated across tenants — at the cost of reconciling divergence nobody had to face before.