DPPBattery PassportEU

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.

Use this comparison to separate scope, timing, data fields, access rights, identifiers, registry obligations, and evidence without importing unsupported battery thresholds or dates.

Author
Sorena AI
Published
May 9, 2026
Updated
May 9, 2026
Sections
2

Structured answer sets in this page tree.

Primary sources
5

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated May 9, 2026
Overview

The ESPR Digital Product Passport and the EU battery passport use similar building blocks: a data carrier, a unique identifier, interoperable data, access rights, and responsibility for accurate information. They are not the same obligation. ESPR creates the cross-sector framework for future product-group rules; the Batteries Regulation already defines a battery passport for LMT batteries, industrial batteries above 2 kWh, and electric vehicle batteries placed on the market or put into service from the date stated in Article 77.

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 battery passport under Regulation (EU) 2023/1542.

Review all sources
First framework
ESPR Digital Product Passport

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.

Comparison row 1

Scope and covered activity

ESPR Digital Product Passport

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 battery passport 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 battery passport. Start with the product category: battery passport for the Article 77 battery categories; ESPR DPP only when the relevant ESPR delegated act requires it.

Comparison row 2

Who must act

ESPR Digital Product Passport

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.

Comparison row 3

Trigger or threshold

ESPR Digital Product Passport

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 battery passport 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.

Comparison row 4

Core obligations

ESPR Digital Product Passport

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 battery passport 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 battery passport has Annex XIII content that general ESPR DPPs do not automatically share.

Comparison row 5

Evidence and records

ESPR Digital Product Passport

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.

Comparison row 6

Timing and cadence

ESPR Digital Product Passport

ESPR timing depends on the relevant product-group delegated act. Separately, Article 13 requires 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.

EU Battery Passport

The battery passport 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 ESPR registry and portal infrastructure, and the battery passport Article 77/78 track. Avoid adding battery passport milestone dates that are not in the cited regulation text.

Comparison row 7

Enforcement or assurance route

ESPR Digital Product Passport

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

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.

Comparison row 8

Overlap and reuse

ESPR Digital Product Passport

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 battery passport 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 battery passport keeps its Annex XIII tiers even when the technical rails overlap.

Comparison row 9

Practical decision rule

ESPR Digital Product Passport

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 battery passport 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.

Practical decision rule

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 battery passport 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.
Section 1

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.

  • 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.
Recommended next step

Build a passport crosswalk

Compare ESPR DPP and battery passport requirements field by field before reusing data models, QR-code flows, access controls, or evidence records.

Section 2

Where can one implementation serve both regimes?

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. Battery passport 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 battery passport 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 sources

References and citations

commission.europa.eu
Referenced sections
  • Commission overview used for public context on the ESPR framework and its role in sustainable product requirements.
"Ecodesign for Sustainable Products Regulation"
Related guides

Explore more topics

Annex III Data Model Planning for EU Digital Product Passports
Plan EU Digital Product Passport data fields, identifiers, access rights, update owners, registry inputs, and evidence records against ESPR Annex III and product-specific delegated acts.
Digital Product Passport vs Digital Twin
Compare EU Digital Product Passports with digital twins: legal access duties, identifiers, public and restricted data, evidence, governance, and reuse limits.
Digital Product Passport vs Paper Product Passports
Compare EU regulated digital product passports with paper, PDF, web, and internal product passports across access, identifiers, data carriers, restricted data, customs checks, registry, and interoperability.
DPP customs access review workflow for ESPR products
Review public, restricted, and customs access for EU Digital Product Passports, including registry handoffs, portal access rights, and release-for-free-circulation evidence.
DPP Data Governance RACI Template for EU Digital Product Passports
Assign accountable owners for EU Digital Product Passport data, access rights, supplier inputs, resolver links, registry uploads, verification checks, and retained evidence.
DPP data-model intake workflow for EU Digital Product Passports
A grounded intake workflow for EU Digital Product Passport data models: product group, delegated-act status, source owner, supplier data, access class, identifiers, carrier, checks, and publication readiness.
DPP Governance, Verification and Audit Controls
Build EU Digital Product Passport governance controls for data owners, supplier evidence, access logs, validation checks, audit records, and product release gates.
DPP QR code vs NFC data carrier choices under EU ESPR
How to choose QR code, NFC, or another data carrier for an EU Digital Product Passport without assuming ESPR mandates one universal carrier.
DPP registry and web portal integration under EU ESPR
Grounded guide to EU Digital Product Passport registry and web portal integration under ESPR, covering identifiers, data carriers, access rights, service providers, and lookup design.
DPP vs EPREL Comparison
Compare the EU Digital Product Passport with EPREL: product-passport scope, energy-label database role, access model, identifiers, data carriers, and overlap limits.
DPP vs GS1 Digital Link: Duties vs Standard
Compare EU Digital Product Passport requirements with GS1 Digital Link: legal scope, identifiers, data carriers, access rights, registry, portal, customs checks, and implementation consequences.
EU Digital Product Passport access: public, restricted, and customs views
How ESPR Digital Product Passport access should be split across public users, restricted actors, authorities, customs, the EU registry, and the web portal.
EU Digital Product Passport API and resolver architecture
Grounded DPP architecture guidance for data carriers, product identifiers, resolver lookup paths, access rights, registry integration, and interoperability without premature protocol mandates.
EU Digital Product Passport Applicability Test
Check whether an ESPR delegated act or battery passport rule may require a Digital Product Passport, which operator owns it, and what evidence to keep.
EU Digital Product Passport architecture and integration
Grounded guide to EU Digital Product Passport architecture: data carriers, identifiers, access rights, registry, portal, supplier flows, customs checks, and governance.
EU Digital Product Passport checklist
A concrete EU Digital Product Passport readiness checklist covering product-group scope, passport fields, identifiers, data carriers, access rights, supplier evidence, registry preparation, and publication controls.
EU Digital Product Passport compliance: ESPR requirements
Grounded EU Digital Product Passport compliance guide covering ESPR passport data, identifiers, data carriers, access rights, registry readiness, supplier validation, and evidence.
EU Digital Product Passport Data Carriers, Access Control, and UX
How to choose DPP data carriers, identifiers, access rights, and scanning UX under ESPR Articles 9-14, with QR, NFC, RFID, registry, and customs constraints.
EU Digital Product Passport data requirements and fields
How to plan Digital Product Passport data fields under ESPR: delegated-act scope, Annex III data categories, access rights, customs data, and supplier validation.
EU Digital Product Passport deadlines and compliance calendar
Grounded EU Digital Product Passport calendar for ESPR and battery passport milestones, with product-group dates flagged as dependent on delegated acts.
EU Digital Product Passport FAQ
Direct answers on EU Digital Product Passport scope, creators, product groups, registry, customs checks, access rights, identifiers, data carriers, and governance.
EU Digital Product Passport identifier and data carrier design
How to design Digital Product Passport identifiers, QR or other data carriers, resolver links, registry records, access paths, and evidence without overclaiming the EU rules.
EU Digital Product Passport penalties and enforcement
What ESPR says about Digital Product Passport penalties, Member State fine rules, market surveillance, customs checks, and unresolved product-specific delegated acts.
EU Digital Product Passport Product Group Readiness
Prepare product groups for EU Digital Product Passport rules by tracking ESPR delegated-act status, data fields, suppliers, identifiers, access rights, and registry handoffs.
EU Digital Product Passport requirements under ESPR
source-linked overview of EU Digital Product Passport requirements under ESPR: product-specific delegated acts, data fields, identifiers, carriers, registry, access rights, supplier data validation, and open points.
EU Digital Product Passport supplier data validation controls
Build a supplier data validation file for EU Digital Product Passports: source owner, product link, access class, data model fit, evidence quality, approval record, and release gate.
EU DPP customs access: registry, portal, and restricted data
FAQ on customs access under the EU Digital Product Passport: what customs can verify, how the registry and public portal differ, and how access rights limit DPP data.
EU DPP implementation playbook and vendor selection
Select Digital Product Passport vendors against ESPR requirements for identifiers, data carriers, access rights, decentralized storage, registry readiness, portal access, and verification evidence.
EU DPP Product-Group Readiness Checklist
A source-grounded checklist for preparing a product group for an EU Digital Product Passport delegated act, covering data fields, suppliers, identifiers, carriers, access rights, and registry readiness.
EU DPP QR Code and Data Carrier Implementation Guide
Grounded guidance for using QR codes and other data carriers in EU Digital Product Passport programs, including unique identifiers, access, resolver testing, and evidence.
EU DPP supplier data validation workflow
A grounded workflow for checking supplier data before it is used in an EU Digital Product Passport, covering product linkage, evidence, owners, access class, and approval records.
EU DPP unique identifier requirements: product, operator and facility IDs
FAQ on how ESPR Digital Product Passport identifiers connect products, economic operators, facilities, data carriers, resolvers and registry evidence.
Public vs restricted EU Digital Product Passport data
How to separate public, restricted, authority, and customs access in EU Digital Product Passport designs under ESPR and battery passport rules.
What is a Digital Product Passport under ESPR?
A visitor-friendly explanation of EU Digital Product Passports under ESPR: product data, identifiers, data carriers, access rights, registry, web portal, and delegated acts.
What is the EU Digital Product Passport registry?
FAQ on the ESPR Digital Product Passport registry: what it stores, who uploads data, how identifiers work, and what teams should avoid assuming.
Which products come first for the EU Digital Product Passport?
FAQ on EU Digital Product Passport product priority: batteries have a separate passport rule, while ESPR product groups depend on the working plan and delegated acts.
Who must create an EU Digital Product Passport?
DPP responsibility under the EU ESPR: how manufacturers, importers, distributors, suppliers, service providers, and delegated acts fit together.