GS1 Digital Link QR codes: the barcode that also opens a web page
Strip the standards language and a GS1 Digital Link is a normal https URL with GS1's identifiers arranged in the path. The product identifier GTIN sits under /01/, a production batch under /10/, a serial number under /21/. A code pointing at https://yourbrand.example/01/0950600014347 opens in any browser like any other link, and a 2D-capable till can read the same square and extract the GTIN it needs. There is no proprietary format to license and no special symbology: it is a QR code encoding an ordinary web address that happens to be built to GS1's rules. Any QR generator that takes a URL can produce one, including the generator on this site; what makes it a GS1 Digital Link is that the URL is built from your GS1 identifiers and resolves at a domain you control.
The date that matters is the end of 2027: GS1's industry guidance asks that retailer point-of-sale systems be capable of scanning 2D barcodes by then, in the UK, the US and across GS1's member organisations. Until retailers are fully there, packs in transition typically carry the existing EAN-13 or UPC alongside the QR code, then drop the linear barcode once the category's retail channels are confident. The artwork implication is real but bounded: one more code on the pack for a transition period, and a planned end state where the 2D code is the only barcode on the shelf edge and the pack.
| Path | What it identifies | What it buys |
|---|---|---|
| /01/GTIN | The product, to GTIN precision | Till-readable product code plus a consumer product page: the minimum viable Digital Link |
| /01/GTIN/10/BATCH | The product and its production batch | Adds recall scoping and shelf-life traceability to the same printed square |
| /01/GTIN/21/SERIAL | The individual unit | Unit-level traceability for warranty, authenticity and registration flows |
The GTIN's home becomes your domain, not GS1's and not a code vendor's, which quietly makes the QR code's destination part of your infrastructure. That domain has to resolve, on TLS, indefinitely, for every pack in the field. Brands already running their own product pages on their main domain are mostly done. Brands considering a redirect service should think about it the way they think about their website: uptime, expiry and what happens if the vendor disappears. A dynamic code adds a redirect hop with edit-anywhere flexibility, which is the right trade-off for consumer-facing panels and for surviving artwork mistakes; whatever resolution path you choose, the register of which GTIN maps to which URL belongs in your own records, not only in a tool's database.
Treat till-facing codes as infrastructure, not marketing
A shopper-facing code that fails is a missed visit. A till-facing code that fails is a failed scan at a checkout queue, and the retailer's response is not sympathy. If the same printed code serves both, its resolution path has to be dependable enough for the till, which argues for conservative infrastructure decisions: your own domain, boring hosting, and change control on the destination. There is nothing wrong with running two codes in transition, one resolved for the till and one for marketing, if the two needs genuinely pull apart.
The URL is text, so a set of Digital Link codes is a spreadsheet job: one row per SKU, the full Digital Link URL built from the GTINs in your GS1 account, a label per file. Run it through the bulk generator, size the output for the substrate, and export SVG at the die-line size with a manifest mapping every file to its GTIN for the artwork studio. Two checks before it reaches artwork: that every GTIN in the sheet is one you actually own, and that each URL resolves today, because the code will faithfully encode whatever the spreadsheet says.
Adding a Digital Link code to the next artwork round
Pull GTINs from your GS1 account
Only identifiers allocated to you, matched to the SKUs actually going on the artwork.
Decide the path depth
GTIN alone for most packs; add batch if recall scoping matters, serial only where unit identity genuinely pays.
Build and test the URLs
Every URL in the sheet must resolve in a browser before it is encoded in anything.
Generate at final size, as vector
SVG at the millimetre size the panel allows, quiet zone respected, manifest checked against the sheet.
Proof with a real 2D reader
Scan the press proof with a phone and, where you can, a retail-grade 2D scanner, since the till is the stricter reader.