EU Digital Circularity Vehicle Passport (DCVP): What Changes for Cars and Vans from 2032?

The EU has adopted a vehicle-specific Digital Circularity Vehicle Passport for in-scope passenger cars and light commercial vehicles. The 2032 duty is fixed, as are the passport's main information territories and its requirement to work with other vehicle and product passports. The technical carrier, identifier, storage model, access conditions and final interoperability profile are not yet settled.

What has actually changed in EU vehicle law?

Regulation (EU) 2026/1738 is already in force. It entered into force on 13 August 2026 and generally applies from 1 September 2028. That general application date is not the DCVP start date.

The Commission's Article 13(6) implementing-act provision applies from 14 September 2026. That does not start the 2032 manufacturer duty.

The vehicle-passport sequence is better read as three separate milestones:

This distinction matters because vehicle circularity obligations develop before 2032. The DCVP is one part of a wider vehicle-circularity regime, not the date on which the whole Regulation suddenly begins.

Which vehicles need a DCVP?

Article 13 says each vehicle in its scope must have a DCVP from 1 September 2032. But “each vehicle” must be read with Article 2, which contains explicit exclusions from Article 13.

The practical core is therefore:

• ordinary M1 passenger cars
• ordinary N1 light commercial vehicles

Article 13 does not apply to:

• heavy M2 and M3 passenger vehicles
• N2 and N3 heavy goods vehicles
• O-category trailers
• L-category vehicles such as motorcycles and many other powered two- and three-wheel vehicles
• special-purpose vehicles covered by the Regulation's exclusions

So “every vehicle gets an EU vehicle passport in 2032” is too broad. The DCVP owner question is narrower: which vehicles fall within Article 13 of Regulation (EU) 2026/1738, and what must that vehicle-level passport do?

What information will the DCVP contain?

The complete technical field schema is not final, but the Regulation already fixes four mandatory information territories.

This is important for data teams. The law already tells you the territories that need governed information, but it does not yet justify inventing a final DCVP field list or locking a database to a presumed schema.

Article 11 is also relevant before the DCVP itself applies. From 1 September 2029, specified professional actors are to receive standardised, non-discriminatory access to certain dismantling, repair, replacement and circularity information for new type-approved vehicle types. The later DCVP then incorporates the Article 11 information territory into the vehicle passport.

The DCVP is not an ESPR DPP for a car

The naming is similar, but the legal ownership is different.

The ESPR framework, Regulation (EU) 2024/1781, creates Digital Product Passports for product groups through its own product-specific rulemaking. The DCVP is created directly by the separate vehicle-circularity Regulation (EU) 2026/1738.

That difference is not academic. It affects which legal act sets scope, which implementation powers apply, whether current ESPR Registry rules automatically apply and what can safely be inferred from horizontal ESPR standards.

A useful shorthand is:

Same digital-passport direction, different legal passport.

The DCVP is required to interoperate with relevant ESPR passports, but interoperability does not make it an ESPR passport.

How does the DCVP fit with the Battery Passport and Euro 7 vehicle passport?

A vehicle can sit inside several regulated information systems at the same time because the regulated objects and purposes are different.

The law goes further than simply asking these systems to coexist. Article 13 requires alignment, interoperability and, where possible, integration. It also contains an anti-duplication rule: where required information is already accessible through an interoperable Battery Passport, Environmental Vehicle Passport or relevant ESPR passport, that information should not be duplicated in the DCVP.

That points towards a federated information model rather than one giant legal record. A user may experience connected access, while the underlying battery, vehicle, emissions and product records retain their own legal ownership.

Interoperability does not mean one universal passport

The anti-duplication rule is one of the most consequential parts of the DCVP design.

It means the implementation problem is not simply “copy every relevant field into a vehicle passport”. A better architecture has to know:

• which regulated object owns the fact
• which passport already makes it accessible
• whether the data is current at the point of access
• who is entitled to see or update it
• how the relationship survives changes across the vehicle lifecycle

This is why “one passport for everything” is the wrong conclusion. The legislation supports interoperability and non-duplication, not the disappearance of distinct legal records.

What is already fixed technically?

Article 13 already sets several design principles for DCVP information. It must use open standards and an interoperable format, operate through an open and interoperable data-exchange network and avoid vendor lock-in. The information must also be machine-readable, structured and searchable.

Those are binding design principles, but they are not a complete reference architecture.

The final technical layer sits mainly in Article 13(6):

The Commission must adopt those implementing acts by 14 August 2030.

Will the DCVP use a QR code or the VIN?

The final rule is not yet established.

The adopted vehicle-circularity Regulation leaves the location of the “data carrier or other identifier” to the Article 13(6)(e) implementing layer. It does not currently make a QR code the mandatory DCVP carrier, and it does not establish the VIN as the DCVP unique identifier.

There is an easy source of confusion here. The separate Euro 7 Environmental Vehicle Passport has more developed implementation mechanics, including QR-based access and VIN-related vehicle identification. That is useful evidence of what a vehicle passport can look like, but it is not a legal shortcut to the DCVP decision.

For now, the low-regret design move is to keep three things separate in your architecture:

1. the vehicle's persistent identity
2. the access carrier or entry point
3. the DCVP record and its links to other regulated records

That leaves room for the final Article 13(6) implementation without hard-coding today's assumption as tomorrow's law.

Will DCVP data be stored in the EU DPP Registry?

Not automatically under the law in force today.

The EU DPP Registry is already operational for the regimes within its legal scope. Its current implementing regulation also contains a route for other Union legislation, but that route depends on the other legislation requiring both a DPP and its registration in the ESPR Registry.

Regulation (EU) 2026/1738 currently creates the DCVP without adding that Registry-registration trigger. DCVP storage and processing are themselves subjects for the future Article 13(6)(b) technical rules.

The safe conclusion is therefore “not currently established”, not “the DCVP will never use the Registry”. A future implementation could reuse or interconnect with existing EU infrastructure, but that decision has not yet been made in the adopted DCVP framework.

Who will be able to access the DCVP?

The Regulation establishes free-of-charge access, but that does not mean every DCVP field will be public to everyone.

The detailed access conditions and rights, together with data-protection and intellectual-property treatment, are still to be specified under Article 13(6)(d). A final role-by-field permissions matrix would therefore be premature.

This is another reason not to build the DCVP as a single flat public dataset. Prepare the information so access can be governed by role and purpose without changing the underlying factual record.

What should vehicle manufacturers prepare before 2032?

There is enough law to prepare usefully without pretending the final technical solution already exists.

1. Govern the four fixed information territories

Start with Article 11 information, hazardous-substance derogation information, recycled-content declarations and the official spare-parts catalogue. Treat them as governed information domains with evidence, ownership, versioning and lifecycle rules.

2. Separate vehicle identity from carrier choice

Design a stable vehicle-level identity model, but do not make a QR format, VIN-as-DCVP-ID assumption or proprietary resolver irreversible before Article 13(6) settles the implementation.

3. Map the neighbouring passports

Know which information belongs to the EV Battery Passport, Euro 7 Environmental Vehicle Passport and relevant ESPR passports. The future DCVP will need to interoperate without duplicating information that is already accessible there.

4. Design for role-based access

Free access and universal public access are different things. Structure permissions so public, professional and other authorised views can evolve when the Commission defines the final access conditions.

5. Avoid provider lock-in

The law already requires open standards, interoperable formats and an open interoperable data-exchange network. Portability and exit should therefore be treated as core architecture requirements, not optional procurement preferences.

6. Keep evidence with the fact

The DCVP is likely to span information produced by engineering, compliance, aftersales, recycling and supply-chain systems. Keep source, method, version, responsible owner and validity with each governed fact so later passport views do not become unexplained copies.

Automotive DPP work is emerging, not final DCVP compliance

Automotive data-space initiatives are already working on passport models, exchange patterns and verification. Catena-X, for example, has active 2026 work spanning battery, ESPR and vehicle-circularity needs.

That is useful EMERGING implementation evidence. It is not proof that the final DCVP technical architecture has been settled or that any current platform is a certified DCVP compliance solution. Catena-X's own material identifies integration gaps, while Tractus-X documentation continues to evolve.

The sensible use of that work today is preparation: learn from the data models and exchange patterns, but keep the implementation adaptable to the Commission's final Article 13(6) acts.

Direct questions

When does the EU Digital Circularity Vehicle Passport become mandatory?

For vehicles within Article 13 scope, the DCVP obligation begins on 1 September 2032.

Does every car, truck, bus and motorcycle need a DCVP?

No. Article 13 has explicit scope exclusions. Heavy M2/M3/N2/N3/O vehicles, L-category vehicles and special-purpose vehicles are outside Article 13. The practical core is ordinary in-scope M1 passenger cars and N1 light commercial vehicles.

Is the DCVP the same as the EV Battery Passport?

No. The Battery Passport belongs to the battery and applies under separate battery law. The DCVP belongs to the in-scope vehicle. The two must interoperate and information should not be duplicated where it is already accessible through the battery passport.

Is the DCVP the same as the Euro 7 Environmental Vehicle Passport?

No. They are separate vehicle passports with different legal purposes. Regulation (EU) 2026/1738 explicitly requires the DCVP to interoperate with the Euro 7 Environmental Vehicle Passport.

Will the DCVP use a QR code or VIN?

The final DCVP carrier and identifier are not yet established. Euro 7 uses QR/VIN mechanics for its separate Environmental Vehicle Passport, but those mechanics do not automatically become the DCVP rules.

Is the DCVP already part of the EU DPP Registry?

No automatic DCVP Registry-registration requirement is established in the current law. Future Article 13(6) implementation could create reuse or interconnection, so this remains an open implementation question.

What would change this page

The answer would materially change if the Commission:

• adopts the Article 13(6) implementing acts before or by 14 August 2030
• fixes the DCVP carrier, identifier, storage or access architecture
• creates an explicit legal route into the EU DPP Registry
• adopts a DCVP-specific technical profile or standards basis
• changes Article 13 scope or the 1 September 2032 application date

Until then, the useful boundary is stable: the 2032 vehicle-passport duty and its core information/interoperability principles are adopted, while the final technical implementation remains open.

Sources

• Regulation (EU) 2026/1738 on circularity requirements for vehicle design and management of end-of-life vehicles
• European Commission, End-of-Life Vehicles
• Regulation (EU) 2023/1542 concerning batteries and waste batteries
  EU law
• Regulation (EU) 2024/1257 on Euro 7
• Commission Implementing Regulation (EU) 2025/1707 on Euro 7 vehicle information requirements
• Regulation (EU) 2024/1781 establishing the ESPR framework
  EU law
• Commission Implementing Regulation (EU) 2026/1778 on the DPP Registry
  Delegated act
• Catena-X Digital Product Passport Expert Group, 2026 profile