Know what is live and what still depends on your product
The Commission announced the Registry and testing environment on 20 July 2026. Implementing Regulation 2026/1778 establishes its operational arrangements. Those facts do not create a single application date for every product group. Your product’s own rules still determine whether, when and at what level a passport and registration are required.
ESPR Article 13 establishes the central register. It is not the full evidence archive. Maintain the hosted passport and its access controls as a separate service responsibility, and check the applicable product rules before populating an entry. Infrastructure availability and legal obligation are two different project inputs.
Source: European Commission — Registry launch, 20 July 2026Source: Implementing Regulation (EU) 2026/1778 — DPP RegistrySource: Regulation (EU) 2024/1781 — ESPR
Prepare organisation verification
The Commission user guide reviewed here is version 1.02, published 24 August 2026. It describes EU Login, organisation enrolment, identity verification and registration. Its verification workflow includes a sealed declaration and the appropriate qualified electronic signature or seal. A login account alone is not the same as a verified organisation.
Operational recommendation: involve the person who can represent the correct legal entity and arrange the required trust-service credentials early. Reconcile the organisation details with certificate information before submission. Nominate a deputy, record where rejection messages are handled, and keep test identities separate from production credentials.
Source: Implementing Regulation (EU) 2026/1778 — DPP RegistrySource: European Commission — Registry user guide v1.02, 24 August 2026
Keep three kinds of reference distinct
Article 8 of Regulation 2026/1778 connects registration with the required model, batch or item level. The product identifier identifies the product or permitted grouping; the passport location leads to the hosted information; the registration identifier is returned by the Registry. Their relationship must remain understandable to your operations team.
Operational recommendation: keep those references in separate fields in your integration record. Document how an item relates to its model and batch where relevant. A QR destination that opens the right webpage can still be connected to the wrong registration or product configuration. Compare the references on a real sample, not only on a slide showing the architecture.
Source: Implementing Regulation (EU) 2026/1778 — DPP Registry
Rehearse submission and read the result
Article 8 permits registration through the secure interface or API. Its checks address matters such as semantic conformity, applicable granularity, coherent mandatory data and relevant commodity codes or backup references. Article 9 allows a proof of registration to be generated. These checks are useful evidence about registration; they are not a replacement for product assessment.
Operational recommendation: first use the official test environment with suitable sample data. Record the submitted version, response, identifiers and any rejection reason. Decide who corrects a failed mapping before retrying. Keep the previous response when an issue is fixed so that the team can explain what changed and why the next attempt was accepted.
Source: Implementing Regulation (EU) 2026/1778 — DPP RegistrySource: European Commission — the DPP Registry
Use proof for the question it answers
ESPR Article 13(5) expressly states that communication of a registration identifier is not proof of compliance with the regulation or other EU law. Store the registration evidence beside, rather than instead of, your product assessment and source documents.
Article 15 contains the customs connection and distinguishes its operational trigger. Do not assume that announcement of the Registry has activated every automatic customs check. Operational recommendation: agree with your customs representative which references and proof are needed for the relevant product and procedure, and verify the current technical route before the first shipment.
Source: Regulation (EU) 2024/1781 — ESPRSource: Implementing Regulation (EU) 2026/1778 — DPP Registry
Plan the work after the first registration
Article 19 of the Registry regulation retains responsibility with the verified operator when a third party performs registration work; the third party also needs the prescribed verification. Delegating technical work therefore needs a documented scope and a clear identity, rather than shared passwords or an assumption that any software account carries Registry authority.
Operational recommendation: rehearse credential renewal, staff changes, corrected data, provider migration and an unreachable hosted passport. Keep your internal review record, live passport version and registration evidence reconcilable. Passvanta can help prepare product records and approved evidence. Confirm the actual Registry integration and supported transaction types separately before describing the process as automated.
Source: Implementing Regulation (EU) 2026/1778 — DPP Registry