Skip to content
InfoDPP Logo
InfoDPP
ESPR knowledge hub
what-is-dpp

GS1 Digital Link for DPP: GTIN URLs, QR Codes and ESPR

Learn how GTIN, batch and serial data become DPP URLs, what to print in QR codes, and what ESPR does and does not require today.

· 11 min read · InfoDPP

Editorial update, 16 July 2026: the references to six horizontal DPP standards were published by Decision (EU) 2026/1736. That does not make GS1 Digital Link the only mandatory format or replace sector-specific rules on the data carrier. Scope of the presumption of conformity →

DPP Registry: technical requirements. The Commission’s user guide v1.03, dated 16 September 2026, specifies an https URL in JTC 24 format, up to 2000 characters long, for the identifier submitted to the Registry. A correctly formatted URL is only part of the process: the data encoded in the carrier, such as a QR code, and the registration data must match the product identifier. The guide also states that battery passports cannot be registered until their semantic catalogue, which defines the required data and its structure, has been established.

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 practical implementation option, but not one mandated by the ESPR text itself.

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/05901234123457

In 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 alongside 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 one available approach, not the only possible architecture.

What the ESPR Requires

The relevant provisions are:

  • ESPR Article 10(1)(a) requires the DPP to be linked to a unique product identifier.
  • ESPR Article 10(1)(c) sets the standards basis for identifiers and carriers. Its interim reference to Annex III standards or equivalents applies until harmonised references are published; Decision (EU) 2026/1736 has now cited EN 18219 and EN 18220.
  • Annex III includes a Global Trade Identification Number under ISO/IEC 15459-6 or equivalent. It does not universally require GS1 membership.
  • ESPR Article 12(6)(c) says implementation rules should remain as technologically neutral as possible.

These provisions leave room to choose a suitable identifier scheme:

GTIN is one practical option, and GS1 Digital Link provides a standard way to express it in a web address.

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/05901234123457
  • 01 = GTIN
  • 05901234123457 = product identifier

Batch level

https://resolver.example.com/01/05901234123457/10/LOT2026-03
  • 10 = batch or lot number

Item level

https://resolver.example.com/01/05901234123457/10/LOT2026-03/21/SN000471
  • 21 = 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

ElementWhat it identifiesTypical use
GTINproduct modeldefault model-level DPP
Lot / batchproduction runtraceability for grouped units
Serialindividual itemitem-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 or another data carrier on the product, label, packaging or documentation, depending on the applicable rule,
  • a product URL,
  • and still need a compliant product-data record accessible through 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/05901234123457

That resolver then routes the user to the correct passport view or returns the appropriate data. This architecture is popular because it gives manufacturers stable links 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 20 September 2026, implementation still requires checking:

  • the scope of the six cited standards and any further citations
  • implementing details from the Commission
  • sector-specific datasets and application dates, including pending ESPR delegated acts
  • exact interoperability expectations between systems

Choose a widely recognised structure that fits your products, then check it against the applicable rules and standards. A familiar identifier format is not, by itself, proof of DPP compliance.

A Practical Decision Rule for Manufacturers

If you are preparing DPP infrastructure now, a sensible approach is:

  1. use a product identifier architecture that can support GTIN
  2. structure URLs in a way that can support model, batch, and item levels
  3. keep your data exportable and check your implementation against the applicable standards
  4. avoid messaging that says GS1 Digital Link is already the only legal route

This provides a practical starting point while leaving room for product-specific requirements.

If you want the full DPP context first, read What is a DPP? and our step-by-step implementation guide.

Official Sources


Want to see how a product passport works when someone scans its QR code? Try OriginPass.eu and create an example for your product.

Continue Reading

OriginPass

Prepare Your Product Data for ESPR

Start building your Digital Product Passport — structure product data, map identifiers, and get ready before delegated acts arrive. Free plan available.

No credit card required · Free plan available · Start at your own pace