GS1 Digital Link for DPP: How Product URLs Work
How GS1 Digital Link structures DPP product URLs, how GTIN, batch and serial data fit in, and what ESPR does not explicitly require today.
Why Manufacturers Keep Seeing “GS1 Digital Link”
When companies start preparing for a Digital Product Passport, one technical term appears almost immediately: GS1 Digital Link. It matters because it describes a practical way to turn a product identifier into a web URL that can be printed in a QR code and opened by a phone.
At the same time, it is important to stay precise: the ESPR does not name GS1 Digital Link as the mandatory DPP standard. What the regulation does require is a unique product identifier, a data carrier, and rules that remain as technologically neutral as possible.
That makes GS1 Digital Link a strong and widely expected implementation approach — but not something that should be presented as already mandated by the ESPR text itself.
What GS1 Digital Link Actually Is
GS1 Digital Link is a way to express product identifiers inside a standard web address.
Instead of treating a code as just a number in a barcode database, the identifier becomes part of an HTTP URL such as:
https://resolver.example.com/01/05901234123457In practice, this means:
- the code can be encoded in a QR code
- the QR code opens a normal web address
- the same identifier can connect the physical product to digital information
- the URL can be extended with batch or serial information when needed
This is why GS1 Digital Link is often discussed in the same breath as DPP.
Why It Fits the DPP Use Case So Well
A Digital Product Passport needs a bridge between the physical product and its digital record. A URL-based identifier is convenient because it works across packaging, smartphones, internal systems, and web services.
GS1 Digital Link is attractive for DPP projects because it can support:
- product-level identification through GTIN
- batch-level granularity through lot data
- item-level granularity through serial data
- web access for consumers, authorities, recyclers, or repair actors
It is not the only imaginable architecture. It is simply one of the most mature and market-ready ones.
What the ESPR Requires — Carefully Stated
Here is the legally safer summary:
- ESPR Article 9(1) requires the DPP to be linked to a unique product identifier.
- ESPR Article 10(1)(c) points to relevant standards in Annex III, or equivalent European or international standards.
- Annex III references the ISO/IEC 15459 series, including the route through which GTIN is relevant.
- ESPR Article 12(6)(c) says implementation rules should remain as technologically neutral as possible.
The practical conclusion is not “GS1 Digital Link is mandatory today.” The practical conclusion is:
GTIN is strongly anchored in the regulatory discussion, and GS1 Digital Link is a leading technical way to express that identifier in a web-native format.
How the URL Structure Works
A typical GS1 Digital Link style URL uses application identifiers inside the path.
Product model level
https://resolver.example.com/01/0590123412345701= GTIN05901234123457= product identifier
Batch level
https://resolver.example.com/01/05901234123457/10/LOT2026-0310= batch or lot number
Item level
https://resolver.example.com/01/05901234123457/10/LOT2026-03/21/SN00047121= serial number
This is useful because one URL pattern can represent the three DPP granularity levels discussed across ESPR and battery-related implementation scenarios.
GTIN, Lot and Serial: What They Mean
| Element | What it identifies | Typical use |
|---|---|---|
| GTIN | product model | default model-level DPP |
| Lot / batch | production run | traceability for grouped units |
| Serial | individual item | item-level traceability |
For many manufacturers, the GTIN is the starting point. Batch and serial layers become important when the applicable product rules require deeper traceability.
Where the QR Code Fits In
A QR code is not the whole DPP. It is simply the data carrier that helps someone reach the digital information.
That distinction matters because regulatory discussions often get blurred. A company may have:
- a QR code on the label,
- a product URL,
- and still need a compliant backend data record behind that URL.
In other words:
- QR code = access mechanism
- URL / identifier = linking logic
- passport data = the actual DPP content
The three are connected, but they are not the same thing.
Why Manufacturers Use a Resolver Domain
Most implementations place the identifier behind a resolver domain such as:
https://resolver.example.com/01/05901234123457That resolver then routes the user to the correct passport view or returns the appropriate data. This architecture is popular because it gives manufacturers a stable link layer even when backend systems evolve.
It is also one reason DPP providers talk so much about URL architecture: once a code is printed on packaging, changing it later is operationally expensive.
What Is Still Not Fully Settled
Even though GS1 Digital Link is a strong practical choice, companies should avoid oversimplifying the legal position.
As of March 2026, what is still evolving includes:
- final harmonised technical standards
- implementing details from the Commission
- product-specific delegated acts across non-battery sectors
- exact interoperability expectations between systems
So the right message is not certainty for certainty’s sake. The right message is prepare with a low-risk, widely recognised structure without claiming that every detail is already fixed by law.
A Practical Decision Rule for Manufacturers
If you are preparing DPP infrastructure now, a sensible approach is:
- use a product identifier architecture that can support GTIN
- structure URLs in a way that can support model, batch, and item levels
- keep your implementation exportable and standards-aware
- avoid messaging that says GS1 Digital Link is already the only legal route
That gives you a practical implementation path while staying aligned with regulatory caution.
If you want the full DPP context first, read What is a DPP? and our step-by-step implementation guide.
Official Sources
- ESPR Regulation (EU) 2024/1781
- European Commission ESPR Working Plan 2025–2030
- Battery Regulation (EU) 2023/1542
- GS1 Digital Link overview
Need a practical DPP setup path without overengineering? Start free on OriginPass.eu and test a standards-aware passport flow on a pilot product.