Logo

DPP Basics: An Overview of Regulations and Deadlines

Reading time:

minutes

When it comes to the Digital Product Passport, by 2026 the question will no longer be simply when individual products require a DPP. Companies must understand how the regulatory components interact. The ESPR, work plan, delegated acts, sectoral regulations, and DPP registry each serve different functions. By distinguishing between these levels, companies can plan more effectively and avoid confusing political timelines with legal obligations.

Four Levels Instead of a Single Regulation

 

For decision-makers, the DPP regulatory framework can be viewed as a four-level model.

 

Level 1

The framework: The ESPR (Regulation (EU) 2024/1781) defines basic rules for the Digital Product Passport. It has been in effect since July 2024. Among other requirements, a product passport must be linked to a data carrier with a unique product identifier.

 

Level 2

Product law: Only the legal acts applicable to a product group determine, for example, what data belongs in the DPP, what data carrier is used, who is authorized to view the information, and whether the passport is maintained at the model, batch, or item level.

 

In addition, sector-specific regulations exist. The most prominent example is the Battery Regulation with its own battery passport.

Level 3

The Infrastructure: The EU DPP Registry has been operational since July 20, 2026. It functions as a central index. In particular, unique identifiers and metadata are registered; the complete product information is generally provided decentrally.

 

Level 4

The Implementation Date: It is only at this stage that it becomes decisive for companies when a specific obligation actually takes effect. Therefore, a year listed in the ESPR work plan should not automatically be interpreted as a DPP deadline.

 

Work Plan ≠ DPP Deadline

The ESPR Work Plan 2025–2030 prioritizes, among other things, iron and steel, aluminum, textiles and apparel, furniture, tires, and mattresses.


The Commission provides indicative timelines for its regulatory work. These show companies the direction in which regulation is heading, but do not replace product-specific legislation.

For C-level executives, these timelines are therefore early warning signals, not compliance deadlines.

 

Which DPP deadline is already binding?

There is a clear deadline for the battery passport, starting February 18, 2027, electric vehicle batteries, batteries for light-duty vehicles, and industrial batteries with a capacity of more than 2 kWh must, as a general rule, have a battery passport.

The difference is significant, in this case, the deadline stems directly from the Battery Regulation. For many ESPR product groups, however, the relevant legal act must first be in place.

 

In 2026, the DPP landscape will change


With the operational DPP registry and published technical standards, the Digital Product Passport is increasingly evolving from a regulatory concept into a real European data infrastructure.
This also changes the management question.

Instead of asking solely, “When do we need to have a DPP?” companies should also clarify:

  • Can our systems manage unique product identities? 
  • Where is the relevant data located?
  • Who is responsible for its quality and updates?
  • Can data from PIM, MDM, ERP, and supplier systems be consistently consolidated?


These questions remain relevant even if individual product-specific mandatory fields have not yet been finalized. 

 

A DPP roadmap should have two speeds


Companies therefore do not need a rigid implementation for all products at the same time.


Compliance Track: Products with requirements that are already binding or at an advanced stage are assigned clear deadlines, responsibilities, and implementation budgets.


Readiness Track: For product groups to be addressed later, product identities, data models, supplier processes, and interfaces are prepared without preempting pending regulatory acts.


This turns regulatory requirements into a guiding framework for investments. asioso can provide particular support in integrating these requirements with product data management and existing system architecture.

 

The key principles of DPP cannot be reduced to a simple list of deadlines. What matters most is the interplay between the regulatory framework, product-specific regulations, technical infrastructure, and the actual implementation date.


For management teams, this leads to a clear set of priorities: implement mandatory requirements, monitor upcoming product regulations, and simultaneously create a reusable database. This way, there is no need to start a new DPP project for every new product group.

 

Is the DPP Registry already available?

Yes. The European Commission launched the DPP Registry and a test environment on July 20, 2026.


Does an entry in the ESPR Roadmap already mean that DPP is mandatory?
No. The Roadmap prioritizes regulatory measures. The specific requirements are set forth in the relevant legal acts.


Is all product data stored centrally by the EU?
Generally, no. The registry primarily serves as an index for identifiers, registration information, and metadata. The actual DPP data follows a decentralized approach.


Which DPP deadline is particularly relevant?
The Battery Passport will be mandatory starting February 18, 2027, for the battery categories specified in the Battery Regulation.

 

Would you like to consolidate regulatory requirements, your product portfolio, and data architecture into a single DPP roadmap? A DPP readiness check with asioso can help you distinguish between mandatory actions and sensible preparatory steps.

Does this fit your project?

Share

Categories

Digital Product Passport - Is my product affected?


September 29, 2026

Which industries does the Digital Product Passport affect?


September 08, 2026

DPP Basics


September 08, 2026