Case Pack Quantity
Case pack quantity is the fixed number of individual sellable units ("eaches") contained in one case — the standard shipping and ordering unit a supplier ships as a single carton. It sits in the middle of the GS1 packaging hierarchy between the each and the pallet, and under GS1 rules each distinct pack configuration gets its own GTIN: changing the case pack quantity means assigning a new identifier, not editing the existing one. In a product catalog, it's the attribute that determines whether a buyer ordering "24 units" gets exactly one case, a partial case plus loose units, or an order that doesn't cleanly resolve at all.
Where case pack sits in the packaging hierarchy
GS1's trade item hierarchy defines four common packaging levels, each identified by its own GTIN. Each is the lowest level intended for individual sale — the unit a shopper buys one of. Inner pack is an intermediate grouping of eaches (or a predefined assortment) that isn't always present. Case is the standard shipping unit containing a fixed number of eaches, either loose or grouped into inner packs. Pallet is the shipping-level grouping of cases, inner packs, or eaches, and must contain only one GTIN regardless of how many items are on it.
Case pack quantity specifically describes the each-to-case ratio: a case pack of 24 means one case contains exactly 24 individually sellable units. It's distinct from inner pack quantity, which describes an intermediate grouping that may or may not exist for a given item.
Why a changed case pack quantity needs a new GTIN
GS1's GTIN management rules treat pack configuration as part of a trade item's identity, not a mutable attribute of an existing identifier. If a supplier changes a case from 24 units to 36 units, that's a new trade item under the standard, requiring a new GTIN at the case level — the old GTIN (and any barcode or ASN referencing it) now describes a configuration that no longer exists.
This rule exists because downstream systems — a retailer's receiving process scanning a case-level barcode, a warehouse management system calculating pallet cube from case count — rely on the GTIN resolving to one fixed quantity. A supplier that reuses a case-level GTIN after changing the pack quantity silently breaks every downstream system's assumption about what that barcode means, which shows up as short shipments, receiving discrepancies, and — if it happens with a retail trading partner — chargebacks.
Where case pack quantity data breaks down in practice
A few recurring failure patterns: the each-level GTIN and the case-level GTIN both exist in a feed but the multiplier connecting them (case pack quantity) is missing, so a system can't derive one from the other. A supplier changes packaging without assigning a new GTIN, silently corrupting every downstream ASN, invoice, and receiving scan that assumes the old quantity. Or the attribute is populated but inconsistently — a PIM record says 24, a price list says 12-count cases, and nobody reconciled the two after a packaging change.
Case pack quantity also directly feeds MOQ and order-increment logic: a supplier that only sells by the full case needs the order system to know the case pack quantity to enforce or round to a valid order amount, and needs it to be correct for the ASN generated once that order ships.
Frequently asked questions
What is the difference between case pack quantity and inner pack quantity?
Case pack quantity is the total number of individually sellable units (eaches) in one case. Inner pack quantity describes an optional intermediate grouping inside the case — for example, a case of 24 might be organized as 4 inner packs of 6. Not every item has an inner pack level; case pack quantity is the more universally present of the two.
Why does changing a case pack quantity require a new GTIN?
Under GS1 GTIN management rules, the pack configuration is part of a trade item's identity. A GTIN is expected to resolve to one fixed set of contents; changing the unit count inside a case without assigning a new GTIN means the existing barcode no longer accurately describes what's in the box, which breaks receiving, ASN reconciliation, and pallet-cube calculations downstream.
How does case pack quantity relate to MOQ?
They're related but distinct. Case pack quantity is a fixed packaging fact — how many units are in one case. MOQ is the smallest total order a supplier will accept, which is sometimes expressed as a number of full cases. A supplier might set an MOQ of one case (thereby indirectly setting it via the case pack quantity) or a higher multi-case MOQ on top of that packaging unit.
What happens if case pack quantity data is missing from a catalog?
A buyer or ordering system can't reliably derive how many cases to ship for a given each-level order quantity, which shows up as rounding errors, partial-case orders a supplier can't fulfill, or ASN quantities that don't match what was actually shipped. It's a common gap in supplier-fed catalogs where the each-level GTIN made it into the PIM but the case-level packaging data didn't.