GS1 Digital Link: What It Is, What Resolves It and How It Carries a Passport

Status at 3 September 2026

Starting with product identity?

If you have not yet decided what identifier a new product needs, start with Your first product identifier: GTIN, SKU, barcode, EAN and UPC. This page stays the Digital Link owner.

What GS1 Digital Link actually is

The current normative specification is GS1 Digital Link Standard: URI Syntax 1.7.0, published in August 2026.

Its job is to make GS1 identification keys usable in web URIs. A simplified illustrative shape looks like this:

https://id.example.com/01/09506000134352

In that shape:

• https://id.example.com is the domain and path authority under somebody's control;
• 01 identifies the GS1 Application Identifier used for GTIN;
• 09506000134352 is the GTIN value.

Qualifiers such as batch or serial identity can be added under GS1 Digital Link rules. Data attributes can also be represented where the standard permits them.

The point isn't that every DPP should use that example. It's that the identity becomes part of a standards-defined web address rather than being trapped as an opaque number inside a printed symbol.

Digital Link is not a QR Code

A QR Code is a physical 2D symbology. GS1 Digital Link is URI syntax.

That means:

• a QR Code can contain a GS1 Digital Link URI;
• a Data Matrix can contain a GS1 Digital Link URI;
• a QR Code can contain a normal URL that is not GS1 Digital Link;
• GS1 DataMatrix can carry GS1 element-string data rather than a web URI.

If you need to compare those combinations, use the 2D Product Identity Map.

Digital Link is not a GTIN either

A GTIN is the number. A Digital Link is the address that carries it.

The same GTIN can exist in three places at once and mean the same thing in all three:

• as a plain key in your product record, 09506000134352;
• inside a linear barcode or a GS1 DataMatrix as a GS1 element string;
• inside a Digital Link URI as the value following Application Identifier 01.

Nothing about writing a GTIN as a Digital Link changes what the GTIN identifies, who allocated it or what it costs. It changes what a scan can do with it. A scanner reading an element string gets data it has to know how to interpret; a browser reading a Digital Link URI gets somewhere to go.

So "we need Digital Link" and "we need a GTIN" are not the same procurement question, and why the second is answered on Barcodes and Product Identifiers: What You Need rather than here.

Digital Link is not a resolver either

This is one of the most persistent implementation errors.

The GS1 Digital Link URI Syntax standard and the GS1-Conformant Resolver Standard are separate standards. The current resolver standard is version 1.2.1, ratified in August 2026.

GS1 explicitly states that applications must not assume a GS1 Digital Link URI identifies a GS1-Conformant Resolver. A Digital Link URI can lead directly to a resource. A resolver is an optional service layer that can map one GS1 identity to one or more resources according to defined link types and request behaviour.

So this architecture is possible:

2D carrier -> GS1 Digital Link URI -> product page

And this architecture is also possible:

2D carrier -> GS1 Digital Link URI -> resolver -> selected resource

The second is more flexible. It is also another service that must remain available and governed.

Who runs it is not a standards question. Whoever controls the domain in the URI is whoever answers the request, so the resolver is operated by the economic operator, by a service provider acting for them, or by whoever the domain has been delegated to. That is a commercial and a durability decision rather than a technical one, and it is the subject of who should control the domain below.

For the end-to-end flow, see What Actually Happens When Somebody Scans the Code.

When a resolver earns its place

A resolver is useful when the same product identity needs to lead to different resources without changing the printed identity.

Examples include:

• a consumer information page;
• a Digital Product Passport resource;
• repair information;
• recycling information;
• a language-specific destination;
• a business-to-business data resource;
• a future resource that does not exist when the product is printed.

The resolver does not make those resources true. It does not decide access rights by itself. It does not make a product legally compliant. Its value is routing and discovery.

So the domain and operating model matter more than the word “resolver” in a vendor proposal.

One identity can lead to several services

The value is not that a QR Code can open a page. The change is that one persistent product identity can be associated with several human-readable and machine-readable resources or services, while resolution helps a client discover the appropriate destination. The product data can remain in the systems that own it.

PRODUCT → STABLE GS1 IDENTITY → DIGITAL LINK / RESOLUTION → PRODUCT PAGE + DPP + REPAIR + RECALL + MACHINE DATA

Before this layer is useful, map the GS1 identity to the product records in ERP, PIM and ecommerce. For the exact identifiers and qualifiers carried in a request, use GS1 Application Identifiers.

Once one identity can resolve to the right services, it stops being only an identifier. Continue to what connected product identity can do with external data and services.

How a Digital Link carries a passport

It does not carry the passport. It carries the way to the passport, and the distinction is the whole of the architecture.

Regulation (EU) 2024/1781 requires a Digital Product Passport to be connected through a data carrier to a persistent unique product identifier. A Digital Link implementation fills three of those slots and leaves the rest alone:

So the shortest honest description of the chain is: a carrier holds a Digital Link URI, the URI names the product, and either that URI or a resolver behind it returns the passport resource. Everything about what the passport must contain, who may read which part and how long it has to stay available sits outside the URI and is unaffected by choosing this syntax over another.

The end-to-end version of that chain, including where the carrier stops being responsible, is on What Actually Happens When Somebody Scans the Code.

What you have to do to use one

Five decisions, in this order, and none of them is "buy a Digital Link":

1. Settle the identifier. Digital Link expresses an identifier you already have. If you do not have one yet, Your first product identifier: GTIN, SKU, barcode, EAN and UPC is the page for that decision, not this one.
2. Check the product rule first. If the applicable product regime establishes another implementation, that settles it and the rest of this list is moot.
3. Choose direct or resolver. A URI that points straight at one stable resource needs no resolver. A single identity that has to reach several resources over the product's life does.
4. Secure the domain for the life of the product. The URI gets printed. The domain in it has to outlive the print run, the supplier contract and any change of provider.
5. Choose the carrier, then check it can be read. QR Code and Data Matrix can both hold the URI. Whether the systems that need to read it can process it is a separate question, and at retail point of sale it is the question below.

The order matters because four and five are reversible and one to three are not. A printed URI on a domain you do not control is the expensive mistake this list exists to avoid.

A Digital Link URI, a resolver and a Digital Twin Registry are not the same thing

There is one more discovery layer worth separating from the resolver.

A GS1 Digital Link URI expresses a GS1 identifier in web-address form. The current URI Syntax 1.7.0 is explicit that software must not assume the URI points to a GS1-Conformant Resolver.

A GS1-Conformant Resolver is an optional web-routing layer. It can take the identified product and return or redirect towards resources such as a DPP, repair information or another typed destination. Its job is resource resolution.

A Digital Twin Registry, such as the DTR used in Catena-X, solves a different industrial discovery problem. It registers and helps participants discover digital twins and their aspects inside that ecosystem. It does not replace the EU DPP Registry and it is not another name for a web resolver.

The distinction is easiest to remember by asking what is being discovered:

None of those layers, on its own, proves the passport content is correct or grants access to restricted data. For the wider cross-company architecture, see what a data space is and how Catena-X fits Digital Product Passport architecture.

Does EU DPP law require GS1 Digital Link?

No universal requirement is established by the current primary EU evidence.

Regulation (EU) 2024/1781 creates the horizontal DPP architecture around persistent unique product identifiers, data carriers, open standards, interoperability and product-specific delegated acts. Annex III includes GTIN under ISO/IEC 15459-6 or equivalent among information that a delegated act can select, but that is not the same as saying every DPP must use GTIN or Digital Link.

The standards layer has also moved. EN 18219:2026 on unique identifiers and EN 18220:2026 on data carriers are among the six harmonised DPP standards cited in the Official Journal by Commission Implementing Decision (EU) 2026/1736.

That strengthens the European standards route. It still does not convert GS1 Digital Link into a universal statutory requirement.

The generic legal question “does my DPP need GTIN or GS1?” remains owned by Barcodes and Product Identifiers: What You Need.

What Digital Link can solve well

A stable identity can survive a changing destination

The product's printed identity can remain stable while the web resource behind it changes. That is valuable for products with a life measured in years rather than weeks.

The condition is that the domain and routing layer remain under durable control. A standards-compliant URI printed on a product is still fragile if the domain is allowed to expire or the service contract disappears.

That operational risk is covered in When the Link Dies.

The same identity can support several resource types

A resolver can expose several links for the same identity rather than forcing one permanent landing page to contain every use case.

This is useful when different actors need different resources. It is not a substitute for the access-control rules a product regime may require.

GS1 identifiers remain recognisable inside the web address

For businesses already using GTIN and GS1 Application Identifiers, Digital Link provides a bridge from the existing identification model to web architecture.

That can reduce the temptation to create a second, unrelated “DPP ID” simply because the passport is digital.

What Digital Link does not solve

It does not answer any of these on its own:

• whether your product legally needs a DPP;
• whether the passport is model, batch or item level;
• which data fields the product law requires;
• who can see restricted data;
• whether the carrier will survive the product's physical life;
• whether a retailer POS estate can process the chosen 2D implementation;
• whether the passport content is accurate;
• whether your resolver or destination will still exist in ten years.

Those are different layers and different governance problems.

How GS1 Application Identifiers fit into the URI

GS1 Application Identifiers, usually shortened to AIs, identify the meaning of data elements in the GS1 system.

Common examples include:

• AI 01 for GTIN;
• AI 10 for batch or lot;
• AI 17 for expiration date;
• AI 21 for serial number.

They are not “DPP fields” merely because they can be encoded in a carrier or URI. They are GS1 semantics for data elements. Whether a DPP legally requires the underlying fact is a separate question.

The full mapping belongs on GS1 Application Identifiers for Digital Product Passports.

Who should control the domain?

If a URI is going to be printed onto products, domain control is an architecture decision, not a marketing detail.

The safest operating principle: the economic operator should know who controls the domain, what happens if a service provider changes and how the URI continues to resolve if a commercial relationship ends.

A provider-controlled domain can work. But the exit route must be explicit before printing begins. Otherwise the most durable part of the system, the physical product, is bound to one of the least durable parts, a vendor contract.

Questions to ask before printing:

1. Who owns or controls the domain in the URI?
2. Can we move resolver or hosting provider without changing the printed URI?
3. What is the redirect or link-management model?
4. What happens if the provider ceases trading?
5. Can the identity resolve without a proprietary app?
6. Which part of the response is open and which part is access-controlled?
7. Can we export the routing data and link relationships?

Does Digital Link make one code work at retail POS?

Not by itself.

GS1's current retail guideline recognises QR Code and Data Matrix carrying GS1 Digital Link URI syntax as future-state POS 2D options, alongside GS1 DataMatrix. But retail implementation depends on scanner capability, decoding software, host-system behaviour, placement and transition rules.

During the migration period, GS1 says a retail 2D barcode needs an accompanying linear barcode until its stated 90% POS scanning-solution capability threshold is reached.

So “it contains a GTIN in Digital Link” is not the same as “every till can process it today”.

See Ambition 2027: What Retail's 2D Barcode Transition Means for Digital Product Passports.

When Digital Link is a strong choice

Digital Link deserves serious consideration when most of these are true:

• your commercial identity already uses GS1;
• you want a standards-defined web expression of that identity;
• the same physical mark may need to support several digital resources;
• destination flexibility matters over the product's life;
• retail or supply-chain systems already consume GS1 identifiers;
• you can control or govern the printed domain for the required life;
• your product-specific DPP rule does not require a conflicting carrier or syntax.

Serialising at unit level is where that choice earns most, and ActivateDigital can protect a serialised product identity built on the same structure. GS1 does not certify, approve or endorse that.

When not to force it

Do not add Digital Link simply to make a project sound standards-led.

It may be unnecessary where:

• the applicable product regime establishes another implementation;
• a non-GS1 identity scheme is the chosen compliant route;
• the carrier has a single stable direct destination and the added routing layer has no user value;
• the business cannot govern the domain or resolver lifecycle properly;
• the implementation creates a second identity system alongside a perfectly adequate existing one.

Useful technology is not automatically useful architecture.

A procurement test in six sentences

Ask a supplier to explain its proposal without using the word “QR” as shorthand.

A good answer should be able to say:

1. which identifier is being encoded;
2. which scheme allocates it;
3. which URI or element-string syntax is used;
4. which physical carrier holds it;
5. whether the URI points directly to a resource or to a resolver;
6. who controls the domain and how destinations move after printing.

If those six answers cannot be separated, the implementation is not yet designed.

You can build a Digital Link from an identifier and see the URI it produces before you ask a vendor for one, which makes the six sentences above easier to score.

What is established, and what is not

What would change this answer

Recheck if:

• a product-specific EU act explicitly mandates or excludes a Digital Link implementation;
• GS1 Digital Link URI Syntax changes materially beyond 1.7.0;
• the GS1-Conformant Resolver Standard changes materially beyond 1.2.1;
• EN 18219 or EN 18220 changes in a way that affects the relationship between identifier, syntax and carrier.

Last verified 3 September 2026.

Sources and legal basis

• Regulation (EU) 2024/1781, Ecodesign for Sustainable Products Regulation
  EU law
• Commission Implementing Decision (EU) 2026/1736
  Delegated or implementing act
• GS1 Digital Link Standard: URI Syntax 1.7.0
  Standards body
• GS1-Conformant Resolver Standard 1.2.1
  Standards body
• GS1 General Specifications 26.0
  Standards body
• GS1 2D Barcodes at Retail Point-of-Sale Implementation Guideline, Release 1.1.0, ratified December 2025
  Standards body
• BS EN 18219:2026 public scope
  Standards body