In Acumatica a template item holds the attributes, sizes and colours and lengths, and Acumatica generates a stock item for each combination. Each of those generated items is a real inventory item with its own cost, its own stock and its own price. The template is a convenience for creating and maintaining them.
Commerce platforms model the same idea as a product with variants, and they put ceilings on it. Shopify limits the number of product options, so a template item with more attributes than that ceiling cannot be represented as one product on the storefront. Attribute values that duplicate after formatting, sizes recorded as both 10 and 10.0, will fail validation. Reordering attributes in the ERP can reorder variants on the storefront, which quietly changes what a customer sees in a dropdown.
None of this is a reason to avoid matrix items. It is a reason to model your attributes deliberately before you publish, because the cost of restructuring an attribute set after five thousand variants exist on a live storefront is far higher than the cost of thinking about it first.
Why it decides a platform
Matrix items map onto commerce platform variants imperfectly, and the mismatch produces real sync errors. Shopify, for example, supports a limited number of product options, so a product with more attributes than that cannot be represented as one product.
Also called: template item, matrix items.
Last updated 2026-08-20.