A sheet of decorative laminate can sit in a warehouse for months, then on a kitchen wall for many years. The QR code on its back is fixed the day it is printed. The website it leads to, the brand's warranty process and its campaigns will all change several times in that period. This article explains why brands should keep those two things — the printed identity and the digital experience — deliberately apart, and what that means in practice.
Two clocks running at different speeds
Everything printed on a pack runs on a slow clock. Artwork is approved months ahead, packs are produced in batches, and products stay in homes, shops and building sites long after they are sold.
Everything digital runs on a fast clock. Websites are redesigned, campaigns last weeks, loyalty schemes are relaunched, agencies change, and a recall can appear overnight.
Problems start when a pack carries something from the fast clock. A QR code that encodes a campaign address dies with the campaign. A code that encodes a page on last year's website breaks when the site is rebuilt. The pack is still in someone's hands, but the code now leads nowhere.
Print identity, resolve experience
The alternative is to print only what will stay true: what the product is. A GS1 Digital Link does exactly that. It is a web address built from the product's GTIN and, where needed, its batch and serial number, such as:
https://id.suryalaminates.example/01/09506000134369/10/B2611
That address says nothing about campaigns or page layouts. It names the product (and here, the production batch) on a domain the brand controls. A resolver sitting behind that domain then decides where the scan should go today. The GS1-Conformant Resolver Standard gives every identified item exactly one default link, plus any number of typed links, and those can all change without touching the printed code. The mechanics are explained in what a GS1 resolver is.
For the fictional brand Surya Laminates, that means:
- this year, a scan opens a product page with design inspiration;
- next year, after a website rebuild, the same scan opens the new page;
- if a batch has a finishing defect, scans of that batch alone open a service notice;
- a contractor's app asks for installation instructions using the
gs1:instructionslink type, from the same code.
The pack never changed. Only the links did.
Choosing the domain: a long-term decision
The domain printed in the code is the one part of the address the brand chooses freely, and it lasts as long as the pack. GS1 recommends that brands use their own domain. Some practical guidance:
- Use a domain the company owns outright, registered to the company rather than to an agency, freelancer or campaign platform.
- Consider a dedicated sub-domain such as
id.on the brand's main domain. It keeps scan traffic separate from the marketing website and makes it easier to move the resolver to a different provider later. - Avoid campaign or product-launch domains. They tend to lapse once the campaign is over.
- Renew and monitor it like a licence. A lapsed domain is not just a broken link; someone else could register it and receive your customers' scans.
GS1 also operates id.gs1.org, which describes itself as "The GS1 AISBL Resolver", and the canonical form of a Digital Link uses that domain. That is useful for comparing and exchanging identifiers, but GS1's guidance for packs is to use the brand's own domain, and the resolver standard does not describe id.gs1.org as a host for brands' consumer content.
Keep every issued address alive
Once an address is printed, the brand is responsible for it for as long as the pack might be scanned. A few habits make that manageable:
- Keep an inventory of every pattern of address ever printed — which domain, which identity level, which product range, from which date.
- Never let an address return nothing. If a destination is retired, point the link to the product's current page. The standard's rule of exactly one default link per item helps here: there is always somewhere to go.
- Use inheritance, not exceptions. Links registered at GTIN level also answer batch- and serial-level scans that have no links of their own, so retiring a campaign often means removing one link rather than editing thousands.
- Test before changing routing. Scan real packs from each era after any migration, on real phones, before announcing the change.
- Watch for errors. A sudden rise in "not found" responses for an old address pattern usually means something was missed in a migration.
Decide the identity level before you print
The digital experience can change endlessly, but the identity on the pack cannot be enriched later. A pack printed with a GTIN-only code can never tell one unit from another, so it cannot later support one-time loyalty claims or unit-level warranty. A batch in the code makes targeted recall messages possible; without it, every scan of the product looks the same.
This is a packaging and factory decision as much as a digital one, because batch and serial values are printed on the line. Practical preparation is covered in how to prepare your packaging for the next generation of product identity.
What this does not change
Separating identity from experience does not mean the code becomes a security feature; a copied code resolves just like the original. It also does not affect the checkout: a 2D-capable till reads the GTIN straight from the address and prices it from the retailer's own system, whatever the resolver is doing.
The business case in one sentence
The printed identity is an asset that should outlive any single campaign, website or supplier — the business side of that argument is set out in why the product identity should outlive the marketing campaign. If you are deciding how much resolver capability you need on day one, resolver vs redirect shows when a simpler setup is enough.