Battery Passport software · LMT and industrial batteries

Battery Passport software for manufacturers and EU importers.

Prepare for 18 February 2027. Under Regulation (EU) 2023/1542, LMT batteries, including e-bike batteries, and industrial batteries above 2 kWh placed on the market or put into service will need a digital Battery Passport.

NexusDpp coordinates supplier data, supporting documents, approvals and QR codes. Identify gaps in your supply chain and build a practical process for creating and updating your battery passports.

Explore a sample Battery Passport: fictional data, open access and no demo request form required.

The 2 kWh threshold applies to industrial batteries, not LMT batteries. Electric-vehicle batteries are also covered. Read Article 77 of the Batteries Regulation.

Photo: Matti Blume · CC BY-SA 4.0 · resized

NexusDpp Battery 360 demo dashboard

Manufacturers, brands and importers

From supplier documents to the battery passport.

Start with your operating model: the data to collect, approval responsibilities and the link to each unit.

Manufacturing e-bike batteries

Connect model records to individual batteries and define serial-number checks.

E-bike data and serials

Importing non-EU batteries

Define what to request from the manufacturer, who reviews documents and how gaps are resolved.

Importer workflow

Planning the budget

Separate data preparation and setup from usage volumes, integrations and support.

Plan the DPP budget

The public example contains fictional data and can be opened without completing a demo request.

Your role in the supply chain

Built around the work of battery manufacturers, OEMs and importers.

Define the workflow around your economic-operator role, battery category and the people responsible for each source of information.

Manufacturers and OEMs: connect model data to each battery

If you design, assemble or market batteries under your own brand, coordinate engineering, quality and supplier teams around a shared record. NexusDpp links models, variants, documents and individually identified batteries.

  • Match technical sheets and evidence to the right model.
  • Connect shared model data with individual serial numbers.
  • Assign review and approval responsibilities.
  • Manage revisions and lifecycle updates.

Explore the e-bike battery data and serial-number workflow.

EU importers: control data from non-EU suppliers

When importing finished batteries from China or other non-EU countries, agree exactly what the manufacturer and component suppliers need to provide. Define the owner and supporting document for each required field.

NexusDpp helps you assign supplier fields, request missing information and retain control of approval before publication.

Practical tasks may be delegated to authorised parties. Responsibility for the Battery Passport remains with the economic operator placing the battery on the market.

See DPP software for EU importers and organise data collection from non-EU suppliers.

Data and compliance preparation

Map the information that applies to your battery category.

Start with Regulation (EU) 2023/1542, Annex XIII and the requirements applicable to your product. Connect each field to its source, relevant model or unit, and person responsible for review.

Battery identity and manufacturing site

Organise manufacturer details, model references, production location and individual battery identifiers. Keep the relationship between the model record and each unit clear when reviewing or updating information.

Chemistry, composition and technical characteristics

Structure battery chemistry, materials, rated capacity, voltage, power and relevant performance parameters. Distinguish pack-level information from cell and component data according to the required level of detail.

Carbon footprint and environmental information

Prepare the collection of carbon-footprint values and supporting documents, with the relevant model, manufacturing site and methodology. Organise recycled-content and responsible-sourcing information around their respective application dates.

Declarations, test reports and relevant certificates

Link the EU declaration of conformity, test reports and relevant certificates to the battery and document revision. Give reviewers a clear basis for checking the source, consistency and currency of the evidence.

Public information and restricted access

Organise public views and restricted information for authorities, relevant bodies and persons with a legitimate interest. Configure permissions against applicable legal requirements while protecting commercially sensitive information.

Performance, status and use-related updates

Plan how to handle relevant state-of-health, usage-cycle and lifecycle information. Define sources, update rules and responsibilities. BMS or business-system integrations depend on available data, authorisation and technical compatibility.

Apply the right requirements at the right time. The Commission’s current battery FAQs state that carbon-footprint, recycled-content and due-diligence information will not yet be required when Battery Passports begin in February 2027. These requirements have separate application dates. Prepare the data against the obligations that actually apply to your battery.

Access policies also need to follow the applicable acts. The Commission’s FAQs describe the restricted-data implementing act as still in preparation. Review the Battery Passport access-rights guidance.

Sources checked on 29 October 2026: Regulation (EU) 2023/1542, Articles 77–78 and Annex XIII; European Commission battery FAQs; data points by category, updated 19 October 2026. Guidance supports preparation and must be read alongside applicable legislation.

The operating workflow

From supplier information to an updatable Battery Passport.

Use four practical steps to organise the work and test the result on a real sample.

01 · ONBOARD

Set up suppliers and responsibilities

Identify the battery category, your role and the parties holding the information. Define required fields, documents and reviewers. Suppliers receive requests tied to the relevant product and their area of responsibility.

02 · REVIEW

Collect, check and approve the data

Use guided input, files and agreed integrations to collect the information. Reviewers check completeness and consistency, request corrections and approve the version for publication. Keep each field connected to its source.

03 · PUBLISH

Create the passport and its QR code

Link the approved passport to the individual battery’s identifier and make it accessible through a QR code. Test the unit mapping, public view and restricted access. Define the EU Registry workflow separately from passport publication.

04 · MAINTAIN

Manage revisions and lifecycle updates

Agree who may update information, which changes need approval and how compatible systems feed the passport. NexusDpp maintains the relationship between revisions, documents and the battery. Integration scope and availability are defined in the project.

A practical starting point

One model, one battery and a source for every field.

A small sample helps reveal missing information before you extend the process to the full catalogue.

Illustrative data only: DEMO-36-14 is a fictional sealed LMT battery, 3.5 kg, 36 V and 14 Ah (504 Wh). This example is not a real product specification or a complete passport.

LevelExampleWhat to verify
ModelDEMO-36-14 · 36 V · 14 AhMatch the technical sheet to the exact variant and record its revision.
Individual batterySerial DEMO-000001Check the relationship between serial number, model and passport identifier.
EvidenceIllustrative technical sheet, revision 2Assign a source, reviewer and status; record missing information.
UpdateApproved correctionTest the revision and access rules while retaining the previous record.
Frequently asked questions

Before starting your Battery Passport project.

Do e-bike batteries below 2 kWh need a Battery Passport?

Yes, where they fall within the LMT category. The above-2-kWh threshold in Article 77 applies to industrial batteries. The passport requirement starts on 18 February 2027 for covered batteries placed on the market or put into service.

Source: Article 77 of the Batteries Regulation.

Who checks information supplied by a non-EU manufacturer?

The project identifies the people responsible for review. NexusDpp supports correction requests and approval before publication. The responsible economic operator must ensure that the passport information is accurate, complete and up to date.

Source: European Commission Battery Passport FAQs.

Are carbon footprint and recycled content required in February 2027?

The Commission’s current FAQs state that these fields, together with due-diligence information, follow their own application dates and are not required when the passport first becomes mandatory in February 2027. Assess the battery category and market-placement date against the applicable obligations.

Source: European Commission Battery Passport FAQs.

Does a pilot require an immediate BMS integration?

A pilot can start with available information and documents. Define sources, acquisition methods and any integrations for dynamic data during the project. Applicable information requirements must be covered before operational use; a missing integration does not remove those obligations.

Compare BMS, QR code and NFC

What supplier data do I need to start?

To scope a NexusDpp pilot, start with manufacturer details, the model technical sheet, a sample of serial numbers and available documents. Assign a source and an owner to each input. The starter CSV helps organise the request; it is not a complete regulatory dataset.

Download the starter supplier data template

Is a QR code enough to create a Battery Passport?

The QR code provides access to the passport linked to the battery identifier. A Battery Passport also includes the required data, access levels and update management. A NexusDpp pilot checks the relationship between data, the identifier and the accessible passport.

Read Articles 77 and 78 of the Batteries Regulation

How do the public example, platform demo and pilot differ?

The public example shows a Battery Passport with fictional data and requires no registration. A platform demo illustrates the operational workflow. A pilot uses an agreed scope of products and company data to test collection, approvals, access and updates.

Open the sample Battery Passport

Does the EU Registry store the complete Battery Passport?

The Registry records identifiers and registration metadata. The passport and its detailed information are maintained by the responsible operator or its authorised provider, which manages access. Creating the passport, publishing it and registering it are distinct steps to verify in a NexusDpp project.

Source: European Commission, battery FAQ 6.5

Battery pilot project

Prepare before the deadline. Start with a defined battery pilot.

Identify missing data, involve the right suppliers and test the workflow before extending it to your whole catalogue.

Start with one battery model, one supplier and a sample of real units. Agree the activities and acceptance criteria for:

  • a map of available information and unresolved gaps;
  • clear responsibilities for collection, review and updates;
  • a pilot Battery Passport accessible through a QR code;
  • an access-rights test and a recorded data update;
  • a practical plan for extending the process to more models and higher volumes.

Use the pilot to assess timing, integrations and operational readiness. It supports compliance preparation; the battery’s conformity assessment follows the applicable legal procedures.

Want to see the workflow first? Book a NexusDpp demo for manufacturers and importers.