EU regulations often set out principles and powers, then hand the Commission authority (under Article 290 of the Treaty) to adopt delegated acts that specify the technical detail. This keeps the parent law stable while the specifics evolve. The ESPR uses this structure heavily: it establishes that a DPP can be required and what it can contain, but defers the binding per-product-group rules to delegated acts, each preceded by impact assessment and stakeholder consultation.
This is why so many DPP timelines read "expected" or "to be confirmed." Until the delegated act for a given product group is adopted and enters into force, the exact data fields, the data-carrier rules and the compliance date for that group are not yet legally fixed. The major exception is batteries, governed by their own regulation (EU) 2023/1542, which already sets a firm 18 February 2027 deadline for the battery passport. When a date for any other group is still pending, the honest statement is that it awaits its delegated act.
Frequently asked
Why does my product's DPP deadline depend on a delegated act?
Because the ESPR is a framework: it enables the DPP but leaves the binding rules — data fields, carrier requirements and the compliance date — to a delegated act adopted per product group. Until that act enters into force, the exact requirements for your group are not legally fixed.
How is a delegated act different from the regulation itself?
The regulation (the parent law, like the ESPR) is adopted by the European Parliament and Council and sets the framework and powers. A delegated act is adopted by the Commission under that delegated power to add technical detail, and Parliament and Council can object within a scrutiny period.
Are any DPP requirements already fixed without waiting for a delegated act?
Yes — batteries. The battery passport is set directly by Regulation (EU) 2023/1542 with a firm deadline of 18 February 2027, so it does not wait on an ESPR delegated act. Most other product groups still do.