DPP vs Battery Passport ESPR and Batteries Regulation Comparison
The ESPR DPP is a horizontal product-passport framework applied through product-specific delegated acts. The battery passport is a sector rule in Regulation (EU) 2023/1542 for specified battery categories.
This comparison helps separate scope, timing, data fields, access rights, identifiers, registry obligations, and evidence without importing unsupported battery thresholds or dates.
The ESPR Digital Product Passport and the EU use similar building blocks: a data carrier, a unique identifier, interoperable data, access rights, and responsibility for accurate information. They are separate legal obligations. ESPR creates a cross-sector framework that applies through product-group delegated acts. Article 77 of the Batteries Regulation directly requires a battery passport from 18 February 2027 for light means of transport (LMT) batteries, industrial batteries with a capacity greater than 2 kWh, and electric vehicle batteries placed on the market or put into service.
Comparison matrix
ESPR DPP vs Battery Passport: side-by-side comparison
Read the rows as a control crosswalk. The left side describes the ESPR horizontal DPP framework; the right side describes the under Regulation (EU) 2023/1542.
A framework in Regulation (EU) 2024/1781. It makes DPP requirements operational through delegated acts that specify the product group, data, carrier, access rights, update roles, model/batch/item level, and availability period.
Second framework
EU Battery Passport
A battery-specific electronic record in Regulation (EU) 2023/1542. Article 77 defines covered battery categories, a QR-code link to a unique identifier, access tiers, information accuracy duties, and interoperability with other EU ecodesign passports.
ESPR DPP vs Battery Passport: side-by-side comparison
ESPR applies DPP duties when an applicable delegated act for a product group requires a passport. Article 9 says the delegated act must specify the passport data, carrier, presentation, access, update roles, and whether the passport is at model, batch, or item level.
The rule is narrower and already sector-specific: Article 77 covers each LMT battery, each industrial battery with capacity greater than 2 kWh, and each electric vehicle battery placed on the market or put into service.
Do not treat every ESPR product as having the . Start with the product category: battery passport for the Article 77 battery categories; ESPR DPP only when the relevant ESPR delegated act requires it.
ESPR places key passport duties on the economic operator placing the product on the market or putting it into service, including providing dealer or marketplace access where the buyer cannot physically access the product and making a back-up copy available through a DPP service provider.
For batteries, the economic operator placing the battery on the market must ensure passport information is accurate, complete, and up to date. If a battery is prepared for reuse, repurposed, remanufactured, or becomes waste, Article 77 transfers the responsibility as specified there.
Assign ownership by legal role, not by IT system owner. Battery teams also need a status-change handoff process because responsibility can move after reuse, repurposing, remanufacturing, or waste status.
ESPR does not create one universal DPP trigger for all products in the regulation text. The operative trigger is the applicable delegated act for the product group, which must specify data, access, carrier, and passport level.
The has a direct statutory trigger in Article 77: from 18 February 2027, the listed LMT, industrial-above-2-kWh, and electric-vehicle batteries placed on the market or put into service must have the electronic record.
Keep the clocks separate. For ESPR, track the delegated act for the product group. For batteries, use Article 77 rather than importing unsupported dates, chemistry thresholds, or penalty assumptions from other battery requirements.
The ESPR DPP must connect through a data carrier to a persistent unique product identifier, use open and interoperable data, regulate access by stakeholder type, avoid storing customer personal data without consent, and remain available for the period set in the delegated act.
The must contain battery-model information and individual-battery information as set out in Annex XIII, be accessible through the Article 13 QR code, link to a unique identifier, use open interoperable data, and restrict access according to Annex XIII and the Article 77(9) implementing act.
Build a shared technical pattern for identifiers, data carriers, machine-readable data, access control, and integrity, but map the data fields separately because the has Annex XIII content that general ESPR DPPs do not automatically share.
For ESPR, keep the delegated act mapping, product-group scope, passport level, data fields, access-rights matrix, data-carrier standard, unique-identifier process, registry upload evidence, backup-provider arrangement, and update-role record.
For batteries, keep evidence that Annex XIII public, restricted, authority-only, and individual-battery data are populated as applicable, including model composition, carbon footprint and recycled content information where applicable, performance and durability data, dismantling information, test-report results, status, and use data.
A common evidence repository can help, but the battery evidence pack must prove Annex XIII coverage and Article 77 responsibility. ESPR evidence must prove the product-specific delegated-act mapping and Chapter III technical controls.
ESPR timing depends on the relevant product-group delegated act. Separately, Article 13 required the Commission to set up the DPP registry by 19 July 2026 and says the registry stores at least unique identifiers, including battery identifiers referred to in the Batteries Regulation. The Commission announced the registry and its testing environment as live on 20 July 2026.
The date is Article 77's 18 February 2027 requirement for the covered batteries. Article 77 also states that by 18 August 2026 the Commission is to adopt implementing acts on persons with a legitimate interest and their access to Annex XIII information.
Use three planning tracks: ESPR product delegated acts, the live DPP registry testing and registration infrastructure, and the Article 77/78 track. Registry availability does not move the 18 February 2027 battery-passport trigger or determine the content required for a particular battery.
ESPR DPP assurance is tied to product compliance, market surveillance, customs access to the registry, data authenticity, and the rule that the registry communication of a unique registration identifier is not proof of compliance.
assurance sits within the Batteries Regulation's market-surveillance system. Article 79 allows authorities to evaluate a battery presenting risk and require corrective action, withdrawal, or recall for non-compliant batteries.
Do not present a registry identifier, QR code, or passport URL as compliance proof. The evidence still needs to show the product or battery meets the underlying regulation and the passport data is accurate and current.
ESPR is designed for interoperability with other passports and allows data required or allowed under other Union law to be included in the DPP through the applicable delegated act.
Article 78 requires the to be fully interoperable with other digital product passports required by Union ecodesign law, but the battery content and access tiers remain those in the Batteries Regulation.
Reuse the platform architecture where possible, especially identifiers, access control, searchability, backup, and data exchange. Do not merge legal scope or access rights: the keeps its Annex XIII tiers even when the technical rails overlap.
Use the ESPR DPP analysis when the question is about a non-battery product group, a product-specific ESPR delegated act, the horizontal passport registry, a general DPP technical requirement, or cross-sector interoperability.
Use the analysis when the question is about LMT batteries, industrial batteries above 2 kWh, electric vehicle batteries, Annex XIII data fields, Article 77 access tiers, QR-code access, or battery status changes.
If both regimes are relevant, maintain one crosswalk with separate columns for legal basis, data field, access tier, owner, identifier, carrier, registry record, and evidence source. A shared system can serve both only when each requirement remains traceable to the correct regulation.
ESPR applies DPP duties when an applicable delegated act for a product group requires a passport. Article 9 says the delegated act must specify the passport data, carrier, presentation, access, update roles, and whether the passport is at model, batch, or item level.
EU Battery Passport
The rule is narrower and already sector-specific: Article 77 covers each LMT battery, each industrial battery with capacity greater than 2 kWh, and each electric vehicle battery placed on the market or put into service.
Operational implication
Do not treat every ESPR product as having the . Start with the product category: battery passport for the Article 77 battery categories; ESPR DPP only when the relevant ESPR delegated act requires it.
ESPR places key passport duties on the economic operator placing the product on the market or putting it into service, including providing dealer or marketplace access where the buyer cannot physically access the product and making a back-up copy available through a DPP service provider.
EU Battery Passport
For batteries, the economic operator placing the battery on the market must ensure passport information is accurate, complete, and up to date. If a battery is prepared for reuse, repurposed, remanufactured, or becomes waste, Article 77 transfers the responsibility as specified there.
Operational implication
Assign ownership by legal role, not by IT system owner. Battery teams also need a status-change handoff process because responsibility can move after reuse, repurposing, remanufacturing, or waste status.
ESPR does not create one universal DPP trigger for all products in the regulation text. The operative trigger is the applicable delegated act for the product group, which must specify data, access, carrier, and passport level.
EU Battery Passport
The has a direct statutory trigger in Article 77: from 18 February 2027, the listed LMT, industrial-above-2-kWh, and electric-vehicle batteries placed on the market or put into service must have the electronic record.
Operational implication
Keep the clocks separate. For ESPR, track the delegated act for the product group. For batteries, use Article 77 rather than importing unsupported dates, chemistry thresholds, or penalty assumptions from other battery requirements.
The ESPR DPP must connect through a data carrier to a persistent unique product identifier, use open and interoperable data, regulate access by stakeholder type, avoid storing customer personal data without consent, and remain available for the period set in the delegated act.
EU Battery Passport
The must contain battery-model information and individual-battery information as set out in Annex XIII, be accessible through the Article 13 QR code, link to a unique identifier, use open interoperable data, and restrict access according to Annex XIII and the Article 77(9) implementing act.
Operational implication
Build a shared technical pattern for identifiers, data carriers, machine-readable data, access control, and integrity, but map the data fields separately because the has Annex XIII content that general ESPR DPPs do not automatically share.
For ESPR, keep the delegated act mapping, product-group scope, passport level, data fields, access-rights matrix, data-carrier standard, unique-identifier process, registry upload evidence, backup-provider arrangement, and update-role record.
EU Battery Passport
For batteries, keep evidence that Annex XIII public, restricted, authority-only, and individual-battery data are populated as applicable, including model composition, carbon footprint and recycled content information where applicable, performance and durability data, dismantling information, test-report results, status, and use data.
Operational implication
A common evidence repository can help, but the battery evidence pack must prove Annex XIII coverage and Article 77 responsibility. ESPR evidence must prove the product-specific delegated-act mapping and Chapter III technical controls.
ESPR timing depends on the relevant product-group delegated act. Separately, Article 13 required the Commission to set up the DPP registry by 19 July 2026 and says the registry stores at least unique identifiers, including battery identifiers referred to in the Batteries Regulation. The Commission announced the registry and its testing environment as live on 20 July 2026.
EU Battery Passport
The date is Article 77's 18 February 2027 requirement for the covered batteries. Article 77 also states that by 18 August 2026 the Commission is to adopt implementing acts on persons with a legitimate interest and their access to Annex XIII information.
Operational implication
Use three planning tracks: ESPR product delegated acts, the live DPP registry testing and registration infrastructure, and the Article 77/78 track. Registry availability does not move the 18 February 2027 battery-passport trigger or determine the content required for a particular battery.
ESPR DPP assurance is tied to product compliance, market surveillance, customs access to the registry, data authenticity, and the rule that the registry communication of a unique registration identifier is not proof of compliance.
EU Battery Passport
assurance sits within the Batteries Regulation's market-surveillance system. Article 79 allows authorities to evaluate a battery presenting risk and require corrective action, withdrawal, or recall for non-compliant batteries.
Operational implication
Do not present a registry identifier, QR code, or passport URL as compliance proof. The evidence still needs to show the product or battery meets the underlying regulation and the passport data is accurate and current.
ESPR is designed for interoperability with other passports and allows data required or allowed under other Union law to be included in the DPP through the applicable delegated act.
EU Battery Passport
Article 78 requires the to be fully interoperable with other digital product passports required by Union ecodesign law, but the battery content and access tiers remain those in the Batteries Regulation.
Operational implication
Reuse the platform architecture where possible, especially identifiers, access control, searchability, backup, and data exchange. Do not merge legal scope or access rights: the keeps its Annex XIII tiers even when the technical rails overlap.
Use the ESPR DPP analysis when the question is about a non-battery product group, a product-specific ESPR delegated act, the horizontal passport registry, a general DPP technical requirement, or cross-sector interoperability.
EU Battery Passport
Use the analysis when the question is about LMT batteries, industrial batteries above 2 kWh, electric vehicle batteries, Annex XIII data fields, Article 77 access tiers, QR-code access, or battery status changes.
Operational implication
If both regimes are relevant, maintain one crosswalk with separate columns for legal basis, data field, access tier, owner, identifier, carrier, registry record, and evidence source. A shared system can serve both only when each requirement remains traceable to the correct regulation.
How should teams decide which passport rule controls?
Classify the product first: covered battery category under Article 77, or product group governed by an ESPR delegated act.
Map data fields next: ESPR delegated-act data and Annex III concepts on one side, Batteries Regulation Annex XIII information on the other.
Keep access rights separate: ESPR access is specified at product-group level, while access is tiered through Annex XIII and Article 77(9).
Treat common infrastructure as reusable only when the identifier, carrier, registry, backup, access-control, and evidence rules remain traceable to the correct regulation.
What should a DPP and battery passport crosswalk contain?
A useful crosswalk should not stop at saying both regimes use a passport. It should list the legal basis, product category, passport level, data fields, access tier, responsible economic operator, data carrier, unique identifier, registry touchpoint, update rights, backup arrangement, and evidence source for each requirement.
For ESPR, the unresolved item on many product roadmaps is the product-specific delegated act. For batteries, the first scoping question is whether the battery is an LMT battery, an electric vehicle battery, or an industrial battery above 2 kWh under Article 77. All batteries must carry the Article 13 QR code from 18 February 2027, but batteries outside those three Article 77 categories use that QR code for other specified information rather than a .
Separate ESPR Annex III and delegated-act data mapping from Batteries Regulation Annex XIII battery data.
Record whether the passport is model, batch, item, or individual-battery specific.
Identify which information is public, restricted to authorities, restricted to legitimate-interest actors, or available to update roles.
Treat the QR code, unique identifier, registry record, and passport data store as separate controls that need their own evidence.
The technical overlap is real: both regimes rely on machine-readable, structured, searchable, interoperable data and regulated access rights. A common platform can reduce duplication for identity, access control, carrier resolution, data quality checks, backup continuity, and registry integration.
The legal overlap is limited. content, legitimate-interest access, status-change responsibility, and the passport end point after recycling come from the Batteries Regulation. ESPR product passports still depend on the product-specific delegated act unless another Union-law information system is accepted for that product group.
Reuse technical services for open data exchange, authentication, access logging, and data integrity.
Do not reuse a battery data model as the default ESPR data model for unrelated products.
Do not assume a QR code, identifier, or registry entry proves compliance with either regulation.
Keep source citations at the field level when a public claim or authority response uses passport data.
Primary legal source for the ESPR Digital Product Passport framework, including Articles 9 to 14 on data, access rights, identifiers, registry, web portal, and delegated-act dependency.