DPP vs Battery Passport: What's the Difference?
The Digital Product Passport and the battery passport come from two different EU laws. Here is which regime applies to you, and why the distinction matters.
The one-sentence answer
The battery passport is a specific obligation set by the Battery Regulation (EU) 2023/1542, while the broader Digital Product Passport (DPP) is a framework created by the ESPR, Regulation (EU) 2024/1781, that applies to other product groups through delegated acts. They share the same DNA, but they are two distinct legal regimes - and confusing them is the most common mistake in compliance planning.
The practical point: if you make batteries, your obligation is binding and dated. If you make almost anything else, your obligation is coming through the ESPR but is not yet fixed for most groups.
Two laws, one idea
Both instruments exist to make a product's sustainability data transparent and machine-readable through a QR code. But they were adopted separately and serve different functions:
- The Battery Regulation (EU) 2023/1542 was adopted in 2023 and entered into force in August 2023. Its battery passport is a sector-specific obligation with a fixed application date.
- The ESPR (EU) 2024/1781 is a horizontal framework. It does not impose a DPP on any product by itself - each product group becomes subject to a DPP only when the Commission adopts a delegated act for it.
The battery passport actually came first. It is widely treated as the proof of concept and reference model for the wider DPP system, which is why the two look so similar. We unpack the battery passport on its own in What Is a Battery Passport?, and the ESPR framework in our ESPR pillar.
Side-by-side comparison
| Dimension | Battery passport | Digital Product Passport (ESPR) |
|---|---|---|
| Legal basis | Battery Regulation (EU) 2023/1542 | ESPR, Regulation (EU) 2024/1781 |
| Type of law | Sector-specific regulation | Horizontal framework + delegated acts |
| Products covered | EV, LMT, and industrial batteries above 2 kWh | Almost all physical products, group by group |
| Timeline | Binding: 18 February 2027 | Indicative per group; first delegated acts expected from ~2026 onward |
| Data carrier | QR code on the battery | QR code, NFC, or other carrier |
| Dynamic data | Yes - state of health updated through life | Group-dependent; mostly static at launch |
| Status | First DPP to become mandatory | Reference model still rolling out |
Which one applies to you
Work through this in order:
- Do you place EV, LMT, or industrial batteries above 2 kWh on the EU market? Then the battery passport under Regulation (EU) 2023/1542 applies, and 18 February 2027 is a binding date. This is your primary obligation.
- Do you make a non-battery product in a named ESPR priority group (textiles, furniture, iron and steel, tyres, aluminium)? Then the DPP under the ESPR applies once that group's delegated act is in force. Timing is indicative - prepare now, but the date is not yet fixed.
- Do you make a battery-powered product (an e-bike, a cordless tool, an EV)? You may sit at the intersection: the battery inside carries a battery passport, and the finished product may later carry its own ESPR DPP. These are separate passports for separate items.
- Do you make a physical product not yet named? You are almost certainly in a later ESPR wave. Track the ESPR Working Plan 2025-2030.
Why the distinction matters in practice
Three reasons this is not just legal trivia:
Deadlines differ in kind. The battery passport date is binding and close. Most ESPR dates are indicative and further out. Treating an indicative ESPR date as a hard deadline wastes resources; treating the binding 2027 battery date as flexible is dangerous. Get the category right and you get the urgency right.
The data set differs. The battery passport mandates battery-specific fields - carbon footprint per kWh, state of health, due diligence for critical raw materials - that an ESPR textile DPP will never ask for. Build to the wrong spec and you collect the wrong data.
Dynamic vs static. The battery passport expects data like state of health to be updated through the battery's life. Most early ESPR DPPs are closer to a static record set at manufacture. That difference changes the system you need - one that can ingest lifecycle updates versus one that publishes a fixed record.
The good news: one capability covers both
Despite two legal regimes, the underlying machinery is shared. A unique product identifier, a QR data carrier, a verified data store, tiered access, and a public-facing passport are common to both. If you build a DPP capability that handles the battery passport's stricter, dynamic requirements, you are over-prepared for most ESPR groups - not the other way around. This is why early movers often start with the battery passport even when they also sell non-battery products.
Where DPPAutomate fits
DPPAutomate handles both regimes from one platform. It maps each of your products to the correct law - Battery Regulation or ESPR delegated act - applies the right data model and access tiers for each, supports dynamic fields like state of health, and generates compliant passports either way. You stop guessing which rules apply and work from one clear picture.
Not sure which regime your products fall under? Run a free scope check or read What Is a Battery Passport?.
Continue reading.
EU Battery Regulation 2027: Deadline Tracker
Every key date for Battery Passport compliance - Feb 2027 issuance obligation, supplier data deadlines, audit windows. Updated as regulators clarify guidance.
EU Battery Regulation 2027: What You Need to Know
Complete breakdown of the EU Battery Regulation (2023/1542) and mandatory Battery Passport requirements coming February 2027.
ESPR Compliance: A Complete Guide to EU Ecodesign Regulation
Everything you need to know about the Ecodesign for Sustainable Products Regulation (ESPR) and how it affects your business. Requirements, timelines, and compliance strategies.