> EU DPP Registry enrolment and verification steps | dpp.coach · https://eu.dpp.coach/en/execution · English · Markdown version of this page
> Free to use · independent, vendor-neutral guide · Sponsored by Narravero (https://www.narravero.com/)

Track B · EU level · one sitting, strict order

# Execution: enrol and verify your organisation in the EU Digital Product Passport (DPP) Registry

Five steps in the order the Commission’s user guide sets out. Each one consumes something you prepared in Track A. Do not skip ahead — every step depends on the output of the one before.

Last updated: 26 October 2026 · Checked against the European Commission’s [DPP Registry User Guide for Economic Operators](https://single-market-economy.ec.europa.eu/document/download/079a45e2-469f-4eec-b1e5-32e8e05d1357_en?filename=dpp_registry_user_guide_for_economic_operators.pdf) (v1.03, 16 September 2026).

Step 1 · Uses Track A, step 1

## Log in to the DPP Registry with your EU Login

**In short:** Open the registry at registry.product-passport.ec.europa.eu on the computer with your seal set-up, sign in with the company’s EU Login and its second factor, and check that the Welcome page offers “Enrol New Organisation”.

### Instructions

Open the [EU Digital Product Passport Registry](https://registry.product-passport.ec.europa.eu/) and authenticate with the EU Login account you prepared. The registry has no accounts of its own: it redirects you to EU Login and back.

1. Open [registry.product-passport.ec.europa.eu](https://registry.product-passport.ec.europa.eu/) on the computer where your seal infrastructure is installed.
2. You are redirected to the EU Login sign-in page: enter the e-mail address and password from Track A.
3. Approve the second-factor prompt on your registered phone or enter the code.
4. You are taken back to the registry’s Welcome page. Confirm it offers the button “Enrol New Organisation”.

### Helper tool

**Readiness gate**

Execution assumes these three results from Track A exist. Confirm each before you log in.

- EU Login with two-factor authentication works (Track A · step 1)
- Qualified seal (card and reader, or remote service) produces a valid test seal (Track A · step 2)
- Company data sheet filled in from the Handelsregisterauszug and checked against the seal certificate (Track A · step 3)

### Typical pitfalls

- Logging in with a colleague’s private EU Login: whoever completes the verification becomes the organisation’s Administrator in the registry.
- Starting on a laptop without the card reader and middleware — step 4 will then fail mid-session.
- Practising in the test environment with the same EU Login: the test registry needs its own, separate EU Login account.

Step 2 · Uses Track A, step 3

## Create the organisation application

**In short:** Choose “Enrol New Organisation”, select Legal Person and enter legal name, registered address, country, the National Trade Register (NTR) identifier and a compliance contact — exactly as in your seal certificate. Then Save and Start Verification.

### Instructions

The application form collects your organisation’s identity. The registry later compares legal name, country of registration and identifier with the attributes of your qualified seal certificate, character by character — so copy them from your data sheet and check them against the certificate.

1. Click “Enrol New Organisation”. Under “Organisation type” choose “Legal Person” (a natural person is an individual acting in their own name, such as a sole trader).
2. “Legal name”: the registered name exactly as in the Handelsregister and in the seal certificate, including “GmbH” — not a trading name.
3. Legal address: “Street address” of the registered seat, plus postal code and locality; “Country of Registration”: Germany.
4. “Identifier Type”: “NTR – National Trade Register” (preferred). “Identifier”: the coded NTRDE identifier — use the builder on the right, and compare it with the certificate.
5. Add a compliance contact (e-mail, country code, phone). Authorities may use it for questions about your DPP registrations; it is not shown publicly.
6. Click “Save”, check the confirmation, then click “Start Verification”.

### Typical pitfalls

Legal name, country of registration and identifier must match, character for character, the organizationName, countryName and organizationIdentifier attributes of your qualified seal certificate. A mismatch is the most common reason a verification fails.

- Typing the court name or “HRB 12345” instead of the coded NTRDE identifier — the registry compares it with the certificate’s organisation identifier.
- Using an old company name after a rename that the seal certificate still carries — or the reverse.
- Changing the organisation type after typing the data: the entries are lost and must be typed again.

### Helper tool Trickiest part

**National Trade Register (NTR) identifier builder (Germany)**

The EU form asks for your organisation identifier; for a German company, use the National Trade Register (NTR) identifier. It is not the text on your Handelsregisterauszug but a coded string that also appears in your qualified seal certificate. Pick your register court, choose the department and enter the number — the tool assembles the identifier.

(Two minutes: what the NTR identifier is and how it is assembled.)

**Seal match check**

Paste the organisation identifier from your seal certificate and what you are about to type into the form. They are compared character for character, including spaces and upper/lower case — as the registry does.

Step 3 · Verification steps 1–3

## Name the legal representative, request and download the EC-sealed declaration

**In short:** Enter the legal representative who will seal, click “Request Declaration” and “Continue”, then “Download PDF”. The declaration arrives already sealed by the European Commission, in English; save it unchanged.

### Instructions

Verification starts with the person who will seal. The registry then generates a PDF declaration with your organisation’s data and seals it with the Commission’s institutional seal; you countersign that file in step 4.

1. Provide the legal representative’s information: first name, last name and e-mail of the person legally entitled to seal for the GmbH (usually a Geschäftsführer).
2. Click “Request Declaration”, then “Continue” to confirm.
3. Wait until the “Download PDF” button becomes available — the declaration is generated in the background — and click it.
4. Save the file unchanged in a folder you will find again. Do not open it in an editor, print it to PDF or re-save it.

PDF
**Output: EC-sealed PDF declaration**

Generated by the registry from your application and already sealed by the European Commission. Currently available in English only. Your countersignature is the only change allowed.

### Typical pitfalls

Changing the organisation details after this point restarts the verification: you must request and download a new declaration.

- If the declaration request shows as failed in the Activity Dashboard (the sealing service was briefly unavailable), simply request a new declaration.
- Naming a person who is not entitled to seal for the company: the legal representative is the one who countersigns in step 4.
- Editing, annotating or renaming the PDF before sealing: the registry checks that it is exactly the document the Commission sealed.

Step 4 · Uses Track A, step 2 · verification step 4

## Countersign the declaration with your qualified electronic seal

**In short:** With the seal card in the reader (or a qualified remote sealing service), add your GmbH’s qualified seal to the unchanged EC-sealed PDF in PAdES format — in Acrobat via “CAdES-Equivalent” — and check it in the DSS Validation WebApp.

### Instructions

Now the chain from Track A does its job. The declaration already carries the Commission’s seal; you add your GmbH’s qualified electronic seal as the second and only other signature. This happens outside the registry.

1. Connect the card reader and insert the seal card (or prepare your qualified remote sealing service). Wait until the middleware shows the certificate as available.
2. In Adobe Acrobat: Preferences › Signatures › Creation & Appearance › More… › set “Default Signing Format” to “CAdES-Equivalent” and click OK. This embeds the seal in the PAdES format the registry requires.
3. Open the downloaded EC-sealed declaration and choose “Sign with certificate” (or your tool’s seal function). Select the qualified seal certificate of your GmbH — not a personal certificate.
4. Enter the seal PIN on the reader’s keypad when prompted, and save the sealed file under a new name.
5. Check the sealed file in the Commission’s [DSS Validation WebApp](https://ec.europa.eu/digital-building-blocks/DSS/webapp-demo/validation): the format must be PAdES-BASELINE (B, T, LT or LTA) and the qualification of your seal “QESeal”.

### Helper tool

**Pre-seal checklist**

Run through this in the minute before you press “Sign”.

- Card reader connected and seal card inserted (or remote sealing service ready)
- Middleware shows the company certificate as available
- The file open is the unchanged EC-sealed declaration downloaded in step 3
- Selected certificate is the qualified seal of the GmbH, not a .p12/.pfx file
- Default signing format set to “CAdES-Equivalent” (In Adobe Acrobat: Preferences › Signatures › Creation & Appearance › More… › Default Signing Format. This produces the PAdES seal the registry requires; Acrobat’s default may not.)
- PIN letter at hand

### Typical pitfalls

- Leaving Acrobat on its default signing format: the seal is embedded in a format that is not PAdES and the declaration is rejected even with a valid certificate.
- Sealing with a certificate installed as a software file (.p12/.pfx): it only produces an advanced seal (“AdESeal-QC”) and the verification fails.
- Signing with a personal qualified signature instead of the company seal — a GmbH must use a qualified electronic seal.
- Printing, hand-signing and scanning the declaration, or entering the wrong PIN three times and blocking the card — have the PIN letter at hand.

Step 5 · Verification steps 5–7

## Upload the sealed declaration, verify your organisation and check the status

**In short:** Upload the sealed PDF with “Choose File”, click “Verify your Organisation” and “Continue”, then follow the status in the Activity Dashboard. On SUCCESS you become the organisation’s Administrator; the report shows when your seal expires.

### Instructions

Back in the registry, upload the countersigned declaration and submit it. The registry checks both seals, the PAdES format, the qualification level and that the certificate identity matches your application.

1. Return to the registry (log in again if the session expired) and open “Verification”.
2. Click “Choose File” or drag the sealed PDF into the upload area — the file saved under the new name in step 4 (PDF only, file name up to 100 characters).
3. Click “Verify your Organisation”, then “Continue”.
4. Open the Activity Dashboard and follow the request: PROCESSING, then SUCCESS or FAILURE. “View Detail” shows the success or error report.
5. On FAILURE, read the error report: it lists every mismatch at once. Correct the organisation information, or restart the verification, and repeat — do not upload the same file again unchanged.
6. On SUCCESS, keep the success report with your compliance records and note the seal expiry date it shows.

### Typical pitfalls

- Uploading the unsealed declaration from step 3 by mistake — check the file name.
- Treating a mismatch error as a platform fault: it is the application or the seal certificate that differs.
- Forgetting the expiry: the verified status lasts until your seal certificate expires and at most three years; afterwards you cannot register new DPPs until you verify again.

### Helper tool

**Verification tracker**

Follow your request in the registry’s Activity Dashboard and tick off each state here.

1. **Declaration downloaded** (EC-sealed PDF saved unchanged (step 3).)
2. **Sealed declaration uploaded** (Countersigned PDF selected with “Choose File”.)
3. **PROCESSING** (“Verify your Organisation” submitted; the Activity Dashboard shows the request.)
4. **SUCCESS** (Organisation verified — you are its Administrator. The success report shows the seal’s expiry date.)

Finish

### Organisation verified

Your GmbH is a verified economic operator in the EU DPP Registry and you are its Administrator. Keep the success report: verify again before your seal expires, and at the latest after three years, to keep registering DPPs.

[Back to overview](https://eu.dpp.coach/en/)

## Prefer a human to walk you through it?

A Narravero Expert takes you through every step personally — from ordering the seal to the final verification.

[Hire a Narravero Expert](https://www.narravero.com/en/contact)