Home > Implementation > Battery Passport Data Storage & Hosting
Battery Passport Data Storage & Hosting
A Battery Passport record lives in back-end systems run by or for the economic operator, and the platform retrieves it at the time of each scan. Storage and hosting decide whether the record is available on request, complete, and provable for the life of the battery under Regulation (EU) 2023/1542. What the QR code itself carries is covered on QR Codes & Architecture.
What happens after a scan
| Step | What happens |
|---|---|
| 1. Resolve | The scanned URL reaches a resolver that identifies the unit |
| 2. Authorize | The platform applies access rules for public and restricted fields |
| 3. Retrieve | The system reads the record and its evidence links from storage |
| 4. Render | A web page or application programming interface (API) response is returned |
| 5. Log | Access and changes are written to the audit log |
Storage models
Most implementations keep passport fields in a central database and store evidence files and immutable logs separately. Some programs add multi-actor updates through signed data claims.
| Storage model | How it works | Strengths and limits |
|---|---|---|
| Central database | Passport fields in a cloud database, served by a web app and API | Simplest and fastest to build; the operator is the single trust anchor and uptime is critical |
| Central database plus immutable audit log | Database holds current state; append-only log holds every change and event | Supports audits and disputes; more engineering and retention management |
| Registry plus evidence library | Key fields in the database; evidence files in object storage with immutable links | Handles large artifacts; drifts into PDF sprawl unless key fields stay structured |
| Multi-actor signed claims | Suppliers, service providers and recyclers submit signed data; the platform verifies and displays it | Clear confidentiality boundaries; integration, identity and signature validation add complexity |
| Ledger or blockchain pointers | Hashes or pointers are tamper-evident; full data stays off-chain | Tamper evidence for references; rarely required, with privacy, cost and governance overhead |
Current state and audit history
Store history as well as current values, because regulators and customers ask who changed a record, when, and why. Keep two layers:
- Current state record - the latest approved model and unit values, which most users see.
- Event history log - an append-only timeline of changes and lifecycle events, which proves compliance and responsibility.
Each audit log entry, kept per unit and per model revision, should capture:
- Actor identity - the user or system, with its role.
- Timestamp - immutable, under a stated time zone policy.
- Change delta - before and after values, field by field.
- Event type - from a controlled list, with notes, so the change ties to a lifecycle activity.
- Evidence link - an immutable link to the supporting document or record.
Evidence storage and retention
Test reports, supplier declarations, calculations, certificates and change records usually sit outside the main database as files linked from the structured record. Evidence that can be overwritten or deleted without trace leaves the passport record exposed in an audit.
| Evidence control | Recommended practice |
|---|---|
| Immutable storage | Write-once or versioned object storage |
| Versioning | Keep prior versions linked to effective dates |
| Retention policy | Define how long records and evidence are kept |
| Legal hold | Block deletion during investigations or litigation |
Locking and archiving the record after end of life is covered under data closure on Battery Passport Lifecycle.
Availability and continuity
A record that an authority or customer cannot reach at the time of inspection is a compliance failure. Run uptime, backups and disaster recovery as controlled operational processes, with high availability for the resolver endpoint, monitoring, incident response and tested restores.
| Availability risk | What it looks like | Control |
|---|---|---|
| Resolver downtime | Scans fail and the record cannot be reached | High-availability hosting, monitoring, rollback plan |
| Data store outage | The page loads but data is missing | Redundancy, backups, restore testing |
| Permissions outage | Authorized users are blocked from required fields | Role regression tests and staged releases of access rules |
| Data loss | History is lost and past updates cannot be defended | Backups, immutable logs, restore tests |
Hosting providers and responsibility
No hosting provider, cloud platform or software vendor is designated by regulation as an approved Battery Passport solution. Cloud infrastructure, product lifecycle management (PLM) systems and digital twin tools can host or process passport data, but the economic operator keeps legal responsibility for its accuracy and availability. Official schemas, registries and recognized service providers are covered on Registries & Schemas, and system selection on Battery Passport Software.
Related Coverage
- Battery Passport QR Codes & Architecture
- Battery Passport Registries & Schemas
- Battery Passport Audits & Surveillance
Disclaimer. Informational guidance only. Not legal advice. Validate requirements against official regulation text and implementing acts.