Digital Battery Passport 2027: What Manufacturers Need to Know Now

Webinars, open-source tools, and new standards: the EU Battery Passport is gaining momentum. A July 2026 status overview and the open questions ahead of the February 2027 deadline.

di QR3 Redaktion

Digital Battery Passport 2027: What Manufacturers Need to Know Now

The February 2027 Deadline Is Closing In

The clock is ticking. Starting in February 2027, certain batteries placed on the EU market must be equipped with a Digital Product Passport (DPP). The legal basis is the Battery Regulation (EU) 2023/1542, which entered into force in August 2023 and is widely regarded as the first concrete use case for the DPP. Since then, the regulatory landscape has grown considerably denser — with new standards, public test environments, and mounting pressure from industry.

Recent developments make clear that the sector is entering a decisive phase: abstract requirements are becoming concrete technical specifications, and pilot projects are maturing into production-ready systems.


Standards and Compliance: What CEN/CENELEC Requires

The June 25, 2026 Webinar

On June 25, 2026, CEN and CENELEC hosted a public webinar to explain the recently adopted European standards and answer industry questions. The focus was on data structure, interoperability, and integration with national registries.

Just two weeks later, on July 7, 2026, the European Commission followed up with a second webinar dedicated specifically to the Battery Passport — this time centered on data requirements, interoperability, and industry readiness. The message from both events was unambiguous: companies that still lack an implementation strategy are falling behind schedule.

Static and Dynamic Data: An Underestimated Challenge

The Battery Regulation implicitly distinguishes between two categories of data. On one side are data points that are fixed at the time of market placement: chemistry, manufacturer, capacity, and carbon footprint. On the other side are data points that change continuously during operation — most notably State of Health (SoH) and State of Charge (SoC), which shift with every charge and discharge cycle.

This distinction carries significant technical weight. While static data can be entered into the passport once at the end of production, dynamic data requires a continuous data infrastructure — from the battery itself through the battery management system (BMS) all the way to the central data carrier. For manufacturers, this means the Battery Passport is not a one-time documentation project but an ongoing data process.


Technical Infrastructure: Test Environments and Open-Source Tools

BatteryPass-Ready Goes Live

On June 24, 2026, the BatteryPass-Ready consortium launched a public test environment for the Digital Battery Passport. The platform — in which Fraunhofer IPK plays a leading role — allows manufacturers and suppliers to validate their data structures against normative requirements before going live in production.

This offering matters because the certification requirements are complex: manufacturers must not only supply the right data points, but do so in machine-readable form, via standardized interfaces, and with traceable provenance. The test environment provides, for the first time, the opportunity to work through these requirements in a controlled setting.

DP-AWB: Open-Source Assessment of Passport Structures

In July 2026, researchers published the Digital Passport Assessment Workbench (DP-AWB) as an open-source tool. Published in Open Research Europe, the tool computes deterministic assessment results directly from SHACL model specifications — that is, from the formal descriptions of what a valid product passport must look like.

For developers, this means the DP-AWB can be integrated into CI/CD pipelines to automatically check DPP datasets for conformance. A simple command-line usage example:

# DP-AWB conformance check against a SHACL schema
dp-awb validate \
  --data battery-passport-instance.jsonld \
  --shapes battery-dpp-shapes.ttl \
  --output report.html

The tool is not an official certification instrument, but it fills an important gap: until now, there was no standardized, reproducible method for assessing DPP data structures in an automated way.


Industry Perspective: Registries, Identifiers, and Scalability

The preferred format for linking a physical product to its digital record is the GS1 Digital Link. This standard URL scheme allows a single QR code or barcode to provide access to the associated product passport — while simultaneously encoding product identification (GTIN), serial number, and additional attributes within the URL.

For the Battery Passport, this is particularly relevant because every battery must be individually identified. A battery is not a generic product — it has a serial number, a production batch, and a specific lifecycle history. The GS1 Digital Link connects this physical identity to the digital record without requiring proprietary systems.

Orgalim: Registries Must Scale

Orgalim, the European industry association for technology companies, has set out clear requirements for the planned EU registry: it must support high-volume, automated registration processes. Manufacturers producing millions of battery cells per year cannot manage the manual registration of individual units.

This demand is technically well-founded. An automotive manufacturer producing electric vehicles with several hundred cells per vehicle faces the task of creating a compliant data record for each of those cells, registering it, and keeping it continuously up to date. Without bulk-import functionality and API-driven automation, this is simply not feasible.

Textiles in Focus: ESPR and the Limits of the Information Approach

The Battery Passport is not the only DPP use case currently gaining traction. In the textile sector, the Ellen MacArthur Foundation has published a position paper that raises an important regulatory question: is information transparency alone sufficient to transform the market?

The Foundation's answer is clear: no. The ESPR delegated act for textiles must mandate binding performance requirements — such as durability and recyclability thresholds — not merely disclosure obligations. Providing information about a product does not change the product itself. This debate is directly relevant to the Battery Passport as well: the passport documents a battery's carbon footprint, but it does not set a maximum value. Whether information obligations alone are sufficient to shift design decisions remains an open regulatory question.

In parallel, a JRC study has proposed concrete DPP data requirements for textiles, including mandatory fields such as GTIN/SGTIN for product identification and GLN (Global Location Number) for production sites — both GS1 standards that are also used in the battery sector.


Conclusion: Seven Months to the Mandatory Deadline

February 2027 is no longer a distant target. For battery manufacturers and their suppliers, this means the technical infrastructure must be built now — not after the next round of standardization.

The good news: the ecosystem is maturing quickly. With the BatteryPass-Ready test environment, the DP-AWB, and the webinars from the Commission and CEN/CENELEC, there are more guidance resources available than there were a year ago. The bad news: many companies have not yet fully integrated the complexity of the dynamic data component — SoH, SoC, lifecycle data — into their IT planning.

If you start implementing now, you still have time to correct mistakes. If you wait, you risk scrambling in January 2027 to deploy solutions under time pressure that are either non-compliant — or simply don't scale.

Sources