EU DPP Registry Launches 20 July 2026: What the European Commission Just Confirmed

What Changed in July 2026

In short: the European Commission launched the DPP Registry, together with a testing environment, on 20 July 2026. That is one day after 19 July 2026, the date this site and others had tracked since the ESPR was published, which was the deadline Article 13(1) of the ESPR set for the Commission to set up the registry, not an announced 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. The Commission launched the Registry one day later: its news item dated 20 July 2026 states, “Today, the European Commission launches the Digital Product Passport Registry together with a testing environment.”

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 launched the Registry portal itself, and 6 August is when the implementing regulation governing how it operates is legally in force. This post corrected our earlier coverage 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 DPP Registry page, checked on 26 September 2026, the Registry stores “the unique identifiers, registration data, and high-level metadata for each product, rather than the full detailed product information contained in the DPP itself.” 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 matches the architecture set out elsewhere in the ESPR: recital 41 says the digital product passport should be “based on a decentralised data system”, and Article 11, point (c), requires it to be stored by the economic operator responsible for its creation or by digital product passport service providers. Product data therefore remains the responsibility of the economic operator, while the Registry set up under Article 13 provides the common EU-level index that ties a product identifier to where its passport data actually lives.

Registration Becomes a Market-Access Requirement Once a Product’s DPP Rules Apply

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 list of verified DPP service providers registered in the Registry, 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. A sole trader required to be established in the EU proves its identity with a qualified electronic signature under Regulation (EU) No 910/2014 (eIDAS), an electronic identification means at assurance level “high”, or an electronic attestation of attributes issued under Union law. A legal person required to be established in the EU proves its identity and establishment with a qualified electronic seal supported by a qualified certificate issued by a qualified trust service provider, or with a qualified electronic attestation of attributes; operators not required to be established in the EU use the options in Article 4(1)(b) and 4(2)(b). Verified status lasts until the underlying electronic identification means expires, and never longer than three years, after which the operator must re-verify before it can register or modify anything. Value chain actors, such as repairers, refurbishers, remanufacturers and recyclers, go through equivalent verification under Article 5, and only verified value chain actors have access to the registry.

Once registration is submitted, Article 8(7) requires the Commission to automatically confirm the passport’s semantic conformity with the applicable delegated act or other Union law, its conformity with the required granularity level (model, batch, or item) and, where relevant, the coherence of the mandatory data, the validity of the commodity code, and the link to the back-up copy hosted by a digital product passport service provider. 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 launched a Testing Environment alongside the live Registry on 20 July 2026, described on its DPP Registry page 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 first confirmed, binding DPP deadline 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. Other Union laws outside the ESPR already fix later dates: 23 September 2029 for detergents and end-user surfactants under Regulation (EU) 2026/405 (Articles 21 and 37), and 1 August 2030 for toys under Regulation (EU) 2025/2509. Under Article 7 of the Implementing Regulation, 18 February 2027 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. As of 26 September 2026, however, the DPP Registry User Guide for Economic Operators states that successful registration of battery DPPs is not yet available, because the semantic catalogue for batteries has not yet been defined. 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, and the Registry has been live since 20 July 2026, well ahead of them.

What to Do to Prepare for Registration

In short: the Registry and its testing environment have been open since 20 July 2026, and four concrete steps are worth taking before your first registration obligation applies.

• Work out how your organisation will complete eIDAS identity verification. The DPP Registry User Guide for Economic Operators describes one route: the Commission seals a PDF enrolment declaration, which your organisation then countersigns with a qualified electronic signature or seals with a qualified electronic seal from a qualified trust service provider. Article 4 of Implementing Regulation (EU) 2026/1778 also accepts other means, such as an electronic attestation of attributes issued under Union law. Verification makes you a “verified economic operator” able to register DPPs. Plan for it now, since verified status lasts no longer than three years and has to be renewed.
• Set up a separate EU Login account for the Testing Environment, as the Commission’s DPP Registry page instructs, so you can explore DPP features and workflows without affecting live data.
• Confirm your DPP platform or service provider can issue the Unique Product Identifier the Registry requires: the DPP Registry User Guide for Economic Operators specifies a URL-based identifier “conforming to a URL format compliant with JTC 24 standards”.
• 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.