Answer in brief
The EU battery-passport duty reaches defined battery categories on 18 February 2027, while due-diligence obligations start later. Small product companies should classify batteries first, then secure structured supplier data and evidence.
The first task is classification, not data collection
A battery-passport project can be unnecessary in its assumed form if the company never checks scope. Article 77 of Regulation (EU) 2023/1542 requires a passport from 18 February 2027 for each light means of transport battery, each industrial battery with a capacity greater than 2 kWh, and each electric-vehicle battery placed on the market or put into service. Those categories do not describe every small rechargeable product. A compact device may contain a portable battery that is subject to other provisions of the Battery Regulation without being in the Article 77 passport scope. Before requesting dozens of fields from a supplier, document the battery category, rated capacity, product configuration and the company's economic-operator role.
Classification should be treated as a controlled regulatory record because product architecture can change it. A larger capacity pack, a different intended application or a switch from an off-the-shelf replaceable battery to a custom assembly can alter obligations. Record who approved the classification and which technical data supported it. If scope is uncertain, obtain specialist regulatory advice rather than asking the supplier to decide for you. The supplier knows the battery, but the company placing a finished product or battery on the market may hold obligations that depend on the complete commercial context. Good passport readiness begins with knowing exactly which legal object the company is responsible for.
Keep the February and August 2027 clocks separate
There are two prominent 2027 dates and they should not be merged. The battery-passport obligation for the specified categories starts on 18 February 2027. Separately, EU legislators postponed the application of battery supply-chain due-diligence obligations to 18 August 2027 through Regulation (EU) 2025/1561. The Council described the measure as stopping the clock on those due-diligence rules, and the Commission's battery-passport material continues to show the February passport date. The later due-diligence date therefore does not create a general six-month extension for passports. A project plan should carry the legal references beside each date so an update to one workstream is not mistakenly propagated to another.
A third implementation milestone has already passed: the Commission launched the DPP registry on 20 July 2026. That infrastructure milestone is relevant to how identifiers and registration fit into the broader DPP ecosystem, but it is not itself the date on which every in-scope battery suddenly needed a passport. For a small company, the practical sequence is to classify now, freeze the data model early enough to integrate and test it, and leave schedule margin for suppliers that discover gaps. Waiting until January 2027 to ask for evidence turns a regulatory implementation problem into an emergency procurement problem.
Build a supplier data dictionary, not a giant questionnaire
The Commission's August 2026 guidance maps battery-passport data points and emphasizes that its guidance supports implementation but does not replace the legislation. Use that principle when designing supplier requests. Every field in the internal dictionary should have a name, legal or business basis, definition, unit, format, applicability rule, source system, required evidence, responsible party, update trigger and access classification. Do not send a spreadsheet with columns such as 'carbon,' 'materials' and 'compliance' and expect suppliers to infer methodology. Ambiguous requests produce incomparable data, especially when several cell and pack suppliers are involved.
Also distinguish battery-model information from data that belongs to the individual battery. Article 77 and Annex XIII organize passport information at different levels and with different access conditions. A supplier may be able to provide model-level chemistry and manufacturing information while the final assembler or economic operator creates the unique identity and lifecycle record for the finished battery. Map the handoff explicitly. If the finished pack combines cells, a battery-management system and enclosure from different sources, the company needs a rule for which supplier facts become attributes of the finished battery and which remain supporting evidence only.
Carbon and material claims need method, scope and evidence
Carbon-footprint information is particularly easy to mishandle because a number without methodology and scope is not useful. The Battery Regulation contains carbon-footprint obligations that phase in by battery category and are supported by delegated and implementing measures. A passport data program should therefore link any carbon value to the legally applicable methodology, declared unit, production site or model scope, calculation period and supporting declaration rather than treating one supplier's corporate footprint as a battery value. Where a field is not yet applicable to the battery or date in question, mark it as not applicable or pending under the actual rule instead of forcing a guessed number into the database.
The same discipline applies to material composition, recycled content and substances. Supplier declarations should identify what physical object they describe and which evidence supports the claim. If a cell supplier reports chemistry while the pack supplier adds electronics, busbars, thermal material and a housing, the finished battery record may require information that no single supplier owns. Create a responsibility matrix at component level and then define the aggregation method. This is where small companies benefit from preparing early: the technical work is not scanning a QR code; it is reconciling data from organizations whose commercial systems were never designed to produce one regulatory record.
Traceability and due diligence intersect, but they are not identical
Passport traceability can help a due-diligence program, and due-diligence evidence can support some passport information, but the legal concepts should remain separate. The passport is a structured electronic record for an in-scope battery with defined information and access requirements. Supply-chain due diligence concerns policies and management systems for sourcing specified raw materials and associated risks under the Battery Regulation. The 2025 amendment changed the application timing of the due-diligence obligations; it did not rewrite Article 77 into a later passport deadline. Keeping separate data owners for passport publication and responsible-sourcing governance can reduce confusion while allowing them to share verified supplier evidence.
For supplier onboarding, ask which upstream facts the direct supplier can substantiate and which depend on sub-suppliers. A tier-one pack vendor may not itself generate mine or refiner evidence. If the company requires such information for an applicable obligation, the contract and process need a flow-down mechanism and a way to handle missing or low-confidence data. Do not convert an unresolved provenance gap into a precise-looking database field. Record status, source and confidence, escalate the gap, and update the value when evidence arrives. Traceability is strongest when uncertainty is visible rather than silently normalized.
Put the data obligation into supplier contracts before leverage disappears
A purchase order that specifies only electrical performance and price leaves regulatory data dependent on goodwill. New or renewed supplier agreements should define the product data to be delivered, the format or interface, delivery timing, evidence standard, correction process, retention expectations, confidentiality treatment and change-notification events. Material substitution, factory change, chemistry change, capacity revision and supplier reorganization can all invalidate passport data. The agreement should identify which changes require advance notice and which require a new or revised data package. It can also require cooperation with reasonable verification or audit processes where appropriate to the company's obligations.
Contract language should be proportional to role and bargaining power. A small company buying a standardized battery may not be able to impose a custom API on a large manufacturer, so the procurement strategy may instead prioritize suppliers that already publish structured regulatory data. The essential point is to evaluate data deliverability as a sourcing criterion before design lock. Legal counsel should tailor clauses to jurisdiction and the company's economic-operator position. There is no single official EU 'battery passport supplier contract'; the recommended clauses are controls that make the statutory data work feasible.
Design access, identifiers and versions before building the front end
The passport is not simply a public webpage. The Battery Regulation provides for different categories of information and access, including information available to the public and information accessible to specified actors. Build the underlying data model with access classification at field level and keep commercially sensitive evidence separate from the consumer presentation. The unique battery identifier and data carrier must resolve reliably to the correct record, while replacement, remanufacturing or status changes need to be handled according to the regulation. A static PDF behind a QR code may look like a passport demo but does not by itself solve versioning, access control or lifecycle requirements.
Version every consequential change. If a supplier corrects a carbon value, a facility changes, or a battery is remanufactured, the system should know what changed, when, why and who authorized it. Do not overwrite evidence silently. Test what happens when a product is returned, a replacement battery is installed, a data carrier is damaged or a supplier record is corrected after units have shipped. These operational cases are where an attractive prototype becomes a compliance system. They also determine whether customer support can explain a mismatch instead of sending screenshots between departments.
Use the next project cycle as the implementation deadline
Small companies do not need a massive transformation program to make progress. In the next product cycle, complete four artifacts: a battery scope register, a passport field dictionary, a supplier-responsibility matrix and a working record for one representative battery. Then test that record against Article 77, Annex XIII and the Commission's current guidance. Ask the supplier to correct one field and simulate a component change. Confirm that the data owner can update the record without breaking the identifier or exposing restricted evidence. If the battery is out of passport scope, retain the classification and redirect effort to the Battery Regulation provisions that do apply.
The management objective is schedule control. By the time an in-scope product approaches 18 February 2027, the company should be integrating verified supplier data rather than negotiating what 'material composition' means. Keep the 18 August 2027 due-diligence date on its own compliance track and monitor further official guidance, delegated acts and implementing measures that affect the relevant battery category. Battery passport supplier data is ultimately a contracting and data-governance problem as much as a labeling one: the physical supplier relationship has to produce evidence in a form the digital record can sustain.
Practical checklist
- Classify every battery by EU regulatory category, capacity and economic-operator role before building a passport project.
- Map Annex XIII passport fields and other applicable Battery Regulation data to the internal system that owns each value.
- Send suppliers a versioned data dictionary with units, evidence requirements and update triggers.
- Add contractual duties for timely corrections, material or supplier changes and supporting documentation.
- Separate public passport information from restricted data and define access before integration work starts.
- Test identifier, QR/data-carrier, versioning and replacement-battery workflows on a real product before 18 February 2027 if the passport scope applies.
Questions and answers
Which batteries need an EU battery passport from 18 February 2027?
Regulation (EU) 2023/1542 states that from 18 February 2027 each light means of transport, or LMT, battery, each industrial battery with a capacity greater than 2 kWh, and each electric-vehicle battery placed on the market or put into service must have an electronic battery passport. That means a company should not assume every battery in a small consumer product is automatically in passport scope. First determine the legal battery category, capacity and who is the responsible economic operator. Other Battery Regulation duties can still apply even when the product is outside the passport categories, so scope analysis should cover the regulation as a whole.
Did the EU postpone the battery-passport deadline to August 2027?
No. The two dates concern different obligations. The battery-passport requirement in Article 77 of Regulation (EU) 2023/1542 remains 18 February 2027 for the specified battery categories. A later amending regulation postponed the application of the battery supply-chain due-diligence obligations to 18 August 2027. The European Commission's August 2026 battery-passport guidance still identifies 18 February 2027 as the passport date. Companies should maintain separate workstreams and legal calendars rather than assuming a delay in one part of the Battery Regulation automatically moves another.
What should a small product company require from a battery supplier now?
Start with a versioned data specification tied to the battery category and the fields that actually apply. For each requested value, define the unit, methodology or legal reference where relevant, evidence document, product or batch scope, responsible supplier contact, confidentiality level and change-notification trigger. Contracts can then require delivery in a structured format, timely correction of errors, notice of material or facility changes, retention of supporting evidence, and flow-down to sub-suppliers where the supplier relies on them. This is an operational recommendation rather than one mandatory EU contract form; legal counsel should tailor obligations to the company's role and supply chain.