--- title: "EU Digital Product Passport requirements under ESPR" canonical_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/requirements" source_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/requirements" author: "Sorena AI" description: "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." published_at: "2026-05-09" updated_at: "2026-07-24" keywords: - "EU Digital Product Passport" - "ESPR" - "Digital Product Passport requirements" - "unique product identifier" - "data carrier" - "DPP registry" - "access rights" - "battery passport" - "Digital Product Passport" - "Requirements" - "unique identifier" - "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) --- # EU Digital Product Passport requirements under ESPR 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. *DPP* *Requirements* *EU ESPR* ## EU Digital Product Passport Requirements Understand what ESPR already fixes for Digital Product Passports and what each product-specific delegated act still has to define. This overview helps scope passport data, identifiers, carriers, access rights, registry uploads, customs checks, and supplier evidence without treating unfinished technical rules as final. EU Digital Product Passport requirements vary by product group. Under Regulation (EU) 2024/1781, ESPR creates the horizontal passport framework, while product-specific delegated acts decide when a product group needs a passport and which data, carrier, access rights, and passport level apply. Teams should design DPP readiness around those two layers: stable ESPR architecture first, then product-group rules as they are adopted. ## Definitions ### Digital Product Passport under ESPR **Term:** Digital Product Passport A Digital Product Passport under Regulation (EU) 2024/1781 is a product-specific set of data connected through a data carrier to a persistent unique product identifier. Its data must be accurate, complete, and up to date, use open and interoperable formats as required, and remain available for the period fixed by the applicable product-group act. **Why it matters here:** ESPR supplies the horizontal architecture. The applicable delegated act or another binding Union act decides whether a particular product needs a passport and fixes its fields, carrier and placement, model/batch/item level, access and update rights, application date, and exceptions. Sources: - [Regulation (EU) 2024/1781, Articles 9-11](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) ### Harmonised standards for Digital Product Passports **Term:** harmonised DPP standards Harmonised DPP standards are European standards developed for the Digital Product Passport system whose references, or the references to their harmonised parts, the European Commission publishes in the Official Journal. The cited standards address technical subjects such as identifiers, data carriers, interoperability, APIs, data exchange, and storage. **Why it matters here:** A harmonised standard can support technical implementation within its cited scope, but it does not decide whether a product needs a passport or set that product group's fields, access rights, granularity, or application date. Those requirements come from the applicable Union legislation. Sources: - [European Commission: harmonised DPP standards](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards/digital-product-passport-dpp_en?ref=sorena.io) ## What ESPR already requires for a Digital Product Passport ESPR links Digital Product Passport obligations to information requirements in delegated acts. A covered product can be placed on the EU market or put into service only if the required passport is available under the applicable delegated act and the ESPR passport rules. The passport data must be accurate, complete, and up to date. The delegated act for the product group is the controlling document for operational scope. It must specify the passport data, the data carrier, carrier layout and positioning, whether the passport is at model, batch, or item level, pre-contract access including distance selling, who can access which data, who can create or update data, how updates are made, and how long the passport remains available. Regulation (EU) 2024/1781 entered into force on 18 July 2024, but that date did not make a passport mandatory for every product. Each final product-group act supplies its own application and transition terms; ESPR generally prevents an Article 4 delegated act from applying earlier than 18 months after entry into force unless an earlier date is duly justified. The Commission may also exempt a product group from a DPP where the required technical specifications are unavailable or another Union-law digital information system achieves the relevant access and authority-verification objectives. - Start with the product group and commodity-code coverage in the delegated act, not with a generic DPP template. - Separate ESPR horizontal requirements from product-specific requirements, because the product act decides the final data set and passport level. - Treat passport availability, data accuracy, access rights, and retention as compliance requirements, not just IT publishing tasks. - Plan DPP information for value-chain access, competent-authority verification, market surveillance, and traceability. Sources for this answer: - [Regulation (EU) 2024/1781 establishing ESPR](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Articles 7 to 11 establish information requirements, the product-specific delegated-act model, passport availability, data accuracy, passport level, carrier, access, and technical operation. ## Data fields, identifiers, and carriers to design around Annex III gives the menu of passport elements that product-specific delegated acts can require. That menu includes the unique product identifier, GTIN or equivalent product identifiers, commodity codes, compliance documentation, user instructions, manufacturer and importer information, unique operator identifiers, unique facility identifiers, and the DPP service provider reference for the back-up copy. ESPR also defines the carrier and identifier architecture. The passport must be connected through a data carrier to a persistent unique product identifier. The carrier must be physically present on the product, packaging, or accompanying documentation as the delegated act specifies. References to harmonised DPP standards were published by July 2026; check the cited standard's scope and the applicable product rule before selecting identifiers or carriers. - Model the passport around product, operator, facility, importer, EU responsible person, compliance-document, and back-up-provider fields. - Keep a clear link between the visible carrier and the persistent unique product identifier that resolves to the passport. - Do not assume QR code is always the final carrier for every ESPR product group; the delegated act specifies the carrier or carriers. - Preserve version history for data introduced or updated by different actors, because ESPR restricts update rights by access rights. Sources for this answer: - [Regulation (EU) 2024/1781 establishing ESPR](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Articles 10 to 12 and Annex III define the passport connection to a persistent unique product identifier, the physical carrier requirement, identifier categories, and standards references. - [European Commission: harmonised DPP standards](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards/digital-product-passport-dpp_en?ref=sorena.io) - Current official page for references to harmonised DPP standards; confirm each standard's scope before applying it to identifiers, carriers, interoperability, APIs, exchange, or storage. ## Registry, web portal, customs, and access rights The Commission launched the DPP Registry and a testing environment on 20 July 2026. The Registry indexes DPPs and stores unique identifiers, registration data, and high-level metadata rather than the full passport. Commission Implementing Regulation (EU) 2026/1778 sets its operational framework and takes effect on 6 August 2026; registration is available through a secure user interface or API. For imports, customs controls use the Registry to match the unique registration identifier and commodity code where the applicable Union legislation requires a DPP. Automated validation and proof of registration confirm registry processing, not the substantive correctness of the product data or overall compliance. Access is not all-public. ESPR names broad actor categories, including customers, economic operators, repairers, refurbishers, remanufacturers, recyclers, market surveillance authorities, customs authorities, civil society organisations, trade unions, and other relevant actors, but the applicable delegated act determines who can access which product-group data and who can introduce or update it. - Build a registry upload record for unique identifiers, commodity codes where relevant, and any extra registry fields later specified for the product group. - Do not represent the registry response as a compliance approval; it is an identifier returned after upload. - Design access-control matrices by actor category and data field, then revise them when the product-specific delegated act sets final access rights. - Coordinate customs master data with DPP identifiers and commodity codes before products are placed under release for free circulation. Sources for this answer: - [Regulation (EU) 2024/1781 establishing ESPR](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Articles 11, 13, 14, and 15 support the access-rights model, Commission registry, public web portal, registry upload, unique registration identifier, and customs-control checks. - [Commission Implementing Regulation (EU) 2026/1778](https://data.europa.eu/eli/reg_impl/2026/1778/oj?ref=sorena.io) - Binding Registry implementation arrangements, published on 17 July 2026 and effective from 6 August 2026, covering verification, user roles, registration through the interface or API, unique registration identifiers, automated checks, versioning, logging, and the semantic repository. - [European Commission: DPP Registry](https://single-market-economy.ec.europa.eu/single-market/digital-product-passport/dpp-registry_en?ref=sorena.io) - Current operational source for the live Registry, testing environment, organisation enrolment, decentralised data model, and economic-operator user guide. ## Supplier data validation and evidence controls DPP teams need supplier evidence because many passport fields depend on upstream material, component, facility, process, durability, repairability, recycled-content, or substance data. ESPR allows delegated acts to require supply chain actors to provide relevant information free of charge to manufacturers, notified bodies, and competent national authorities. Where supplier information is missing, ESPR can require supply chain actors to allow manufacturers to assess supplied products or services and access relevant documents or facilities. It can also require supply chain actors to enable notified bodies and competent national authorities to verify the accuracy of information related to their activities. - Add supplier fields for the claim, source system, measurement or calculation method, facility or actor identifier, date received, and approver. - Validate supplier values before passport publication when they affect compliance documentation, sustainability claims, substances of concern, recycled content, or repair and recycling instructions. - Keep evidence that explains whether a value came from a supplier declaration, test report, calculation, bill of materials, facility record, or authority-verifiable document. - Escalate missing supplier evidence before market placement for products whose delegated act requires the field in the passport. Sources for this answer: - [Regulation (EU) 2024/1781 establishing ESPR](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Article 38 supports supplier information requests, manufacturer access to documents or facilities where information is absent, and authority or notified-body verification of supplier-related information. *Recommended next step* *Placement: after evidence section* ## Turn DPP requirements into a controlled data model This overview helps separate fixed ESPR passport architecture from product-specific delegated-act details before you publish passport data or commit supplier workflows. - [Open Research Copilot](/solutions/research-copilot.md): Check DPP implementation questions against cited EU source material. - [Discuss DPP implementation](/contact.md): Review product scope, passport data fields, supplier evidence, and access controls with Sorena. ## Battery passports show how product-specific rules become concrete The Batteries Regulation is the clearest example of a product-specific passport already written into EU law. From 18 February 2027, it requires a battery passport for each LMT battery, each industrial battery with a capacity greater than 2 kWh, and each electric vehicle battery placed on the market or put into service. The battery passport illustrates why DPP implementation cannot stop at the ESPR horizontal framework. Annex XIII of the Batteries Regulation splits battery passport information into public battery-model data, data for persons with a legitimate interest and the Commission, data for notified bodies, market surveillance authorities and the Commission, and individual-battery data for persons with a legitimate interest. - Public battery-model data includes material composition, carbon footprint information, responsible sourcing, recycled content, renewable content, capacity, voltage, power capability, expected lifetime, energy efficiency, markings, declaration of conformity, and waste-battery information. - Restricted battery-model data includes detailed composition, replacement-spare source details, dismantling information, and safety measures. - Authority-only data includes test-report results proving compliance with the Batteries Regulation and its delegated or implementing acts. - Individual-battery restricted data includes performance and durability values, state of health, battery status, use data, charge/discharge cycles, negative events, operating conditions, and state of charge. Sources for this answer: - [Regulation (EU) 2023/1542 concerning batteries and waste batteries](https://eur-lex.europa.eu/eli/reg/2023/1542/oj/eng?ref=sorena.io) - Article 77, Article 78, and Annex XIII provide the battery passport scope, QR-code and unique-identifier connection, accuracy duty, access tiers, interoperability rules, and concrete battery passport data fields. ## What is not final yet For most ESPR product groups, the decisive details are not final until the relevant delegated act is adopted. Teams should not publish fixed field lists, carrier choices, access tiers, or passport-level assumptions for a product group unless they can tie them to the applicable delegated act or another binding EU act such as the Batteries Regulation. Several technical and governance pieces still depend on future or product-specific acts. ESPR empowers the Commission to set DPP service-provider requirements and, where appropriate, a certification scheme; to set procedures for digital credentials for actors with access rights; and to establish life-cycle rules for unique identifiers and data carriers. Product-group acts still control fields, carrier placement, granularity, access, update rights, and availability. Registry implementation is no longer an entirely open point: Implementing Regulation (EU) 2026/1778 now sets the operational framework and takes effect on 6 August 2026. Service-provider certification and product-specific access rules should still be tracked separately rather than inferred from the Registry launch. - Do not claim that one common DPP field list applies to all ESPR products. - Do not lock the carrier, placement, access rights, update permissions, or retention period before the product-specific delegated act defines them. - Apply the final Registry rules from Implementing Regulation (EU) 2026/1778 from 6 August 2026, but do not treat service-provider certification, product-specific digital credentials, or identifier life-cycle rules as settled unless a final EU act supports the claim. - Use battery passport rules as a concrete example, not as a universal template for every ESPR product group. Sources for this answer: - [Regulation (EU) 2024/1781 establishing ESPR](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Articles 9 to 13 reserve product-group passport details, service-provider requirements, digital credentials, identifier life-cycle rules, and registry implementation arrangements for delegated or implementing acts. - [European Commission consultation on the Digital Product Passport](https://single-market-economy.ec.europa.eu/news/commission-launches-consultation-digital-product-passport-2025-04-09_en?ref=sorena.io) - Commission consultation page supports treating DPP service-provider data storage, management, and possible certification as still subject to rule development rather than final operating detail. - [Commission Implementing Regulation (EU) 2026/1778](https://data.europa.eu/eli/reg_impl/2026/1778/oj?ref=sorena.io) - Separates the now-adopted Registry arrangements from product-group requirements and other service-provider or credential rules that remain dependent on further acts. ## Primary sources - [Regulation (EU) 2024/1781 establishing ESPR](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Primary legal source for the ESPR Digital Product Passport framework, including Articles 7 to 15, Article 38, and Annex III on information requirements, passport contents, identifiers, carriers, access, registry, customs, and supplier-information verification. - Quote: "Digital Product Passport" - [Regulation (EU) 2023/1542 concerning batteries and waste batteries](https://eur-lex.europa.eu/eli/reg/2023/1542/oj/eng?ref=sorena.io) - Primary legal source for the battery passport example, including Article 77, Article 78, and Annex XIII on battery passport scope, access tiers, QR-code link, unique identifier, accuracy duty, and concrete data categories. - Quote: "INFORMATION TO BE INCLUDED IN THE BATTERY PASSPORT" - [European Commission consultation on the Digital Product Passport](https://single-market-economy.ec.europa.eu/news/commission-launches-consultation-digital-product-passport-2025-04-09_en?ref=sorena.io) - Commission source for the point that DPP service-provider storage, management, and possible certification requirements were being consulted on and should not be treated as final product-group implementation detail. - Quote: "future Digital Product Passport" - [Commission Implementing Regulation (EU) 2026/1778](https://data.europa.eu/eli/reg_impl/2026/1778/oj?ref=sorena.io) - Current binding source for DPP Registry implementation arrangements, with effect from 6 August 2026. - [European Commission: DPP Registry](https://single-market-economy.ec.europa.eu/single-market/digital-product-passport/dpp-registry_en?ref=sorena.io) - Current official source for the live Registry and testing environment. - [European Commission: harmonised DPP standards](https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards/digital-product-passport-dpp_en?ref=sorena.io) - Official reference page for harmonised DPP standards. ## 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): An intake workflow for EU Digital Product Passport data models: product scope, legal status, field owner, evidence, access class, identifiers, carrier, registry mapping, 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): Official source 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. - [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): 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): 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): 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): EU Digital Product Passport calendar covering the live DPP Registry, ESPR product-rule milestones, and fixed battery passport dates. - [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): How EU Digital Product Passport breaches can lead to national penalties, corrective action, market restrictions, and customs holds under ESPR or battery law. - [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 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 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): 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 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.md) | [Terms of Use](https://www.sorena.io/terms-of-use.md) | [DMCA](https://www.sorena.io/dmca.md) | [About Us](https://www.sorena.io/about-us.md) (c) 2026 Sorena AB (559573-7338). All rights reserved. Source: https://www.sorena.io/artifacts/eu/digital-product-passport/requirements.md