The pointer
- Unique passport identifier
- Your Operator ID
- Pointer to passport data (URL)
- Registration status
EU registry submission pipeline · operator view
| Timestamp | Packet ID | Passport | Status |
|---|---|---|---|
| 2026-05-10 14:02:11.05Z | EU-DPP-2026-7K2P-441 | EV-2027-A1245 | Verified |
| 2026-05-10 14:02:10.88Z | EU-DPP-2026-7K2N-440 | IND-2027-B0942 | Verified |
| 2026-05-10 14:02:09.12Z | EU-DPP-2026-7K2L-438 | LMT-2027-E2104 | Processing |
| 2026-05-10 14:02:08.55Z | EU-DPP-2026-7K2J-435 | EV-2027-A1239 | Verified |
| 2026-05-10 14:02:07.21Z | EU-DPP-2026-7K2H-432 | IND-2027-B0938 | Rejected |
Field carbon_footprint_intensity missing for 2 EV passports submitted at 14:02:08Z.
From 18 February 2027, every EV, Industrial, and LMT battery placed on the EU market must have a Digital Product Passport registered with the European Commission. You create the passport, you authorise submission, and the platform files it to the registry on your instruction.
The registry does not store the full passport data — it stores references. We host the data; the registry holds the pointer. When customs officers scan the QR code, they query the registry which directs them to the live passport data.
The full lifecycle of a single submission. Steps 02 onward are handled by us automatically — you create the passport in step 01 and watch it move through the rest.
Enter all Annex XIII fields in EU Digital Passport Processor. Validate completeness before submission.
The platform submits to the EU registry on your instruction, using your Operator ID as the authorising credential.
The Commission checks Annex XIII completeness and schema compliance.
A unique Registry ID is assigned to your passport and stored in EU Digital Passport Processor.
Your battery is cleared for EU customs. QR scan at any port confirms registration.
Each passport is checked against the registration requirements — Operator ID, an active public passport, a resolvable GS1 Digital Link and the mandatory Annex XIII fields — and any gap is named in plain language before you submit.
Every attempt is recorded — schema version, payload content hash, registry response and outcome — so what you filed and when is one export away.
The EU DPP Registry became operational on 20 July 2026, with a testing environment alongside it. Until we have completed onboarding and verified conformance with the published specification, filings carry a placeholder reference. On cutover, every active passport is resubmitted to carry a real one — oldest first, once each, never double-filed.
The registry Implementing Regulation requires every DPP submission to carry a qualified electronic seal from a QTSP on an EU Trusted List, and rejects submissions without one automatically. Our submission pipeline is built with that sealing step in place. Qualified seal certificates will be procured from an EU Trusted List QTSP ahead of live registry onboarding; we do not hold one today, and no submission is sealed yet.
Source: Implementing Regulation (EU) 2026/1778, adopted 16 July 2026 (OJ 17.7.2026, in force 6 August 2026). Requirement carried from the draft text, pending our review of the adopted annex.
Every economic operator placing batteries on the EU market registers once with the Commission to receive an Operator ID. You enter that ID once in your Settings, and every submission you authorise is then filed under it as your authorising credential.
One Operator ID covers all manufacturer clients you represent. Our AR account type is built for this — manage passports for multiple manufacturers under a single account. The AR client picker in the wizard ties each passport to the correct end client at submission time.
The registry performs validation checks. If rejected, we show the specific field that failed and guidance on how to fix it. Correct the data and resubmit — there is no penalty for rejected submissions, only for not having a registered passport when batteries are on the market.
The most common rejection reason. EU Digital Passport Processor prevents this with full Annex XIII validation before you submit.
The passport number is already registered by another operator. Use a unique passport number.
Your EU Registry Operator ID has not been activated. Register with the Commission first, then add your ID to Settings.
The passport was created against an outdated Annex XIII version. EU Digital Passport Processor tracks schema updates automatically.
EU Battery Regulation 2023/1542 establishes a certification scheme for DPP Service Providers under Article 2(32) ESPR via delegated act. The scheme has not yet been adopted by the European Commission. Our technical and operational practices are designed to align with the expected requirements of the anticipated scheme. We make no claim of certification at this time.
You need to register with the European Commission to obtain an Operator ID — this is a one-time step you do directly with the Commission. Once you have your ID, enter it in EU Digital Passport Processor and we handle all registry submissions on your behalf.
A DPP Service Provider is a company like EU Digital Passport Processor that hosts battery passport data and submits to the registry on behalf of economic operators. The European Commission is establishing a certification scheme for providers under Article 2(32) ESPR; the scheme has not yet been adopted by the Commission.
The EU DPP Registry became operational on 20 July 2026, but EU Digital Passport Processor remains in mock-submission mode until we have completed registry onboarding and verified conformance with the published specification. Your passport data is fully stored and compliant with Annex XIII. When you click Submit, a mock submission is created. At cutover, EU Digital Passport Processor moves to live submission and resubmits your active passports — no action required from you.
Yes — the registry will provide a direct submission API. However, this requires your own integration, schema validation, error handling, and polling logic. EU Digital Passport Processor handles all of this automatically, including status tracking and error-resolution guidance.
EU market surveillance authorities can take enforcement action including product withdrawal, fines, and customs holds. The penalty framework varies by member state but non-compliance is a significant commercial and regulatory risk.
The EU DPP Registry became operational on 20 July 2026 with a testing environment, but its production validation timings are not yet something we can quote from experience. EU Digital Passport Processor's mock mode simulates a validation window of approximately 90 seconds for testing purposes. Once we are live, EU Digital Passport Processor polls for status updates automatically every 5 minutes.
Before any passport can be registered, the operator behind it must be verified in the Commission's DPP Registry — the one step no platform can do for you. Our step-by-step walk-through covers the qualified electronic seal, the identifier format, and the failure modes to avoid, based on our own verification in the registry's acceptance environment.
What changed in EU battery and product-passport regulation, what it means for operators, and the dates ahead.
Demo accounts are available on request. Get set up so your team has time to walk through an end-to-end Annex XIII passport well before the deadline.