Many brands already have QR codes on their packs. Most of them were added for a campaign: a contest, a recipe video, a launch page. They work well for a few months. Then the campaign ends, the agency changes, the website is rebuilt — and the code on thousands of packs starts leading somewhere stale, or nowhere at all.
This guide explains why that happens, what "connected product infrastructure" means instead, and how to move from one to the other without a disruptive reprint.
What a typical marketing QR looks like
Picture a fictional snack brand, Halden Foods. Its crisps packs carry a QR code that opens https://halden-summer.example/win — a contest microsite built by an agency. The code was designed by the creative team, approved with the artwork, and printed on every pack for the season.
That pattern is common, and it has some recognisable traits:
- It encodes a destination, not a product. Every flavour and pack size carries the same code.
- It is time-bound. The address was designed for one campaign.
- It is owned by one team — often through an agency or a third-party platform.
- It sits beside the barcode, not with it. Retail systems cannot read anything useful from it.
None of this is wrong for a short campaign. The trouble is that packs outlive campaigns.
Where marketing QR codes fall short
When Halden's contest ends in September, packs printed in July are still on shelves in November. Scans now lead to an expired microsite. Next year, the brand wants a recall message for one production run of one flavour — but every pack carries the same code, so it cannot tell one batch from another. The quality team asks for a separate code. Then the trade team wants one for retailer loyalty. The pack starts collecting QR codes.
The deeper issue is that the code carries no product identity. It cannot tell the brand which product was scanned, it cannot serve the checkout, and it cannot be reused by anyone other than the team that created it.
What connected product infrastructure means
Connected product infrastructure starts from the opposite end: the code identifies the product, and everything else is a destination behind it. It is what connected packaging looks like when it is built to last.
- The code carries a GS1 Digital Link built from the product's GTIN and, where useful, its batch. For example,
https://id.halden.example/01/09506000134376/10/L2609. - The domain belongs to the brand, chosen to last as long as the packs.
- A resolver decides where each scan goes today — the product page by default, a campaign while it runs, a recall notice for one affected batch.
- Several teams share it. Marketing runs campaigns through it, quality uses it for notices, trade marketing for loyalty, and supply chain for traceability.
The GS1 basics are explained in what GS1 Digital Link is, and the full route from factory to phone in the connected product journey.
Side by side
| Marketing QR | Connected product infrastructure | |
|---|---|---|
| What the code identifies | A campaign page | The product (and optionally batch or serial) |
| Lifespan | The campaign | The life of the pack |
| Different products | Often the same code | Different codes, one per GTIN or finer |
| Changing destination | New code or broken link | Change the resolver's links |
| Who uses it | One team | Marketing, quality, trade, supply chain |
| Checkout | Cannot use it | A 2D-capable POS can read the GTIN from it |
| Domain owner | Often an agency or platform | The brand |
The checkout row deserves a note. A QR code carrying a GS1 Digital Link is one of the 2D symbols approved for retail POS scanning, and the till extracts the GTIN offline without visiting any website. During the transition, GS1 rules require the linear barcode to stay alongside the 2D code. How one code can serve both shopper and checkout is explained in why the same GS1 2D code can work for checkout and consumers.
How to evolve, step by step
Very few brands can reprint everything at once, and none needs to. A practical sequence:
- Inventory what is already printed. List every QR code in circulation, what it points to, who controls the domain, and roughly how long those packs will stay in the market.
- Keep existing codes alive. Point expired campaign addresses to a sensible current page. Make sure the domains stay registered to the company.
- Choose your identity domain. Pick a domain or sub-domain the brand will own for years and that is not tied to any campaign.
- Decide the identity level per product line. GTIN alone suits product information; batch adds recall targeting; serial adds unit-level loyalty and warranty but requires changes on the packaging line.
- Switch at the next artwork change. Replace the campaign code with a GS1 Digital Link as each pack is redesigned anyway.
- Start simple behind the code. A single default page per product, reached through a plain redirect, is a legitimate first step; resolver vs redirect explains when you will need more.
- Agree who changes links. Give marketing control over campaign destinations, quality over notices, and IT over the domain, with a record of who changed what.
For brands in India moving existing QR programmes this way, how existing QR programmes can evolve toward GS1 Digital Link covers the local context.
What does not change
Marketing still owns the experience. Campaigns, contests, content and creative work all continue; they simply become destinations behind a stable identity rather than being printed into the pack. What changes is that the brand stops throwing away the most durable piece of real estate it has every time a campaign ends. Why that matters commercially is the subject of why the product identity should outlive the marketing campaign.