The EU DPP Registry & the 2027 Battery Deadline: What to Prepare Now

Two regulatory clocks are ticking: the central EU Digital Product Passport registry is expected to come online in 2026 under ESPR, and the battery passport becomes mandatory on 18 February 2027. Lead times are long, so here is what to prepare now, with API code.

by QR3 Redaktion

The EU DPP Registry & the 2027 Battery Deadline: What to Prepare Now

Two regulatory clocks are ticking, and they are closer than they look. The EU is standing up a central Digital Product Passport (DPP) registry under the Ecodesign for Sustainable Products Regulation (ESPR), and the battery passport becomes mandatory on 18 February 2027 for industrial and electric-vehicle batteries under the EU Battery Regulation 2023/1542.

That second date is firm. And here is the uncomfortable part: collecting battery master data, getting carbon-footprint figures verified, and wiring your IT systems to a registry are all things with long lead times. If you start in late 2026, you are already behind. This is a practical, no-drama guide to what to prepare now, and how the qr3 API helps you validate early, create at scale, and submit to the EU registry when it opens.

The two deadlines that matter

There are two distinct things people conflate, so let us separate them clearly:

  • The central EU DPP registry — expected in 2026. ESPR (Reg (EU) 2024/1781) establishes a central registry and a public web portal where passports are registered and can be looked up. It is expected to come online during 2026, but a specific go-live day is not firmly confirmed yet, so plan for it without betting on an exact date.
  • The battery passport — mandatory 18 February 2027. This date is well established. From 18 February 2027, industrial batteries above 2 kWh and EV batteries placed on the EU market must carry a battery passport, accessible via a QR code, under Regulation 2023/1542.

The practical reading: the battery passport is your hard deadline, and the registry is the channel you will most likely register through. Prepare for both as one programme.

What a battery passport must contain

A battery passport is not a marketing page — it is a structured set of attributes that has to be accurate and, in places, third-party verified. The headline data points include:

  • Carbon footprint of the battery (per the regulation's carbon-footprint rules).
  • Recycled content — the share of recovered cobalt, lithium, nickel and lead in the active materials.
  • Battery chemistry and capacity, state-of-health and expected lifetime parameters.
  • Origin and manufacturer details, plus due-diligence information.
  • Recyclability information and handling/safety data.

In the qr3 model these map onto battery_data fields such as capacity_kwh, carbon_footprint_kg, recycled_content_pct, recyclability_pct, and manufacturer_warranty_years. The point of listing them now is simple: most of these have to be sourced from suppliers or measured, and that does not happen overnight.

A prep checklist & timeline for 2026

Treat 2026 as your runway. A realistic sequence:

Quarter Focus Concrete step
Q1 2026 Master data Inventory products in scope; assign GTIN + serial scheme; list required fields
Q2 2026 Supplier data Collect carbon-footprint & recycled-content figures from cell/material suppliers
Q2 2026 Data quality Validate every record against the passport schema (client.dpp.validate)
Q3 2026 IT integration Wire your PLM/ERP to the passport API; automate batch creation
Q3 2026 Dry run Create passports at scale in staging (client.dpp.batch) and test QR resolution
Q4 2026 Registry readiness Prepare registry submission flow (client.dpp.registerForEuRegistry)
By 18 Feb 2027 Go live Passports created, QR codes on labels, records submitted

The single most common mistake is leaving supplier data to the end. Carbon-footprint and recycled-content figures often require supplier questionnaires and verification — start those in the first half of 2026.

Validate before you commit

Before you create thousands of passports, check that each record is complete and well-formed. client.dpp.validate returns a structured { valid, errors } result, so you can fix data quality issues while there is still time:

import { QR3 } from "@qr3/sdk";

const client = new QR3({ apiKey: process.env.QR3_API_KEY! });

const candidate = {
  gtin: "04019999999902",
  serial: "SN-00012345",
  product_name: "PowerCell 5 kWh LFP",
  manufacturer: "ExampleTech GmbH",
  origin_country: "DE",
  category: "battery",
  market_countries: ["DE", "FR", "ES"],
  battery_data: {
    capacity_kwh: 5,
    carbon_footprint_kg: 62,
    recycled_content_pct: 12,
    recyclability_pct: 95,
    manufacturer_warranty_years: 8,
  },
};

const { valid, errors } = await client.dpp.validate(candidate);
if (!valid) {
  console.error("Fix before creating:", errors);
}

Run validation continuously across 2026 as supplier data lands — it turns a year-end panic into a steady, boring data-cleanup task.

Create at scale

Once records validate, you rarely create passports one at a time. client.dpp.batch accepts up to 100 items per call, so you process your catalogue in chunks:

const items = candidates.slice(0, 100); // batch max is 100

const result = await client.dpp.batch({ items });
// each created passport returns its QR in qr.svg / qr.png / qr.pdf / qr.eps

Loop over your catalogue in batches of 100, persist the returned identifiers, and send the vector QR (SVG or EPS) to your label pipeline. This is the step you want to have rehearsed in staging well before February 2027.

Submit to the EU registry

When the central registry is available, you register each passport so it is discoverable through the EU portal. client.dpp.registerForEuRegistry(id) handles the submission (Business plan and up):

const submission = await client.dpp.registerForEuRegistry(passportId);

console.log(submission.data.eu_registry_status);          // e.g. queued / processing
console.log(submission.data.registry_request_id);         // track this request
console.log(submission.data.estimated_processing_seconds); // rough ETA

Because the registry's exact launch timing is not yet pinned down, build this into your flow now but keep it behind a feature flag you can switch on the moment it goes live. The data and the QR codes are useful regardless; registration is the final handshake.

FAQ

Is the 18 February 2027 battery date really fixed? Yes — it is well established in Regulation 2023/1542 for industrial and EV batteries. Treat it as a hard deadline.

When exactly does the central DPP registry launch? It is expected to come online during 2026 under ESPR (Reg (EU) 2024/1781), but a specific go-live day is not firmly confirmed. Prepare for it; do not hard-code a date.

We are not a battery maker — does this matter to us? The battery passport is first, but ESPR extends DPPs to many product groups over time. The master-data and validation work you do now is reusable for whatever category comes next.

What if my supplier data is not ready? Start the supplier questionnaires in the first half of 2026. Use client.dpp.validate to see exactly which fields are still missing, and chase those specifically.

Sources

Start for free and prepare your passports before the deadline: app.qr3.app/sign-up