Vehicle and product identity
Govern model, type, variant, VIN, production batch and component identifiers without collapsing them into one record.
Automotive industry guide
Digital Product Passport for Automotive and Mobility Manufacturers
Connect vehicle identity, batteries, components, evidence, service and circularity data while keeping each EU regulatory track legally distinct.
Regulatory position
Automotive has connected—but separate—digital requirements
ESPR does not impose one universal automotive DPP. Article 1(2)(h) limits overlap for vehicle aspects already covered by sector-specific Union legislation, while vehicle circularity and EV battery passports follow their own legal frameworks.
The practical challenge is therefore interoperability: relate the vehicle, battery, components, materials and lifecycle evidence without merging their identities or overstating what one record proves.
Readiness capabilities
Six foundations automotive teams can strengthen now
Parts and material structure
Connect approved BOMs, component provenance, substances, recycled content and material evidence to the correct configuration.
EV battery relationship
Associate the regulated battery passport with the vehicle while preserving its separate identity, data and access obligations.
Service and replacement
Record repair, component replacement, software context, remanufacture and status changes without rewriting manufacturing truth.
Dismantling and circularity
Deliver controlled reuse, removal, safe handling, recycling and end-of-life information to legitimate actors.
Tiered access
Separate public and owner information from repairer, dismantler, authority and commercially sensitive supplier evidence.
Model the vehicle hierarchy
Shared model and variant data should be inherited, while VIN-specific build, battery, service and end-of-life history stays attached to the physical vehicle. Replacement must create accountable relationships rather than erase the original configuration.
Review DPP data modellingVehicle model and type
Shared design, homologation and controlled specification
Variant and configuration
Market, propulsion, trim and approved component options
VIN-level vehicle
Build, ownership, service, status and end-of-life context
Regulated EV battery
Separate identity, passport, composition and lifecycle records
Components and materials
Traceable parent-child relationships and supplier evidence
Regulatory stack
Keep each obligation in its proper lane
| Framework | Role in automotive product data |
|---|---|
| Vehicle sector legislation | Vehicle type approval and circularity rules govern vehicle-specific requirements and should remain the primary legal track. |
| EU Battery Regulation | From 18 February 2027, each EV battery must have its own battery passport under Article 77. |
| ESPR | Vehicle aspects already governed by sector-specific EU law are limited under Article 1(2)(h); components or other aspects may follow applicable product rules. |
| Chemicals and product compliance | REACH, safety, homologation and other duties remain separate even when evidence is linked through a digital record. |
Connect OEM and supplier systems
PLM, ERP, MES, supplier, homologation, quality and service platforms should remain authoritative. A passport layer maps approved data to persistent identities and permitted stakeholder views.
Review enterprise integrationEngineering BOM and approved configurations
Supplier component and material declarations
Build and quality records
Battery identity and passport link
Service, replacement and software context
Dismantling, reuse and recycling information
Preserve evidence through change
A battery replacement, repair or component change should append effective lifecycle context while retaining the as-built configuration, evidence source and historical versions.
Give each actor the right view
Owners, workshops, dismantlers, recyclers and authorities require different information. Apply purpose-based access instead of exposing the full engineering and supplier record publicly.
Review access-control designImplementation roadmap
Eight steps to an automotive data pilot
Define legal scope
Separate vehicle, EV battery, component and material obligations for the target product family and markets.
Map the identity hierarchy
Relate model, type, variant, VIN, assembly, regulated battery and replaceable component identities.
Inventory authoritative data
Identify PLM, ERP, MES, supplier, homologation, quality, service and sustainability sources.
Prioritise critical evidence
Select approved materials, substances, recycled-content, repair, dismantling and conformity records.
Design access roles
Define views for public users, owners, repairers, recyclers, auditors and market authorities.
Test lifecycle changes
Prove battery or component replacement, software update, repair, ownership transfer and end-of-life scenarios.
Validate downstream exchange
Test machine-readable data exchange across OEM, tier suppliers, service networks and dismantlers.
Scale with governance
Measure completeness, supplier gaps, evidence age, reconciliation effort and operating ownership.
Prove the connected vehicle record
Test identity, battery linkage, supplier evidence, service changes, access and end-of-life information using one representative product family.
Common questions
Automotive DPP FAQ
Do all vehicles need an ESPR Digital Product Passport?
No. ESPR Article 1(2)(h) limits its application to covered vehicles for product aspects already addressed by sector-specific Union legislation. Vehicle, battery, component and material requirements must be assessed under their applicable legal tracks.
Is a vehicle circularity passport the same as an ESPR DPP?
No. A vehicle circularity passport belongs to the EU vehicle-circularity framework. It may share digital identity and data-governance principles with ESPR passports, but its legal basis, scope, information and timetable are distinct.
Does an electric vehicle need a separate battery passport?
Yes. From 18 February 2027, Article 77 of Regulation (EU) 2023/1542 requires a battery passport for each electric vehicle battery. That passport retains its own identifier and regulated dataset even when linked to a vehicle record.
What identity level should automotive manufacturers support?
Support model, type, variant, production batch and VIN-level relationships, plus separately identified batteries and relevant components. The applicable regulation determines which level must be published.
Can service and replacement events be added?
A governed platform can append repair, replacement, software and status events while retaining original manufacturing records, source attribution, effective dates and access controls.
How should an OEM or supplier begin?
Start with one vehicle or component family, map its regulatory stack and product hierarchy, identify source systems and evidence, then test access, replacement and end-of-life scenarios in a controlled pilot.
Primary sources
See Regulation (EU) 2024/1781, Regulation (EU) 2023/1542, and the Council’s vehicle-circularity adoption notice.
Regulatory note: General readiness guidance only. Confirm the current vehicle, battery, component and market-specific legal requirements before implementation.