GS1 Digital Link for Digital Product Passports: What It Is and Whether You Need It

GS1 Digital Link can put GS1 product identity into a web URI, but EU DPP law does not universally require it. Understand the URI, resolver and domain decisions before you build.

Last verified: 3 September 2026

LinkedIn X Email

Navigate this page

Overview
The short answer
What GS1 Digital Link actually is
Digital Link is not a QR Code
Digital Link is not a resolver either
When a resolver earns its place
Does EU DPP law require GS1 Digital Link?
What Digital Link can solve well
What Digital Link does not solve
How GS1 Application Identifiers fit into the URI
Who should control the domain?
Does Digital Link make one code work at retail POS?
When Digital Link is a strong choice
When not to force it
A procurement test in six sentences
What is established, and what is not
What would change this answer
Sources and legal basis
Keep exploring

GS1 Digital Link is a standard way to express GS1 identifiers in a web URI. It can connect a product identity such as a GTIN to web resources and can carry qualifiers such as batch or serial identity in the URI structure. It is not a barcode symbology. It is not a Digital Product Passport. It is not the same thing as a resolver. And current EU DPP framework law does not establish GS1 Digital Link as a universal requirement for every Digital Product Passport. That makes it a potentially useful architecture choice rather than a default legal answer.

The short answer

Use GS1 Digital Link when you have chosen the GS1 identity system and you want that identity to work naturally on the web, particularly where one persistent product identity may need to lead to different resources over time.

Do not adopt it because somebody has told you “DPP requires Digital Link”. Regulation (EU) 2024/1781 requires a DPP to be connected through a data carrier to a persistent unique product identifier. It does not name GS1 Digital Link as the universal URI scheme for all products.

Three decisions stay separate:

the identifier, such as a GTIN;
the Digital Link URI syntax that expresses that identifier on the web;
the physical carrier, such as QR Code or Data Matrix, that contains the URI.

A fourth decision is whether the URI points straight to a resource or is handled by a resolver.

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 is not that every DPP should use that example. The point is 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 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.

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.

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

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 is simple: 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:

Who owns or controls the domain in the URI?
Can we move resolver or hosting provider without changing the printed URI?
What is the redirect or link-management model?
What happens if the provider ceases trading?
Can the identity resolve without a proprietary app?
Which part of the response is open and which part is access-controlled?
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.

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:

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

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

What is established, and what is not

Proposition	Status at 3 September 2026
GS1 Digital Link is a GS1 URI syntax standard	Established
Current URI Syntax version is 1.7.0	Established
A Digital Link URI must point to a GS1-Conformant Resolver	False
Current Resolver Standard version is 1.2.1	Established
Every EU DPP must use GS1 Digital Link	Not established
QR Code and Data Matrix can carry GS1 Digital Link URI syntax	Supported by GS1 standards/guidance
Digital Link makes the underlying DPP content legally correct	False

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.

Keep exploring

The questions this page usually raises next.

Does this reach your products?

Give ActivateDigital one product and it works out which obligations apply from the product's own character, and says which it cannot decide.

Check a product How a value is decided

Help someone else make sense of product passports.