dpp.cloud logo
HomeComplianceIntegrationPricing
Resources
BlogFAQ
Company
About usPartnerContact
Schedule a Call
EN
DE

Menu

  • Home
  • Compliance
  • how it works?
  • Pricing Plan
  • Partner
  • Blog
  • About
  • Faq
  • Contact
Schedule a call
GS1 solution partner - Sqanit

How to Register a Digital Product Passport in the EU Registry: Implementing Regulation 2026/1778 Step by Step

October 21, 2026
Julian Sotek
/
ESPR & EU Regulations

Short answer: Before you can register a Digital Product Passport in the EU registry, your company has to become a "verified economic operator" through an eIDAS identity check, usually with a qualified electronic seal. After that you register each passport through the registry website or its API, at the level your product law requires: model, batch or item. The registry checks the entry automatically and sends back a unique registration identifier and a sealed proof of registration. The rules come from Implementing Regulation (EU) 2026/1778, which entered into force on 6 August 2026. The first products that must be registered are batteries, from 18 February 2027.

What does the EU DPP registry store?

The registry doesn't store your passport; that data stays with you or your DPP service provider. What the registry holds is identifiers and links: which product identifier belongs to which operator, which commodity code applies, and where the passport and its backup copy can be found. Customs and market surveillance use it to check whether a product has a passport. We wrote about the launch on 20 July 2026 in the EU registry is live. This article is about the rules that have applied since.

Which products have to be registered?

Regulation 2026/1778 covers every product for which EU law requires a DPP and its registration:

  • Batteries with a passport under Regulation (EU) 2023/1542: EV, LMT and industrial batteries above 2 kWh (from 18 February 2027, see our battery passport guide)
  • Products covered by future ESPR delegated acts, such as steel, textiles, tyres and furniture
  • Construction products, toys, and detergents and surfactants under their own regulations

Step 1: become a verified economic operator

Under Article 4, an economic operator has to prove its identity through eIDAS before it can register anything. Article 5 sets up a comparable verification for value chain actors such as repairers, refurbishers and recyclers. The accepted means depend on who you are:

Type of operatorAccepted means
Company established in the EUQualified electronic seal or qualified electronic attestation of attributes
Company outside the EUQualified electronic seal or electronic attestation of attributes
Sole trader in the EUQualified electronic signature, eID at assurance level high, or electronic attestation of attributes
Sole trader outside the EUQualified electronic signature or electronic attestation of attributes

Two details are worth knowing. Your verified status expires when your eIDAS credential does, and after three years at the latest, so put the renewal in the calendar. If your company is already verified in a comparable EU system, such as EPREL for energy labelling, you don't have to go through the check again.

Getting a qualified electronic seal from a trust service provider can take a few weeks. If you place batteries on the market, get started now.

Step 2: register the passport

You submit through the registry website or its API (Article 8). The registration follows the granularity your product law sets: model, batch or item. For batteries that means each individual battery. Through the website you fill in an online form for a single passport or upload a JSON or XML file. For automated registration, the API accepts 1 to 100 passports per call and returns a task ID; the result is read in the activity dashboard. If one passport in a submission is non-compliant, none of them is registered. The upload file carries the registration data; the passport itself must be reachable at its product identifier URL when you submit, and the registry requests it in JSON. Official JSON schemas exist so far only for batteries, and the published registry API (v1.0.0) so far specifies only the battery product group.

The registry then runs automated checks:

  • Does the data structure match the semantic model for the product group?
  • Is the granularity the one the law requires?
  • Are the mandatory data coherent, where this applies?
  • Is the commodity code valid?
  • Is there a link to a backup copy held by a DPP service provider?

Recital 16 makes clear that passing these checks doesn't prove compliance. A passport can go through registration and still be incomplete or wrong, and that stays your responsibility.

Step 3: what you get back

After a successful submission, the registry issues a unique, persistent registration identifier. You can also download a proof of registration (Article 9) with the product identifier, commodity code, your identity, date and time, a cryptographic hash of the passport version and the Commission's qualified electronic seal and time stamp. The proof stays downloadable for 90 days and can be generated again later.

Can a DPP provider register passports for you?

A third party, such as your DPP provider, may act in the registry on your behalf where Union law provides for this, but only after completing its own verification (Article 19(4)). You stay fully liable for what it submits. If the company changes owners, merges or stops trading, registered passports can be transferred to another verified operator.

Registration data is deleted automatically after 10 years unless the product law sets another period. Member states have to name a national administrator for the registry by 18 February 2027.

A quick checklist

  1. Order a qualified electronic seal for your company, or check whether you're already verified via EPREL.
  2. Decide who registers: your own team through the web interface, or, where the applicable product law permits third-party registration, your DPP provider through the API.
  3. If your provider registers for you, confirm that it has completed its own registry verification and agree the liability terms in writing.
  4. Make sure your passports use identifiers that follow EN 18219 and data carriers that follow EN 18220 (see the harmonised standards).
  5. Keep a back-up copy of each passport with an independent DPP service provider (ESPR Art. 10(4)) and make sure you can supply the link the registry asks for.

"Registering itself is quick. What takes time is getting the qualified seal and deciding who in the company is responsible. Those aren't technical questions, which is why they tend to get pushed back."

Christian Hieronimi, CEO, dpp.cloud

How dpp.cloud fits

dpp.cloud generates the passport from your PIM or ERP data, at the level your product law requires and with persistent identifiers the registry can index. In a strategy session we work through the registry side with you: who registers (your team or a verified provider) and what that means for liability and the backup copy. If you're still deciding between an internal project and a platform, read our build-vs-buy comparison or book a strategy session.

Sources

  • Commission Implementing Regulation (EU) 2026/1778, EUR-Lex: eur-lex.europa.eu
  • European Commission, the Digital Product Passport Registry is now live (20 July 2026): single-market-economy.ec.europa.eu/news
  • Regulation (EU) 2024/1781 (ESPR), EUR-Lex: eur-lex.europa.eu/eli/reg/2024/1781/oj

FAQ

How do I register a Digital Product Passport in the EU registry?

First, your company becomes a verified economic operator through an eIDAS identity check, for companies usually a qualified electronic seal. Then you submit each passport through the registry website or API. The registry runs automated checks and returns a unique registration identifier and a proof of registration.

What is Implementing Regulation (EU) 2026/1778?

It is the Commission regulation that sets the rules for the EU Digital Product Passport registry: identity verification, registration, automated checks, proof of registration, data retention and logging. It was adopted on 16 July 2026 and entered into force on 6 August 2026.

Does the EU registry store my product data?

No. The registry stores identifiers, commodity codes and links. The passport data itself stays with the economic operator or its DPP service provider, and a back-up copy sits with an independent DPP service provider.

Can my DPP provider register passports for me?

Yes, where Union law provides for it and once the provider has completed its own verification under Article 19(4). The company placing the product on the market remains fully liable for the data submitted on its behalf.

Is registration in the registry proof of compliance?

No. Recital 16 of Regulation 2026/1778 states that the registry's automated checks cover structure and completeness only and are not proof of compliance with the product rules.

Julian Sotek

Founders Associate, sqanit

Related Posts

Digital Product Passport with entitys: From PIM and DAM Data to a Compliant DPP in Weeks, Not Months
entitys already lists dpp.cloud as a native integration on its own partner page. Here's what that means in practice for manufacturers running entitys as their PIM: what maps directly, how the DAM adds extra assets, and what a first project looks like.
Simon Manz
Simon Manz
August 5, 2026
DPP Registry API Guidelines of 30 October 2026: Registration, Service Accounts and the Battery Passport
On 30 October the Commission published the technical documentation for the EU DPP registry API: batch submission, service accounts and protected data. We go through it, together with the battery guidance V3.2 of 19 October, and list what to do before February 2027.
Julian Sotek
Julian Sotek
November 13, 2026
Osapiens Alternatives 2026: 10 DPP Platforms When You Need a Passport, Not an ESG Suite
Osapiens makes sense when a corporation consolidates CSRD, supply chain due diligence, and DPP into one platform. When the actual job is compliant passports for your catalog, focused alternatives cost a fraction and go live in weeks. Ten options compared, with the three-year TCO math.
Julian Sotek
Julian Sotek
August 31, 2026
sqanit Is Now an Official GS1 Germany Solution Partner - What This Means for DPP Customers?
sqanit is now an official GS1 Germany Solution Partner, meaning every sqanit code carries the world's most trusted product identification standard, structurally aligned with EU Digital Product Passport requirements. Existing customers get full GS1 backing immediately, with zero migration required.
Benedikt Biallowons
Benedikt Biallowons
March 11, 2026
Digital Product Passport with Akeneo: From PIM Attributes to Compliant DPP in 3 Weeks
Your Akeneo attributes already cover most of what ESPR requires. This guide shows the exact mapping, a real 3-week project timeline, typical data gaps, and what the integration costs.
Julian Sotek
Julian Sotek
July 16, 2026

Browse by Category

Platform comparisons
Implementation & Integration
Business Case & ROI
Industry-Deep-Dives
Company News
ESPR & EU Regulations
DPP Fundamentals

Browse by Authors

Sebastian Eberhardt
Julian Sotek
Benedikt Biallowons
Christian Hieronimi
Dinesh Parmar
Lisa Fauland
Simon Manz
Leopold Holverscheid
dpp.cloudsqanit.com
Create your digital product passports in no time and with minimal effort.
Member of Digital Product Passport ProMEMBERDIGITAL-PRODUCT-PASSPORT.PRO
Google walletGoogle payFORRESTER
Contact us
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
    HomeComplianceBlogPricingIntegrationPartner
        About UsFAQVisit sqanitContact usLegal
          © 2025 sqanit GmbH – All rights reserved.
          ‍