Digital Product Passport
Guide to ESPR scope, product-group rollout, data carriers, unique identifiers, registry, portal, customs access and data readiness.
This hub explains the framework in the Ecodesign for Sustainable Products Regulation (ESPR), Regulation (EU) 2024/1781. A product does not receive a universal DPP duty merely because ESPR is in force: start with the product group and the applicable delegated act.
Use the guides to identify the responsible , then map the delegated act's passport level (model, batch, or item), Annex III data, carrier, access rights, update roles, availability period, registry steps, and evidence.
Do not treat DPP as a fixed spreadsheet. The delegated act determines the data, access rights, update roles, presentation of the , passport level and availability period. Harmonised standards support the technical build but do not select the product group or its mandatory fields.
Consumers, repairers, refurbishers, recyclers, market-surveillance authorities, customs authorities and other actors receive access based on rights set for the product group.
The Registry is live for organisation enrolment and DPP registration. For covered imports, keep the registration identifier and commodity code aligned with registry data; customs release is not proof of product compliance.
Check whether an adopted product-specific delegated act requires a DPP. A working-plan priority or consultation is a preparation signal, not by itself a live product duty.
Identify the placing the product on the market or putting it into service, then extract the passport level, , , open-data, backup, access, and update rules. For the Article 10 and 11 technical requirements, check the six EN 182xx:2026 standards cited in the Official Journal on 15 July 2026.
The Commission launched the DPP Registry and a testing environment on 20 July 2026. Prepare enrolment, registration, market-surveillance, and customs handoffs without treating a registry record or customs release as proof that the product complies.
Use the milestone view to coordinate delegated-act monitoring, product-data modelling, supplier evidence, data-carrier decisions, registry integration, portal access, service-provider controls and customs-readiness work.
New to DPP? Establish the product-group trigger and responsible operator first. If those decisions are documented, jump to the data model, architecture, implementation evidence, deadline, comparison, or focused question you need.
Understand what an ESPR DPP is, test whether a product-specific rule creates a passport duty, and separate fixed legal dates from delegated-act-dependent product deadlines.
Translate Articles 9 to 15, Annex III, and the applicable delegated act into product fields, access categories, authority handoffs, and enforcement exposure.
Design the passport as a connected system: product identity, physical carrier, resolver, role-based views, decentralised data, backup service, EU registry, and public portal each perform a different function.
Turn the legal design into owned data intake, supplier validation, access governance, customs review, release gates, audit records, and vendor requirements.
Separate ESPR duties from battery-passport rules, EPREL, GS1 Digital Link, digital twins, and legacy product records, or use the FAQ for a direct answer.
"guidelines for decision-making on designing a Digital Product Passport"
"structured collection of product-specific data conveyed through a unique identifier"
"The objective is to gather stakeholders' views on how data should be stored and managed by service providers"
"aims to significantly improve the sustainability of products placed on the EU market"
"The data in the digital product passport shall be accurate, complete and up to date."
Next steps
Assign confirmed DPP duties to product, regulatory, engineering, supplier, sustainability and trade teams in ESG Compliance. Keep the supporting data model, identifier records, registry evidence and access-control decisions in SSOT.
Manage product-group monitoring, supplier evidence, sustainability data and DPP readiness work from one workflow.
Keep DPP data models, identifiers, carrier decisions, registry uploads, access rules and customs evidence in one governed system.
Align delegated acts, registry setup, portal access, customs checks and product-data readiness.
Review product scope, DPP data fields, identifier strategy, access controls, service-provider choices and release planning.