GS1 Digital Link: the data carrier behind the product passport QR code

What is GS1 Digital Link?

GS1 Digital Link is not software but a convention: it sets out how a GS1 identifier - as a rule the GTIN, the article number behind every classic barcode - becomes an ordinary web address that can be opened in a browser.

The structure is plain: a domain, an application identifier for the type of identifier, the value itself.

https://example.org/01/09506000134369

The 01 is the GS1 application identifier for the GTIN, and the digits after it are the article number. Batch, serial number or best-before date can optionally be appended - turning a model identifier into a batch or individual item identifier.

This is governed by the GS1 Digital Link URI Syntax standard, currently in Release 1.7.0 (ratified in August 2026); the previous version carried the version number 1.1.4. Both are freely accessible in the GS1 standards reference.

Decisive for understanding this: the QR code is only the data carrier. It transports a character string, nothing more. What that character string is worth is decided elsewhere.

Why a QR code alone is not enough

An ordinary QR code contains a fixed address and leads to exactly one page. That is sufficient for a campaign landing page - not for a product that will be scanned over years by very different parties.

GS1 Digital Link therefore places a resolver between the code and the content: a service that receives the URL and decides where the request goes. GS1 Germany describes the effect as allowing “different apps to read the same barcode but to route users to a completely different destination”. The GS1-Conformant Resolver Standard (Release 1.2.1, August 2026) formulates the rule: the request is forwarded to the default destination unless it contains something from which a better answer can be derived - language, app context, requested link type.

One code, four answers - without printing new labels. That is exactly what makes the standard interesting for the product passport, which by definition addresses several audiences at once. What this looks like is shown in our annotated DPP example.

GS1 Digital Link and the Digital Product Passport

The Ecodesign Regulation itself names no brand and no provider. It requires that the product information be “easily accessible by scanning a data carrier, such as a watermark or a QR code”, and that data carriers and identifiers should “comply with international standards” in the interests of interoperability - as set out in recitals 36 and 37 of Regulation (EU) 2024/1781. The fundamentals are explained in our article ESPR explained.

It only becomes concrete one level down. On 27 May 2026 CEN/CENELEC published six European standards for the product passport, including the two that govern exactly this question:

• EN 18219:2026 - unique identifiers for products, economic operators and locations, at model, batch or individual item level.
• EN 18220:2026 - data carriers, that is optical 2D codes, RFID tags and NFC chips, together with requirements for encoding and durability.

They are complemented by standards on storage, interfaces and interoperability; two security standards were still in the formal vote. You will find the full picture in our overview of DPP norms and standards.

GS1 Digital Link is therefore one possible implementation of these standards, not a replacement for them. The advantage lies in the ecosystem: the GTIN already exists in retail and is internationally standardised, and the ongoing move to 2D codes at the checkout - driven by GS1 under the banner Sunrise 2027 - is bringing QR codes onto packaging anyway. An important point of context: Sunrise 2027 is an industry initiative, not a law; GS1 Germany expects the across-the-board changeover only “from 2028”. Additional pressure comes from the EU Packaging and Packaging Waste Regulation (PPWR), Regulation (EU) 2025/40, which for certain labelling expressly provides for “a QR code or another type of standardised, open digital data carrier”.

The resolver - and the question of who owns the URL

This is where the most expensive mistake you can make during rollout lies - and it has nothing to do with technology.

A QR code that has been printed on tens of thousands of labels or sewn into garments can no longer be changed. It still has to resolve in five years’ time. Whoever controls the domain in that URL controls your product passports.

The decisive point: data export is rarely the problem - the standards on data exchange and interoperability now take care of that. The printed URL cannot be exported. It sits physically on goods that are already in the market, and it has to keep resolving even once the article has long since been sold or recycled.

We described this point in our DPP software comparison as the most frequently overlooked mistake, and nothing has since made it less relevant. Clarify it before the first print run, not at the end of the contract.

Do I absolutely need GS1 Digital Link?

An honest answer separates what is settled from what is open.

Settled: the product passport needs a data carrier and a unique identifier in line with international standards. EN 18219 and EN 18220 have been available since May 2026 - they describe requirements, not a single provider. GS1 identifiers meet them and are established in retail.

Open: what is specifically required per product group is set by the delegated acts - not yet adopted for most groups. Only there will it be stated which identifier level is required: model, batch or individual item. We track the dates in the deadline overview.

In practice this means: GS1 Digital Link is the dominant route, but not the only one. Anyone who already runs GTINs will use them. Anyone who has none should choose a solution that can retrofit a GS1-conformant URL structure later, without changing the labels - again a question of the domain, not of the standard.

What this means for small brands

GTINs are not free. They require a contract with the national GS1 organisation; at GS1 Austria this runs through GS1 Connect with a turnover-dependent annual fee that starts at 95 euros net for up to 1,000 GTINs, plus a one-off provisioning fee. For a brand with 200 articles that is manageable, but it is a recurring line item - not always justified for very small, purely direct-selling labels.

For a Shopify brand the realistic route looks like this:

1. Check what you already have. In many shops the GTINs have long been in the barcode field of the variants, because marketplaces or retailers required them - in which case the identifier question is settled.
2. Fix the domain. Before anything is printed: reserve a subdomain of your own brand for the product passport URLs.
3. Only then print labels. The data carrier is the last step, not the first. How this fits into shop processes is shown in our article on the DPP in e-commerce, and sector-specifically on the page DPP for textile companies.

Which requirements apply specifically to your product group is determined in a few minutes by the DPP configurator.

Checklist for the provider conversation

1. On which domain do my product passport URLs sit - and can I store my own subdomain instead?
2. Do you generate GS1 Digital Link conformant URLs in the current URI syntax, including batch and serial numbers?
3. Do you operate a conformant resolver that delivers different destinations depending on the request - or is it a simple redirect?
4. What happens to codes that have already been printed if I terminate? Is there forwarding assured in writing, and for how long?
5. How do you keep up with changes to EN 18219, EN 18220 and the delegated acts - and what does that cost?
6. Can I export my data in structured form, including the mapping of identifier to product passport?

The answers to questions 1 and 4 matter more than any feature list: they decide whether your labels still work in five years’ time.

Anyone who clarifies these points before printing has the most unpleasant part of the product passport behind them. SolveDPP’s DPP software generates the public product passport pages including QR code directly from your Shopify catalogue - and we answer the question about the domain first in the conversation, not last. The wider context is provided by our guide to the Digital Product Passport.