GS1 Standards: Traceability Needs a Shared Language, Not Just Better Software

A pallet of frozen seafood leaves one cold store, reaches a distributor, moves again into a foodservice warehouse, and suddenly everyone is using a different name for the same thing: supplier code, internal item code, case code, customer SKU, pallet label, batch number. GS1 standards are the global identification and data-sharing rules that give food, locations, logistic units and barcodes a common language, so a frozen case, pallet, site or shipment can be recognised beyond one company’s own software. Without that shared language, traceability often becomes translation under pressure.

The problem is rarely the barcode. It is what the barcode means.

Most food businesses can scan something. A case, a pallet, a retail pack, a warehouse label. The scan makes a sound, a field fills in, the line moves. That part is not the hard part.

The harder question comes later: did the scan identify the same thing for everyone else?

A frozen vegetable producer may have one internal item code. The retailer may have another. The distributor may shorten the description. The warehouse may record a pallet under a local location code. The transport document may use a shipment reference that does not link cleanly to the finished goods record. None of this looks dramatic during normal trade. During a recall, withdrawal, complaint or temperature dispute, it becomes expensive confusion.

GS1 standards try to remove that confusion by giving the food sector shared identifiers. A Global Trade Item Number (GTIN) identifies a trade item, such as a retail pack, case or other defined selling unit. A Global Location Number (GLN) identifies a legal entity, physical location or functional location, such as a plant, cold store, distribution centre or customer site. A Serial Shipping Container Code (SSCC) identifies a logistic unit, commonly a pallet or mixed load moving through storage and transport.

Those codes are not glamorous. They are plumbing.

But good plumbing matters. A pallet of frozen bakery cases should not need to be renamed at every handover. A shipment of ice cream should not become harder to identify because one party uses an internal depot name and another uses a customer address line. Traceability works better when the unit, place and movement are described in a form other companies can understand.

GTIN, GLN and SSCC carry different jobs

The Global Trade Item Number is usually the identifier people meet first, because it is tied to the item being sold or handled. A retail bag of frozen fries may have one GTIN. A case containing several retail bags may have another. A foodservice carton may have its own GTIN. If the pack size, configuration or trade presentation changes, the identification may need to change as well.

That distinction matters more than many teams expect.

A 1 kg retail bag and a 2.5 kg foodservice bag are not just two descriptions of “fries”. They move differently, are ordered differently, priced differently, scanned differently and may sit under different customer contracts. If the GTIN logic is loose, later data becomes muddy.

The Global Location Number does a different job. It tells the network where something is, where it came from, or which business location is involved. A factory, external cold store, retailer depot, co-packer, head office billing entity or loading point can each need precise identification. “Warehouse 2” may be enough inside one company. It is not enough when trading partners, auditors, carriers or authorities need a shared reference.

The Serial Shipping Container Code is the pallet-level workhorse. It can identify a logistic unit as it travels through the route. That matters for frozen food because pallets often move through several hands before reaching a store or kitchen. A pallet may be built at the plant, wrapped, labelled, moved into cold storage, transferred to an outside warehouse, split, consolidated, dispatched and received elsewhere. The SSCC gives that unit a traceable identity while it exists.

None of these identifiers replaces good lot control. They make lot control easier to exchange.

Data carriers are the visible part of a deeper decision

Barcodes and other data carriers are where standards meet the physical pack. A retail scanner may read an EAN or UPC barcode. A case label may use GS1-128. A small item or healthcare-style application may use GS1 DataMatrix. Radio frequency identification (RFID) may be used in some logistics contexts. Newer two-dimensional codes, including QR Codes powered by GS1, are part of the move toward richer pack-level data in some markets and categories.

This is where GS1 Digital Link is becoming more relevant. It allows GS1 identifiers such as GTINs, GLNs and SSCCs, along with data such as batch, lot, serial number or expiry date, to be encoded in a web-addressable structure that can connect a physical product to richer digital information. For frozen food, this links naturally with QR Traceability: the code on the pack should not become a marketing decoration, but a controlled bridge between product identity, traceability data and information that trading partners or consumers can actually use.

The choice is not only aesthetic. It decides what can be carried, where it can be read, how reliably it survives the route, and whether the next company can use it without manual rescue.

Frozen operations are hard on labels. Condensation, frost, abrasion, stretch wrap, curved packs, wet cartons, low-light receiving areas and damaged case corners can all turn a perfectly specified data carrier into an unreadable nuisance. A pallet label placed cleanly in the packing room may be half-covered after wrapping. A case code may be readable before freezing and poor after storage. A retail barcode may scan in a calm office and fail in a busy receiving bay with gloves and cold air in the doorway.

Application Identifiers are another part of the language. In GS1 barcodes, Application Identifiers tell the scanner what the following data means: GTIN, batch or lot, expiry date, net weight, serial number, SSCC and so on. Without that structure, a string of numbers can be read, but not properly understood.

The point is simple. A code is not just printed ink. It is a data contract on a pack, case or pallet.

Industry misconception: our ERP already gives us traceability

A familiar claim in food businesses is that traceability is covered because the company has an enterprise resource planning (ERP) platform, warehouse scans and internal item codes. That may be true inside the walls. It may not be true once the goods move.

Internal systems speak internal language.

Traceability across the frozen route needs other parties to read the same identity. Supplier, co-packer, cold store, distributor, retailer depot, foodservice wholesaler, carrier. If each one translates the item, location and pallet into its own local code, the route can still function commercially. It becomes weaker when speed matters.

The weakness appears during incidents. A batch problem at a supplier. A wrong label. A temperature excursion in transport. A retailer asking which depots received affected cases. A distributor trying to isolate stock without blocking more than necessary. If the identities are not shared, people start matching spreadsheets by description, date, delivery note and hope.

Hope is a poor traceability tool.

Standards do not solve bad data. A GTIN used incorrectly, a GLN missing from a location, an SSCC not scanned at handover, a lot code printed badly or a date entered in the wrong format can still break the trail. GS1 gives the common grammar. Companies still have to write the sentence properly.

That is the practical test. Do identifiers survive real trade, or do they fall apart after the first exception?

Questions buyers should ask suppliers

GS1 standards should not be left only to packaging artwork teams or IT departments. They affect recall speed, receiving accuracy, stock control, customer data and cold-chain accountability.

• Which GTINs are assigned to retail packs, foodservice packs, cases and other trade units?
• When pack size, case count, formulation, label language or customer format changes, how is GTIN change assessed?
• Which GLNs identify manufacturing sites, external cold stores, depots, co-packers and shipping or receiving points?
• Are SSCCs used on pallets or logistic units, and are they scanned at dispatch, receipt and transfer?
• Which data carriers are used on retail packs, cases and pallets: EAN/UPC, GS1-128, GS1 DataMatrix, RFID or two-dimensional codes?
• Can lot code, date, quantity and other traceability data be encoded or linked in a way trading partners can read?
• How is barcode readability tested after freezing, wrapping, storage, transport and handling?
• Can the supplier exchange traceability data with customers and logistics partners without manual spreadsheet translation?

These questions are practical because standard identification only matters when it survives the route. A perfect code in a master data file does not help if the pallet label is unreadable, the location is vague, or the customer cannot connect the identifier to its own receipt.

GS1 standards are not a fashionable digital layer. They are the shared naming structure underneath traceable food. They help companies say: this exact item, from this location, in this logistic unit, moving through this handover.

Frozen food needs that clarity because its route is long. Goods move through factories, cold stores, carriers, depots, retail freezers, foodservice distributors and kitchens. Each handover is a chance to preserve identity or blur it.

The best traceability language is boring when everything goes well and very valuable when something goes wrong.