Documentation research checked 14 October 2026. Scope: GS1 open supply-chain identification; local legal requirements not interpreted. No hands-on test or supplier audit is reported.
A sourcing offer that identifies a product’s individual unit may still leave the case being ordered ambiguous. Keep the base unit, case quantity and case identifier in separate fields. That allows the buyer to compare equivalent quantities rather than mistaking a familiar unit code for a complete packaging specification.
The documented packaging distinction
The GS1 GTIN Management Standard, Release 1.1, ratified September 2023, addresses pack and case quantity in section 2.8. It describes a new GTIN for changes in the number of trade items in a case or cases in a predefined pallet configuration, at the higher packaging levels. This is a source-bounded description of that section, not an instruction approving an actual identifier allocation.
Write an order line that exposes its unit
A buyer can request the supplier’s base-unit identifier, case identifier, units per case and number of cases offered. Give each field a clear heading instead of putting all quantities in a description such as “one box.” The goal is to show what the quoted quantity counts. It does not require guessing a supplier’s packaging hierarchy.
If an offer does not provide a case identifier, record the missing field and ask the supplier to clarify the trade item being offered. Do not invent a code from the base-unit code. A purchaser’s spreadsheet is not a source of identifier assignments, and a product photograph cannot settle the hierarchy.
Normalise quantities without inventing commercial terms
Once the supplier has confirmed the relevant quantities, a comparison can retain both cases and base units. Show any arithmetic and keep its inputs attached. Do not perform the calculation using an assumed pack size; a case-size assumption can distort the comparison while leaving the price cells looking precise.
This article contains no supplier prices, minimum order quantities, stock or delivery terms. If a team later adds those fields, it should preserve the dated offers and the unit each price applies to. A unit-price comparison is not meaningful when the quantity basis has been silently changed between offers.
Record a changed case as a changed record
For repeat sourcing, retain the prior packaging description beside the new one. Mark what changed and which supplier document supports it. A product can remain recognisable to a buyer while the ordering or receiving record needs further clarification. Do not erase the previous record just to make a replacement offer appear identical.
The responsible product-data owner should review the actual hierarchy and applicable requirements. This publication does not determine legal obligations, allocate GTINs or confirm a trading partner’s system acceptance. Barcode readability, product authenticity and quality also need evidence distinct from an identifier field.
The practical enquiry
Ask the supplier to identify precisely what is counted and ordered at each packaging level. Retain the case quantity and identity with the base-unit information, then route unresolved allocation questions to the responsible specialist. The resulting comparison is more transparent while remaining an informational procurement record, rather than a claim that Allam has validated the supplier or its products.
Evidence and limits
No allocation service, GS1 implementation approval, barcode test, product authenticity or jurisdictional compliance. Responsible data owner must review actual hierarchy.
Leave a Reply