| Scope and covered activity | 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 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. | 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. |
|---|
|
| Who must act | 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. |
|---|
|
| Trigger or threshold | 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 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. | 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. |
|---|
|
| Core obligations | 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 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. | 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. |
|---|
|
| Evidence and records | 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. |
|---|
|
| Timing and cadence | 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. | 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. | 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. |
|---|
|
| Enforcement or assurance route | 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. | 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. | 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. |
|---|
|
| Overlap and reuse | 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 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. | 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. |
|---|
|
| Practical decision rule | 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 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. | 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. |
|---|
|