1. The URI structure
Every Digital Link URI follows the pattern:
https://{domain}/{primary key AI}/{value}/{qualifier AI}/{value}?{attribute AI}={value}
The primary key identifies the thing (usually a GTIN, normalised to 14 digits). Key qualifiers narrow it down (variant → batch → serial, in that order). Data attributes such as dates go in the query string.
2. Common Application Identifiers
| AI | Meaning | Position |
|---|---|---|
| 01 | GTIN | Primary key (path) |
| 22 | Consumer product variant | Qualifier (path) |
| 10 | Batch / lot | Qualifier (path) |
| 21 | Serial number | Qualifier (path) |
| 17 | Expiry date YYMMDD | Attribute (query) |
| 15 | Best before YYMMDD | Attribute (query) |
| 414 | GLN — location | Primary key (path) |
| 00 | SSCC — logistic unit | Primary key (path) |
3. Resolver or no resolver? Three ways people use the same QR code
Look at the packs on a shelf today and you'll find three different levels of sophistication behind the QR code. They can all coexist with a 2D barcode programme — the difference is what happens on the server side. (Note: a retail POS scanner never goes online — it parses the GTIN and other AIs straight out of the URI for checkout.)
Level 1 — Just a link (no resolver)
The QR code simply encodes an ordinary web address such as https://yourbrand.com/products/widget. This is what most brands do today: point the code at a product page, a landing page or a PDF. You can set it up in an afternoon with any free QR generator, and there is nothing to maintain.
The trade-offs: the code is not a Digital Link, so a till scanner or a retailer's app can't recognise the product by its GTIN. The destination is frozen into the artwork — if the URL changes, you reprint. And one code gives everyone the same experience.
Level 2 — A Digital Link URI with simple redirects (no resolver, really)
The QR code encodes a genuine GS1 Digital Link URI on your own domain, for example https://yourbrand.com/01/09506000134352/10/ABC123. A plain redirect rule — the kind you can add to any web server, CDN or static host — sends it to the product page.
This is the sweet spot for "cheap and standards-based": the identifiers are now machine-readable, so any GS1-aware scanner, retailer app or regulator tool can parse the GTIN, batch or serial straight from the code. Because the destination lives in a redirect rule rather than the printed artwork, you can change where it goes without reprinting. It still answers with the same page for everyone, though.
Level 3 — A true resolver
A resolver is an application, not just a redirect rule. It uses the product identifiers, available typed links and request preferences (such as the case-sensitive linkType parameter) to select a destination, or return a directory of resources called a linkset. Those resources can include instructions, FAQs, recipes, registration and product data. Apps must request and interpret these resources; the resolver does not automatically know who is asking. Read the detailed GS1 resolver guide for the standard's discovery and support mechanisms.
4. Quick and cheap now, future-ready later
The good news: you don't have to choose once and forever. A Digital Link URI never needs to change — the intelligence behind it can grow over time. A pragmatic ladder looks like this:
| Level | What you do | Effort | What you get — and can't yet do |
|---|---|---|---|
| 1. Plain QR | QR code → existing product page | Hours, free | Instant consumer link. Not machine-readable, destination fixed at print time. |
| 2. Digital Link + redirect | Encode a real Digital Link URI; add a redirect rule on your domain | A day, near-free | Machine-readable GTIN/batch/serial; destinations changeable without reprinting. |
| 3. Managed resolver | Route by linktype, language, app and qualifiers — SmartLinks.app does this for you | Days, low running cost | Different content for different scanners; recall-by-batch; scan analytics. |
| 4. Full data platform | Return structured data, connect to registries and DPP systems | Ongoing project | Ready for Sunrise 2027 POS scanning, EU DPP and machine-to-machine consumers. |
Most brands should start at Level 2 or 3 with their next packaging refresh. The printed code stays the same while the behaviour behind it levels up — that is the core promise of Digital Link.
5. Giving data back, not just web pages
A resolver doesn't have to answer with a web page. Depending on who is asking, it can return machine-readable responses:
- Schema.org / JSON-LD product data — so search engines, shopping platforms and AI assistants understand exactly what the product is, without guessing from page text.
- GS1 link type responses — the same URI answers differently when a retailer app asks for "product information" versus a consumer app asking for "instructions", as defined by the GS1 Digital Link standard's link type vocabulary.
- Supply chain data — batch, expiry and serial lookups that regulators, marketplaces and traceability systems (including FSMA 204 and Digital Product Passport programmes) can consume directly.
That last step is the "future" part: the code on pack becomes an API for the product. Everything printed today keeps working as you add these responses behind the scenes.
6. Link types
One product can have many destinations. Resolvers use GS1 "link types" (for example product information, instructions, recall status or certification info) so different apps can request the specific content they need from the same code — the mechanism behind Level 3 and 5 above.
For the actual terms — including gs1:recipeInfo, gs1:faqs, gs1:instructions and gs1:registerProduct — see link types, app discovery and customer support in detail. The guide also explains why a linkset is different from structured data on a product page.
7. Your domain or GS1's
You may use any domain you control. Using your own brand domain gives you analytics and control over the experience, and keeps you free to swap resolver vendors later. A managed resolver such as SmartLinks.app lets you start at Level 3 without building infrastructure.
Try encoding your own: open the Digital Link builder.