Anyone working in product, ecommerce or compliance recognises two things on a piece of packaging: the barcode that has been there since the 1970s, carrying an identifier a till can read, and the QR code that has been there for the last decade, usually opening a webpage. What gets less attention is the standard that connects them. GS1 Digital Link is the URI syntax that turns a product identifier into a web address, so the same code can be read by a supermarket checkout, a consumer’s phone, a regulator’s scanner and an AI assistant pulling product data on the fly.

It matters because the same URI syntax sits underneath three things that brands have to address in the next two years: the Digital Product Passport regime under ESPR, the Sunrise 2027 transition at retail point of sale, and the wider question of how product data is published in a form that AI assistants and trading partners can read. The available writing on the standard tends to come from GS1 themselves or from vendors selling QR generators. This piece is the implementer’s view, written by a team that’s been building on it for the last year.

What it actually is

A GS1 Digital Link URL is a web address structured around a GTIN, the same Global Trade Item Number that already sits behind the linear barcode on the back of the pack. The shape looks like this:

https://example.com/01/09506000164908

The /01/ is a GS1 application identifier. In GS1 syntax, 01 means “GTIN”. The fourteen digits that follow are the GTIN itself. Any system that knows the standard can read the URL two ways at once: a browser sees a web address and opens the page, while a scanner sees a GS1 data structure and extracts the GTIN without ever loading anything. That dual readability is the property the standard exists to provide.

This is the smallest possible Digital Link URL. The standard supports two extensions:

https://example.com/01/09506000164908/10/B2426
https://example.com/01/09506000164908/10/B2426/21/SN001234

The /10/ segment carries a batch or lot number; the /21/ segment carries a serial number for an individual item. The first URL above identifies a specific batch of a specific product type, and the second narrows further to one individual item within that batch. The three levels (GTIN, GTIN-plus-batch, GTIN-plus-serial) match the granularity hierarchy used in DPP regulation, where facts about a product type sit at the GTIN level and inherit downward through batch and item without needing to be restated.

The full standard supports more application identifiers (expiry date, country of origin, weight, dimensions and others), but in practice GTIN, batch and serial cover the publishing surface a brand needs.

What it lets you do that a plain QR code doesn’t

A QR code can encode any string. A plain URL inside a QR code points at a single page controlled by whoever owns the domain, with no structure beyond the URL itself. The page can move, the brand can change name, the domain can change owners, and the QR code is dead the moment any of those happen. A regulator wanting to verify the product identifier from the URL can’t, because the identifier isn’t in there in any standard form.

A GS1 Digital Link URL is different in two ways that matter.

The identifier is in the URL in a form any standards-aware system can read. A regulator’s scanner, a marketplace’s catalogue importer, an AI assistant ingesting product data, a customs system in another jurisdiction: each of them can extract the GTIN from the URL without ever loading the page. The web address is also a data structure.

The identifier persists independently of the domain. If example.com ever disappears, the GTIN is still recognisable. The Digital Link resolver standard provides a mechanism for redirecting any GTIN to its current authoritative URL, through a network of resolvers operated by GS1 member organisations and by individual brands. The product survives the website.

Scan then select

The other useful property of the standard is what GS1 calls “scan then select”. One QR code on a product can resolve to multiple destinations depending on who’s scanning it. A consumer scanning at home might be sent to the marketing page, a trade buyer to the technical datasheet, a regulator to the passport, a repair partner to the service manual. The same physical QR routes to the right destination based on who’s asking and what link types the brand has chosen to publish.

The mechanism is straightforward: the brand operates a resolver at the domain in the URL, and when a scan hits the resolver, the resolver looks at the request headers, the language settings and sometimes a query parameter before returning the appropriate link. Brands can publish their available link types via a standardised endpoint (/01/<GTIN>?linkType=all), which lists what’s resolvable for that product.

This breaks the working assumption that a QR code on a product needs to point at one fixed page. It can point at as many pages as the brand cares to maintain, with one code, one resolver and a list of link types.

Where it connects to ESPR

The ESPR (EU Regulation 2024/1781) requires Digital Product Passports for an expanding list of categories from 2027 onward. The regulation talks about a unique product identifier resolvable via a data carrier. It doesn’t mandate Digital Link by name, but the GS1 standards documents published in collaboration with the European Commission make it the practical answer. The reasons are circular but solid: GS1 is the global authority that issues GTINs, GTINs already sit on the linear barcode of every product placed through general retail, and Digital Link is the URI syntax GS1 has standardised for resolving them.

A passport URL conformant to ESPR is, in practice, also conformant to GS1 Digital Link. A brand that adopts Digital Link now is doing the foundational work that 2027 compliance will require, and getting the benefit of it earlier through the consumer and trade-facing applications the same identifier supports.

Where it connects to Sunrise 2027

Sunrise 2027 is GS1’s industry-wide transition to 2D barcodes (QR codes powered by GS1 Digital Link) as the primary data carrier across global retail. The endpoint is that checkout scanners worldwide will read 2D codes natively for till transactions, replacing the linear barcode that has done the job for fifty years. The published programme covers 51 countries representing 90 per cent of global GDP.

The practical implication is that the 2D barcode on a product won’t be a separate marketing addition; it will be the primary identifier the till reads at the checkout. A brand printing a QR code on the pack today, on a GS1 Digital Link URL, is printing the code that will work at checkout in 2027 and at the same time work in every other context the URL supports: passport access, consumer information, regulatory verification, conversational PDPs, third-party catalogue ingestion.

A brand printing a QR code today on a domain that doesn’t follow the standard is printing a code that will need to be reprinted before 2027.

What changes for the brand adopting it

Three things move when a brand starts publishing on Digital Link URLs.

The data infrastructure has to be designed around the GTIN as the resolved identifier, not around the SKU, the internal product code or the slug from the ecommerce CMS. The GTIN becomes the primary key, and everything that resolves from a Digital Link URL has to be addressable through the GTIN-batch-serial hierarchy.

The web infrastructure has to include a resolver. This is a small piece of software (a few hundred lines, in our experience) that sits between the QR scan and the destination page. It reads the Digital Link URL, identifies the link type requested, decides which destination to return, and either serves the content directly or redirects to it. Modern hosting platforms make this straightforward; the work is in the routing logic and the catalogue of available link types, not in the standard itself.

The catalogue of available link types has to be maintained. Each product can have a passport URL, a marketing page URL, an instructions URL, a warranty URL, a conversational interface URL, a returns URL and so on. The list is the brand’s choice and grows over time. Keeping it accurate is an operational discipline that didn’t exist before, because there was previously only one destination per QR.

These are real pieces of work but none of them are large. Brands that already have a structured PIM and a competent web team can adopt the standard in weeks rather than months.

Common questions

Do I need to be a GS1 member to use Digital Link URLs? In practice, yes. The URL syntax encodes a GTIN, and GTINs come from GS1, which is the only authorised issuing agency. Cost depends on company turnover and the number of GTINs needed. UK pricing is on gs1uk.org.

Can I use Digital Link with my existing domain? Yes. The standard works on any domain the brand controls. The structure /01/<GTIN> is the requirement; the domain in front of it is the brand’s choice.

What if my GTIN doesn’t have fourteen digits? Pad it with leading zeros to fourteen. A thirteen-digit GTIN-13 becomes the same number with a leading zero in the Digital Link URL. A twelve-digit UPC-A becomes the same number with two leading zeros. The standard is GTIN-14 internally even when the printed barcode is shorter.

How does this work for a product without a GTIN? It doesn’t, directly. Digital Link is built around the GTIN as the persistent identifier. Products without one (industrial parts, internal SKUs, prototypes) need a different identifier scheme. For the common case of a consumer or trade product, the GTIN already exists on the linear barcode.

Can a single QR code carry both a Digital Link URL and a separate marketing URL? No, only one URL per QR. The “scan then select” pattern handles multiple destinations from a single URL through the resolver, not through multiple URLs in one code.

Does the resolver have to be operated by the brand? No. The brand can operate its own resolver, or use a platform that operates one on its behalf, or use a GS1 member organisation’s resolver, or any combination. The standard is the URL syntax and the resolver behaviour, not the hosting arrangement.

Where this sits in the wider picture

GS1 Digital Link is one of those standards that looks abstract until it’s implemented and then looks obvious. The product identifier and the web address turn out to be the same thing, with the QR code acting as the bridge between the physical product and the data the brand publishes about it. The same code can carry the consumer to a marketing page, the regulator to a passport, the till to a price and the AI assistant to a structured datasheet, decided each time by the resolver at the brand’s domain.

For brands heading toward 2027, the practical advice is the same as for the wider DPP question: start the standards work now. The technical layer is well-defined and the tooling is mature; the harder work sits in the catalogue of destinations the brand wants to publish, and the data infrastructure that supplies them. Brands that begin in 2026 will have something running by the time compliance bites. Brands that start in 2027 will be doing the same work under more pressure and with fewer options.

The standard is settled and the resolvers are already in operation. The global retail transition has funding and a timeline. The remaining question for any brand is whether to start the adoption work now or wait until the timeline forces it.