---
title: "DPP vs GS1 Digital Link: Duties vs Standard"
canonical_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/dpp-vs-gs1-digital-link"
source_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/dpp-vs-gs1-digital-link"
author: "Sorena AI"
description: "Compare EU Digital Product Passport requirements with GS1 Digital Link: legal scope, identifiers, data carriers, access rights, registry, portal, customs checks, and implementation consequences."
published_at: "2026-05-09"
updated_at: "2026-05-09"
keywords:
  - "DPP vs GS1 Digital Link"
  - "EU Digital Product Passport"
  - "GS1 Digital Link"
  - "ESPR data carrier"
  - "DPP registry"
  - "DPP unique identifier"
  - "Digital Product Passport"
  - "ESPR"
  - "unique identifier"
  - "data carrier"
  - "registry"
---
**[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform

[Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io)

---

# DPP vs GS1 Digital Link: Duties vs Standard

Compare EU Digital Product Passport requirements with GS1 Digital Link: legal scope, identifiers, data carriers, access rights, registry, portal, customs checks, and implementation consequences.

*DPP* *GS1 Digital Link* *EU*

## DPP vs GS1 Digital Link legal duties vs resolver standards

The EU Digital Product Passport is a regulatory information and access-rights framework under ESPR. GS1 Digital Link is a GS1 URI syntax and resolver approach that can help connect identifiers and data carriers to online information.

Use this comparison to keep legal DPP requirements separate from technical identifier, barcode, and resolver implementation choices.

DPP and GS1 Digital Link are often discussed together because both start from a product identifier that can be read from a data carrier. They are not interchangeable. ESPR DPP rules define when a passport is required, what data and access rights must exist, how registry and portal integration works, and which economic operator remains responsible. GS1 Digital Link can be one way to encode GS1 identifiers into a Web URI and route users or systems to information, but it does not define the ESPR passport content or replace delegated-act requirements.

## DPP vs GS1 Digital Link: what each one controls

The rows below separate legal passport obligations from identifier and resolver implementation standards so product, compliance, packaging, data, and IT teams do not treat a QR code as proof of DPP compliance.

- **EU Digital Product Passport**: A product-passport obligation under ESPR when an applicable delegated act requires it, including passport data, access rights, unique identifiers, data carriers, registry, portal, customs, and availability requirements.
- **GS1 Digital Link**: A GS1 standard approach for encoding GS1 data such as GTIN and attributes into Web URI syntax for use in QR Code, Data Matrix, and, where applicable, NFC or resolver-based access.

| Dimension | EU Digital Product Passport | GS1 Digital Link | Operational implication | Sources |
| --- | --- | --- | --- | --- |
| Scope boundary | DPP is a legal compliance construct under ESPR. Products may only be placed on the market or put into service with a passport when the applicable delegated act requires one, and the passport data must be accurate, complete, and up to date. | GS1 Digital Link is not the DPP law. It is a GS1 technical standard for URI syntax and resolver-enabled access to product information using GS1 identifiers. | Treat GS1 Digital Link as a possible technical layer inside a DPP design, not as a replacement for the delegated act, required passport data, access rights, registry upload, or compliance evidence. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - ESPR assigns DPP details to delegated acts, so a technical link standard alone cannot determine legal passport compliance.<br>[GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Supports the GS1 side: the GS1 specification describes Digital Link as URI syntax for encoding GS1 data in data carriers. |
| Covered actors | DPP scope depends on ESPR delegated acts for product groups. Those acts specify the covered products, data to include, data carrier, layout and positioning, passport granularity, accessible pre-sale information, access actors, update actors, update arrangements, and availability period. | GS1 Digital Link can be used by product teams before or outside an ESPR DPP trigger. Its scope follows GS1 identifier and application rules, not the ESPR product-group trigger. | Start DPP scoping with the product group and delegated act. Then decide whether a GS1 Digital Link URI can carry or resolve the identifier design for that scoped product. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Lists the DPP elements that delegated acts must specify for covered product groups.<br>[GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Shows that GS1 Digital Link belongs to GS1 application and syntax rules rather than ESPR product-group scoping.<br>[CEN-CENELEC CWA 18186:2025](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - DPP design guidance says DPP information categories and methods should be determined by the product-specific delegated act. |
| Trigger | A DPP must be connected through a data carrier to a persistent unique product identifier. ESPR allows the delegated act to set whether the passport is established at model, batch, or item level. | GS1 Digital Link commonly starts from GS1 identifiers such as GTIN and can add attribute data in the URI. GS1 specifications distinguish class-level, sub-class-level, and instance-level identifiers, but the DPP granularity still has to match the delegated act. | Do not assume a GTIN-only design is enough for every DPP. If the DPP must operate at batch or item level, the identifier, URI path, barcode content, resolver records, and source systems must preserve that granularity. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the DPP requirement for a persistent unique product identifier and delegated-act granularity.<br>[GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Defines GS1 identifier levels and describes Digital Link URI syntax with GTIN and attribute data.<br>[CEN-CENELEC CWA 18186:2025](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Explains that DPP designers should choose model, batch, or item granularity and then select product, operator, registry, facility, and other identifiers. |
| Core obligations | ESPR requires the data carrier to be physically present on the product, packaging, or accompanying documentation as the delegated act specifies. It must connect the physical product to the persistent identifier and passport access route. | GS1 Digital Link can be encoded in QR Code or Data Matrix and may also be relevant for NFC. GS1 describes it as explicitly encoding a resolvable Web URI rather than only a direct product number. | A DPP label decision is not just a packaging artwork decision. It must cover physical placement, durability, pre-sale digital access, scanner behavior, and whether the encoded value resolves reliably for consumers and professional users. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports physical data-carrier placement requirements under ESPR.<br>[GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Supports QR Code, Data Matrix, NFC, and resolvable URI behavior for GS1 Digital Link.<br>[CEN-CENELEC CWA 18186:2025](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Guidance compares QR codes, DataMatrix, RFID, NFC, and related characteristics for DPP data-carrier selection. |
| Evidence record | DPP data is the regulated product information set. It must use open standards and interoperable formats and be machine-readable, structured, searchable, and transferable where appropriate without vendor lock-in. | GS1 Digital Link does not define the ESPR passport data set. It gives a standard way to encode GS1 data into a URI and route users or systems toward resources that the brand owner or service provider makes available. | Use a data model and evidence process for the passport itself. Use GS1 Digital Link, if selected, to reach that data or related resources without pretending the URI syntax supplies the required DPP content. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports open-standard, interoperable, machine-readable, searchable, transferable DPP data requirements.<br>[GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Supports that GS1 Digital Link is about URI syntax and encoded GS1 data rather than ESPR passport data categories.<br>[CIRPASS DPP System Architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - CIRPASS separates the access route from DPP data and highlights interoperable data formats for the passport itself. |
| Access rights and role control | ESPR requires access to DPP data to be regulated by actor-specific access rights. It names customers, economic operators, repairers, recyclers, market surveillance authorities, customs authorities, civil society, trade unions, and other relevant actors. | A GS1 Digital Link resolver can route different link types or resources, but access control, credentials, authorization, and role-specific data release must be implemented by the DPP system and aligned with ESPR delegated-act access rights. | Design public, business, authority, repair, recycling, and update paths separately. A single public landing page reached from a GS1 Digital Link URI is not the same as a role-aware DPP access model. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports restricted rights to introduce, modify, or update passport data.<br>[CIRPASS DPP System Architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - Explains resolver flows and that endpoint responses can differ by credentials and access level. |
| Enforcement | ESPR creates Commission-managed DPP infrastructure: a registry that stores at least unique identifiers and, for customs release for free circulation, commodity code data; a public web portal to search and compare passport data; and customs verification through registry interconnection. | GS1 Digital Link is not the EU DPP registry, web portal, or customs system. A resolver can help discovery, but it does not automatically upload identifiers, obtain a unique registration identifier, support the EU portal, or satisfy customs registry checks. | Implementation plans need separate work packages for GS1 identifier and resolver governance, EU registry upload, unique registration identifier handling, portal discoverability, and customs data alignment. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports registry, web portal, and customs-control obligations for DPP infrastructure.<br>[CIRPASS DPP System Architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - Describes GS1 Digital Link-inspired HTTP URI architecture as one route from product identifier to resolver, separate from EU registry functions.<br>[CEN-CENELEC CWA 18186:2025](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Guidance identifies the EU central registry and EU DPP web portal as systems DPPs should be linked to. |
| Overlap and reuse | ESPR requires DPP storage by the responsible economic operator or a digital product passport service provider, a backup copy, and availability for the period specified in delegated acts, including after insolvency, liquidation, or cessation of activity in the Union. | GS1 Digital Link persistence depends on identifier governance, domain and resolver operation, and link maintenance. GS1 rules and CIRPASS architecture material both make clear that resolvable URIs and resolver records need operational stewardship. | Do not let the marketing domain or packaging code become the only persistence plan. Preserve ownership of identifiers, domains, resolver records, backup access, and service-provider handover before products enter the market. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the requirement that the passport remain available for the period specified by delegated acts.<br>[CIRPASS DPP System Architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - Explains UID-to-URI transformation, resolver use, and caution around domain-name transfer and archive access.<br>[GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Supports the need to maintain records and follow GS1 allocation and non-reuse rules when GS1 identification ownership changes. |
| Practical decision rule | DPP implementation starts with legal scoping and data governance: delegated-act requirements, product granularity, passport data model, source evidence, access rights, update rights, registry upload, portal search, customs data, backup, and retention. | GS1 Digital Link implementation starts with identifier governance and resolution: GS1 keys and attributes, URI syntax, barcode or NFC encoding, resolver records, link types, domain stewardship, scanner behavior, and routing to public or restricted resources. | The useful architecture is a crosswalk, not a substitution. Map each DPP obligation to the system component that fulfils it, then mark which components GS1 Digital Link can support and which must be handled elsewhere. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the core DPP implementation components: data, access rights, update rights, registry, portal, customs, and technical design.<br>[GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Supports GS1 Digital Link implementation components: GS1 data, URI syntax, data carriers, and GS1 standard references.<br>[CIRPASS DPP System Architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - Supports the practical crosswalk approach by separating product identifier discovery routes from the underlying interoperable DPP data. |

Sources for Scope boundary - EU Digital Product Passport:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the DPP side: ESPR makes passport availability and data quality legal requirements when a delegated act requires a DPP.
  - Quote: "accurate, complete and up to date"

Sources for Scope boundary - GS1 Digital Link:

- [GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Supports the GS1 side: the GS1 specification describes Digital Link as URI syntax for encoding GS1 data in data carriers.
  - Quote: "uses a Web URI syntax to encode GS1 data"

Sources for Scope boundary - operational implication:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - ESPR assigns DPP details to delegated acts, so a technical link standard alone cannot determine legal passport compliance.
  - Quote: "as specified in the delegated act"

Sources for Covered actors - EU Digital Product Passport:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Lists the DPP elements that delegated acts must specify for covered product groups.
  - Quote: "specify the following"

Sources for Covered actors - GS1 Digital Link:

- [GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Shows that GS1 Digital Link belongs to GS1 application and syntax rules rather than ESPR product-group scoping.
  - Quote: "GS1 Digital Link Standard: URI syntax"

Sources for Covered actors - operational implication:

- [CEN-CENELEC CWA 18186:2025](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - DPP design guidance says DPP information categories and methods should be determined by the product-specific delegated act.
  - Quote: "determined in the specific delegated act"

Sources for Trigger - EU Digital Product Passport:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the DPP requirement for a persistent unique product identifier and delegated-act granularity.
  - Quote: "model, batch or item"

Sources for Trigger - GS1 Digital Link:

- [GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Defines GS1 identifier levels and describes Digital Link URI syntax with GTIN and attribute data.
  - Quote: "GTIN and attribute data"

Sources for Trigger - operational implication:

- [CEN-CENELEC CWA 18186:2025](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Explains that DPP designers should choose model, batch, or item granularity and then select product, operator, registry, facility, and other identifiers.
  - Quote: "Product Model"

Sources for Core obligations - EU Digital Product Passport:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports physical data-carrier placement requirements under ESPR.
  - Quote: "physically present on the product"

Sources for Core obligations - GS1 Digital Link:

- [GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Supports QR Code, Data Matrix, NFC, and resolvable URI behavior for GS1 Digital Link.
  - Quote: "explicitly encodes a resolvable Web URI"

Sources for Core obligations - operational implication:

- [CEN-CENELEC CWA 18186:2025](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Guidance compares QR codes, DataMatrix, RFID, NFC, and related characteristics for DPP data-carrier selection.
  - Quote: "QR codes, DataMatrixes, passive RFID tags"

Sources for Evidence record - EU Digital Product Passport:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports open-standard, interoperable, machine-readable, searchable, transferable DPP data requirements.
  - Quote: "open interoperable data exchange network"

Sources for Evidence record - GS1 Digital Link:

- [GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Supports that GS1 Digital Link is about URI syntax and encoded GS1 data rather than ESPR passport data categories.
  - Quote: "GS1 DL URI"

Sources for Evidence record - operational implication:

- [CIRPASS DPP System Architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - CIRPASS separates the access route from DPP data and highlights interoperable data formats for the passport itself.
  - Quote: "DPP Data itself remains the same"

Sources for Access rights and role control - EU Digital Product Passport:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports named actor categories and free, easy access based on delegated-act access rights.
  - Quote: "based on their respective access rights"

Sources for Access rights and role control - GS1 Digital Link:

- [CIRPASS DPP System Architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - Explains resolver flows and that endpoint responses can differ by credentials and access level.
  - Quote: "determines the appropriate access level"

Sources for Access rights and role control - operational implication:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports restricted rights to introduce, modify, or update passport data.
  - Quote: "introduce, modify or update data"

Sources for Enforcement - EU Digital Product Passport:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports registry, web portal, and customs-control obligations for DPP infrastructure.
  - Quote: "publicly accessible web portal"

Sources for Enforcement - GS1 Digital Link:

- [CIRPASS DPP System Architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - Describes GS1 Digital Link-inspired HTTP URI architecture as one route from product identifier to resolver, separate from EU registry functions.
  - Quote: "points to a resolver"

Sources for Enforcement - operational implication:

- [CEN-CENELEC CWA 18186:2025](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Guidance identifies the EU central registry and EU DPP web portal as systems DPPs should be linked to.
  - Quote: "EU central registry and the EU DPP web portal"

Sources for Overlap and reuse - EU Digital Product Passport:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports DPP storage, backup, and continuity requirements after economic-operator disruption.
  - Quote: "including after an insolvency"

Sources for Overlap and reuse - GS1 Digital Link:

- [CIRPASS DPP System Architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - Explains UID-to-URI transformation, resolver use, and caution around domain-name transfer and archive access.
  - Quote: "updating the resolver"
- [GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Supports the need to maintain records and follow GS1 allocation and non-reuse rules when GS1 identification ownership changes.
  - Quote: "maintain records of all GS1 identification keys"

Sources for Overlap and reuse - operational implication:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the requirement that the passport remain available for the period specified by delegated acts.
  - Quote: "remain available for the period specified"

Sources for Practical decision rule - EU Digital Product Passport:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the core DPP implementation components: data, access rights, update rights, registry, portal, customs, and technical design.
  - Quote: "Technical design and operation"

Sources for Practical decision rule - GS1 Digital Link:

- [GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Supports GS1 Digital Link implementation components: GS1 data, URI syntax, data carriers, and GS1 standard references.
  - Quote: "QR Code or Data Matrix"

Sources for Practical decision rule - operational implication:

- [CIRPASS DPP System Architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - Supports the practical crosswalk approach by separating product identifier discovery routes from the underlying interoperable DPP data.
  - Quote: "Whatever means are used to access"

### How should teams use GS1 Digital Link in a DPP program?

- Use ESPR and the relevant delegated act to decide whether a passport is required, which product level applies, what data is mandatory, who can access or update it, and how registry and customs integration must work.
- Use GS1 Digital Link only where the identifier, data carrier, URI, and resolver design fits the DPP requirements and the organization's product-identification governance.
- Keep a crosswalk that separates DPP legal requirements from GS1 implementation choices: identifier source, encoded value, resolver owner, link targets, access categories, registry fields, backup route, and evidence owner.

Sources for the practical decision rule:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Primary legal source for DPP requirements, delegated-act scoping, data carriers, unique identifiers, access rights, registry, portal, customs, storage, and availability.
  - Quote: "digital product passport"
- [GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Primary GS1 source for Digital Link URI syntax references, GS1 identifiers, data carriers, and related application rules.
  - Quote: "GS1 Digital Link URI"
- [CIRPASS DPP System Architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - Architecture source for resolver-based access, UID-to-URI transformation, decentralized DPP repositories, and separation between access route and DPP data.
  - Quote: "From Data Carrier to a Usable URI"

## When the comparison matters

This comparison matters when packaging, master-data, sustainability, compliance, and IT teams are deciding whether the same QR code or resolver can serve both product-identification and EU DPP access needs.

The practical risk is overclaiming. A GS1 Digital Link URI can be a strong route to product information, but DPP compliance also needs the regulated passport data set, actor-specific access controls, update rights, registry upload, web-portal discoverability, customs integration where relevant, and long-term availability.

- Use the DPP side to define legal scope, passport content, access categories, registry fields, and evidence ownership.
- Use the GS1 Digital Link side to define identifier syntax, barcode or NFC content, resolver behavior, link types, and domain operations.
- Escalate designs that rely only on a public marketing page, a GTIN-only identifier, or an unmanaged domain redirect for a product that needs a regulated DPP.

Sources for this answer:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the legal DPP requirements that go beyond simply placing a scannable code on a product.
- [GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Supports the GS1 implementation focus on GS1 identifiers, URI syntax, data carriers, and message-processing rules.
- [CEN-CENELEC CWA 18186:2025](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Supports DPP design choices for data carriers, portal setup, searchability, exchange management, traceability, and lifecycle availability.

*Recommended next step*

*Placement: after comparison section*

## Separate DPP obligations from identifier design

Use this comparison to build a DPP implementation crosswalk that shows which legal requirements are satisfied by the passport data model, which are supported by GS1 Digital Link, and which require registry, portal, access-control, or customs integration work.

- [Open Research Copilot](/solutions/research-copilot.md): Check DPP implementation questions against cited ESPR, GS1, CIRPASS, and CEN-CENELEC source material.
- [Discuss DPP architecture](/contact.md): Review identifier, data-carrier, resolver, access-rights, and registry choices for a DPP rollout.

## Primary sources

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Primary legal source for DPP requirements, delegated-act scoping, data carriers, unique identifiers, access rights, registry, portal, customs, storage, and availability.
  - Quote: "digital product passport"
- [GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Primary GS1 source for Digital Link URI syntax references, GS1 identifiers, data carriers, and related application rules.
  - Quote: "GS1 Digital Link URI"
- [CIRPASS DPP System Architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - Architecture source for resolver-based access, UID-to-URI transformation, decentralized DPP repositories, and separation between access route and DPP data.
  - Quote: "From Data Carrier to a Usable URI"
- [CEN-CENELEC CWA 18186:2025](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Guidance identifies the EU central registry and EU DPP web portal as systems DPPs should be linked to.
  - Quote: "EU central registry and the EU DPP web portal"

## Related Topic Guides

- [Annex III Data Model Planning for EU Digital Product Passports](/artifacts/eu/digital-product-passport/annex-iii-data-model-planning.md): Plan EU Digital Product Passport data fields, identifiers, access rights, update owners, registry inputs, and evidence records against ESPR Annex III and product-specific delegated acts.
- [Digital Product Passport vs Digital Twin](/artifacts/eu/digital-product-passport/dpp-vs-digital-twin.md): Compare EU Digital Product Passports with digital twins: legal access duties, identifiers, public and restricted data, evidence, governance, and reuse limits.
- [Digital Product Passport vs Paper Product Passports](/artifacts/eu/digital-product-passport/dpp-vs-traditional-product-passports.md): Compare EU regulated digital product passports with paper, PDF, web, and internal product passports across access, identifiers, data carriers, restricted data, customs checks, registry, and interoperability.
- [DPP customs access review workflow for ESPR products](/artifacts/eu/digital-product-passport/customs-access-review-workflow.md): Review public, restricted, and customs access for EU Digital Product Passports, including registry handoffs, portal access rights, and release-for-free-circulation evidence.
- [DPP Data Governance RACI Template for EU Digital Product Passports](/artifacts/eu/digital-product-passport/dpp-data-governance-raci-template.md): Assign accountable owners for EU Digital Product Passport data, access rights, supplier inputs, resolver links, registry uploads, verification checks, and retained evidence.
- [DPP data-model intake workflow for EU Digital Product Passports](/artifacts/eu/digital-product-passport/dpp-data-model-intake-workflow.md): A grounded intake workflow for EU Digital Product Passport data models: product group, delegated-act status, source owner, supplier data, access class, identifiers, carrier, checks, and publication readiness.
- [DPP Governance, Verification and Audit Controls](/artifacts/eu/digital-product-passport/governance-verification-and-audit.md): Build EU Digital Product Passport governance controls for data owners, supplier evidence, access logs, validation checks, audit records, and product release gates.
- [DPP QR code vs NFC data carrier choices under EU ESPR](/artifacts/eu/digital-product-passport/faq/qr-code-vs-nfc-carrier-choices.md): How to choose QR code, NFC, or another data carrier for an EU Digital Product Passport without assuming ESPR mandates one universal carrier.
- [DPP registry and web portal integration under EU ESPR](/artifacts/eu/digital-product-passport/dpp-registry-and-web-portal-integration.md): Grounded guide to EU Digital Product Passport registry and web portal integration under ESPR, covering identifiers, data carriers, access rights, service providers, and lookup design.
- [DPP vs Battery Passport: ESPR and Battery Regulation Comparison](/artifacts/eu/digital-product-passport/dpp-vs-battery-passport.md): Compare the ESPR Digital Product Passport framework with the EU Batteries Regulation battery passport by scope, timing, data, access rights, identifiers, registry, governance, and evidence.
- [DPP vs EPREL Comparison](/artifacts/eu/digital-product-passport/dpp-vs-eprel.md): Compare the EU Digital Product Passport with EPREL: product-passport scope, energy-label database role, access model, identifiers, data carriers, and overlap limits.
- [EU Digital Product Passport access: public, restricted, and customs views](/artifacts/eu/digital-product-passport/public-restricted-and-customs-access.md): How ESPR Digital Product Passport access should be split across public users, restricted actors, authorities, customs, the EU registry, and the web portal.
- [EU Digital Product Passport API and resolver architecture](/artifacts/eu/digital-product-passport/api-and-resolver-architecture.md): Grounded DPP architecture guidance for data carriers, product identifiers, resolver lookup paths, access rights, registry integration, and interoperability without premature protocol mandates.
- [EU Digital Product Passport Applicability Test](/artifacts/eu/digital-product-passport/applicability-test.md): Check whether an ESPR delegated act or battery passport rule may require a Digital Product Passport, which operator owns it, and what evidence to keep.
- [EU Digital Product Passport architecture and integration](/artifacts/eu/digital-product-passport/architecture-and-integration.md): Grounded guide to EU Digital Product Passport architecture: data carriers, identifiers, access rights, registry, portal, supplier flows, customs checks, and governance.
- [EU Digital Product Passport checklist](/artifacts/eu/digital-product-passport/checklist.md): A concrete EU Digital Product Passport readiness checklist covering product-group scope, passport fields, identifiers, data carriers, access rights, supplier evidence, registry preparation, and publication controls.
- [EU Digital Product Passport compliance: ESPR requirements](/artifacts/eu/digital-product-passport/compliance.md): Grounded EU Digital Product Passport compliance guide covering ESPR passport data, identifiers, data carriers, access rights, registry readiness, supplier validation, and evidence.
- [EU Digital Product Passport Data Carriers, Access Control, and UX](/artifacts/eu/digital-product-passport/data-carriers-access-control-and-ux.md): How to choose DPP data carriers, identifiers, access rights, and scanning UX under ESPR Articles 9-14, with QR, NFC, RFID, registry, and customs constraints.
- [EU Digital Product Passport data requirements and fields](/artifacts/eu/digital-product-passport/data-requirements-and-fields.md): How to plan Digital Product Passport data fields under ESPR: delegated-act scope, Annex III data categories, access rights, customs data, and supplier validation.
- [EU Digital Product Passport deadlines and compliance calendar](/artifacts/eu/digital-product-passport/deadlines-and-compliance-calendar.md): Grounded EU Digital Product Passport calendar for ESPR and battery passport milestones, with product-group dates flagged as dependent on delegated acts.
- [EU Digital Product Passport FAQ](/artifacts/eu/digital-product-passport/faq.md): Direct answers on EU Digital Product Passport scope, creators, product groups, registry, customs checks, access rights, identifiers, data carriers, and governance.
- [EU Digital Product Passport identifier and data carrier design](/artifacts/eu/digital-product-passport/unique-identifier-and-data-carrier-design.md): How to design Digital Product Passport identifiers, QR or other data carriers, resolver links, registry records, access paths, and evidence without overclaiming the EU rules.
- [EU Digital Product Passport penalties and enforcement](/artifacts/eu/digital-product-passport/penalties-and-fines.md): What ESPR says about Digital Product Passport penalties, Member State fine rules, market surveillance, customs checks, and unresolved product-specific delegated acts.
- [EU Digital Product Passport Product Group Readiness](/artifacts/eu/digital-product-passport/product-group-readiness.md): Prepare product groups for EU Digital Product Passport rules by tracking ESPR delegated-act status, data fields, suppliers, identifiers, access rights, and registry handoffs.
- [EU Digital Product Passport requirements under ESPR](/artifacts/eu/digital-product-passport/requirements.md): source-linked overview of EU Digital Product Passport requirements under ESPR: product-specific delegated acts, data fields, identifiers, carriers, registry, access rights, supplier data validation, and open points.
- [EU Digital Product Passport supplier data validation controls](/artifacts/eu/digital-product-passport/supplier-data-validation.md): Build a supplier data validation file for EU Digital Product Passports: source owner, product link, access class, data model fit, evidence quality, approval record, and release gate.
- [EU DPP customs access: registry, portal, and restricted data](/artifacts/eu/digital-product-passport/faq/customs-access.md): FAQ on customs access under the EU Digital Product Passport: what customs can verify, how the registry and public portal differ, and how access rights limit DPP data.
- [EU DPP implementation playbook and vendor selection](/artifacts/eu/digital-product-passport/implementation-playbook-and-vendor-selection.md): Select Digital Product Passport vendors against ESPR requirements for identifiers, data carriers, access rights, decentralized storage, registry readiness, portal access, and verification evidence.
- [EU DPP Product-Group Readiness Checklist](/artifacts/eu/digital-product-passport/product-group-readiness-checklist.md): A source-grounded checklist for preparing a product group for an EU Digital Product Passport delegated act, covering data fields, suppliers, identifiers, carriers, access rights, and registry readiness.
- [EU DPP QR Code and Data Carrier Implementation Guide](/artifacts/eu/digital-product-passport/dpp-qr-code-implementation-guide.md): Grounded guidance for using QR codes and other data carriers in EU Digital Product Passport programs, including unique identifiers, access, resolver testing, and evidence.
- [EU DPP supplier data validation workflow](/artifacts/eu/digital-product-passport/supplier-data-validation-workflow.md): A grounded workflow for checking supplier data before it is used in an EU Digital Product Passport, covering product linkage, evidence, owners, access class, and approval records.
- [EU DPP unique identifier requirements: product, operator and facility IDs](/artifacts/eu/digital-product-passport/faq/unique-identifier-requirements.md): FAQ on how ESPR Digital Product Passport identifiers connect products, economic operators, facilities, data carriers, resolvers and registry evidence.
- [Public vs restricted EU Digital Product Passport data](/artifacts/eu/digital-product-passport/faq/public-vs-restricted-passport-data.md): How to separate public, restricted, authority, and customs access in EU Digital Product Passport designs under ESPR and battery passport rules.
- [What is a Digital Product Passport under ESPR?](/artifacts/eu/digital-product-passport/what-is-a-dpp.md): A visitor-friendly explanation of EU Digital Product Passports under ESPR: product data, identifiers, data carriers, access rights, registry, web portal, and delegated acts.
- [What is the EU Digital Product Passport registry?](/artifacts/eu/digital-product-passport/faq/dpp-registry.md): FAQ on the ESPR Digital Product Passport registry: what it stores, who uploads data, how identifiers work, and what teams should avoid assuming.
- [Which products come first for the EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/which-products-come-first.md): FAQ on EU Digital Product Passport product priority: batteries have a separate passport rule, while ESPR product groups depend on the working plan and delegated acts.
- [Who must create an EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/who-must-create-a-digital-product-passport.md): DPP responsibility under the EU ESPR: how manufacturers, importers, distributors, suppliers, service providers, and delegated acts fit together.


---

[Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us)

(c) 2026 Sorena AB (559573-7338). All rights reserved.

Source: https://www.sorena.io/artifacts/eu/digital-product-passport/dpp-vs-gs1-digital-link