Topic hub
ESPR and the Digital Product Passport
Maintained by Y. Lietzke, editor · 5 issues in this hub
In short
The Ecodesign for Sustainable Products Regulation (Regulation (EU) 2024/1781) is a framework: it creates the Digital Product Passport and the power to set product requirements, but the substantive obligations arrive per product group through delegated acts. The working plan tells you which groups are queued; the delegated act sets the scope, data fields, and application date that bind you. Practically, the working plan is an 18–36 month early-warning signal and the transition period is your supplier-negotiation window.
What is espr and the digital product passport, and why does it matter?
ESPR replaced the old Ecodesign Directive with something far broader: it can regulate durability, repairability, recycled content, substances of concern, and — through the Digital Product Passport — the information that must travel with a product. Almost none of that is enforceable against a specific product until the Commission adopts a delegated act for that product group.
This hub follows the pipeline and the mechanics: how to read the working plan, what a delegated act typically contains, how the passport's data requirements land on a bill of materials, and how enforcement is expected to work. If you only take one thing from the coverage: build the data register before you shortlist a platform.
What do you need to get right?
- What ESPR is
- A framework regulation creating the Digital Product Passport and the power to set per-category product requirements.
- What actually binds you
- The delegated act for your product group — it sets scope, data fields, and the application date.
- How much notice you get
- The working plan signals intent well in advance; the transition period after adoption has historically run around 18–24 months.
- What to build first
- A one-table data register: field, source system, named owner, and whether the field is supplier-dependent.
Which issues cover this topic?
No. 013 ·
What the ESPR working plan actually commits the Commission to
How to read the ESPR working plan: which product groups are queued for delegated acts, and what that means for your DPP planning horizon.
No. 012 ·
The supplier data clause that decides your DPP timeline
Why Digital Product Passport programmes slip on supplier response time, and the contract language that fixes it at renewal.
No. 011 ·
How market surveillance authorities will actually check a product passport
What an authority sees when it scans a data carrier, and the three failure modes that turn a passport check into a finding.
No. 010 ·
Choose your data carrier and identifier before you choose a platform
Why identifier and resolver decisions outlast your DPP platform choice, and how to avoid reprinting carriers later.
No. 009 ·
Importers carry passport liability for data they never created
What EU importers are accountable for under the Digital Product Passport, and how to get leverage over data held outside the EU.
Which resources help most here?
- ESPR / DPP Readiness Kit — Know exactly where your product data fails, and what to fix first. (from €149)
- DPP Vendor & Standards Landscape Report — Choose a DPP vendor without a six-month evaluation. (from €199)
Frequently asked questions
- Does ESPR require a Digital Product Passport for every product?
- No. ESPR creates the passport, but a product only falls in scope once a delegated act for its product group applies.
- How long do companies have after a delegated act is adopted?
- Expect roughly 18–24 months between adoption and application, based on previous ecodesign measures. Supplier data collection typically consumes most of it.
- What should we do before our product group is regulated?
- Map candidate data fields against source systems and owners, and add data-supply clauses to supplier contracts at the next renewal. Both survive whatever the delegated act requires.
Other topic hubs
Track this topic weekly
One issue a week, Tuesday at 07:00 CET. Free, and unsubscribe in one click.