Home > Implementation > Battery Passport QR Codes & Architecture

Battery Passport QR Codes & Architecture


A Battery Passport QR code encodes a reference that resolves to the passport record for one battery unit. The code must keep resolving to the correct unit record through service, reuse and end of life (EOL), including after a damaged label is replaced. Where the record is stored and how it stays available is covered on Data Storage & Hosting.


Unit identifier, QR content and passport record

The physical label can be damaged, replaced or counterfeited; the unit identity behind it must not change.

Element Purpose What must stay stable
Unit identifier Identifies the physical battery unit Unchanged across service, reuse and EOL
QR code content Encodes the reference used to retrieve the record Resolves correctly; may be re-issued when a label is replaced
Passport record Holds model and unit data plus lifecycle updates Version-controlled and auditable

Identifier formats and physical marking are covered on Battery ID & Serialization.


QR code content and encoding

Encode a stable resolver URL that maps to an opaque unit identifier (ID). Keep meaning in the system, not in the code string, and keep business logic and sensitive data out of the code, since many parties will scan it. When endpoints move, change them behind the resolver instead of reprinting labels.

Option Advantages Drawbacks
Resolver URL plus opaque unit ID Stable; easy to migrate behind the resolver Depends on resolver uptime and a redirect strategy
Direct deep link to the record location Fewer hops; simpler debugging Breaks when hosting or paths change
Structured fields embedded in the code Readable and decodable offline Leaks information; hard to version when rules change

Resolver architecture

A minimal architecture has a stable unit ID, a resolver, a controlled data store and an audit log. Build the identifier service and resolver first, then structured storage and logging, then supplier intake and lifecycle update workflows.

Component What it does Implementation note
Identifier service Allocates and validates unit IDs Enforce global uniqueness and immutability
Resolver endpoint The URL or service the QR code points to Keep stable; no environment-specific paths on labels
Access control Decides who can read and who can update Separate public and restricted fields; role-based permissions
Data store and audit log Hold the record and its change history See Data Storage & Hosting

Public and restricted access routing

A public scan should open the public view with minimal friction, while restricted fields require authentication and are logged. Decide early which fields are public, which are restricted and who may update them, and build the split into the data model and application programming interface (API) instead of the page layer. The legal access tiers are set out on Annex XIII Data Requirements.

Data class Typical content Control
Public Required public fields and general model information Open access; consistent availability
Restricted Detailed composition, sensitive supply chain and internal quality data Role-based access, logging, confidentiality controls
Update-authorized Lifecycle event fields written by service, reuse or EOL actors Strong authentication, defined responsibilities, audit log

Field definitions, units, permissible values and versioning rules that let these actors exchange data are covered on Registries & Schemas.


Related Coverage

Disclaimer. Informational guidance only. Not legal advice. Validate requirements against official regulation text and implementing acts.