Technician scanning a battery pack QR code on a production line
How-to Guide

How to Implement an EU Battery Passport: Manufacturer's 2027 Guide

A practical roadmap for battery manufacturers preparing for EU Battery Passport requirements.

Reviewed 29 September 2026 · 12 min read

On this page
  1. Step 1 - Separate Battery Passport scope from QR-code and labelling scope
  2. Step 2 - Identify who is legally responsible and who may operate the platform
  3. Step 3 - Build a realistic February 2027 data checklist
  4. Step 4 - Obtain supplier information before it blocks publication
  5. Step 5 - Choose an identification and QR activation method that works on your line
  6. Step 6 - Integrate business systems; do not create a parallel manual database
  7. Step 7 - Separate public, restricted and legitimate-interest information
  8. Step 8 - Plan Registry onboarding, integrity and continuity as distinct controls
  9. Step 9 - Test evidence, interoperability and live operating scenarios
  10. Step 10 - Assign ongoing ownership, cost and change-management triggers
  11. Frequent manufacturer questions - answered
  12. Does an SLI battery need an individual Battery Passport?
  13. Can I issue only one passport for a battery model?
  14. Must cells and modules have a separate Battery Passport?
  15. Are all 71 Commission data points compulsory on 18 February 2027?
  16. Are carbon footprint, recycled content and due diligence fields already mandatory in the February 2027 passport?
  17. Must the passport stream real-time BMS data?
  18. Can I operate my own DPP software?
  19. Do I need a blockchain or a qualified electronic signature on every passport?
  20. What if a supplier refuses to share information?
  21. Can a passport be updated after sale or repurposing?
  22. Practical checklist for the first production pilot
  23. Sources and implementation references

Published 29 September 2026 12 min read GoodsTag Editorial Team Batteries

Quick answer: Start by classifying each finished battery and identifying the responsible economic operator. Build a battery-category-specific data checklist from the EU's August 2026 guidance, identify reliable sources and supporting evidence, assign an individual identifier to each battery requiring a passport, and connect its QR code to a versioned digital record. Then test access permissions, lifecycle updates, data integrity, independent continuity, and registration in the EU DPP Registry. Do not wait for every remaining technical detail before starting your data and production work.

Regulatory status, reviewed 29 September 2026: Article 77 of Regulation (EU) 2023/1542 requires a Battery Passport from 18 February 2027 for each EV battery, LMT battery and industrial battery above 2 kWh placed on the EU market or put into service. It does not impose a full passport on all batteries. The separate QR-code obligation under Article 13(6) starts on the same date for all batteries. The European Commission's Battery Passport FAQ and data-point guidance clarify implementation but do not replace binding legislation.

Editorial disclosure: GoodsTag provides Digital Product Passport software and publishes this operational guide. The implementation patterns are illustrative; compliance and technical evidence remain the responsibility of the relevant economic operators. This article is not legal advice.

Step 1 - Separate Battery Passport scope from QR-code and labelling scope

Create a product portfolio table before choosing software. Record battery category, rated energy, responsible entity, finished battery model, manufacturing site, destination market, planned market-placement date and whether the record concerns a finished battery or merely a cell/module supplied for assembly.

Battery categoryFull Battery Passport from 18 February 2027?QR-linked regulatory information?
Electric vehicle (EV) batteryYes, individual batteryYes
Light means of transport (LMT), including relevant e-bike batteriesYes, individual battery, regardless of the industrial 2 kWh thresholdYes
Industrial battery greater than 2 kWhYes, individual batteryYes
Industrial battery at or below 2 kWh (unless independently classed as EV/LMT)No Article 77 passportYes, Article 13(6) information
Starter, lighting and ignition (SLI)No Article 77 passportYes, including category-specific information
Portable batteriesNo Article 77 passportYes

Do not conflate the QR code date with the separate general physical label timing under Article 13(1)-(3): the latter depends on its implementing act and the Regulation's "whichever is later" rule. Track other measures - carbon-footprint disclosures, recycled-content documentation and due diligence - against their own application conditions.

Deliverable: one approved product-scope register signed off by compliance/legal, with the reason for each classification. Review edge cases (mixed-purpose packs, repurposed batteries, battery assemblies and batteries integrated into vehicles) instead of assuming that a component and a finished battery trigger the same passport obligation.

Step 2 - Identify who is legally responsible and who may operate the platform

Under Article 77(4), the economic operator placing the finished battery on the market is responsible for complete, accurate and current passport information. Another operator can create or update it with written authorisation, but this does not transfer ultimate responsibility. The Commission's FAQ distinguishes a completed battery supplied to a vehicle OEM from a battery only completed by that OEM (for example through the addition of essential components).

Write down a RACI matrix for producer, importer, OEM/assembler, product owner, quality, compliance, IT, suppliers and outsourced DPP provider. Decide who signs off model information, who activates an individual battery, who corrects data and who handles requests from authorised downstream operators. Build these permissions into the system rather than relying on informal email approvals.

Deliverable: a named legal accountable owner and a written delegation/approval workflow for each market-entry model.

Step 3 - Build a realistic February 2027 data checklist

Do not turn Annex XIII into a blind 100%-mandatory spreadsheet. The Commission's 15 August 2026 updated data-point guidance, announced on 21 August, organises 71 data points and distinguishes data required at launch, conditional fields, category-specific fields and fields not yet applicable in February 2027. Validate the checklist against the current guidance version before going live.

Structure data in four layers:

  1. Operator/model: economic operator, battery category, model identification, chemistry, nominal technical characteristics and related product documentation.
  2. Finished battery/item: individual identifier, manufacturing record, model association, status and information specific to the battery.
  3. Supporting evidence: test reports, methods, calibration/measurement conditions, conformity assessment and technical documents, with access restrictions where required.
  4. Lifecycle information: performance/durability information and applicable dynamic fields; future carbon-footprint, recycled-content and responsible-sourcing data activated only when their underlying requirements apply.

A chemistry name such as "LFP" is not a substitute for a complete legally applicable composition disclosure. A model PDF is not a substitute for a structured, individual Battery Passport. Record data source, unit, test conditions, evidence reference, responsible owner, validation status and update trigger for each field.

Deliverable: version-controlled applicability matrix with columns field / battery category / legal basis / mandatory status at date / granularity / source / evidence / owner / validation rule / publication access.

Step 4 - Obtain supplier information before it blocks publication

An assembler often has cell and module datasheets but not the methodology behind declared values. Article 39 requires suppliers of cells and modules to provide information and documentation necessary for battery-regulation compliance, free of charge. This is not a general entitlement to every trade secret, and cell-level measurements do not automatically describe the performance of the finished pack.

Send structured requests stating the battery model and each specific required parameter; request units, referenced test standards, charge/discharge conditions, temperature, state of charge and underlying supporting documentation where necessary. Track the gap and ask procurement to escalate unresolved cases. Where appropriate, use technically justified representative testing or calculations; label approximations honestly and validate them. Do not publish a mandatory value merely because a generic supplier brochure mentions it.

Deliverable: supplier evidence register: supplier / component / field / missing information / due date / evidence link / quality decision.

For a deeper treatment, see Missing Battery Data from Suppliers?.

Step 5 - Choose an identification and QR activation method that works on your line

For Article 77 batteries, design a persistent individual battery identifier aligned with ISO/IEC 15459 requirements; determine the supported issuing/identification approach with your technical and compliance advisers. GS1 Digital Link is a practical approach but do not tell staff that every battery must buy a GS1 company prefix in all circumstances. Confirm standards-conformant identity, uniqueness, resolvability, persistent domain control, and whether the physical carrier remains readable in the intended environment.

A sensible physical-to-digital workflow can be:

  1. Pre-print a controlled supply of serialized QR labels, or generate them inline if your process requires it.
  2. Scan and activate one label for the finished battery when the relevant production record is available.
  3. Resolve the code to a model record plus that item's production data.
  4. Validate and publish only when applicable mandatory information is complete; keep incomplete records as drafts.
  5. Maintain the same persistent identifier while versioning permitted updates.

Pre-printed labels are an implementation option, not a legal requirement. The GoodsTag/NBA Batterie/SIAP production-line demonstration illustrates it; do not claim that this demonstration proves every Registry or factory integration is already in production.

For portable, SLI and small industrial batteries without passports, a model-level QR with a trustworthy batch lookup is under industry discussion but should not be described as universally confirmed compliant. The operator must still connect the physical battery to the correct production record. See one QR per battery model.

Deliverable: tested QR and identity specification (model, item, label durability, reprint policy, duplicate-prevention, offline failures, resolver continuity).

Step 6 - Integrate business systems; do not create a parallel manual database

Use existing ERP for product masters, MES for production orders and serialisation, PLM/PIM for specifications, QA/LIMS for test and inspection data, and document systems for controlled declarations. Connect supplier files through structured imports where APIs are unavailable. Choose one authoritative system per field and record transformations. A DPP layer should aggregate trusted information rather than manufacture technical evidence.

Pilot a single battery from production order → identifier assignment → field validation → published record → correction/version history → QR scan. Measure wrong-item links, missing values, scan failures and corrective-action effort. For each field define whether updates happen automatically, through scheduled reconciliation or after human approval.

Step 7 - Separate public, restricted and legitimate-interest information

Article 77 and Annex XIII distinguish public information, information for authorities/notified bodies, and information available on the basis of legitimate interest. The Commission's implementing act clarifying restricted access rights was still in development at this review date. Implement flexible, auditable role-based permissions, not only public/private. Test scenarios for a consumer, battery purchaser, recycler, repairer, auditor and authority without exposing suppliers' proprietary data.

The EU Registry does not host the full passport and does not centrally authenticate every downstream recipient. Passport hosting and access-control responsibilities need to be defined explicitly. Confirm in writing how legitimate-interest roles are verified, permissions granted and revoked, and requests logged.

Step 8 - Plan Registry onboarding, integrity and continuity as distinct controls

The EU DPP Registry became operational on 20 July 2026. Under Commission Implementing Regulation (EU) 2026/1778, economic operators verify their identity using prescribed eIDAS mechanisms; organisations should plan for a qualified electronic seal or qualifying attestation mechanism. Test the actual registration workflow in the Commission's environment; the Registry supports manual processes and interfaces for more automated use cases.

Do not confuse (a) qualified identity verification for Registry onboarding, (b) the Registry's proof of registration, and (c) cryptographic protection of passport content. A registry hash alone is not a complete strategy for data provenance, updates and continuity; equally, avoid claiming that the law necessarily mandates one qualified seal on each individual DPP. See what the Registry validates.

Agree what is backed up - structured records, evidence references, versions, metadata, access rules and resolution information - who holds the independent copy, how recovery works, how QR resolution survives a primary-provider failure, what happens at termination, and who owns export rights. Do not treat GoodsTag's included 10-year hosting offer as a universal legal minimum for every DPP.

Step 9 - Test evidence, interoperability and live operating scenarios

Before releasing production, run these eight test cases: (1) valid individual record; (2) missing mandatory field blocked; (3) wrong battery category rejected; (4) duplicate identifier rejected; (5) restricted document inaccessible to a public visitor; (6) updated data with a verifiable history; (7) restored passport or exported portable data after service failure; (8) Registry submission and proof/receipt retrieval where applicable.

The BatteryPass-Ready testing approach described by GoodsTag can complement internal validation if the current tool remains available. Third-party test reports are useful technical evidence, not official EU certification of a Battery Passport provider.

Step 10 - Assign ongoing ownership, cost and change-management triggers

At go-live, agree who monitors new technical standards, changes to Commission guidance, failed supplier integrations, expired economic-operator verification, battery lifecycle events, unresolved data corrections and provider contingency arrangements. Budget separately for one-off setup, the number of new passports, updates to existing records, integration work, production labels, storage/continuity and any required trust services. Request a cost scenario for 5,000, 100,000 and 1,000,000 new batteries per year, as applicable.

Illustrative rollout plan (not a statutory schedule): Weeks 1-2 product scope and RACI; weeks 3-5 data/evidence map; weeks 6-8 one-line activation pilot; weeks 9-10 permissions, Registry and backup tests; weeks 11-12 change control and phased scale-out. The actual timeline depends on site complexity and available data.

Frequent manufacturer questions - answered

Does an SLI battery need an individual Battery Passport?

No. SLI batteries are outside Article 77's passport scope but remain subject to Article 13 QR-linked information and other applicable obligations.

Can I issue only one passport for a battery model?

No, not when Article 77 covers the battery: each relevant individual battery has an electronic passport containing model-level and item-specific information.

Must cells and modules have a separate Battery Passport?

Component supply alone does not automatically trigger a finished-battery passport. Identify which economic operator places the finished covered battery on the market and how assembly changes legal responsibility.

Are all 71 Commission data points compulsory on 18 February 2027?

No. Requirements are category-dependent, conditional and phased. Use the Commission's versioned applicability guidance.

Are carbon footprint, recycled content and due diligence fields already mandatory in the February 2027 passport?

Not as a blanket rule. The Commission's current guidance treats these fields as linked to later underlying regulatory application dates; confirm the exact category and current acts.

Must the passport stream real-time BMS data?

Not universally. The Commission's FAQ discusses updates at status changes and recognises offline products; BMS-dependent requirements must be evaluated separately.

Can I operate my own DPP software?

The battery rules do not require purchasing a particular commercial provider, but the economic operator still must satisfy applicable technical, access, continuity and Registry requirements.

Do I need a blockchain or a qualified electronic signature on every passport?

No mandated blockchain. Treat operator verification, record integrity and proof of registration as different questions; no universal per-passport qualified signature requirement is established here.

What if a supplier refuses to share information?

Use a regulation-based Article 39 request for cell/module suppliers, escalate through procurement and assess documented testing or validated calculations where suitable. An unresolved mandatory gap cannot simply be ignored.

Can a passport be updated after sale or repurposing?

Yes. Design for authorised lifecycle updates and the legally required linking of original and successor passports for specified repurposing/remanufacturing scenarios.

Practical checklist for the first production pilot

  • Portfolio classification and responsible economic operator approved.
  • February 2027 data-field applicability confirmed against Commission guidance.
  • Supplier evidence and performance test conditions documented.
  • Individual identifiers and physical QR carrier tested.
  • Production activation, data validation and versioning tested.
  • Public/restricted access matrix and change rights exercised.
  • Registry onboarding and registration flow validated.
  • Independent backup, export, recovery and continuity agreed.
  • Legal, quality, IT and production sign-off recorded.

Sources and implementation references

Binding law / official guidance: Batteries Regulation (EU) 2023/1542 (Arts. 13, 38, 39, 77-78 and Annex XIII); ESPR (EU) 2024/1781; DPP Registry implementing regulation 2026/1778; Commission battery FAQ; Commission August 2026 data-point guidance.

Industry and practical implementation: CIRPASS-2 Community of Practice (interoperability and provider governance); GoodsTag supplier data; pre-printed labels; independent backup analysis; manufacturer demo.

Related: Compare Battery DPP providers - General DPP implementation guide - GoodsTag Battery DPP solution.

Discuss your Battery Passport implementation: Request a Battery DPP readiness assessment. The first discussion should focus on a scoped product list, a real production record and current supplier evidence - not a generic QR demo.

Last regulatory and editorial review: 29 September 2026. Re-check newly adopted implementing/delegated acts, standards and Commission FAQs before relying on this guidance for a legal sign-off.