The EU DPP Registry: How Product Identities Get Checked at the Border

A Digital Product Passport is not only read by customers. Under the ESPR — Regulation (EU) 2024/1781 — it is also checked by the system itself: against a central EU registry, and, when a product is released for free circulation, by customs authorities. Articles 13 to 15 build that machinery: what the registry stores, what the registration identifier is — and is not — and how the border check will work.

What the registry stores

Article 13(1) sets the deadline and the content: “By 19 July 2026, the Commission shall set up a digital registry which stores in a secure manner at least the unique identifiers.” For products intended for the customs procedure “release for free circulation”, it also stores the commodity code. And it stores the unique identifiers of batteries, under Article 77(3) of the Batteries Regulation (EU) 2023/1542 — so the same registry serves the battery passport applying from 18 February 2027.

The full passport data does not move into the registry. Under Article 13(2), each product group’s delegated act specifies which other data must also be stored there — judged against three criteria in the law: verifying the authenticity of the passport, improving market surveillance and customs controls, and avoiding disproportionate burden. The Commission manages the registry; the Commission, national authorities and customs access it for their duties (Article 13(6)).

The registration identifier: what it is, and what it is not

The duty to feed the registry sits with the operator: under Article 13(4), “the economic operator placing the product on the market or putting it into service shall upload” the required data. Once it does, the registry automatically communicates a unique registration identifier for that product (Article 13(5)). Two identifiers, two different jobs:

And one limit, in the Regulation’s own words: that communication “shall not be deemed to be proof of compliance with this Regulation or other Union law”. A registration identifier proves a product is registered, not that it complies — just as anchoring a passport record proves it existed and has not been altered, not that the data first entered was true.

How the customs check works

Article 15 connects the registry to the border — precisely, to release for free circulation, the procedure that lets a non-EU product move freely in the single market. It checks products entering the EU, not EU exports, and it works in stages:

• The declarant provides the identifier (Article 15(1)): any person intending to place a product covered by a delegated act under release for free circulation must provide or make available to customs the product’s unique registration identifier. This duty applies from the moment the registry is operational;
• Customs verify before release (Article 15(2)): customs may release a product only after verifying, as a minimum, that the registration identifier and the commodity code provided correspond to the data stored in the registry. The verification is electronic and automatic, through the interconnection below, and applies from when it is operational. Release, again, “shall not be deemed to be proof of compliance”;
• The interconnection (Article 15(3)): the Commission interconnects the registry with the EU Customs Single Window Certificates Exchange System (EU CSW-CERTEX), so the check runs inside the customs systems traders already use. It must be operational within four years of the entry into force of the registry’s implementing act under Article 13(5). Under Article 15(4), the Commission and customs may also use passport and registry data for risk management and controls.

Read the sequence honestly: registry by 19 July 2026, the declarant’s duty from when the registry is operational, automated verification from when the CERTEX interconnection is operational. “No ID, no circulation” is the direction of travel for covered products — not a switch that flips for everything on one morning in 2026.

The public side: the web portal

Article 14 adds the public counterpart: a publicly accessible web portal where stakeholders search for and compare passport data. Public does not mean unlimited: the portal must work “in a manner that is consistent with their respective access rights” in the delegated acts. The registry is the authorities’ verification layer; the portal is the market’s window onto the same system.

What importers and exporters to the EU should do now

• Know which of your products will be covered: the check applies to products covered by an ESPR delegated act (and to batteries under their own regulation). Our ESPR timeline maps the sequence.
• Build identifiers that can be registered: unique product, operator and facility identifiers on open standards — the registration identifier is issued against them, so weak identifiers upstream become border problems downstream.
• Treat the upload as a process, not an event: registration data must match what customs will see — identity and commodity code — and stay accurate as models and suppliers change.
• Align customs data early: whoever files your declarations will need the registration identifier at declaration time. Put it in the data flow to your customs broker now, not at the first held shipment.

How Ledger Consortium helps

Ledger Consortium aggregates your product data and anchors each passport record on a governed blockchain — timestamped and tamper-evident — so the identity you register is the identity whose history can be verified, as we explain in our piece on verifiable identity. The upload to the EU registry remains, by law, the operator’s act; our work is to make the data behind it complete and structured. Anchoring does not certify that client data is true; costs are predictable, with no token and no crypto exposure, and the platform is GDPR- and eIDAS-aligned. In Italy, the Ledger DPP is distributed by Il Sole 24 Ore (Valore24), whose channel onboards dozens of companies per month. See a working passport in our live demo and browse News.