The barcode on a retail product is being replaced by a URL. Not a picture of a URL printed next to the barcode, but the product identifier itself, written as a web address that a phone can open and a checkout scanner can still read.
That is what a GS1 Digital Link does. It takes the GTIN — the number inside a product's barcode — and expresses it as a structured URL. The same QR code then works two ways: a point-of-sale scanner reads the product number, and a shopper's phone opens a web page.
If you build anything that touches retail, packaging, inventory, or traceability, it is worth understanding how this works. This post covers the URL structure, how a resolver handles it, and how to create one.
The direction is set, so start there
GS1 — the organization behind the UPC and EAN barcodes on nearly every retail product — has a stated long-term goal: move retail from the 1D barcode to 2D barcodes that carry a GS1 Digital Link. Its milestone for that transition is Sunrise 2027: the point by which retailers aim to accept 2D barcodes at checkout.
The nuance matters for anything you build:
- It is a direction, not a deadline for the end of the 1D barcode. The existing UPC stays in use for years.
- During the transition, packaging carries both: the current 1D barcode and a GS1 Digital Link QR code beside it. The term for this is dual marking.
- A brand that dual-marks now keeps scanning at every checkout exactly as it does today with the traditional 1D barcode, while putting a web-native identifier (GS1 digital link QR code) in place for where retail is heading.
So no one removes a working barcode. But the trajectory is real, and it is why these codes are starting to appear on packaging. The part worth your attention is what that second mark can do.
One QR code, two readers
A GS1 Digital Link is a structured URL. The canonical form looks like this:
https://id.example.com/01/09506000134352
The /01/ is not an arbitrary path. 01 is the GS1 Application Identifier for a GTIN (Global Trade Item Number — the number encoded in a product's barcode). The full grammar supports more:
https://id.example.com/01/{GTIN}[/10/{lot}][/21/{serial}][/17/{expiry}][?linkType=...]
-
01→ GTIN -
10→ batch/lot -
21→ serial number -
17→ expiry date (YYMMDD)
The GTIN sits in the URL as plain text, which is what makes the dual-read work:
- A 2D-capable retail scanner at checkout reads the GTIN out of the string and ignores the rest. To the point-of-sale system it is a product number, the same as the old barcode provided.
- A shopper's phone camera sees a normal URL and opens it in a browser.
The same QR code serves both readers. One takes the product number, the other opens the URL.
One caveat, so this is not oversold: whether a given store's checkout actually reads the 2D code depends on that retailer's POS hardware and its product file. That is the Sunrise 2027 work happening on the retail side, not something the packaging forces on its own. The brand's job is to put a conformant mark on the package. The checkout side belongs to the retailer and GS1.
What happens when the phone opens the URL: the resolver
When a phone opens https://id.example.com/01/09506000134352, it does not land on a static page. It reaches a resolver — a service that performs content negotiation on the product identifier. The standard defines how it behaves.
A browser is redirected to the default destination:
curl -sI "https://id.qrchameleon.com/01/09506000134352"
# HTTP/2 302
# location: https://cascadeharvest.example/granola/maple-pecan
# cache-control: no-cache
Request a specific link type, and it routes to that one instead:
curl -sI "https://id.qrchameleon.com/01/09506000134352?linkType=gs1:recipeInfo"
# HTTP/2 302
# location: https://cascadeharvest.example/granola/maple-pecan/recipes
Request all of the links, and the resolver returns a linkset as JSON (RFC 9264 application/linkset+json):
curl -s "https://id.qrchameleon.com/01/09506000134352?linkType=all" \
-H "Accept: application/linkset+json"
{
"anchor": "https://id.qrchameleon.com/01/09506000134352",
"resolverRoot": "https://id.qrchameleon.com",
"supportedLinkType": ["gs1:pip", "gs1:recipeInfo", "gs1:instructions", "gs1:traceability", "gs1:promotion"],
"linkset": [
{
"anchor": "https://id.qrchameleon.com/01/09506000134352",
"gs1:pip": [{ "href": "https://cascadeharvest.example/granola/maple-pecan", "title": "Product page" }],
"gs1:recipeInfo": [{ "href": "https://cascadeharvest.example/granola/maple-pecan/recipes", "title": "Recipes" }]
}
]
}
The gs1: values are link types from the GS1 vocabulary: gs1:pip (product information page), gs1:recipeInfo, gs1:instructions, gs1:traceability, gs1:promotion, and others. One GTIN can resolve to different destinations depending on who is asking, what they requested, and in what language. A compliance system requests gs1:traceability; a shopper's browser falls through to the default product page; a marketing campaign points at gs1:promotion.
This is the part that behaves like an API. The QR code on the package is a stable key, the resolver is the routing layer, and the linkset is the configuration you can change at any time.
You can change the destination without reprinting
The printed QR code only ever encodes the GTIN-keyed URL. The destinations behind it live server-side in the linkset. That means:
- At launch, point
gs1:pipat the launch page. - Three months later, the same printed pouch resolves to a recipe hub.
- During a recall, change the default to a safety notice, on product that is already on shelves.
No new label, no new print run, no new QR code. And because every scan passes through the resolver, you get analytics on the physical product — where, when, and on what device it was scanned — which a 1D barcode cannot provide.
What "GS1-conformant" means
GS1 publishes a conformance test suite for resolvers. It checks the URI parsing, the content-negotiation rules, the linkset format, the /.well-known/gs1resolver descriptor, GTIN check-digit handling, and the redirect behavior — the full contract described above. A resolver either passes it or it does not.
This matters when you evaluate tools. Many "GS1 QR code generators" encode a Digital Link string and stop there. That produces a URL-shaped QR code, but not a conformant resolver behind it: no linkset negotiation, no typed-link routing, no tested behavior. Encoding the string is the simple part. The conformant resolver behind it is the larger part, and the part worth checking first.
(For disclosure: I work at QR Chameleon, and our resolver passed GS1's official conformance suite, Standard 1.2.1. The distinction between a string and a resolver holds regardless of which tool you use.)
Trying it yourself
You need two things to put a real GS1 Digital Link on a package: a GTIN, which you license from GS1 (no tool issues GTINs for you), and a resolver to point it at.
To see the mechanics end to end, you can create a product and its linkset over the API:
# 1. Register a product (the GTIN is validated, check digit included)
curl -X POST https://qrchameleon.com/api/v1/gs1/products \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "gtin": "09506000134352", "brand_name": "Cascade Harvest" }'
# 2. Add a default destination (a typed link)
curl -X POST https://qrchameleon.com/api/v1/gs1/products/{product_id}/links \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "link_type": "gs1:pip", "target_url": "https://cascadeharvest.example/granola", "is_default": true }'
Then open https://id.qrchameleon.com/01/09506000134352 and watch it redirect to your link, or append ?linkType=all to see the linkset. The free tier covers a couple of products, which is enough to wire the whole loop together. There is also a dashboard if you would rather not work through the API.
Why this matters now
Packaging outlives the software you write today. A package (CPG) designed this quarter stays on shelves for a year or more, and retail is moving toward 2D barcodes over that horizon. A GS1 Digital Link is how the product barcode and the web become the same thing.
Once your GS1 Digital Link QR code is created, you do not have to replace anything. Your existing barcode keeps working. The QR code beside it is both a product identifier (GTIN) and a web endpoint, which opens up recalls, traceability, dynamic campaigns, and per-item analytics, all keyed off a number that is already on the package.
The direction is set. The standard and the tools to build for it are available now.
The full write-up — dashboard flow, bulk GTIN import, linkset version history, and pricing — is on the QR Chameleon blog.
Top comments (0)