What proof of registration proves, and what a buyer will assume it proves

The document sits after a successful Registry event

Proof of registration is not the thing you submit to create a DPP registration. It is an artefact the Registry can generate after a DPP has been registered.

The operational sequence is: host the complete DPP outside the Registry, submit the Registry registration record, pass the applicable Registry checks, receive the Registry-generated unique registration identifier, then generate proof where needed.

The current submission journey is covered in How to register a DPP in the EU Registry.

As checked on 7 October 2026, Commission User Guide v1.03 says successful Battery DPP registration is not yet available because the Battery semantic content is still under development, so what follows is what proof means under the law, not a sign that a production Battery proof can already be generated from a successful registration today (current Registry state).

Article 9(4)'s ninety-day period is the period for which the generated proof remains available in the Registry. It is not a ninety-day lifetime for the underlying DPP registration, and a new proof can be generated again where needed.

"EU certified DPP" and "Registry-approved product" are unsupported too: the proof evidences fulfilment of the Registry registration obligation for the identified DPP, not the substantive truth of the passport or the compliance of the product, and automated Registry checks are not product approval.

For the wider architecture see where passport data lives.

Where this proof sits among the other checks

Proof of registration is one of four things people call verification, and the other three prove different propositions. Article 8 of Commission Implementing Regulation (EU) 2026/1778 gives the Registry a defined set of automated checks; Article 9 gives the proof its narrow evidential job; Article 19 leaves the verified economic operator responsible for the accuracy and completeness of what it submits.

None of the four stands in for another. Three phrases in particular do not survive contact with the instruments: "EU certified DPP", "registration certificate proves compliance", and "Registry verified product data" without naming the check actually performed.

For the full model - Registry check, evidence, conformity assessment, market surveillance - see who checks DPP information and what each check proves.

What the document actually contains

Article 9 of Commission Implementing Regulation (EU) 2026/1778 lets an economic operator, or a third party acting on its behalf, generate proof of registration at any time for one or more passports. It is a secure electronic document, downloadable from the registry through the interface or the API, and Article 9(2) sets a floor of five things it must carry.

Article 9(3) requires the whole document to be guaranteed by a qualified electronic seal as provided for in Article 38 of Regulation (EU) No 910/2014, the same trust framework that sits behind the credential a business needs before it can register anything at all. That is a real cryptographic guarantee of origin and integrity, and it is the reason this document is worth more than a screenshot of a portal.

The two sentences that look like they disagree

Article 9(2) says the proof "shall serve as evidence, including vis-à-vis third parties, that the registration obligation has been fulfilled".

Article 13(5) of the Ecodesign for Sustainable Products Regulation says that the registry's communication of a unique registration identifier "shall not be deemed to be proof of compliance with this Regulation or other Union law".

Nothing in the published coverage we read reconciles these. They reconcile easily: they are about two different propositions.

• The registration obligation was fulfilled. True or false as a matter of record. The registry knows the answer. Article 9 hands you that answer in a sealed document.
• The product complies. True or false as a matter of substance. The registry does not know the answer and does not claim to.

Recital 16 of the implementing regulation makes the same separation from the other end, saying that verification of the substantive correctness of registered data "remains a task for the market surveillance authorities" and that the automated verifications "should not be deemed to constitute proof of compliance". What the registry checks at submission, and how narrow those five automated checks are, is set out at where your passport data actually lives.

So a proof of registration is a strong document about a weak proposition. That is not a criticism. A document that does one thing reliably is more useful than one that gestures at several.

The hash is the part worth understanding

Of the five elements, the hash is the one a counterparty should care about, and it is the one nobody is explaining.

A hash of a passport version means the proof is tied to one exact state of the data. Change any value in the passport and the hash of the new version will not match the one in the document you handed over. That makes proof of registration a tamper evidence instrument rather than merely a receipt.

Two consequences follow, in opposite directions.

For the party receiving one, the useful question is not "do you have a proof of registration" but "does the passport I am looking at today still correspond to the version in this proof". A proof from March against a passport edited in July tells you something real: the record moved.

For the party issuing one, the same property is a discipline. Every correction changes the hash. A business that corrects a value has not invalidated its compliance, but it has invalidated the specific document a customer is holding, and nothing in the instrument requires anybody to tell that customer. Who stays responsible once a value is published, and what happens when one turns out to be wrong, is worked through at who has to own this.

Ninety days, and what that does to a procurement file

Article 9(4) makes the proof available for 90 calendar days from the date it is generated, through the interface or API the operator chose, and it can be generated again.

That number gets misreported. At least one widely read explanation states that proof of registration is retained for ten years. Ten years is the Article 10(3) rule for deleting registration data where Union law sets no specific availability period. It is not the life of the document. Conflating the two overstates the shelf life of the artefact by a factor of about forty, and a buyer relying on it will file something that has quietly stopped being retrievable.

Proof of registration is a document you generate on demand, not a certificate you obtain once and keep. A procurement process that requests one at onboarding and files it has a document that ages twice over: it stops being retrievable from the registry after 90 days, and it stops describing the current passport the moment anybody edits a value.

The better arrangement, for both sides, is to ask for a fresh proof at the moment it matters rather than to hold an old one. That is a change to a supplier onboarding process rather than to a system.

The other thing the registry can evidence

One provision that goes unmentioned everywhere protects you rather than your customer.

Article 15(3) lets the Commission suspend the registry's availability without prior notice where there is a malfunction, a cyber attack or a compelling urgent security need. Article 15(4) then says that where registration was prevented by temporary unavailability or malfunctioning, the Commission records the date and time and makes that information available on request, for no less than five years, to economic operators, value chain actors, competent national authorities and customs authorities.

That is a second, quieter evidence instrument. If a registration could not be made because the registry was down, there is an authoritative record of the outage and you are entitled to ask for it.

Three phrases that do not survive contact with the instrument

The commercial risk in this subject is not that a business fails to obtain proof of registration. It is that somebody describes it wrongly, in writing, to a customer.

The estate's own rule follows from this and applies to the businesses we work with as much as to anybody else: no product is described as registered or compliant on the strength of a registry record. The wider question of what a filled field can and cannot establish about a product is the subject of what a passport field can and cannot prove.

Sources

The ten year misreport described above was found in current published coverage of the registry. It is described rather than linked, because the point is the error and not the publisher.

• Commission Implementing Regulation (EU) 2026/1778 establishing the Digital Product Passport registry
  Delegated or implementing actRelevant provisions reviewed

  Articles 8(7), 9, 10(3) and 15, plus recitals 16 and 17. Article 9(2) and recital 16 quoted from the enacting terms and the recitals respectively.

• Ecodesign for Sustainable Products Regulation (EU) 2024/1781, consolidated text
  EU lawRelevant provisions reviewed

  Article 13(5), quoted, for the proposition that the registration identifier communication is not proof of compliance.

• Regulation (EU) No 910/2014 on electronic identification and trust services (eIDAS)
  EU lawOfficial source confirmed, detailed review pending

  Named because Article 9(3) points at its Article 38 for the qualified electronic seal. Cited for the cross reference rather than read in full.