Battery passport for industrial batteries and battery energy storage

For suppliers of battery energy storage systems, the first task is to determine what the specific battery is, what its category is and who is responsible for the data. One energy project is not automatically one battery identity.

Where product definition begins

For assemblies with modules, cabinets and control systems, the product hierarchy needs to be defined, rather than mechanically issuing a passport for every cell or, conversely, for the whole site. The boundaries follow from the specific design, documentation and legal classification. This decision affects the number of passports, the data model and traceability when parts are replaced.

The overview should cover the batteries supplied, models, revisions and the relevant documentation. The total project capacity stated on a sales sheet may not be enough on its own to set up the passports.

Which information sources to involve

• The battery manufacturer or supplier for the specification and model documentation.
• The production or warehouse system for the identity of individual units.
• The quality and engineering departments for approving data.
• Service for changes and documented events in the life cycle.
• Operational systems only where the data are available and their use has been agreed.

If ongoing operational data are to be part of the solution, the source, the frequency of changes and the authorisation rules must be verified. The QR code itself does not measure the battery's condition. Accounting, energy dispatch, the battery electronics and its digital passport are different systems.

Why the rollout may cost more than with a single spreadsheet

Work is added by harmonising revisions, links between parts, migrating historical documents, multiple source systems or separating access between the manufacturer, the integrator and service partners. Integration costs also include testing faulty input, re-running a batch after an outage and handing over responsibility for operations.

A standard API means a documented way of transferring data. It is not a ready-made connector to every enterprise system. In the offer, we therefore separate the platform, the specific integration and any ongoing connector management. We do not charge for the same work twice.

The result is not just a QR code on a cabinet

The supplier may also need assignment of the correct installation documentation, access for the service network, language versions and approval of changes. Some of the content is regulatory, some serves customer support. Public information and information intended for authorised persons must remain distinguished. Technical interventions rely on the manufacturer's approved documents, not on a generic guide from a software company.

Long-term operations are resolved before launch

For a battery passport, availability and the possibility of handover are important. The Regulation also addresses the cessation of the responsible economic operator and the end of the passport after recycling. The contract must therefore distinguish between regular support, data updates and a continuity plan. The lifetime of the passport cannot simply be equated with the length of the first subscription.

What to prepare for the initial meeting

A diagram of your assembly, a list of models, a sample of serial numbers, an overview of suppliers and information on which systems the data currently exist in are enough. First we define the pilot and its acceptance criteria. Subsequent extension to other products or plants depends on what the pilot has actually validated.

Scope of the battery passport obligation · Information for IT and integration · Book a consultation

Legal basis: Regulation (EU) 2023/1542, Art. 77, 78 and Annex XIII. Overview checked on 11 October 2026. The scope is assessed for the specific product.