The EU Digital Product Passport (DPP) Registry: What It Is, Who Registers, and Its Real Status

The EU digital product passport registry, which the Commission calls the DPP Registry, is the central index of every Digital Product Passport (DPP). Before a covered product goes on the EU market, you register its identifiers there and get a unique registration identifier.

The duty sits with the operator placing the product on the market. The Commission launched the registry on 20 July 2026, and enrolment works. But its own user guide says no passport can be registered successfully yet. It matters if you make, import or sell products in the EU, or supply someone who does.

What is the digital product passport registry?

The digital product passport registry is a central database run by the European Commission under Article 13 of Regulation (EU) 2024/1781 (ESPR) and Implementing Regulation (EU) 2026/1778. It stores each product's unique identifiers, the commodity code for imported goods and registration data, and returns a unique registration identifier. The passport itself stays with the operator or its service provider.

Think of it as an index, not a warehouse. The ESPR required the Commission to set it up by 19 July 2026, storing "at least the unique identifiers". Below, "the implementing regulation" means Regulation (EU) 2026/1778, and "ESPR" marks articles of Regulation (EU) 2024/1781.

Access goes to the Commission, national authorities and customs (ESPR Article 13(6)). Verified operators get access to register their own passports and keep that data accurate (implementing regulation, Articles 4(3) and 19(2)).

The public tool for searching passports is a separate web portal under ESPR Article 14. It has not launched; the Commission says only "in the coming years".

What does the registry store, and what stays with you?

The digital product passport registry keeps a short list of fields. The passport itself stays with you.

The unique product identifier is yours. The ESPR defines it as a unique string that identifies the product and "enables a web link" to its passport. So the registry takes it as a URL that complies with the CEN-CENELEC JTC 24 standards. EN 18219 on unique identifiers is one of six passport standards cited in Implementing Decision (EU) 2026/1736.

The unique registration identifier is the registry's. After a successful upload, the registry sends it back automatically. The user guide abbreviates it as "URI", which collides with the web term. Store both strings for every passport.

The commodity code is your tariff classification. ESPR Annex III cites the TARIC code as an example. The registry's required code format has not been published.

Who registers in the digital product passport registry, and when?

Under ESPR Article 13(4), the operator placing the product on the market or putting it into service uploads the data. The Commission's registry page puts registration before a product is placed on the EU market.

Batteries arrive through a different law. ESPR Article 78 amended the Battery Regulation, whose Article 77(10) now sends battery identifiers to this registry. That is the first real obligation: from 18 February 2027, for LMT batteries (which power light vehicles such as e-bikes), industrial batteries above 2 kWh and electric-vehicle batteries (Battery Regulation Article 77(1)).

Only verified operators can register in the digital product passport registry. The law allows these routes (implementing regulation, Article 4):

• EU-established companies: a qualified electronic seal (QSeal), the company version of a qualified e-signature, or a qualified electronic attestation of attributes, which confirms company details digitally.
• Companies not required to be established in the EU: a QSeal from a qualified trust service provider (QTSP), a certificate issuer approved under the EU's eIDAS rules. An attestation of attributes issued under Union law also works.
• Sole traders: a qualified electronic signature (QES) or an attestation of attributes issued under Union law. EU-established sole traders may also use an eID at assurance level "high".

The user guide currently describes only the QSeal and QES route.

According to the Commission's battery FAQ, a non-EU operator responsible for the passport can enrol and register in the digital product passport registry once verified. The legal duty to upload stays with whoever places the product on the EU market (ESPR Article 13(4)). For battery passports, the same FAQ says the operator placing the battery on the EU market must register. See also the passport for non-EU manufacturers.

Where Union law allows it, a third party such as a service provider can register on your behalf (implementing regulation, Article 8(2)). It must itself be verified, and you "shall remain fully responsible" (implementing regulation, Article 19(4)). For ESPR products, the rules on passport service providers are still to come.

Is the digital product passport registry working yet?

Partly. The platform is up; registrations are not going through.

User Guide v1.03 puts it in one line: "Currently, it is not possible to successfully register DPPs." For batteries, the form currently offers item level only. No date has been published for when registrations will succeed. The two planned dates come from a Commission webinar on 30 September 2026, not from law.

So the digital product passport registry is "live" as a platform and for enrolment, not for completed registrations.

How do you register a product in the digital product passport registry?

The steps follow User Guide v1.03 and the implementing regulation (Articles 4, 8 and 9). Steps 1 to 5 work today.

1. Create an EU Login account. This is the Commission's sign-in service. The test environment needs a separate one.
2. Enrol your organisation. A company gives one identifier: NTR (national trade register number, preferred), LEI (Legal Entity Identifier, ISO 17442), VAT number, eID or a country-prefixed local identifier. Sole traders give a tax number (preferred), personal number, eID, ID card or passport number. It must fully match the attribute in your certificate.
3. Name your legal representative. The registry issues an EC-sealed PDF declaration, currently in English only.
4. Seal or sign it. A company uses a QSeal, a sole trader a QES. It must sit on a qualified device, such as a smart card or USB token, or come from a QTSP remote signing service. A certificate stored as a .p12 or .pfx file gives only an advanced signature and is rejected.
5. Track your verified status. It lasts until your electronic identification means expire, three years at most (implementing regulation, Article 4(4)).
6. Choose a route. The guide offers a web form for one passport and a JSON or XML file for up to 100 (1 GB maximum). The implementing regulation also provides for an API (Article 8(6)); its integration guidelines are still planned.
7. Supply each record. The guide's battery form asks for an https UPI that resolves to the hosted passport (mandatory), plus optional model and batch identifiers. The ESPR and the implementing regulation add the commodity code for imports and the back-up link where relevant; the form does not show these fields yet.
8. Collect the result. A successful request shows the UPI and the unique registration identifier.
9. Generate proof of registration when asked. It is sealed and time-stamped, carries the UPI, commodity code, registrant and a hash of the passport version, and stays downloadable for 90 days (implementing regulation, Article 9).

You choose how to build the UPI. The Commission's battery FAQ says operators can create identifiers locally under the relevant standards or use a commercial service.

A GS1 Digital Link URI is one way to build an https identifier from a GTIN, the GS1 product number. The Commission has not said the registry requires or prefers it; the guide says only "URL format compliant with JTC 24 standards".

To see one inside a QR code, try our free GS1 Digital Link QR generator: no signup, and it runs in your browser.

The digital product passport registry processes your URL during validation. The guide names "excessive URL redirects" and "redirects to a less secure protocol" as causes of failure. Keep any resolver chain short and on https.

How does the digital product passport registry connect to customs?

What you give customs. Anyone releasing a product for free circulation must give customs its registration identifier, from the moment the registry is operational (ESPR Article 15(1)). The duty covers only products under an ESPR delegated act, and none with passport rules applies yet, so today it catches no product.

What customs must check. Customs may release goods only after checking that the registration identifier and commodity code match the digital product passport registry. The check is electronic and automatic, and it starts once the interconnection exists (ESPR Article 15(2)).

When the automatic check starts. The registry is to be connected to EU CSW-CERTEX, the EU system that links national customs systems with other EU databases (Regulation (EU) 2022/2399). ESPR Article 15(3) allows four years from the implementing regulation's entry into force: by our calculation, 6 August 2030 at the latest. The Commission's FAQ expects it around 2029 (expected).

Batteries are the exception. The Commission's battery FAQ says their registration identifier "shall not be entered" into the customs declaration.

The commodity code is where the two systems meet. Where relevant, the digital product passport registry checks the code against a permitted range at registration (implementing regulation, Article 8(7)(d)), and customs will compare it at import. For the actors and the declaration steps, see digital product passports at EU customs.

Walkthrough: 36 batches, one file (hypothetical)

Take a hypothetical distributor in Valencia. It imports a product line once that line's ESPR delegated act applies, and the act sets batch-level passports. Twelve models, three batches each: 36 passports for the digital product passport registry.

1. Check status. It verified with a QSeal on a USB token, and its status is still valid.
2. Collect UPIs. The supplier hosts the passports. Each batch has its own https URL and links its model identifier.
3. Fix the codes. The customs broker confirms one commodity code per model.
4. Build one file. Thirty-six records fit in one JSON file, under the 100-record limit.
5. Submit. The dashboard shows SUCCESS with 36 registration identifiers.
6. Declare. The broker gives customs each identifier with the declaration, as ESPR Article 15(1) requires.
7. Answer the buyer. A retailer asks for evidence; the distributor generates the proof of registration.

Counterfactual one: a single bad row. Say one record carries a commodity code from the wrong chapter, outside the permitted range. Or one UPI starts with http://. Or a copied row repeats an identifier.

Per the user guide, one error rejects every passport in the submission. Thirty-five clean records fail with it, and the broker has no identifiers to declare. We found no published list of permitted ranges, so check each code against your own classification.

Counterfactual two: the wrong seal. Suppose the company had used a certificate stored as a .p12 file on a laptop. Verification fails, and an unverified operator registers nothing. Buying a token or remote service takes time, and that delay lands before the first shipment.

Edge cases: what if your situation is different?

One product, two laws. Register at the most granular level either law requires (implementing regulation, Article 8(3)).

A one-off product. The linking rules apply only "where batch and model design exist" (implementing regulation, Article 8(4)). With neither, there is nothing to link.

Verification expires. After three years at most, you cannot register in the digital product passport registry or change data until you verify again.

A merger or a sale. Registered passports can move to another verified operator, which takes over the obligations from the transfer date (implementing regulation, Article 6a).

The registry is down. If an outage of the digital product passport registry prevents registration, the Commission must record its date and time. It must make that record available to you on request for at least five years (implementing regulation, Article 15(4)). Keep your own evidence too.

You are a sole trader. You verify with a QES (the route the guide describes), and the registry also stores a personal identifier such as a tax number (implementing regulation, Article 18(2)).

Registration is not compliance. ESPR Article 13(5) says the confirmation is not proof of compliance. Registration data is deleted automatically 10 years after registration, unless EU law sets a passport availability period; then that period applies (implementing regulation, Article 10(3)).

Zoom out: one index for several product laws

The digital product passport registry is not only an ESPR tool. The implementing regulation also covers batteries, construction products (Regulation (EU) 2024/3110), toys (Regulation (EU) 2025/2509), detergents and end-user surfactants (Regulation (EU) 2026/405), and any future EU law that requires a registered passport.

Three systems sit side by side. The registry indexes identifiers for authorities and for the operators who register them. The semantic repository holds free, public data models and definitions, with documented APIs. The web portal is the future public window.

Every registration is checked for semantic conformity against those data models (implementing regulation, Article 8(7)). That is why the undefined battery semantic catalogue blocks registrations today.

One enrolment and one seal will therefore serve several product laws. For the framework, see our ESPR guide; for the first obligation, the battery passport.

What should you prepare now for the digital product passport registry?

None of this waits on the missing specifications.

• Buy the right seal: a QSeal on a qualified device or a QTSP remote service, not a .p12 file.
• Match your identifier on the enrolment form to your certificate exactly.
• Clean your product identifiers: one GTIN (or other identifier) per product model, with batch/lot or serial numbers added where your act requires batch- or item-level passports.
• Agree a commodity code per SKU with your customs broker.
• Host a resolvable https passport URL with a short redirect chain.
• Rehearse in the test environment. Verification there works as in production, so you need a real seal there too.
• Write down who registers in your supply contracts. For batteries, it is the operator placing them on the EU market.

The digital product passport registry is real, and its rules are adopted law. What is missing is the data model that lets a registration succeed. Enrol and verify now, and you will be waiting on the Commission, not on your own paperwork.

Further reading: What is a Digital Product Passport? · Digital product passports at EU customs · Battery passport · GS1 Digital Link

Related articles

Digital Product Passports at EU Customs: How Checks WorkESPR ties the digital product passport to import controls: declarants will give the registration identifier, customs will check it against the EU registry.What Is a Digital Product Passport? 2026 GuideWhat a Digital Product Passport is, how it works, which products need one and when (batteries first, 18 February 2027), and what data it carries.The Complete Guide to ESPR & Digital Product PassportsWhat the ESPR requires, how it connects to the digital product passport, and which sectors it reaches and when — the guide for manufacturers and buyers.