--- title: "DPP vs EPREL Comparison" canonical_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/dpp-vs-eprel" source_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/dpp-vs-eprel" author: "Sorena AI" description: "Compare the EU Digital Product Passport with EPREL: product-passport scope, energy-label database role, access model, identifiers, data carriers, and overlap limits." published_at: "2026-05-09" updated_at: "2026-05-26" keywords: - "Digital Product Passport" - "DPP" - "EPREL" - "ESPR" - "energy labelling" - "product database" - "data carrier" - "unique product identifier" - "product data" --- **[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 EPREL Comparison Compare the EU Digital Product Passport with EPREL: product-passport scope, energy-label database role, access model, identifiers, data carriers, and overlap limits. *DPP* *EPREL* *EU* ## DPP vs EPREL Product passport versus energy-labelling database DPP and EPREL both connect product information to EU rules, but they are not the same system. Use this comparison to separate the horizontal ESPR product passport from the existing energy-label/product database role of EPREL. The Digital Product Passport is a horizontal product-information mechanism under the Ecodesign for Sustainable Products Regulation. EPREL is treated in the grounding material as the European Product Registry for Energy Labelling and as the database behind energy-label QR access. The practical risk is assuming that one record, label, QR code, or model identifier automatically satisfies both regimes. This page separates the two using only the DPP and ESPR/label grounding available here. ## DPP vs EPREL: what each system is for Read the rows as implementation boundaries: DPP governs passport architecture and access under ESPR; EPREL remains tied to energy labelling and product-database functions. - **Digital Product Passport**: A product passport under ESPR for product-related sustainability, circularity, traceability, compliance, access-rights, and registry use, with details set by product-specific delegated acts. - **EPREL**: The European Product Registry for Energy Labelling, referenced as an existing Union database/tool and as the target of energy-label QR access for relevant energy-labelled products. | Dimension | Digital Product Passport | EPREL | Operational implication | Sources | | --- | --- | --- | --- | --- | | Scope boundary | DPP is the ESPR mechanism for making product information available across the value chain. It is expected to improve access to relevant information, end-to-end traceability, and competent-authority work without exposing confidential business information beyond the access rights set for the product group. | EPREL is not described in the grounding as a general sustainability passport. It is the European Product Registry for Energy Labelling and is discussed as the product database/registry connected to energy labels. | Do not call an EPREL record a DPP unless the applicable ESPR delegated act and DPP technical requirements are also satisfied. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - ESPR says DPP requirements are specified through delegated acts and access rights, so an EPREL record alone should not be treated as passport compliance.
[ETSI TS 103 881](https://www.etsi.org/deliver/etsi_ts/103800_103899/103881/01.01.01_60/ts_103881v010101p.pdf?ref=sorena.io) - Identifies EPREL as the European Product Registry for Energy Labelling in the DPP standards landscape.
[JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Describes energy-label QR access to EPREL and its role in energy-label information. | | Covered actors | DPP requirements arise under ESPR information requirements for product groups. ESPR is broad and can cover sustainability, circularity, value retention, reuse, remanufacturing, recycling, and legal-compliance information depending on the product-specific rules. | EPREL is tied to energy-related products and energy labels under the Energy Labelling Regulation. ESPR expressly says Regulation (EU) 2017/1369 applies in parallel to ESPR for energy-related products. | Start by asking whether the product is covered by an ESPR delegated act requiring a DPP, whether it is energy-labelled, or both. The overlap is product-specific, not automatic. | [CIRPASS DPP system architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - Defines the DPP scope around product-related data for sustainability, circularity, value retention, recycling, and legal compliance.
[Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - States that the Energy Labelling Regulation applies in parallel to ESPR for energy-related products.
[JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Explains that products can sit under both ESPR label considerations and the energy-labelling framework. | | Trigger | DPP data is product-passport data. ESPR says the passport can be specific to the item, batch, or product model, with the level selected in the product-specific delegated act. ETSI describes DPP information as product-specific data conveyed through a unique identifier. | EPREL grounding is model-and-label oriented: energy labels identify a model and link via QR code to EPREL for additional technical specifications and information. The provided grounding does not support treating EPREL as an item-level lifecycle passport. | Map DPP data at the granularity required by the ESPR delegated act. Reuse EPREL model data only where the same attribute, product group, and access need are explicitly supported. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - DPP granularity and data content depend on the applicable delegated act, so EPREL reuse needs an attribute-level mapping.
[ETSI ES 204 082](https://www.etsi.org/deliver/etsi_es/204000_204099/204082/01.01.01_60/es_204082v010101p.pdf?ref=sorena.io) - Defines a digital product passport as structured product-specific data conveyed through a unique identifier.
[JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Supports the energy-label QR link to EPREL and the model identifier context on energy-label layouts. | | Core obligations | DPP access is role-based. ESPR names customers, manufacturers, importers, distributors, dealers, repairers, recyclers, market surveillance authorities, customs authorities, and others, but access is controlled by the rights set in the delegated act. Rights to introduce, modify, or update data are also restricted. | The grounding supports EPREL as an energy-label database that consumers can reach from a label QR code for additional technical specifications and information. It does not support broad claims about EPREL write permissions, restricted fields, or authority workflows. | For DPP, design access control and update authority as part of the passport architecture. For EPREL, keep claims to the energy-label/product-database function unless separate EPREL-specific source material is added. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the need to implement DPP access controls rather than assuming energy-label database access rules apply.
[JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Supports consumer-facing energy-label QR access to EPREL for additional technical information. | | Evidence record | DPP must be linked to a unique product identifier. Where appropriate it can also link to unique operator and facility identifiers. ESPR requires the passport to be accessible by scanning a data carrier such as a watermark or QR code, preferably on the product itself where possible. | EPREL appears in the grounding through energy-label QR access. The JRC label material describes QR codes on energy labels as links to EPREL; it does not establish EPREL as the DPP data carrier or passport identifier system. | A physical QR code can be involved in both user experiences, but the encoded target and identifier governance must be checked separately. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports keeping DPP identifier and data-carrier rules separate from energy-label QR implementation.
[CIRPASS DPP system architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - Defines DPP architecture around a unique product identifier and data carrier.
[JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Supports EPREL as the QR-code target on EU energy labels. | | Timing and deadlines | DPP is designed as a decentralised data system set up and managed by economic operators, with a Commission-managed registry storing at least unique identifiers and, for customs release, commodity codes. The Commission also has to provide a public web portal for searching and comparing passport data according to access rights. | EPREL is an existing Union database/tool that ESPR says the Commission should consider linking to the DPP where feasible. That makes EPREL a possible linked system, not the same as the DPP registry. | Architect integrations as links between systems. Do not collapse the DPP registry, DPP web portal, economic-operator passport data stores, and EPREL into one internal data model. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports treating the DPP registry and web portal as distinct ESPR infrastructure rather than EPREL replacements. | | Enforcement | DPP has explicit customs mechanics in ESPR. Once the registry is operational, a person placing a covered product under release for free circulation must provide or make available the unique registration identifier, and customs checks the identifier and commodity code against registry data. | The provided EPREL grounding does not establish equivalent customs mechanics for EPREL. EPREL may remain relevant to market information for energy-labelled products, but customs-release claims should be tied to the DPP registry when relying on these sources. | Keep customs and border-control implementation on the DPP registry path unless separate EPREL-specific customs sources are added. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports treating customs-release checks as DPP-registry obligations when this source set is used. | | Overlap and reuse | DPP can potentially reuse existing product information where the delegated act permits it and the data fits the required passport field, granularity, access level, freshness, and identifier mapping. | EPREL data may be a useful source for energy-label and model-level information, but the grounding does not support using EPREL as a complete DPP data source for circularity, repair, substances, lifecycle, supply-chain, or customs-registry fields. | Reuse EPREL data as a mapped input, not as a compliance shortcut. Keep a field-by-field trace showing the source, passport field, access rule, and update owner. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - DPP fields and access rights are delegated-act dependent, so reuse needs field-level evidence.
[CIRPASS DPP recommendations](https://cirpassproject.eu/faq/?ref=sorena.io) - Supports policy-coherence concerns and reducing duplicate effort when DPP data overlaps with existing databases such as EPREL.
[JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Supports EPREL as a source of energy-label-linked technical information, not a complete DPP substitute. | | Practical decision rule | DPP can sit behind an ESPR label or other product information route. ESPR says labels can include data carriers or other means to access additional information, including the DPP. | EPREL is strongly tied to the energy label in the grounding: the JRC material describes energy labels with QR codes linking to EPREL, and ESPR says energy labels remain a successful instrument for energy-related products. | For an energy-related product, decide whether ESPR information can be supplementary information on the energy label, whether a separate ESPR label is needed, and whether DPP access belongs on or near that label. | [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the continued parallel role of energy labels for energy-related products.
[JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Supports assessing whether ESPR information should be integrated into an energy label or handled through a separate ESPR label. | Sources for Scope boundary - Digital Product Passport: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports DPP as the ESPR tool for value-chain product information, traceability, differentiated access, and competent-authority use. - Quote: "making information available to actors along the entire value chain" Sources for Scope boundary - EPREL: - [ETSI TS 103 881](https://www.etsi.org/deliver/etsi_ts/103800_103899/103881/01.01.01_60/ts_103881v010101p.pdf?ref=sorena.io) - Identifies EPREL as the European Product Registry for Energy Labelling in the DPP standards landscape. - Quote: "European Product Registry for Energy Labelling" - [JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Describes energy-label QR access to EPREL and its role in energy-label information. - Quote: "QR code with link to EPREL" 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 says DPP requirements are specified through delegated acts and access rights, so an EPREL record alone should not be treated as passport compliance. - Quote: "as specified in the delegated act" Sources for Covered actors - Digital Product Passport: - [CIRPASS DPP system architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - Defines the DPP scope around product-related data for sustainability, circularity, value retention, recycling, and legal compliance. - Quote: "sustainability, circularity, value retention for reuse" Sources for Covered actors - EPREL: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - States that the Energy Labelling Regulation applies in parallel to ESPR for energy-related products. - Quote: "applies, in parallel to this Regulation" Sources for Covered actors - operational implication: - [JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Explains that products can sit under both ESPR label considerations and the energy-labelling framework. - Quote: "covered by both Regulation (EU) 2017/1369" Sources for Trigger - Digital Product Passport: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports item, batch, or product-model granularity for DPP data depending on product-specific rules. - Quote: "specific to the item, batch or product model" - [ETSI ES 204 082](https://www.etsi.org/deliver/etsi_es/204000_204099/204082/01.01.01_60/es_204082v010101p.pdf?ref=sorena.io) - Defines a digital product passport as structured product-specific data conveyed through a unique identifier. - Quote: "structured collection of product-specific data" Sources for Trigger - EPREL: - [JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Supports the energy-label QR link to EPREL and the model identifier context on energy-label layouts. - Quote: "MODEL IDENTIFIER" Sources for Trigger - operational implication: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - DPP granularity and data content depend on the applicable delegated act, so EPREL reuse needs an attribute-level mapping. - Quote: "what data are to or can be included" Sources for Core obligations - Digital Product Passport: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Lists actors with DPP access and requires access and update rights to follow delegated-act rules. - Quote: "based on their respective access rights" Sources for Core obligations - EPREL: - [JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Supports consumer-facing energy-label QR access to EPREL for additional technical information. - Quote: "additional technical specifications and information" Sources for Core obligations - operational implication: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the need to implement DPP access controls rather than assuming energy-label database access rules apply. - Quote: "rights to introduce, modify or update data" Sources for Evidence record - 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 link to unique product identifiers and access through a data carrier. - Quote: "linked to a unique product identifier" - [CIRPASS DPP system architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - Defines DPP architecture around a unique product identifier and data carrier. - Quote: "accessible via electronic means through a Data Carrier" Sources for Evidence record - EPREL: - [JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Supports EPREL as the QR-code target on EU energy labels. - Quote: "QR code with link to EPREL" Sources for Evidence record - operational implication: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports keeping DPP identifier and data-carrier rules separate from energy-label QR implementation. - Quote: "unique identifiers and data carriers" Sources for Timing and deadlines - Digital Product Passport: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the decentralised DPP design, Commission registry, registry contents, and public web portal. - Quote: "based on a decentralised data system" Sources for Timing and deadlines - EPREL: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Names EPREL as an existing Union database/tool that may be linked where feasible. - Quote: "link the digital product passport to existing Union databases" Sources for Timing and deadlines - operational implication: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports treating the DPP registry and web portal as distinct ESPR infrastructure rather than EPREL replacements. - Quote: "publicly accessible web portal" Sources for Enforcement - Digital Product Passport: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports DPP registry customs checks for unique registration identifier and commodity code. - Quote: "customs authorities may release a product" Sources for Enforcement - EPREL: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - The same ESPR source ties customs mechanics to the DPP registry, not to EPREL in the available grounding. - Quote: "data stored in the registry" Sources for Enforcement - operational implication: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports treating customs-release checks as DPP-registry obligations when this source set is used. - Quote: "EU Customs Single Window" Sources for Overlap and reuse - Digital Product Passport: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports linking DPP to existing Union databases where feasible while preserving DPP requirements. - Quote: "Where feasible" - [CIRPASS DPP recommendations](https://cirpassproject.eu/faq/?ref=sorena.io) - Supports policy-coherence concerns and reducing duplicate effort when DPP data overlaps with existing databases such as EPREL. - Quote: "Some data requirements are already fulfilled" Sources for Overlap and reuse - EPREL: - [JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Supports EPREL as a source of energy-label-linked technical information, not a complete DPP substitute. - Quote: "additional technical specifications and information" 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) - DPP fields and access rights are delegated-act dependent, so reuse needs field-level evidence. - Quote: "access rights at product group level" Sources for Practical decision rule - Digital Product Passport: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports labels including data carriers or other means to access additional product information and the DPP. - Quote: "including means allowing access to the digital product passport" Sources for Practical decision rule - EPREL: - [JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Supports the energy-label QR connection to EPREL and discussion of ESPR label interaction with energy labels. - Quote: "European Product Database for Energy Labelling" - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the continued parallel role of energy labels for energy-related products. - Quote: "Energy labels are a successful instrument" Sources for Practical decision rule - operational implication: - [JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Supports assessing whether ESPR information should be integrated into an energy label or handled through a separate ESPR label. - Quote: "incorporate classes of performance" ### Practical decision rule - Use Digital Product Passport when the facts match the left-side scope, trigger, and evidence rows. - Use EPREL when the facts match the right-side scope, trigger, and evidence rows. - Reuse controls only where the comparison rows show the same actor, obligation, timing, and evidence basis. ## How to use the comparison Use this page when an energy-labelled product is also being assessed for ESPR/DPP readiness. The comparison is designed to prevent a common architecture mistake: treating EPREL, an energy-labelling product database, as though it were the full DPP infrastructure. The strongest shared point is linkage, not substitution. ESPR says the Commission should consider linking DPP information requirements to existing Union databases and tools such as EPREL where feasible. That supports integration planning, but it does not remove the DPP requirements for unique identifiers, data carriers, access rights, registry upload, availability, security, and product-specific delegated-act data. - Use EPREL fields as candidate inputs only after mapping the exact DPP field, product granularity, access right, and update owner. - Keep the energy-label QR journey and the DPP data-carrier journey distinct until the product-specific rules and technical design prove they can converge. - Do not publish claims about EPREL penalties, registration thresholds, supplier portals, restricted fields, or customs checks unless those facts are added from EPREL-specific grounding. Sources for this answer: - [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, access rights, registry design, and possible linkage to EPREL. - [JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Grounds the energy-label side of the comparison, including QR-code links to EPREL and interaction between ESPR and energy labels. *Recommended next step* *Placement: after comparison matrix* ## Map DPP and EPREL data before implementation Build a field-level matrix for product identifiers, label data, passport fields, access rights, registry fields, and source ownership before merging DPP and EPREL workstreams. - [Open Research Copilot](/solutions/research-copilot.md): Answer DPP and product-data questions with cited source material. - [Discuss DPP implementation](/contact.md): Review product scope, data-source reuse, and passport architecture with Sorena. ## Primary sources - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports the continued parallel role of energy labels for energy-related products. - Quote: "Energy labels are a successful instrument" - [CIRPASS DPP system architecture](https://doi.org/10.5281/zenodo.10949842?ref=sorena.io) - Defines DPP architecture around a unique product identifier and data carrier. - Quote: "accessible via electronic means through a Data Carrier" - [ETSI ES 204 082](https://www.etsi.org/deliver/etsi_es/204000_204099/204082/01.01.01_60/es_204082v010101p.pdf?ref=sorena.io) - Defines a digital product passport as structured product-specific data conveyed through a unique identifier. - Quote: "structured collection of product-specific data" - [ETSI TS 103 881](https://www.etsi.org/deliver/etsi_ts/103800_103899/103881/01.01.01_60/ts_103881v010101p.pdf?ref=sorena.io) - Identifies EPREL as the European Product Registry for Energy Labelling in the DPP standards landscape. - Quote: "European Product Registry for Energy Labelling" - [JRC methods for ESPR labels](https://publications.jrc.ec.europa.eu/repository/handle/JRC129907?ref=sorena.io) - Supports assessing whether ESPR information should be integrated into an energy label or handled through a separate ESPR label. - Quote: "incorporate classes of performance" - [CIRPASS DPP recommendations](https://cirpassproject.eu/faq/?ref=sorena.io) - Supports policy-coherence concerns and reducing duplicate effort when DPP data overlaps with existing databases such as EPREL. - Quote: "Some data requirements are already fulfilled" ## 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 GS1 Digital Link: Duties vs Standard](/artifacts/eu/digital-product-passport/dpp-vs-gs1-digital-link.md): Compare EU Digital Product Passport requirements with GS1 Digital Link: legal scope, identifiers, data carriers, access rights, registry, portal, customs checks, and implementation consequences. - [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-eprel