Make every battery exported to the EU compliant, traceable and market-ready

01What a Battery Passport Is

The Digital Product Passport (DPP) as applied to batteries.

A Battery Passport is a structured digital record bound to an individual battery, accessed through a QR code as its data carrier. It covers the full life cycle — from raw materials and manufacturing through use, repair, repurposing and recycling — and presents information according to the access level of the visitor.

It consists of four parts

Two kinds of content

• Static information: manufacturer details, model and serial number, place and date of manufacture, weight and capacity, chemistry, material composition, performance parameters, safety information and conformity documents.
• Dynamic data: state of health (SOH), charge/discharge cycles, temperature records, and negative events such as incidents, fire, overheating or mechanical damage.

02Regulatory Requirements and Timeline

Based on Regulation (EU) 2023/1542 (Batteries Regulation) and its implementing rules.

1. Scope: electric vehicle batteries, light means of transport (LMT) batteries — e-bikes, e-mopeds, e-scooters — and industrial batteries above 2 kWh. Stationary battery energy storage systems fall under the industrial battery category and, above 2 kWh, are in the first wave.
2. Mandatory date: from 18 February 2027, the batteries above must carry a Battery Passport when placed on the EU market.
3. Accessible over the lifetime: the passport must remain accessible throughout the battery's life (10 years and beyond); the obligation persists even after the responsible operator ceases operations or withdraws from the EU market (Art. 78e).
4. Purpose limitation: an authorised service provider may store and process passport data, but must not sell, reuse or process it beyond what the service requires (Art. 78d).
5. Lawful delegation: the Regulation allows the responsible operator to mandate another economic operator in writing to act on its behalf (Art. 77(4)); the provision does not require establishing an entity in the EU.
6. Basis for data access: Art. 14 (in force since August 2024) requires battery management systems to provide read-only access to third parties mandated by the battery owner.
7. EU DPP Registry: the registry has been live since July 2026 (including a test environment) and supports both a web interface and an API; the first harmonised standards have been published, covering unique identifiers, data carriers, interoperability, APIs, data exchange protocols and storage.
8. Registration status: registration of the battery product group in the official registry is not yet open (the semantic catalogue for this product group has not yet been defined).

03eIDAS and Qualified Electronic Seals: Why They Are Required

DPP registration and declarations must be signed in the name of the company, with qualified trust services.

Three kinds of electronic signing, for three kinds of signer

Why DPP requires an organisation-level seal

1. The responsible party for a DPP is the economic operator — a company — so the source of the data must be verified at organisation level.
2. Responsibility does not lapse when staff change; a personal signature cannot carry organisational responsibility.
3. Cross-border mandates and transfers of responsibility require credentials signed in the name of the organisation.

Where a QESeal is used

1. Operator registration and organisation verification (enrolment);
2. Submission of conformity declarations and similar documents;
3. Submission of product data and the registry index;
4. Delegation documents;
5. Data updates and version confirmations.

The common thread: each step must be issued or confirmed in the name of the company.

What a seal usable for DPP must satisfy

• The organisation identity has undergone qualified verification;
• It is issued by a QTSP (qualified trust service provider);
• Under eIDAS (Regulation (EU) No 910/2014) it carries the same legal effect as a handwritten signature;
• It supports batch sealing and trusted timestamps;
• It can be delivered as a remote signing service or a smart card / USB token.

Not every field is signed or sealed

Electronic signing in DPP focuses on identity verification, system access and electronic registration evidence — not on signing each individual data field. Content credibility additionally relies on identity binding, unique identifiers, structural and semantic checks, hash verification, permission control, version management, operation logs, backups and regulatory review. Automated system checks are not, by themselves, proof that the data is accurate or fully compliant.

04Platform Capabilities

AECC's battery passport platform is deployed and running; the following capabilities are implemented.

05What the Service Covers

The fully managed service includes the following.

1. Identifiers and records: bulk issuance of compliant identifiers and QR codes, with passport records created battery by battery to the official EU data standard.
2. Data collection and updates: data pipelines are connected so that state of health, cycle counts and other dynamic data are updated continuously, with negative events recorded as they occur.
3. Public page build and maintenance: multilingual public pages that present the company's own brand.
4. Permission enforcement: tiered access for the public, authorities and authorised partners — application, approval, time-limited credentials and auditing, all systematised.
5. Regulatory tracking: implementing rules are adopted as soon as they are published, so you do not have to monitor regulatory change yourself.
6. EU DPP Registry readiness: registration capability and an audit-trail table are in place; connection can be completed once the battery product group opens.
7. Long-term hosting and regulatory response: lifetime storage and accessibility of passports, plus support for regulatory enquiries and data export.

06Commercial and Quotation

Commercial terms are determined by battery volume, service scope and the data integration required.

Fees and commercial terms depend on the battery models involved, the expected number of units, the scope of data integration and the hosting period. Please contact our commercial team — we will prepare a service proposal and a formal quotation based on your situation.

07Delivery Timeline

The platform side can deliver your first scannable passport within 30 days.

08What Companies Need to Have in Place

Compliance is shifting from one-off document submission to an ongoing data capability.

1. Map the applicable regulations and deadlines; define target markets and product scope.
2. Inventory the data sources: manufacturing data, test reports, production and ledger data, and in-service battery data.
3. Define data responsibility: who is accountable for the accuracy, completeness and timeliness of passport content.
4. Establish a unique identifier system: one lifetime-unique identifier per battery, with a permanently resolvable QR address.
5. Design system integration: how production lines, ledgers and monitoring systems will feed the passport.
6. Prepare eIDAS identity and trust services: obtain a qualified electronic seal (QESeal) in the company's name.
7. Pilot with a high-priority product, closing the loop of record creation, publication, scanning and data updates before scaling.

For battery manufacturers, the critical date is 18 February 2027. Data preparation and system integration are long-lead activities — allow sufficient margin ahead of the mandatory date.

09How to Verify a Battery Passport (QR Code) Is Genuine

Credibility does not depend on how polished a page looks, but on facts that can be checked independently.

Three checks anyone scanning a code can perform

1. Check the domain and encryption: the address bar should show the manufacturer's (or its authorised service provider's) official domain over HTTPS — not a short link or an unfamiliar redirect. The passport address is fixed at printing and does not change between versions.
2. Check consistency: the model, serial number and unique identifier (UPI) on the page should match the battery nameplate and the accompanying documents (declaration of conformity, packing list).
3. Confirm through official channels: if anything looks wrong, verify through the manufacturer's published service channel; do not trust contact details displayed on an unverified page.

Why a convincing fake is hard to produce

The ultimate check: the registration record in the EU DPP Registry

1. The responsible operator registers each passport's unique identifier and data hosting location in the official registry; only economic operators that have passed organisation verification (signing the official declaration with a qualified electronic seal) can register.
2. The official registry stores only the minimal registration record, not the full passport data — its role is precisely to evidence whether a passport is registered.
3. The registration record is therefore the independently verifiable anchor: a forged identifier or domain returns no record in the registry. This also gives regulators, market surveillance and trading parties a traceable basis.