Compliance and Europe
The EU Digital Product Passport (ESPR): what product data teams must prepare
Quick answer
The EU Digital Product Passport (DPP) is a machine-readable product record required by the Ecodesign for Sustainable Products Regulation (EU) 2024/1781. The EU DPP registry went live on 20 July 2026. Battery passports apply from 18 February 2027, and ESPR delegated acts for steel, textiles, tyres and aluminium follow from late 2026.
Key takeaways
- ESPR, Regulation (EU) 2024/1781, entered into force on 18 July 2024 and makes the Digital Product Passport mandatory product group by product group through delegated acts.
- The EU DPP registry went live on 20 July 2026; it holds identifiers and registration metadata, while passport content stays with the economic operator or its service provider.
- Battery passports under Regulation (EU) 2023/1542 apply from 18 February 2027, the first large-scale DPP deadline.
- The ban on destroying unsold apparel and footwear has applied to large companies since 19 July 2026 and reaches medium-sized companies in 2030.
- Product teams typically need 12 to 18 months to model, source and govern DPP attributes, so preparation should start before the relevant delegated act is adopted (editorial estimate).
The EU Digital Product Passport (DPP) became operational infrastructure in 2026: the Commission's central registry went live on 20 July 2026, and the first hard deadline, for batteries, falls on 18 February 2027. Product data teams should plan the DPP as a new regulated output channel of their PIM and DAM stack, with its own attribute model, identifiers and governance. Teams that build that model now will absorb each delegated act as a configuration change.
What ESPR and the Digital Product Passport require
The Ecodesign for Sustainable Products Regulation (ESPR), Regulation (EU) 2024/1781, entered into force on 18 July 2024 and covers almost all physical goods. It sets requirements per product group through delegated acts, which define performance criteria (durability, repairability, recycled content, substances of concern) and the information a passport must carry. Each passport must be connected through a data carrier, such as a QR code, to a persistent unique product identifier at the model, batch or item level that the delegated act specifies. The practical consequence is that the DPP is a product-group-specific data contract: a steel passport and a textile passport will share infrastructure and differ in content.
The DPP timeline as of October 2026
The registry and the battery deadline are fixed; most ESPR product-group dates remain indicative.
| Milestone | Date | Status |
|---|---|---|
| ESPR entry into force | 18 July 2024 | In force |
| First ESPR working plan (2025 to 2030) | 16 April 2025 | Adopted |
| Ban on destroying unsold apparel and footwear (large companies) | 19 July 2026 | Applies |
| EU DPP registry and test environment | 20 July 2026 | Live |
| Battery passport, Regulation (EU) 2023/1542 | 18 February 2027 | Upcoming |
| Iron and steel delegated act | Indicatively late 2026 | Expected |
| Textiles, tyres and aluminium delegated acts | Indicatively 2027 | Expected |
| Furniture and mattresses delegated acts | Indicatively 2028 to 2029 | Expected |
Operators generally get around 18 months between adoption of a delegated act and its application, so a fashion brand realistically faces passport obligations from 2028 or 2029. Construction products, toys and detergents receive passports under their own EU legislation and will use the same registry. Plan against adoption dates published in the Official Journal, since indicative timelines have slipped before.
How the EU DPP registry works
The registry is a lookup and verification layer, and your passport data stays in your own systems or with your service provider. Under Implementing Regulation (EU) 2026/1778, economic operators register each passport's identifier and mandatory metadata through a web interface or API, and can request a secure proof of registration for B2B transactions. CEN and CENELEC developed eight harmonised standards for DPP interoperability, covering unique identifiers, data carriers, APIs, data exchange, storage, access rights and data integrity. IT architects therefore need a highly available, access-controlled home for the passport itself, in-house or through a DPP service provider.
What product data teams must prepare
Preparation splits into five workstreams that together cover the full passport:
- Identity: an identifier strategy, often GTIN plus batch or serial encoded as a GS1 Digital Link URI, aligned with GS1 product data standards.
- Attributes: environmental and compliance fields (materials, substances, recycled content, carbon footprint) added to the PIM data model.
- Sourcing: supplier data collection, since much passport content originates in the supply chain.
- Documents and media: manuals, safety instructions, repair guides and declarations of conformity, in all required EU languages.
- Governance: ownership, validation rules and audit trails, measured with the same discipline described in product data quality.
We estimate that a mid-market brand with 5,000 to 20,000 SKUs needs 12 to 18 months for these workstreams, with supplier data collection usually the longest pole.
Where PIM and DAM fit in a DPP architecture
The PIM should master passport attributes, and the DAM should master the documents and media the passport links to. A PIM already holds structured product data and variants, so passport fields belong there. The DAM provides persistent URLs, version history and language variants, which matter because a passport must keep pointing to the correct revision of a manual for the product's full lifetime. A DPP platform or service provider then publishes the passport, manages access rights and registers it, following one of the PIM and DAM integration patterns. When evaluating platforms such as Pimcore, Contentserv or censhare, ask how they model passport attributes, expose stable asset links and connect to registry APIs.
What to do next
- Map your portfolio against the ESPR working plan product groups and the battery rules, with a dated exposure list per category.
- Decide your identifier and granularity strategy (model, batch or item) and test it in the registry's test environment.
- Run a gap analysis of PIM attributes against the preparatory studies and draft delegated acts for your product groups.
- Move compliance documents into the DAM with persistent URLs, versioning and language variants.
- Shortlist DPP service providers and require proof of registry API integration before contracting.
Frequently asked questions
When does the Digital Product Passport become mandatory?
It depends on the product group. Batteries covered by Regulation (EU) 2023/1542 need a passport from 18 February 2027. For ESPR product groups, each delegated act sets its own application date, typically around 18 months after adoption, with iron and steel expected first and textiles, tyres and aluminium indicatively in 2027.
Is the EU DPP registry a central database of product data?
The registry stores unique identifiers and mandatory registration metadata and supports validation, discovery and proof of registration. The passport content itself is held decentrally by the economic operator or a DPP service provider acting on its behalf. Operators can register through a web interface or an API.
Does a DAM system have a role in the Digital Product Passport?
Yes. Passports reference documents and media such as user manuals, safety instructions, repair guides and certificates. A DAM that gives these files persistent URLs, version history and language variants provides the stable links a PIM or DPP platform needs to publish compliant passports.
Which identifiers can be used for a Digital Product Passport?
ESPR requires each passport to be connected through a data carrier, such as a QR code, to a persistent unique product identifier. Many brands plan to use GS1 identifiers (GTIN plus batch or serial number) encoded as a GS1 Digital Link URI, which supports model, batch and item level granularity.