BatteryPass-Ready Launches Test Environment for the Digital Battery Passport

On June 24, 2026, the BatteryPass-Ready consortium launched a public test environment for the Digital Product Passport. Battery manufacturers and suppliers can use it to validate their DPP solutions against the relevant EU standards — before the legal obligation kicks in February 2027. Fraunhofer IPK plays a central role in the platform, taking responsibility for the technical infrastructure.

The initiative arrives at a moment when the industry is under considerable time pressure: fewer than eight months remain until the deadline.

Legal Framework: What the Battery Regulation Requires

The foundation is the Battery Regulation (EU) 2023/1542, which entered into force in August 2023. It requires manufacturers and importers to equip certain battery categories — including industrial batteries from 2 kWh, traction batteries for electric vehicles, and batteries for light means of transport — with a machine-readable data carrier that links to a structured digital data record.

That data record must cover a broad range of information:

Static data such as cell chemistry, CO₂ footprint, material composition, and supply chain documentation
Dynamic data such as State of Health (SoH) and State of Charge (SoC), which change with every charge and discharge cycle

The dynamic parameters in particular pose special challenges for manufacturers: they require a permanently active database connection and clearly defined interfaces for read and write access across the entire product lifecycle.

Standardization: CEN and CENELEC Set the Standard

On June 25, 2026, CEN and CENELEC hosted a public webinar to explain the recently adopted European standards. These standards specify which data fields must be provided, in what format, and how technical interoperability between different systems is to be ensured.

Just two weeks later, on July 7, 2026, the European Commission followed up with a second industry webinar focused specifically on the Battery Passport — this time with an emphasis on data requirements, interoperability, and industry readiness. The message was clear: the Commission expects industry to actively engage with the standardization work rather than wait for further clarification.

What the Test Environment Offers

The platform provided by BatteryPass-Ready at thebatterypass.eu lets companies run their DPP implementations against defined conformance checks. At its core, it answers three questions:

Are all legally required data fields present and correctly populated?
Does the data structure conform to the adopted European standards?
Does the link between the physical product and the digital data record work correctly from a technical standpoint?

For the third point, the preferred format is the GS1 Digital Link — a standardized URI that encodes product identifiers such as the GTIN in a URL structure, enabling machine-readable references to the digital twin. On qr3.app, you can generate such a GS1 Digital Link directly as a QR code and register it with a resolver.

Technical Architecture: Resolver, API, and Data Storage

Before using the test environment, you need to clarify what your own system architecture looks like. A typical setup consists of three layers:

Data storage: Product database or ERP system that maintains the static master data
Resolver: Service that resolves a Digital Link URL to the specific data record — with different endpoints depending on context, for consumers, recyclers, or authorities
Frontend: QR code or other data carrier on the physical product

GS1 Digital Link URI (printed on battery)
    │
    ▼
Resolver (e.g. gs1.org/resolve or custom endpoint)
    │
    ├──► Consumer UI (HTML)
    ├──► Recycling API (JSON-LD)
    └──► Authority dataset (structured XML/JSON)

The BatteryPass-Ready test environment checks whether this resolver call returns the expected responses and whether the returned data conforms to the standards framework.

Industry Perspective: Where the Gaps Remain

Despite progress at the standardization level, open questions remain. Orgalim, the European industry association for technology companies, has set out clear requirements in a position paper on the EU Registry: the planned central EU Registry must support high-volume, automated registration processes. Manually entering records is simply not feasible for manufacturers producing millions of battery units per year.

This is not an academic problem. If you want to retool your production line for DPP compliance today, you need to know how bulk import of serial numbers and product data into your DPP platform works — and whether the EU Registry will eventually offer an API for mass registrations. The latter has not yet been fully specified.

Timeline and Remaining Steps

The key milestones on the path to compliance:

Date	Event
August 2023	Battery Regulation (EU) 2023/1542 enters into force
June 2026	CEN/CENELEC standards adopted; webinar held
June 24, 2026	BatteryPass-Ready test environment goes live
July 7, 2026	EU Commission webinar on data requirements
February 2027	DPP obligation for affected battery categories

The time remaining until February 2027 is sufficient for a structured implementation — but not for an unprepared one. Companies that do not yet have a DPP strategy should use the test environment to assess their own maturity level before investing in technical implementation.

Putting It in Perspective: What the Test Environment Does Not Do

It is worth calibrating expectations. The BatteryPass-Ready platform is a validation tool, not a ready-made production system. It checks conformance — it does not replace your own data strategy, ERP system, or resolver operation. The question of how dynamic data such as SoH and SoC are kept current during ongoing operations is also something each company must solve for itself.

Nor does the test environment clarify which data must be disclosed to which actors. The Battery Regulation provides for different access rights: consumers see different information than recycling companies or market surveillance authorities. This access control must be implemented in your own resolver — and should also be part of your validation process.

The availability of a public test environment is nonetheless a significant step. It makes abstract regulatory texts tangible and gives manufacturers a concrete tool to identify implementation gaps early. In a regulatory environment that is still evolving in many details, that is worth more than it might initially appear.