← Back to DPP guides

Battery Passport · e-bikes and light mobility

E-bike battery passports: from the model to each battery.

An operational guide for manufacturers, brands and importers: organise model data, connect serial numbers and collect supply-chain evidence before publishing the passport.

NexusDpp S.r.l. · Updated

Open automotive lithium-ion battery pack with visible cells and terminals

Project example · illustrative data

Two models, 120 batteries: define your first pilot.

Imagine two models from two manufacturers. The pilot checks that shared documents and individual battery information remain correctly connected.

Organise the two models

Prepare a record for each model with specifications, manufacturer and document versions.

  • Assign a source and an owner to each field.
  • Identify information still to be received.

Connect the 120 serials

Use a unit list linked to model and production grouping.

  • Check for duplicate or missing serials.
  • Check that each QR opens the correct battery.

Test one change

Simulate replacing a document or recording an event on one unit.

  • Check which records need updating.
  • Review history and access separation.

This is an illustrative scope, not a customer case. The public passport uses fictional data; your pilot requires relevant data, evidence and checks.

Which e-bike batteries need a passport?

Regulation (EU) 2023/1542 provides for a passport from 18 February 2027 for each LMT battery placed on the market or put into service. The 2 kWh threshold concerns industrial batteries; it does not exclude an e-bike battery classified as LMT. Check the category and operator’s role for the actual product.

Start with a list of models, variants and organisations. Identify who designs the pack, produces the cells, assembles the battery and places it on the market. This list helps you assign specific supplier requests and identify evidence already available.

Shared model data, an identity for each unit.

The passport includes information about the model and the individual battery, including information resulting from use. Organise the workflow around three levels: a reusable model record, a production grouping and an individual unit record.

LevelInformation examplesOperational check
ModelConfiguration, technical documents and reference suppliers.Approve a version and connect it to the relevant units.
BatchProduction, delivery and records shared by a group.Trace units affected by a change or recall.
Individual batteryIdentifier, serial number, events and available usage data.Open the correct unit’s passport from its QR code.
Batches help organise work.

For batteries covered by Article 77, one generic batch passport does not replace the individual battery passport. Generating records in groups must preserve the link between every unit and its identifier.

Collecting information from a non-EU manufacturer.

Prepare a request matrix for the pack manufacturer and relevant suppliers. Each request should specify the model, expected data, supporting document, responsible person and version.

  1. Assign the information. Separate the brand’s own information from data supplied by the factory or cell supplier.
  2. Check consistency. Compare model codes, measurement units, document versions and test-report references.
  3. Manage missing information. Record the open issue and the person responsible for resolving it. A blank field is not verified information.
  4. Approve the content. Identify who can approve the dataset and who keeps it current.

A NexusDpp project configures this workflow around the company’s responsibilities. The EU importers and non-EU suppliers guide explores evidence collection and review.

Define access and updates before the QR code.

Annex XIII distinguishes public information, information reserved for competent authorities and bodies, and information accessible to legitimate-interest users. The access matrix must follow applicable requirements and relevant implementing acts.

For the operational project, specify who requests access, how their role is checked and which fields they may consult. Define repair, recall and end-of-life workflows, preserving versions and responsibility. For dynamic information such as BMS data, agree availability, format and update frequency with the supplier before adding an integration to the project scope.

BMS, QR code and NFC: how they relate to the passport.

The BMS is the battery management system. The QR code opens the passport; an NFC tag can provide an additional access point. Collecting measurements, identifying a battery and making its information available are separate parts of the project.

What each component does and what to check in a NexusDpp pilot
ComponentRolePilot check
BMSMonitors and manages battery operation. It can be a source for available use-related data.Agree accessible fields, units, timestamps, permissions and the connection to each serial number. Confirm the connector before promising automatic updates.
QR codeProvides access to the passport linked to the battery identifier. Article 77 requires QR access for covered batteries.Scan a sample of units and verify the identifier, destination and public view of each passport.
NFC tagCan provide an additional way to access information. It does not replace the required QR code.Test compatible devices, the physical label and the intended destination. A tag carrying a static link does not automatically provide authentication.
Passport softwareOrganises the product record, evidence, access permissions and revisions.Verify sources and update responsibilities. In NexusDpp, integration availability and scope are agreed for the project.

A useful integration test: for a sample state-of-health value, record its source, calculation definition, timestamp and battery serial number. Check that an update affects the intended battery and that unavailable data is not presented as a verified zero.

See Regulation (EU) 2023/1542, Articles 77–78 and the NexusDpp platform workflow.

A pilot that tests the process.

Start with a real model and a small sample of individual units. The useful outcome is a repeatable process with explicit acceptance criteria:

  • Each sample serial opens the correct record, without duplicates.
  • A revision to model data applies only to the relevant units.
  • A missing or expired document remains identifiable and assigned to an owner.
  • The public view does not expose restricted fields; authorised views are tested separately.
  • A maintenance event updates the correct battery’s history.

Before scaling up, agree data export, service continuity and identifier management. Use the DPP readiness checklist to structure the initial discussion.

Review supplier onboarding, approvals and updates in our Battery Passport software overview, then request an e-bike battery demo to discuss how the workflow fits your sample.

Frequently asked questions.

Is an e-bike battery below 2 kWh excluded?

No, not on that basis. The 2 kWh threshold concerns the industrial category; first verify whether the battery is classified as LMT.

Can we start with information already in our ERP?

Yes, it can be one project source. Check which fields it covers, how they connect to serial numbers and which evidence must come from other systems or suppliers.

Does a demo establish compliance for a real product?

A demo illustrates the workflow. A real product needs relevant data and evidence, defined responsibilities and assessment against applicable requirements.

Does scanning the QR code update the BMS data?

Scanning opens the passport. Transferring new BMS measurements requires an available data source, authorised access and an agreed collection process. The pilot must verify the connector, update frequency and link to the correct battery.

Does a working QR code prove product conformity?

No. A printed QR code can be copied, and opening a page is not a conformity assessment. Check the source, battery identity and relevant evidence. Additional authentication controls require a separately defined and tested technical solution.