Ecodesign for Sustainable Products Regulation
The ESPR establishes a framework for Digital Product Passports. Specific obligations and timing depend on product group measures and applicable delegated acts.
Read the regulationDPP & COMPLIANCE
Make product dataready forwhat comes next.
Regulatory requirements evolve. Your data infrastructure should be ready to evolve with them.
CodeNekt connects vehicle identity, lifecycle records and trustworthy source information to help automotive organisations prepare for increasingly structured product data requirements.
THE DISTINCTION
Infrastructure for compliance. Not a compliance certificate.
A Digital Product Passport is a regulatory information instrument when required by applicable EU rules.
Its obligations depend on the product, its legislation and the information to be made available to different users. CodeNekt focuses on the reusable digital foundations: identity, structured lifecycle information, provenance and controlled access.
Those capabilities can support compliance work, but software infrastructure alone does not establish that a product or operator meets all legal requirements.
REGULATORY LANDSCAPE
Know which requirements apply to which product.
Different passports operate under different legal instruments. Do not confuse a useful vehicle record with a prescribed regulatory passport.
EU Batteries Regulation
Article 77 requires battery passports from 18 February 2027 for covered batteries, including electric vehicle batteries. The passport includes model and individual battery information with differentiated access.
Read Article 77Vehicle lifecycle infrastructure
A Digital Vehicle Passport can connect vehicle identity, service history, condition, ownership transitions and provenance. It is not, by itself, proof of compliance with a particular EU product passport obligation.
Explore vehicle passportsRegulatory information is an overview, not legal advice. Product scope, effective dates, technical standards and delegated acts should be checked against current official EU publications.
CODE NEKT DATA FOUNDATIONS
Build the information layer once. Make it useful across the lifecycle.
Structured lifecycle data
Connect relevant product, vehicle and component information across systems rather than creating another isolated record.
Traceable information
Preserve source, timestamp and supporting evidence so information can be evaluated and audited.
Role based access
Support different information needs for consumers, economic operators, repairers and authorised parties.
Evolving information models
Adapt the information layer as applicable sector specific legal and technical requirements become defined.
CONNECTED BY DESIGN
Three foundations. One vehicle lifecycle.
FREQUENT QUESTIONS
Understand DPP requirements without the confusion.
What is a Digital Product Passport?
A Digital Product Passport is a structured means of making specified product information accessible to relevant actors. The exact data and access requirements depend on the legislation and measures applicable to the product category.
Do all products need a DPP today?
No. The EU's Ecodesign for Sustainable Products Regulation provides a framework, with product specific requirements and dates established progressively through the relevant measures. Separate legislation also establishes passports for particular product categories.
When does the EU battery passport apply?
Under Article 77 of Regulation (EU) 2023/1542, from 18 February 2027 the specified light means of transport batteries, industrial batteries above 2 kWh and electric vehicle batteries placed on the market or put into service must have a battery passport.
Is a Digital Vehicle Passport the same as a battery passport?
No. A Digital Vehicle Passport describes a broader vehicle lifecycle information record, while the battery passport has a defined legal scope and prescribed information requirements under the EU Batteries Regulation.
Does using CodeNekt guarantee regulatory compliance?
No. CodeNekt provides data infrastructure that can support traceability, interoperability and permission aware access. Compliance depends on the applicable legal requirements, accurate data, implementation choices and assessment by the responsible operator.