GS1 Standards for Food Traceability

GS1 standards are a global system of unique identification numbers and barcodes that let trading partners describe products, locations, and shipments the same way, so a lot code scanned at a farm still means the same thing at a distributor and a retailer. For food traceability, three GS1 keys do most of the work: the GTIN for products, the GLN for locations, and the SSCC for pallets and cases.

Traceability breaks whenever two companies call the same thing by different names. GS1 exists to stop that. It is the same organization behind the barcode on a retail package, the U.P.C., and the same numbering system now underpins how food gets traced through the supply chain, including under the FDA’s FSMA 204 rule. This guide explains the core identifiers, how barcodes carry them, how partners share the data, and how it all maps to traceability requirements.

What are GS1 standards?

GS1 standards are a shared framework, maintained by the non-profit GS1 organization, for identifying and communicating information about products and supply-chain entities. The system has three parts: identify (assign unique numbers), capture (encode them in barcodes or RFID), and share (exchange the data between partners in a common format).

The foundation is the GS1 Company Prefix, a licensed number unique to your business. Every identifier you create, for a product, a location, a shipment, is built on that prefix, which is why a GTIN you assign will never collide with one from another company. That global uniqueness is the whole point: it is what lets a number cross company boundaries without a translation table.

You will hear GS1 identifiers called “keys.” There are a dozen or so, but food traceability leans on three, plus batch and date attributes attached to them. Get those right and most of a traceability program falls into place.

What are GTIN, GLN, and SSCC?

They are the three GS1 identification keys that answer the core traceability questions: what the product is, who and where handled it, and which physical unit moved. Each is a globally unique number built on your company prefix.

A crucial detail: the GTIN identifies a type of product, not an individual unit. Every 12-ounce jar of your salsa shares one GTIN. To trace, you pair the GTIN with a batch or lot number and often a production or expiry date, carried as separate data alongside the GTIN. The GTIN says “what,” the lot says “which run.” The SSCC, by contrast, is serialized: each pallet gets its own unique SSCC so it can be tracked as one physical thing from your dock to the customer’s.

How do barcodes carry GS1 data?

Through defined barcode symbologies and “application identifiers” that label each piece of data. The retail package you scan at a checkout uses a U.P.C./EAN barcode carrying just the GTIN. But a case or pallet needs more, the lot, the date, the SSCC, so food logistics uses richer symbols:

• GS1-128 the workhorse barcode for cases and pallets. It can encode multiple data elements in one symbol, each prefixed by an application identifier (AI) that says what the following digits mean: (01) is the GTIN, (10) is the batch/lot, (17) is the expiry date, (00) is the SSCC.
• GS1 DataMatrix a 2D square barcode used where space is tight or a lot of data is needed, common on smaller packs and increasingly on produce.
• GS1 DataBar often used on hard-to-mark fresh items like loose produce, able to carry a GTIN plus batch and date in a small footprint.

The application identifiers are what make a single barcode machine-readable across companies. When a receiving scanner reads (01) then (10) then (17), it knows it has a product, a lot, and a date without anyone agreeing on a custom format first. That is the quiet magic of GS1: the meaning travels with the data.

What is GDSN, and how do partners share the data?

GDSN, the Global Data Synchronization Network, is a network of interoperable data pools that lets a supplier publish standardized product data once and have every subscribing customer receive the same up-to-date record automatically. Instead of emailing spec sheets, you maintain your product attributes (dimensions, weight, ingredients, allergens, GTIN) in one place and they synchronize to trading partners.

GDSN handles the static master data, what a product is. For the moving, event-level data, what happened to a specific lot, when, and where, GS1 defines EPCIS (Electronic Product Code Information Services), a standard for sharing traceability events: the what, when, where, and why of each step. Together they cover both halves of traceability: GDSN keeps everyone’s product catalog aligned; EPCIS carries the trail of events as goods move.

How do GS1 standards support FSMA 204?

They provide the shared vocabulary the rule assumes. The FDA’s FSMA 204 traceability rule requires companies handling foods on the Food Traceability List to capture Key Data Elements (KDEs) at each Critical Tracking Event (CTE), receiving, transforming, shipping, and to hand that data to the next partner. The rule does not mandate GS1, but GS1 identifiers are the practical way to do it, and the GS1 US industry guidance maps the standards directly to the rule.

The fit is close to one-to-one: a GTIN plus batch/lot satisfies the product-identification KDEs, a GLN pins the location KDEs to a specific place, and an SSCC ties a shipment together across a receiving and shipping event. Because the same identifiers are already what large retailers demand, adopting them once serves both the regulation and your customers. Most food traceability programs come together in the same order:

1. License a GS1 Company Prefix. This is the foundation every other identifier is built on. Without it, your numbers are not globally unique.
2. Assign GTINs to your products. One per trade item and packaging level. This is the “what.”
3. Assign GLNs to your locations and partners. Plants, warehouses, dock doors, farms, the “who and where” for every event.
4. Capture lot and date at production. Tie a batch/lot number and production date to the GTIN at the point of make, so every unit can be traced to a run.
5. Apply SSCCs and GS1-128 labels to logistic units. Serialize pallets and cases so a physical unit can be tracked and reconciled at each handoff.
6. Share the data in a standard format. Use GDSN for product master data and EPCIS or standardized documents for event data, so KDEs move with the goods.

Where do GS1 programs break down?

Almost never in the numbering scheme, in the capture. Assigning GTINs and GLNs is a one-time setup. The hard part is reliably recording the lot and date on every unit, at every shift, and passing accurate KDEs at every handoff. A traceability system is only as good as the weakest event in it, and the weakest event is usually a hand-written lot code that got smudged, skipped, or transcribed wrong at 2 a.m.

That is a floor-data problem, not a barcode problem. When lot codes, production times, and pallet builds are captured on paper and re-keyed later, the GS1 label on the pallet inherits whatever error crept in upstream, and a recall that should scope to one lot balloons to a week of product. Plants that capture production and lot data digitally at the line feed clean, time-stamped data straight into their labels and trading-partner messages. That is the foundation Harmony builds for food and beverage manufacturers, paper logs and lot sheets become live, searchable records with no rip-and-replace, the way one manufacturer replaced paper production logging and automated its daily reporting. GS1 gives you the language; clean capture is what makes the sentences true. For the broader picture, see traceability in manufacturing and how it supports HACCP and GFSI programs. Producers earning a farm certificate like GLOBALG.A.P. increasingly adopt the same GTINs their retail buyers require.