"Connected packaging" is used for everything from a recipe QR code to a full supply-chain record. That breadth causes confusion in planning meetings: one person means a loyalty scheme, another means pallet tracking. A simpler way to think about it is in three layers — identity, traceability and engagement — each answering a different question.
Layer 1: Identity — what is this?
Every connected product starts with a product identity: an unambiguous answer to "what is this item?"
GS1 standards provide the vocabulary:
- a GTIN identifies the product type, such as a 90 m coil of 2.5 sq mm house wire;
- a batch or lot identifies a production run;
- a serial number, together with the GTIN, identifies one individual item;
- an SSCC identifies a logistic unit such as a carton or pallet.
The identity then needs a carrier: a linear barcode, a GS1 DataMatrix, or a QR code carrying a GS1 Digital Link, which expresses the identity as a web address. The full set of identifiers is explained in GTIN, batch, serial, SSCC and GLN explained.
Identity is created mostly at two moments: when the brand assigns numbers in its product master, and when the packaging line prints variable data such as batch and serial on each pack.
Layer 2: Traceability — what happened to it?
An identity on its own is a snapshot. Traceability turns it into a history: where the item was made, which carton and pallet it was packed into, when it shipped, where it was received.
Two ideas carry most of the weight:
- Aggregation records parent–child relationships: these units are in this carton, these cartons are on this pallet. It lets a warehouse scan one label and know what is inside. See what aggregation in traceability is.
- Events record what happened, when, where and why. GS1's standard for capturing and sharing such events is EPCIS, with a shared vocabulary (CBV) for business steps such as commissioning, packing, shipping and receiving. See what EPCIS is.
Traceability data stays with the businesses that create it and is shared with trading partners by agreement. Consumers rarely see it directly.
Layer 3: Engagement — what can people do with it?
Engagement is what happens when a person scans the code. A resolver behind the Digital Link connects the identity to one or more services: product information, instructions, product registration, loyalty, recall status, reviews.
Different people want different things from the same code. A shopper wants product facts; an electrician wants loyalty points; a service centre wants installation history. GS1's Web Vocabulary gives these services shared link types, so one printed code can lead to all of them. How that works is covered in how one product identity can lead to product info, warranty, loyalty and traceability.
How the layers build on each other
The layers are a stack, not a menu. Each one depends on the one below.
| Layer | Question it answers | Main GS1 standards | Typical systems | Typical owner |
|---|---|---|---|---|
| Engagement | What can people do with it? | GS1 Digital Link, resolver standard, Web Vocabulary | Product pages, loyalty, warranty, CRM | Marketing, customer service |
| Traceability | What happened to it? | EPCIS, CBV, SSCC, GLN | Event repository, WMS, ERP | Operations, supply chain |
| Identity | What is this? | GTIN, batch, serial, data carriers | Product master, packaging line | Product data, packaging |
Three consequences follow:
- Engagement can only be as precise as identity. A fictional cable brand, Volta Cables, wants to reward electricians once per coil. That needs a serial on each coil; a GTIN-only code cannot tell one coil from the next.
- Engagement becomes richer when traceability exists. If Volta records which batches went to which distributor, a scan can show the right recall notice or reveal that a coil meant for one region was sold in another.
- Traceability needs identity printed reliably. If codes are unreadable or aggregation is skipped on the line, the history breaks before the product leaves the factory.
The whole stack in motion, from factory to consumer, is shown in the connected product journey.
Where authentication fits
It is tempting to add "authentication" as a fourth layer. It is better understood as a control built from all three. A unique serial (identity), a record of where that serial was supposed to go (traceability) and monitoring of who scans it and where (engagement) together make copying harder to hide. None of them, alone, proves a product is genuine.
Choosing where to start
You do not need all three layers at full depth on every product.
- A food brand with expiry concerns might start with GTIN plus batch (identity) and a consumer page that shows freshness information (engagement).
- An electrical brand running trade loyalty needs serials (identity) and a loyalty service (engagement), and benefits from aggregation to know where coils went (traceability).
- A brand selling to retailers that ask for shipment data may invest first in SSCCs, aggregation and EPCIS (traceability), with consumer engagement later.
Whether unit-level serials are worth it is a business decision, discussed in do all products need serialization?.