What Actually Changed Today
In short: the European Commission’s own DPP Registry page now confirms a firm go-live date, 20 July 2026, for the Registry, its testing environment, and the User Guidelines. That corrects the 19 July 2026 date this site and others have tracked since the ESPR was published, which was only ever the Commission’s internal Article 13 set-up deadline, not a confirmed public launch date.
Article 13(1) of the Ecodesign for Sustainable Products Regulation (ESPR, Regulation (EU) 2024/1781) required the Commission to set up the EU Central Digital Product Passport Registry by 19 July 2026. That was always a legal deadline for the Commission to act by, not a published launch date, and the Commission has now published its own launch date, one day later, directly on the Registry’s official page: “The Registry, the testing environment and the User Guidelines will be live as of 20/07.”
There is a third date in play, and it matters for anyone citing this precisely. The Commission also adopted Implementing Regulation (EU) 2026/1778 on 16 July 2026, the act that actually lays down how the Registry works: verification, registration, logging, availability. It was published in the Official Journal on 17 July 2026 and, under its own Article 24, enters into force on the twentieth day after publication, which is 6 August 2026. So three dates now exist for three different things. 19 July is the ESPR Article 13(1) set-up deadline, 20 July is when the Commission says the Registry portal itself becomes usable, and 6 August is when the implementing regulation governing how it operates is legally in force. We’re correcting our earlier coverage today to keep those three separate.
What the Registry Actually Stores
In short: the Registry is a directory, not a data warehouse. It stores unique identifiers and registration data, not the full contents of your Digital Product Passport.
Per the Commission’s own description, the Registry “does not store the complete product information contained in a DPP.” It stores at least unique identifiers and registration data. Depending on the applicable delegated act or other EU legislation for a given product category, additional information may also be required in the Registry, but the detailed product data itself is not centrally warehoused there.
This confirms the architecture already described in Article 13: the DPP itself follows a decentralised model. Product data remains the responsibility of the economic operator, who hosts it directly or through a DPP service provider, while the Registry provides the common EU-level index that ties a product identifier to where its passport data actually lives.
Registration Is Now a Real Market-Access Requirement
In short: before a covered product can be placed on the EU market, the economic operator must register its DPP in the Registry. The Commission’s page states this directly, not as a future intention.
The Commission’s language is explicit: “Before a product can be placed on the EU market, the relevant economic operator must register its DPP in the Registry in accordance with the applicable legislation.” That ties Registry registration directly to market access, not just to good practice.
The Registry also underpins two enforcement functions. Customs authorities can verify electronically that an imported product has a valid registered DPP and that the correct commodity code has been provided, before the product is released for free circulation. Market surveillance authorities get facilitated access to registered DPPs for their own enforcement purposes. Both of these depend on a product’s DPP already being registered, which is the practical reason registration is framed as a market-access condition, not an optional step.
How Registration Actually Works, Per the Implementing Regulation
In short: Implementing Regulation (EU) 2026/1778 spells out the mechanics the Commission’s page only summarises: how you get “verified” status, what happens when you submit a passport, and what proof you get back.
Under Article 3 of the Implementing Regulation, the Registry consists of nine components: a secure website interface, an API for registration and data retrieval, a verification platform, a scheme for generating unique registration identifiers, a storage component for identifiers and customs commodity codes, a public list of verified DPP service providers, a semantic repository, a log system, and identification and authorisation schemes for users.
Before an economic operator can register anything, it must become a “verified economic operator” under Article 4. For a sole trader established in the EU, that means proving identity with a qualified electronic signature under the eIDAS Regulation (EU 910/2014) or an equivalent high-assurance electronic ID. For a legal entity, it means proving identity and establishment with a qualified electronic seal from a qualified trust service provider. Verified status lasts until the underlying electronic ID expires, and never longer than three years, after which the operator must re-verify before it can register or modify anything. Value chain actors, meaning repairers, refurbishers, remanufacturers, and recyclers, go through the same verification under Article 5 before they get any access at all.
Once registration is submitted, Article 8 requires the Commission to automatically check the passport’s semantic conformity against the applicable delegated act, the coherence of the mandatory data, the correct granularity level (model, batch, or item), the validity of the commodity code, and the link to the manufacturer’s hosted passport data. Only after that automated check passes does the Registry generate a unique registration identifier. Note what this verification does not cover: Recital 16 is explicit that automated checks are not proof of substantive compliance with the underlying product rules. That remains a market surveillance function.
Article 9 then gives the registering operator the right to generate a downloadable “proof of registration” at any time: a secure electronic document, sealed with a qualified electronic seal and Commission timestamp, that stays available for 90 calendar days from generation and can be regenerated as needed.
The Testing Environment
In short: a separate sandbox lets you test DPP registration workflows without touching live data, using its own EU Login test account.
The Commission is launching a Testing Environment alongside the live Registry on 20 July, described as a way to “explore DPP features and workflows in a safe test environment, without affecting live data or real processes.” Getting started requires creating a separate EU Login account specifically for testing, distinct from whatever EU Login credentials your organisation may already use for other Commission systems.
The User Guide for Economic Operators
In short: the guide covers the two things every economic operator will actually need to do, enrolling your organisation, and registering and managing your DPPs.
The DPP Registry User Guide for Economic Operators is scoped to two core functions: enrolling an organisation, and registering Digital Product Passports and managing DPP registrations. This is the practical, step-by-step reference for the actual registration workflow, rather than the legal or architectural detail already covered in the ESPR text itself.
How This Fits the Bigger ESPR Timeline
In short: the Registry going live on 20 July is infrastructure becoming available. It lands ahead of the first product category with a confirmed mandatory DPP deadline, which is batteries.
The Registry is one element of the broader DPP architecture under the ESPR. It does not, by itself, create a registration deadline for every product category simultaneously. Product-specific obligations to issue and register a Digital Product Passport come from delegated acts adopted under Article 4 of the ESPR, each on its own timeline.
The one confirmed, binding DPP deadline that currently exists is separate from the ESPR: battery passports become mandatory on 18 February 2027 under Article 77 of the EU Battery Regulation (EU) 2023/1542, covering industrial batteries above 2 kWh, EV batteries, and light means of transport (LMT) batteries. Under Article 7 of the Implementing Regulation, that same 18 February 2027 date is also the deadline for every EU Member State to appoint the “designated national administrator” who manages that country’s Registry access rights for market surveillance and customs authorities, so the registry’s national-access infrastructure and the first mandatory product deadline land on the same day. The ESPR’s own delegated acts for other categories, including textiles and electronics, are still working through adoption on their own schedules and are not yet finalised. The Registry launching now means the shared infrastructure will already be operational and tested by the time those category-specific deadlines start to land.
What to Do Before 20 July
In short: there are four concrete things worth doing in the next few days, none of which require waiting for the Registry to actually open.
- Work out how your organisation will complete eIDAS identity verification: a qualified electronic signature for a sole trader, or a qualified electronic seal from a qualified trust service provider for a legal entity. This is what Article 4 of Implementing Regulation (EU) 2026/1778 requires to become a “verified economic operator” able to register DPPs. Plan for it now, since verified status is only valid for up to three years and has to be renewed.
- Set up a separate EU Login test account now, so you’re not blocked from the Testing Environment on day one.
- Confirm your DPP platform or service provider supports GS1 Digital Link-based identifiers, since that’s the standard the Registry is built around.
- Bookmark the User Guide and Help Desk contact (EC-HELPDESK-DPP@ec.europa.eu, +32 2 296 0431, 08:00 to 20:00 CET) for when questions come up during testing.
For the full legal detail behind registration and verification, see Commission Implementing Regulation (EU) 2026/1778 on EUR-Lex, or our plain-language walkthrough of the DPP Registry Implementing Regulation. To see how a battery passport connects to this registry infrastructure in practice, explore the battery passport pilot program.
