How One Product Identity Can Lead to Product Info, Warranty, Loyalty and Traceability

Many brands have three or four QR codes in circulation already: one for the product page, one for a warranty form, one for a loyalty scheme, perhaps one on the carton for the warehouse. Each was added by a different team, and each leads somewhere different. A GS1 resolver offers a cleaner pattern: one product identity, printed once, that can lead to all of those services.

This article explains how that works, which services fit naturally, and how to give each audience the right level of access.

The principle: one identity, many links

A GS1 Digital Link on a pack carries the product's identity: its GTIN, and optionally its batch and serial number. When a phone opens it, a resolver looks up the links registered for that identity.

Under the GS1-Conformant Resolver Standard, an item can have many links. Each has a target address, a link type and a title. Exactly one is the default, used when a scan asks for nothing in particular. Other links are requested by type, and the full list — the linkset — can be requested by software that wants to see everything on offer. The mechanics are covered in what a GS1 resolver is.

A worked example: a mixer grinder

Take a fictional appliance brand, Orbit Kitchenware, selling a mixer grinder through shops and online. Each unit's box carries a QR code with a Digital Link containing the GTIN, batch and serial number. Behind that one identity, Orbit registers several links:

A shopper in a store scans and lands on the product page. A new owner at home taps "register my product" and arrives at the registration form, with the serial number already known. A shop's sales assistant opens Orbit's trade app, which asks the resolver for the loyalty link. A service centre's system asks for traceability. All of them start from the same printed code.

Matching each service to the right identity level

A useful discipline is to ask, for each service, "what is the smallest thing it needs to know?"

• Product information and instructions are the same for every unit of a product, so they belong at GTIN level. Thanks to inheritance "up the tree", links registered against the GTIN also answer scans of individual serialized units.
• Recall status usually concerns a production batch. Registering a recall link against just the affected batch lets the brand warn the right owners without alarming everyone else.
• Warranty registration is personal to one unit. A serial in the code lets the form know exactly which appliance is being registered and spot an attempt to register the same unit twice.
• Loyalty that rewards a scan once per item needs the serial for the same reason; a GTIN alone cannot tell one box from the next. Loyalty design is covered in how product identity can support loyalty and rewards, and warranty in warranty registration through connected packaging.
• Traceability may work at batch or serial level depending on how the brand records supply-chain events. The detailed history itself lives in EPCIS systems that the brand and its partners run; a gs1:epcis link points to that source rather than copying it.

Not every product needs every level. A detergent brand may only ever need GTIN and batch. The point is to choose deliberately, because the identity printed on the pack limits what services can later do.

Audience-appropriate access

Different users should see different things. A consumer should see recipes and recall notices; a distributor might see shipment history; nobody outside the company should see production yields.

The resolver's job is to direct each request to the right place. It is not where access control lives. In practice:

• Public services — product information, instructions, recall status — can be open to anyone who scans.
• Customer services — warranty, loyalty — ask the person to sign in, verify a phone number or otherwise identify themselves at the destination.
• Partner services — traceability data, service records — sit behind business authentication at the destination, granted per partner.

A linkset tells anyone who asks that a traceability service exists for this product. That is fine; knowing the door exists is not the same as having the key. What matters is that the service behind the link checks who is asking. Keep confidential information out of link titles, since those are part of the published list.

Use the shared vocabulary

The link types in the table come from the GS1 Web Vocabulary. Others defined there include gs1:faqs, gs1:review, gs1:promotion, gs1:sustainabilityInfo and gs1:certificationInfo. Their value is that they are shared: a retailer's app or a repair platform can ask any conformant resolver for gs1:instructions and get a predictable answer. Regulatory information is a growing reason to plan for several audiences: for the product groups it covers, the EU's Digital Product Passport links a product to sustainability and compliance data through a code on the product or its packaging.

Be careful with two things. First, do not invent new names and present them as GS1 terms. Second, do not read more into a name than it says. For example, gs1:verificationService points to a service that checks the status of an identifier — whether the number is valid and known — not whether the physical product is genuine. Anti-counterfeit checks are a separate design question, covered in product verification vs authentication.

How the services evolve over time

The services behind a product change far more often than its packaging. A new loyalty scheme launches, the instruction videos are refreshed, a recall begins and later ends. Because each of these is just a link, the brand updates the resolver and every pack already in circulation follows. Keeping the identity separate from these experiences is a design principle in its own right, explained in why brands should separate product identity from the digital experience.

For a wider view of how identity, traceability and engagement fit together as layers, see the three layers of connected packaging.