A clean GTIN wholesale catalogue is the backbone of B2B ordering. Without consistent codes at unit, inner and case level, retailer scanners reject goods, EDI messages bounce, and portal catalogues drift from what finance invoices. This guide explains how brands assign and maintain GTINs and EANs across pack levels so the whole chain stays aligned.
What is a GTIN in a wholesale catalogue?
A GTIN is a Global Trade Item Number: a standardised identifier for a trade item as it is sold or stocked at a specific packaging level.[1] Consumer units are commonly assigned a GTIN-13 (EAN-13 barcode) or a GTIN-12 (U.P.C.), depending on market and prefix; higher pack levels frequently use GTIN-14.[2][3] Whatever the encoding, the number must uniquely identify that item in that pack configuration in your B2B wholesale catalogue and on the physical label.
Your GS1 company prefix is the licensed base from which you build item reference numbers.[4] You do not invent random barcodes. You allocate from that prefix according to pack hierarchy and change rules, then store the results next to each SKU in your master data.
Nested unit, inner carton and outer case linked by one hierarchy line
How do unit, inner and case pack GTINs differ?
Unit, inner and case pack GTINs differ because each level is a different trade item for scanning, ordering and logistics. The unit each is the consumer-sellable piece (bottle, garment, carton of one). An inner pack is a multi-unit bundle often used for shelf replenishment. A case pack is the shipper retailers and distributors usually order. A pallet is typically identified with an SSCC for logistics tracking rather than a product GTIN for catalogue sale—though palletised configurations still need clear links back to the case GTIN and quantity.[3][5]
Barcode hierarchy B2B practice is simple in principle: one GTIN per sellable or scannable pack level, with explicit quantity relationships (for example, how many units in an inner, how many inners in a case). Reusing the unit EAN on the case label, or leaving the case without a GTIN, is a common source of warehouse and EDI failure.
| Pack level | Typical identifier | Role in wholesale |
|---|---|---|
| Unit (each) | EAN-13 / UPC / GTIN-13 | Shelf scan, consumer unit, base catalogue item |
| Inner pack | Own GTIN (often GTIN-13 or GTIN-14) | Shelf-ready or replenishment multiple |
| Case pack | Often GTIN-14 (or distinct GTIN-13) | Standard order and receiving unit |
| Pallet | SSCC (logistics) | Shipment tracking, not catalogue SKU identity |
How do you assign GTINs and EANs for B2B SKUs?
Start from licensed GS1 capacity and a written allocation rule—not from a designer’s one-off barcode generator. For each SKU variant that is ordered or scanned differently, decide which pack levels you sell or ship. Assign a distinct GTIN to each of those levels. Record indicator or packaging logic consistently if you use GTIN-14 for cases. Map every GTIN to internal SKU, pack quantity, dimensions and the parent–child links in the hierarchy.
Practical assignment checklist:
- Confirm GS1 company prefix and remaining capacity with your national GS1 organisation.
- List every orderable pack (unit, inner, case) per variant—not only the consumer unit.
- Allocate a new GTIN when the pack is a different trade item; do not clone the unit code onto the case.
- Store GTINs in PIM or ERP master data beside SKU, MOQ and case quantity.
- Print and verify labels against that master before first shipment.
- Publish the same codes in line sheets, EDI item masters and the B2B portal catalogue.
This work sits next to SKU management for variants and case packs: variants (size, colour, scent, voltage) usually need their own unit GTINs, and each variant’s case configuration needs its own case GTIN when the trade item differs.
Barcode path from product master to labelled case on a pallet
Why do retailer scanners and EDI fail on bad barcode data?
Retailer scanners and EDI fail on bad barcode data when the number on the label does not match the number in the retailer’s item file, or when pack-level identity is ambiguous. Typical breaks include: case labelled with the unit EAN; GTIN allocated in a spreadsheet but never loaded to EDI; old GTIN left on artwork after a pack change; inner packs sold without their own code; checksum or formatting errors; and catalogues that show only a single barcode field for a SKU that ships in three pack levels.
EDI item maintenance expects stable identifiers per trade item. If your purchase-order response, despatch advice or invoice carries a different GTIN than the buyer’s master, automated receiving stalls and chargebacks follow. Human email orders hide the problem until peak season. Investing in clean masters is cheaper than firefighting mis-scans. For channel context, see whether EDI for wholesale brands fits your retailer mix—either way, GTIN quality is a prerequisite.
What belongs in a clean GTIN wholesale catalogue data model?
A clean GTIN wholesale catalogue data model holds, for every orderable line, the internal SKU, pack level, GTIN at that level, quantity of next-lower units, and links up the hierarchy. It also holds status (active, seasonal, discontinued), artwork or label version, and the markets where that code is valid. UPC versus EAN-13 encoding is a representation choice; the catalogue should still treat identity as GTIN-centric so cross-border retailers do not get duplicate rows for the same trade item.
Prefer a PIM or disciplined product master over scattered line-sheet tabs. PIM for wholesale catalogue data is how many brands keep one truth for portal, EDI and print. Line sheets remain useful for sales conversations; they should pull GTINs from the same master—see what to include on a wholesale line sheet.
Minimum fields worth standardising:
- SKU / variant ID
- Pack level (unit, inner, case)
- GTIN (with encoding noted: EAN-13, GTIN-14, UPC)
- Units per inner; inners or units per case
- Orderable flag and MOQ at that pack level
- Status and replacement GTIN when superseded
How should brands maintain GTINs when packs or variants change?
When packs or variants change, brands should follow GTIN allocation rules rather than overwriting numbers in place. A new net content, a material change that affects the trade item, a new case count, or a new brand presentation often requires a new GTIN at the affected level.[6][7] Reusing a code for a different item breaks historical sales data and retailer files. Declaring a GTIN obsolete, publishing the replacement, and updating portal, EDI and labels together is slower on day one and far safer in peak receiving weeks.
Operational habits that keep hierarchy healthy:
- Own a single GTIN steward (operations or master-data role), not ad-hoc marketing edits.
- Tie artwork approval to master-data approval so labels cannot ship ahead of the catalogue.
- Version pack configurations; do not silently change “case of 12” to “case of 10” on the same code.
- When discontinuing, mark GTINs inactive and map successors for reorders.
- Audit warehouse labels against the master after every range reset.
Two pack configurations diverging into separate identity paths
How do GTINs connect to SKU management and case packs?
GTINs connect to SKU management by giving each orderable pack a shared language with retailers. Your internal SKU can stay human-readable; the GTIN is what external systems key on. Case packs are where wholesale most often goes wrong: sales sell “a case,” warehouse picks a case, finance invoices a case—but only the unit EAN exists in the file. Link case GTIN, case quantity and unit GTIN explicitly so availability, pricing tiers and returns all resolve to the same hierarchy.
When does barcode setup affect B2B portal ordering?
Barcode setup affects B2B portal ordering whenever retailers search, scan-to-order, reorder from history, or match portal lines to store-receiving files. If the portal shows one barcode for a SKU that actually ships as inners and cases, buyers pick the wrong line, MOQs confuse, and downstream invoices disagree with the ASN. Portal UX expectations include trustworthy product identity—not only nice imagery. That is part of what retailer buyers expect in a B2B portal.
Brandgate is the branded B2B storefront where approved retailers see that catalogue—unit, inner and case identifiers included—so orders, reorders and invoices stay tied to the same pack-level data your warehouse labels.
If you want that catalogue exposed cleanly to distributors without spreadsheet drift, Book a demo.