Battery DPP: Your 90-Day Countdown to July 19
The EU DPP Registry opens July 19, 2026. If you manufacture batteries above 2 kWh and sell into the EU market, that date is not a soft launch you can monitor from a distance. It is the moment the central compliance infrastructure goes live — and the moment market surveillance authorities begin expecting registry-linked passports on your products.
You have roughly 90 days. Here is exactly what to do with them.
Key Takeaways
- July 19, 2026 is when the EU DPP Registry portal opens; batteries above 2 kWh are the first mandatory category
- A compliant battery passport requires at minimum 12 core data fields plus a GS1 Digital Link QR code on every physical unit
- You host your own DPP data; the registry stores a validated reference and issues a registry ID you must display on the product
- Missing the deadline carries customs rejection, market withdrawal, and financial penalties — not a grace period
The Timeline: Now to July 19
Understanding where you are relative to the deadline changes how you prioritise the next 90 days.
TODAY (March 30) REGISTRY OPENS ENFORCEMENT ACTIVE
| | |
●━━━━━━━━━━━━━━━━━━━━━━━━●━━━━━━━━━━━━━━━━━━━━━━━●
| | |
91 days July 19 Feb 2027
to prepare Submit & validate DPP mandatory
your first DPP for all EU sales
The period between July 19 and February 2027 is not a grace period. It is a seven-month window where the registry is live and operational, enforcement ramps, and early submission problems surface — while you still have time to fix them before mandatory compliance.
Battery manufacturers who begin registry submission in July have seven months of live testing before the hard February 2027 enforcement date. Those who wait until January 2027 have weeks.
The EU DPP Registry launch overview explains the infrastructure in detail. This post focuses on what battery manufacturers specifically need to do before they can submit anything. Understanding digital product passport requirements helps contextualize how battery DPP fits into the broader regulatory landscape.
The 12 Mandatory Data Fields for Battery DPP
The full battery passport under EU Regulation 2023/1542 Annex XIII runs to 100+ attributes. But a subset of fields is mandatory at submission — the registry will reject passports that omit them. These twelve fields are non-negotiable:
| # | Field | What It Means | Where to Get It |
|---|---|---|---|
| 1 | Battery unique identifier | A globally unique ID per unit or batch, conforming to GS1 or ISO/IEC 15459 | Your ERP or identifier management platform |
| 2 | Battery model and type | Chemistry type (Li-ion, NMC, LFP, etc.) and product model designation | Product engineering records |
| 3 | Manufacturer legal entity | Full legal name and EU-registered address of the manufacturer | Company registration documents |
| 4 | EU authorised representative | Required if manufacturer is outside the EU; must be a registered EU entity | Legal/compliance team |
| 5 | Manufacturing date and location | Production date (at minimum month/year) and country of manufacture | Production records / MES system |
| 6 | Battery capacity (kWh) | Rated energy capacity in kilowatt-hours — determines whether DPP applies | Product specification sheet |
| 7 | Carbon footprint (lifecycle) | Cradle-to-gate carbon footprint in kg CO₂e per kWh of capacity | LCA study or supplier data |
| 8 | Critical raw materials | Cobalt, lithium, nickel, manganese — origin and recycled content percentage | Supply chain data from Tier 1–3 suppliers |
| 9 | Recycled content declaration | Percentage of recycled cobalt, lithium, nickel, lead in the battery | Supplier declarations |
| 10 | State of health parameters | Capacity fade thresholds, internal resistance, cycle life at nominal conditions | Battery management system (BMS) data |
| 11 | End-of-life and dismantling instructions | Safe disassembly procedure reference; hazardous material handling notes | Technical documentation |
| 12 | DPP data location (URI) | The URL where your full DPP data record is hosted and publicly accessible | Your DPP platform or hosting infrastructure |
Fields 7, 8, and 9 are where most manufacturers hit the hardest delays. Carbon footprint data requires either an internal LCA study or verified supplier declarations. Critical raw material provenance requires supply chain traceability that many second- and third-tier suppliers have not historically provided. Start these workstreams first.
For the full technical breakdown of all 100+ attributes, the Battery DPP technical guide covers every category in depth. For manufacturers managing supply chain traceability, critical raw material data will integrate with your existing supplier tracking systems.
QR Code Requirements
Every physical battery unit — or its packaging, for cells and small modules — must carry a machine-readable carrier linking to the DPP. The EU Battery Regulation specifies GS1 Digital Link as the required format for battery passports.
What is GS1 Digital Link? It is a URL-based standard that encodes product identity (GTIN, serial number, batch) directly into a web address. When scanned, it resolves to the DPP data endpoint. Unlike a plain QR code pointing to a generic product page, a GS1 Digital Link QR is structured, machine-parseable, and verifiable by customs authorities and automated inspection systems.
Format requirements
- Standard: GS1 Digital Link (ISO/IEC 18975)
- Carrier: 2D barcode (QR Code preferred; Data Matrix acceptable for space-constrained units)
- Minimum module size: 0.4 mm per module for QR; 0.25 mm for Data Matrix
- Error correction level: M or higher (recovers up to 15% damage)
- Quiet zone: Four modules minimum on all sides
Placement requirements
- Must be on the battery unit itself, or on permanently attached labelling
- If unit size prevents direct marking: on smallest retail or transport packaging
- Must remain legible across the expected service life of the battery
- Must not be obstructed by mounting brackets, cable routing, or installation enclosures
What happens at scan
When a market surveillance officer, customs authority, or end user scans the QR code, they must be taken to a live DPP data record — not a product homepage, not a PDF download, not a registration prompt. The data must be accessible without login, without app installation, and in at minimum English plus the language of the member state where the battery is sold.
Registry Submission: What You Submit vs. What You Host
This distinction confuses most first-time implementors. The EU DPP Registry does not store your full DPP data. Here is how the architecture works:
┌─────────────────────────────────────────────────────────┐
│ YOUR INFRASTRUCTURE │
│ │
│ ┌──────────────────────────────────┐ │
│ │ DPP Data Record (hosted by you) │ │
│ │ - All 100+ battery fields │ │
│ │ - Machine-readable JSON-LD │ │
│ │ - Publicly accessible via URL │ │
│ └──────────────────────────────────┘ │
│ │ │
│ │ URI reference │
│ ▼ │
└─────────────────────────────────────────────────────────┘
│
│ You submit:
│ - Product identifier
│ - Manufacturer details
│ - DPP data URI
│ - Conformity declaration
▼
┌─────────────────────────────────────────────────────────┐
│ EU DPP REGISTRY (opens July 19) │
│ │
│ Validates your submission → Issues Registry ID │
│ Registry ID must appear on product/packaging │
└─────────────────────────────────────────────────────────┘
The registry validates your submission, confirms the URI resolves correctly, checks that your data structure is conformant, and issues a registry ID. That registry ID — typically a short alphanumeric code — must then appear on your product label or packaging alongside the QR code.
This means you need two things working simultaneously before July 19: a live, compliant DPP data endpoint that resolves reliably, and a prepared registry submission package. Neither can be done the week before.
The 90-Day Checklist
This is the operational sequence. Work through it linearly — each phase gates the next.
Week 1–4 (Now through April 27): Data Audit and Gap Analysis
- Identify your in-scope battery SKUs — list every model above 2 kWh sold or planned for EU sale
- Map current data availability against the 12 mandatory fields — score each field as Available / Partial / Missing
- Initiate supplier data requests for carbon footprint, critical raw material origin, and recycled content — these have the longest lead times; start now
- Commission or update your LCA study if carbon footprint data is missing or older than 24 months
- Confirm your EU authorised representative is in place (if you are a non-EU manufacturer)
- Audit your product identifier scheme — do you already use GS1 GTINs with serial-level granularity? If not, this is the blocking dependency
- Assign a DPP project owner with cross-functional authority over engineering, supply chain, legal, and IT
Week 5–8 (April 28 through May 25): Infrastructure Build
- Select your DPP hosting approach — build internal API, use your ERP's emerging DPP module, or deploy a purpose-built DPP platform
- Implement GS1 Digital Link QR generation — integrate with your identifier system so each unit gets a unique, correctly formatted QR
- Build or configure your DPP data endpoint — must return structured data (JSON-LD preferred), must be publicly accessible without authentication
- Complete your data collection pipeline — supplier declarations received, LCA data integrated, BMS parameters documented
- Populate a test DPP record for one battery model and validate the JSON-LD structure against the EU Battery Regulation schema
- Test QR code generation at production scale — minimum module size, print fidelity, scan rate under ambient lighting conditions
- Review DPP enforcement risks — the DPP enforcement and penalties guide sets out what market surveillance authorities can do if submissions are incomplete
Week 9–12 (May 26 through June 22): Validation and Pre-Submission
- Validate your live DPP endpoint — confirm it resolves correctly from external networks, loads in under 3 seconds, returns correct data for every registered identifier
- Complete all mandatory field data — no partial records; the registry will reject incomplete submissions
- Prepare your registry submission package: product identifier, manufacturer details, conformity declaration, DPP data URI
- Confirm QR placement on physical units — labels designed, print process validated, placement compliant with specification
- Train your compliance and logistics teams on what the registry ID looks like and where it must appear on documentation and packaging
- Run a pre-submission review — internal check or third-party audit against the 12 mandatory fields and QR requirements
- Submit to the EU DPP Registry on or shortly after July 19 — early submission allows time to receive feedback and fix issues before February 2027
Ongoing (July 19 onwards): Live Operations
- Receive and record your registry ID — update product labels, packaging specs, and compliance documentation
- Monitor your DPP endpoint uptime — the registry links to your hosted data; if your endpoint goes down, your compliance status breaks
- Update DPP records when product data changes — chemistry reformulations, supplier changes, BMS parameter updates must be reflected
- Begin onboarding remaining SKUs — July submission starts with your highest-volume models; extend to all in-scope SKUs before February 2027
The readiness assessment guide includes a diagnostic tool that maps your current state against this sequence — useful for identifying which phase you are realistically entering today.
What Happens If You Miss July 19
Missing the registry launch does not immediately result in enforcement action — February 2027 is the mandatory compliance date. But waiting beyond July 19 costs you in ways that are easy to underestimate.
Seven months of testing, gone. The July 19 launch is explicitly designed as an operational ramp period. Early submitters will encounter and resolve integration issues — malformed identifiers, endpoint resolution problems, data schema validation errors — with time to fix them. Late submitters encounter the same issues in January 2027 with weeks left. Getting the QR code and product identity infrastructure right during this phase is critical to avoiding last-minute surprises.
February 2027 enforcement is hard. The EU Battery Regulation enforcement regime is not aspirational. Market surveillance authorities at EU borders are already checking battery compliance under the existing regulation — DPP requirements stack on top. What manufacturers need to know about battery DPP enforcement details the current border check process and what non-compliance looks like in practice. For EV and industrial battery makers, understanding how right to repair requirements intersect with DPP obligations is also essential.
Consequences of missing the February 2027 hard deadline:
- Customs rejection — batteries without a valid registry-linked DPP can be refused entry at EU borders
- Market withdrawal — surveillance authorities can require withdrawal of non-compliant batteries already in the EU market
- Financial penalties — member states set their own penalty ranges; Germany and France have indicated fines scaled to revenue, not fixed amounts
- Reputational exposure — non-compliance is a matter of public record under ESPR; enterprise procurement teams are building compliance status into supplier qualification criteria
- No SME exemption — there is no size threshold below which battery DPP requirements do not apply
FAQ
Q: We manufacture batteries outside the EU. Do we need to comply?
Yes. The regulation applies to batteries placed on the EU market, regardless of where they are manufactured. If you sell into the EU — directly or through distributors — you must comply. You also need an EU authorised representative registered in a member state.
Q: Our batteries are assembled from cells we buy from third-party suppliers. Who provides the DPP data?
You do, as the entity placing the product on the market. You may receive data from your cell suppliers — and you should request it — but the DPP obligation sits with the manufacturer or importer of record. Supplier data feeds your record; you own the submission.
Q: Can we submit one DPP for a product model rather than one per unit?
Model-level and batch-level passports are permitted for some data fields. But the unique identifier requirement is serialised to the unit or batch level — meaning your QR code must encode a specific batch or unit identity, not just the model. A single static QR pointing to a generic product page is not compliant.
Q: The registry does not open until July 19. Can we start testing earlier?
The European Commission is expected to publish sandbox or staging documentation before the live launch. Monitor the ESPR implementation portal and your national authority's guidance. In the meantime, you can build and validate your DPP data endpoint, your GS1 Digital Link QR generation, and your submission package so that you are ready to submit on day one.
The 90-day window is real, and it is enough — if you start the data collection phase this week. The blocking dependencies are supplier data and identifier infrastructure. Everything else follows once those are resolved.
BrandedMark provides GS1 Digital Link QR generation, serialised DPP data hosting, and EU registry connectivity out of the box — purpose-built for manufacturers who need compliant infrastructure without building it from scratch. This infrastructure also enables post-purchase revenue streams through direct customer access after the sale. If you are mapping your current state against the checklist above and finding gaps, start with a readiness assessment to identify exactly where to focus first.