The Ecodesign for Sustainable Products Regulation (EU) 2024/1781 entered into force on 18 July 2024. It is a framework regulation: it does not regulate products directly, but empowers the Commission to issue product-specific delegated acts, most of which will require a digital product passport.
That distinction matters more than any deadline. Today batteries have a real passport obligation (18 February 2027, under their own regulation) and packaging has a digital EPR identifier obligation from 12 February 2027 under the PPWR. Every other sector is waiting on its delegated act — the first of them, textiles, is planned for adoption in Q4 2027, with the obligation following at least 18 months later.
The ESPR also mandates the central EU DPP Registry (Articles 12–13). That registry went live on 20 July 2026 and its implementing regulation, (EU) 2026/1778, took effect on 6 August 2026. You can enrol and be verified today; registering passports is not yet possible, because the semantic catalogue is still being defined.
We would rather tell you that than sell you urgency you do not have. But “not yet” is a reason to begin calmly, not a reason to postpone: every part of this that takes real time is independent of the delegated act. Enrolling as a verified economic operator and obtaining a qualified seal can be done now and has a queue. So does getting supplier data into a usable shape.
The companies that will struggle are the ones who treat the act's publication as the start signal. Collect the data gradually, sector by sector, and leave nothing to chance in the last six months.
Battery, textile, tyre, furniture, packaging, electronics, construction, chemicals, toys, machinery, vehicles, cosmetics, food, medical devices and intermediate products — each with regulation-grounded fields.
Identifier-agnostic carriers, QR and DataMatrix, JSON-LD data and a versioned API — the EN 18216, 18219–18223, 18239, 18246 baseline, not a proprietary schema.
Issue passports as W3C Verifiable Credentials (Ed25519), verifiable offline against a public key. No blockchain.
The identifiers the Registry asks for are captured for every product, so registration is a click once the catalogue opens.
An in-dashboard assistant grounded in the regulations, with a weekly EUR-Lex watch so your passports keep pace with the law.
Everything exports as CSV and JSON-LD, your passports are URLs you own, and our schemas and OpenAPI spec are public and MIT-licensed. Leaving should cost you a migration, not your identifiers.
A fully populated EV battery passport — materials, substances, carbon class, documents and a verifiable credential.
Almost certainly not. The ESPR is a framework: it empowers the Commission to set product rules through delegated acts, and only a few exist. Today the real obligations are batteries from 18 February 2027 under their own regulation, and a digital EPR identifier on packaging from 12 February 2027 under the PPWR. Everything else is waiting on its act.
You can enrol your organisation and be verified, and that is worth starting now because the qualified seal it requires has a lead time. Registering passports is another matter: only batteries are offered, and even there the submission cannot complete until the semantic catalogue is defined.
No. EN 18219 recognises five identifier schemes and the ESPR names none of them. GS1 Digital Link is the sensible default for consumer goods that already carry GTINs; intermediate and B2B products often cannot use a GTIN at all.
The qualified electronic seal — not the product data and not the platform. A certificate delivered as a .p12 file produces only an advanced signature and is rejected, and Adobe's default signing format is not PAdES-compliant. Both are avoidable if you know in advance — and dpp.gs is an authorised reseller of the seal, so you can take that whole step through us.
No, and nobody is: the six EN 18216 and 18219–18223 standards were published in May 2026 and cited in the Official Journal, the two security standards EN 18239 and EN 18246 followed on 16 September 2026, and no certification scheme exists for any of them yet. We are built on the same open standards the series rests on, and we would rather say that than imply a certificate we do not hold.
Passports are URLs you own, data exports as CSV and JSON-LD, and our schemas and OpenAPI spec are public and MIT-licensed. Leaving should cost you a migration, not your identifiers.
One platform, 15 sectors, built on the EU standards — and it says plainly which of them obliges you today.