18 February 2027 is the battery passport start date for electric vehicle batteries, light means of transport batteries and industrial batteries above 2 kWh placed on the market or put into service. The scope comes from Article 77 of Regulation (EU) 2023/1542.
A useful preparation plan separates the legal scope from the operational work: identifiers, supplier data, access permissions and updates after a battery leaves the factory.
Confirm which products are covered
Build an inventory by battery category and capacity. Do not assume the passport rule applies identically to every portable battery or every energy storage product. Record the responsible economic operator and the planned market-entry date for each covered line.
Other battery obligations have their own schedules. A passport project should not treat a single year as the start date for all labelling, carbon-footprint, due-diligence and performance requirements.
Plan QR access and optional NFC authentication
The regulation links battery passport access to a QR code and a unique identifier. NFC can provide an additional interaction or authentication channel, but it does not replace the prescribed QR access. See Article 13 and Article 77.
Test the printed label on the actual housing. Include small screens, poor lighting and the conditions in which service teams will scan it. If you also use NFC, test placement against the battery enclosure and installation environment.
See Hashentic tag-placement examples for planning a physical pilot.
Assign a source and owner to each field
Use Annex XIII and the applicable rules as the starting point for the data inventory. The passport includes both model information and information about an individual battery, with different access levels. Battery Regulation, Article 77 and Annex XIII.
For implementation, create a table containing:
- The field and its source system.
- The supplier or team responsible for evidence.
- The person who approves changes.
- The update frequency and handling of missing values.
- The audience allowed to access the information.
Keep unsupported estimates distinct from approved product facts. Ask suppliers to resolve gaps early enough for your own review process.
Design for updates after sale
A record needs an operating process around it. Decide how product changes are recorded, how corrections are approved and how a service partner requests an update. Test a realistic correction during the pilot, not just the first publication.
Choose storage, access control and continuity arrangements against your requirements. Blockchain is one possible technical component; a battery passport does not inherently require a blockchain deployment.
Run a pilot before scaling
Start with one product line and a limited group of users. Measure whether they can scan the label, find the information they need and report a problem. Test both public access and restricted workflows.
Hashentic offers configurable product fields, branded verification pages, NFC authentication and API integrations. These can support a passport implementation alongside your supplier-data and review processes.
Explore Hashentic for DPP, review the platform features, or request a demo with your product category and existing systems.
