1. Make one documented scope decision
Article 77 sets 18 February 2027 as the passport date for EV batteries, LMT batteries and industrial batteries with capacity greater than 2 kWh placed on the market or put into service. The industrial capacity threshold must not be reused as an EV or LMT exclusion. Record the category, capacity evidence, relevant market event and responsible economic operator before estimating implementation work.
Apply Article 1 exclusions separately. Also identify preparation for re-use, repurposing or remanufacturing cases: Article 77(7) has its own responsibility and linked-passport rules. An old manufacturing date alone cannot settle those lifecycle cases. Keep uncertain classifications visible and assign them to a qualified reviewer.
Source: Regulation (EU) 2023/1542 — scope, passport and Annex XIII
2. Give every deliverable an owner
Operational recommendation: nominate a product lead, an evidence reviewer, a person responsible for identifiers and a technical operator for publication. A single coordinator can hold several roles in a small company, but the review and acceptance decisions still need names. Define who approves a changed value after the supplier contact has left.
Create a short release record for the pilot: product model, configuration, expected serial-number range, source systems, approved publication fields and unresolved dependencies. Link supplier part numbers to the battery you actually sell. Otherwise a correct document can be attached to the wrong assembly without creating an obvious missing-data error.
3. Separate launch evidence from later data
Annex XIII contains model and individual-battery information. The Commission guidance reviewed here is version 2.0 of 15 August 2026; it differentiates mandatory, conditional, optional and not-needed-at-launch entries. It does not make all 71 listed points unconditionally due in February 2027. Legal applicability remains governed by the underlying provisions and relevant acts.
Operational recommendation: track applicability separately from collection status. For each launch-relevant field record the source, unit, reviewer and update trigger. Treat a conditional field without a resolved condition as an open decision. Treat unavailable evidence as a collection problem, not as permission to mark the field inapplicable.
Source: Regulation (EU) 2023/1542 — scope, passport and Annex XIIISource: European Commission — battery data guidance v2.0, 15 August 2026
4. Test access with different users
Articles 77–78 and Annex XIII distinguish public information, authority access and legitimate-interest access. The QR code and unique identifier connect the battery to its passport, but the complete evidence folder is not meant to become public merely because the label is public.
Operational recommendation: rehearse the same battery with a customer, service partner and internal reviewer. Check what each can read, whether their identity is established where required, and who can update lifecycle information. Include a denied-access case and an expired-document case. Record external integration gaps before approving labels for production.
Source: Regulation (EU) 2023/1542 — scope, passport and Annex XIII
5. Rehearse registration and the physical handover
The EU Registry has an operational framework under Implementing Regulation 2026/1778 and a separate testing environment. Registry metadata and the hosted passport have different jobs. A successful registration does not independently establish that the battery satisfies every legal requirement.
Operational recommendation: follow the official test workflow with representative data, then reconcile the product identifier, returned registration identifier and actual QR destination. Test a printed label on the intended surface with ordinary phones. Keep test and live records distinct and decide who investigates rejected registrations or unreachable passport destinations.
Source: Implementing Regulation (EU) 2026/1778 — DPP RegistrySource: European Commission — the DPP RegistrySource: Regulation (EU) 2024/1781 — ESPR
6. Make the first release repeatable
Operational recommendation: approve the pilot only when another colleague can reproduce the evidence review and explain unresolved conditions. Check a supplier revision, a corrected unit, a new battery identifier and a service handover. Establish who keeps the record available when a supplier or software provider changes.
Passvanta can support category-bound product records, supplier requests, reviewed document proposals, readiness checks and versioned publication. Use those functions to prepare and audit your workflow. Validate required access, lifecycle and Registry integrations separately; a readiness result or a generated carrier is not certification or automatic Registry acceptance.