---
title: "EU DPP customs access: registry, portal, and restricted data"
canonical_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/faq/customs-access"
source_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/faq/customs-access"
author: "Sorena AI"
description: "FAQ on customs access under the EU Digital Product Passport: what customs can verify, how the registry and public portal differ, and how access rights limit DPP data."
published_at: "2026-05-09"
updated_at: "2026-05-09"
keywords:
  - "EU Digital Product Passport"
  - "DPP customs access"
  - "ESPR registry"
  - "DPP public portal"
  - "DPP access rights"
  - "Digital Product Passport"
  - "ESPR"
  - "customs controls"
  - "DPP registry"
  - "access rights"
  - "EU Single Window"
---
**[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform

[Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io)

---

# EU DPP customs access: registry, portal, and restricted data

FAQ on customs access under the EU Digital Product Passport: what customs can verify, how the registry and public portal differ, and how access rights limit DPP data.

*FAQ* *DPP* *EU*

## EU Digital Product Passport customs access, registry checks, and restricted data

Customs access under ESPR is mainly a registry and access-rights question: border systems verify the DPP registration identifier and commodity code, while broader passport data remains governed by role-based access rights.

Use this FAQ to separate public portal search, customs registry checks, and privileged access to non-public DPP data.

Under Regulation (EU) 2024/1781, products covered by a product-specific DPP delegated act and intended for release for free circulation must be supported by registry data that customs can verify electronically. That does not mean every customs field belongs inside the public passport: the regulation names the unique registration identifier, unique identifiers, commodity code for customs cases, and access rights set in product-specific delegated acts.

## What should teams do about EU DPP customs access?

Treat customs access as a handoff between the product passport, the Commission registry, and customs systems. For a covered product intended to be released for free circulation, the person placing it under that customs procedure must provide or make available the unique registration identifier linked to the DPP registry entry.

Customs may release the product for free circulation only after checking, at minimum, that the unique registration identifier and the commodity code match the data stored in the registry. ESPR also says that this release is not proof that the product complies with ESPR or other Union law, so teams should not use a passed customs check as a general compliance certificate.

- Before import: confirm whether a product-specific ESPR delegated act requires a DPP for the product group.
- For registry upload: maintain the unique identifiers required by Article 13 and, for products intended for release for free circulation, the commodity code.
- For border handoff: provide or make available the unique registration identifier from the registry.
- For compliance records: keep customs verification separate from evidence that the DPP content and ecodesign requirements are correct.

Sources for this answer:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Article 15 supports the customs handoff: customs verifies the unique registration identifier and commodity code against registry data for release-for-free-circulation checks.

## Can customs see public and restricted DPP data?

ESPR distinguishes general access to the DPP from rights to specific data. Customers, economic operators, repairers, recyclers, market surveillance authorities, customs authorities, civil society organisations, trade unions, and other relevant actors must have free and easy access to the DPP based on the access rights in the applicable product-specific delegated act.

That means customs can be a privileged actor for data needed to carry out Union-law duties, but the public does not automatically receive the same view. The DPP must be designed for differentiated access, with rights to introduce, modify, or update data restricted according to the delegated-act access model.

- Public view: data exposed through the DPP and public portal according to the delegated act's access rights.
- Customs view: registry access plus DPP and registry data that customs may retrieve and use for risk management, customs controls, and release for free circulation.
- Restricted view: non-public or sensitive DPP data should be protected by role-based credentials or equivalent access controls.
- Update rights: do not let logistics, broker, or portal users edit DPP data unless their role has the relevant access right.

Sources for this answer:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Articles 10 and 11 support role-based access to DPP data and restricted rights to introduce, modify, or update passport data.
- [CIRPASS DPP System Architecture](https://cirpassproject.eu/wp-content/uploads/2024/06/D3.2v1.9.pdf?ref=sorena.io) - CIRPASS provides implementation architecture support for public versus privileged DPP data access, including credentials for non-public data.

## How do the registry, public portal, and customs systems differ?

The registry is not just the public DPP page. ESPR requires the Commission to set up a secure registry that stores at least unique identifiers and, for products intended for release for free circulation, the commodity code. Economic operators upload the required registry data and receive a unique registration identifier.

The public portal is different: it lets stakeholders search and compare DPP data in a way that respects their access rights. Customs integration is different again: the Commission must interconnect the registry with EU CSW-CERTEX so information can be exchanged automatically with national customs systems through the EU Single Window Environment for Customs.

- Registry: stores the DPP identifiers needed for enforcement and customs checks.
- Public portal: supports search and comparison of DPP data, limited by each stakeholder's access rights.
- EU CSW-CERTEX interconnection: enables automated customs-system checks against registry data.
- Decentralised DPP repositories: remain the source for many passport data elements; the registry entry is not a full substitute for maintaining the DPP.

Sources for this answer:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Articles 13, 14, and 15 define the registry, public web portal, and EU CSW-CERTEX customs interconnection.
- [CIRPASS DPP System Architecture](https://cirpassproject.eu/wp-content/uploads/2024/06/D3.2v1.9.pdf?ref=sorena.io) - CIRPASS explains the DPP architecture pattern in which the portal and registry help discover decentralised passport data rather than replacing the operator's DPP repository.

## Which customs fields should teams avoid inventing in the DPP?

Do not pre-fill a DPP customs template with additional customs clearance fields unless a product-specific delegated act or another sourced legal requirement actually calls for those records.

For this FAQ, the grounded ESPR customs fields are narrower: unique identifiers in the registry, the commodity code for products intended for release for free circulation, the unique registration identifier provided or made available to customs, and any additional registry data later specified by the Commission under the criteria in Article 13.

- Supported now: unique identifiers, commodity code for release-for-free-circulation cases, and the registry-issued unique registration identifier.
- Supported as conditional: additional registry data only when specified in delegated or implementing acts.
- Not supported by this grounding: fixed customs penalties, mandatory broker fields, universal import-document fields, or a customs clearance guarantee created by the DPP.
- Operational control: maintain a product-group mapping that separates ESPR DPP registry data from ordinary customs, tariff, and logistics documentation.

Sources for this answer:

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Article 13 identifies the registry data expressly named for customs cases and limits additional registry data to what delegated acts specify under stated criteria.

## Primary sources

- [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Primary legal source for DPP access rights, the Commission registry, the public portal, EU CSW-CERTEX customs interconnection, and release-for-free-circulation checks.
  - Quote: "customs authorities may release a product for free circulation only after having verified"
- [CIRPASS DPP System Architecture](https://cirpassproject.eu/wp-content/uploads/2024/06/D3.2v1.9.pdf?ref=sorena.io) - Technical architecture source for decentralised DPP repositories, public versus privileged data access, and role-based access-control concepts.
  - Quote: "publicly and an appropriate access needs to be provided"

## Topic Guides

- [Annex III Data Model Planning for EU Digital Product Passports](/artifacts/eu/digital-product-passport/annex-iii-data-model-planning.md): Plan EU Digital Product Passport data fields, identifiers, access rights, update owners, registry inputs, and evidence records against ESPR Annex III and product-specific delegated acts.
- [Digital Product Passport vs Digital Twin](/artifacts/eu/digital-product-passport/dpp-vs-digital-twin.md): Compare EU Digital Product Passports with digital twins: legal access duties, identifiers, public and restricted data, evidence, governance, and reuse limits.
- [Digital Product Passport vs Paper Product Passports](/artifacts/eu/digital-product-passport/dpp-vs-traditional-product-passports.md): Compare EU regulated digital product passports with paper, PDF, web, and internal product passports across access, identifiers, data carriers, restricted data, customs checks, registry, and interoperability.
- [DPP customs access review workflow for ESPR products](/artifacts/eu/digital-product-passport/customs-access-review-workflow.md): Review public, restricted, and customs access for EU Digital Product Passports, including registry handoffs, portal access rights, and release-for-free-circulation evidence.
- [DPP Data Governance RACI Template for EU Digital Product Passports](/artifacts/eu/digital-product-passport/dpp-data-governance-raci-template.md): Assign accountable owners for EU Digital Product Passport data, access rights, supplier inputs, resolver links, registry uploads, verification checks, and retained evidence.
- [DPP data-model intake workflow for EU Digital Product Passports](/artifacts/eu/digital-product-passport/dpp-data-model-intake-workflow.md): A grounded intake workflow for EU Digital Product Passport data models: product group, delegated-act status, source owner, supplier data, access class, identifiers, carrier, checks, and publication readiness.
- [DPP Governance, Verification and Audit Controls](/artifacts/eu/digital-product-passport/governance-verification-and-audit.md): Build EU Digital Product Passport governance controls for data owners, supplier evidence, access logs, validation checks, audit records, and product release gates.
- [DPP QR code vs NFC data carrier choices under EU ESPR](/artifacts/eu/digital-product-passport/faq/qr-code-vs-nfc-carrier-choices.md): How to choose QR code, NFC, or another data carrier for an EU Digital Product Passport without assuming ESPR mandates one universal carrier.
- [DPP registry and web portal integration under EU ESPR](/artifacts/eu/digital-product-passport/dpp-registry-and-web-portal-integration.md): Grounded guide to EU Digital Product Passport registry and web portal integration under ESPR, covering identifiers, data carriers, access rights, service providers, and lookup design.
- [DPP vs Battery Passport: ESPR and Battery Regulation Comparison](/artifacts/eu/digital-product-passport/dpp-vs-battery-passport.md): Compare the ESPR Digital Product Passport framework with the EU Batteries Regulation battery passport by scope, timing, data, access rights, identifiers, registry, governance, and evidence.
- [DPP vs EPREL Comparison](/artifacts/eu/digital-product-passport/dpp-vs-eprel.md): Compare the EU Digital Product Passport with EPREL: product-passport scope, energy-label database role, access model, identifiers, data carriers, and overlap limits.
- [DPP vs GS1 Digital Link: Duties vs Standard](/artifacts/eu/digital-product-passport/dpp-vs-gs1-digital-link.md): Compare EU Digital Product Passport requirements with GS1 Digital Link: legal scope, identifiers, data carriers, access rights, registry, portal, customs checks, and implementation consequences.
- [EU Digital Product Passport access: public, restricted, and customs views](/artifacts/eu/digital-product-passport/public-restricted-and-customs-access.md): How ESPR Digital Product Passport access should be split across public users, restricted actors, authorities, customs, the EU registry, and the web portal.
- [EU Digital Product Passport API and resolver architecture](/artifacts/eu/digital-product-passport/api-and-resolver-architecture.md): Grounded DPP architecture guidance for data carriers, product identifiers, resolver lookup paths, access rights, registry integration, and interoperability without premature protocol mandates.
- [EU Digital Product Passport Applicability Test](/artifacts/eu/digital-product-passport/applicability-test.md): Check whether an ESPR delegated act or battery passport rule may require a Digital Product Passport, which operator owns it, and what evidence to keep.
- [EU Digital Product Passport architecture and integration](/artifacts/eu/digital-product-passport/architecture-and-integration.md): Grounded guide to EU Digital Product Passport architecture: data carriers, identifiers, access rights, registry, portal, supplier flows, customs checks, and governance.
- [EU Digital Product Passport checklist](/artifacts/eu/digital-product-passport/checklist.md): A concrete EU Digital Product Passport readiness checklist covering product-group scope, passport fields, identifiers, data carriers, access rights, supplier evidence, registry preparation, and publication controls.
- [EU Digital Product Passport compliance: ESPR requirements](/artifacts/eu/digital-product-passport/compliance.md): Grounded EU Digital Product Passport compliance guide covering ESPR passport data, identifiers, data carriers, access rights, registry readiness, supplier validation, and evidence.
- [EU Digital Product Passport Data Carriers, Access Control, and UX](/artifacts/eu/digital-product-passport/data-carriers-access-control-and-ux.md): How to choose DPP data carriers, identifiers, access rights, and scanning UX under ESPR Articles 9-14, with QR, NFC, RFID, registry, and customs constraints.
- [EU Digital Product Passport data requirements and fields](/artifacts/eu/digital-product-passport/data-requirements-and-fields.md): How to plan Digital Product Passport data fields under ESPR: delegated-act scope, Annex III data categories, access rights, customs data, and supplier validation.
- [EU Digital Product Passport deadlines and compliance calendar](/artifacts/eu/digital-product-passport/deadlines-and-compliance-calendar.md): Grounded EU Digital Product Passport calendar for ESPR and battery passport milestones, with product-group dates flagged as dependent on delegated acts.
- [EU Digital Product Passport FAQ](/artifacts/eu/digital-product-passport/faq.md): Direct answers on EU Digital Product Passport scope, creators, product groups, registry, customs checks, access rights, identifiers, data carriers, and governance.
- [EU Digital Product Passport identifier and data carrier design](/artifacts/eu/digital-product-passport/unique-identifier-and-data-carrier-design.md): How to design Digital Product Passport identifiers, QR or other data carriers, resolver links, registry records, access paths, and evidence without overclaiming the EU rules.
- [EU Digital Product Passport penalties and enforcement](/artifacts/eu/digital-product-passport/penalties-and-fines.md): What ESPR says about Digital Product Passport penalties, Member State fine rules, market surveillance, customs checks, and unresolved product-specific delegated acts.
- [EU Digital Product Passport Product Group Readiness](/artifacts/eu/digital-product-passport/product-group-readiness.md): Prepare product groups for EU Digital Product Passport rules by tracking ESPR delegated-act status, data fields, suppliers, identifiers, access rights, and registry handoffs.
- [EU Digital Product Passport requirements under ESPR](/artifacts/eu/digital-product-passport/requirements.md): source-linked overview of EU Digital Product Passport requirements under ESPR: product-specific delegated acts, data fields, identifiers, carriers, registry, access rights, supplier data validation, and open points.
- [EU Digital Product Passport supplier data validation controls](/artifacts/eu/digital-product-passport/supplier-data-validation.md): Build a supplier data validation file for EU Digital Product Passports: source owner, product link, access class, data model fit, evidence quality, approval record, and release gate.
- [EU DPP implementation playbook and vendor selection](/artifacts/eu/digital-product-passport/implementation-playbook-and-vendor-selection.md): Select Digital Product Passport vendors against ESPR requirements for identifiers, data carriers, access rights, decentralized storage, registry readiness, portal access, and verification evidence.
- [EU DPP Product-Group Readiness Checklist](/artifacts/eu/digital-product-passport/product-group-readiness-checklist.md): A source-grounded checklist for preparing a product group for an EU Digital Product Passport delegated act, covering data fields, suppliers, identifiers, carriers, access rights, and registry readiness.
- [EU DPP QR Code and Data Carrier Implementation Guide](/artifacts/eu/digital-product-passport/dpp-qr-code-implementation-guide.md): Grounded guidance for using QR codes and other data carriers in EU Digital Product Passport programs, including unique identifiers, access, resolver testing, and evidence.
- [EU DPP supplier data validation workflow](/artifacts/eu/digital-product-passport/supplier-data-validation-workflow.md): A grounded workflow for checking supplier data before it is used in an EU Digital Product Passport, covering product linkage, evidence, owners, access class, and approval records.
- [EU DPP unique identifier requirements: product, operator and facility IDs](/artifacts/eu/digital-product-passport/faq/unique-identifier-requirements.md): FAQ on how ESPR Digital Product Passport identifiers connect products, economic operators, facilities, data carriers, resolvers and registry evidence.
- [Public vs restricted EU Digital Product Passport data](/artifacts/eu/digital-product-passport/faq/public-vs-restricted-passport-data.md): How to separate public, restricted, authority, and customs access in EU Digital Product Passport designs under ESPR and battery passport rules.
- [What is a Digital Product Passport under ESPR?](/artifacts/eu/digital-product-passport/what-is-a-dpp.md): A visitor-friendly explanation of EU Digital Product Passports under ESPR: product data, identifiers, data carriers, access rights, registry, web portal, and delegated acts.
- [What is the EU Digital Product Passport registry?](/artifacts/eu/digital-product-passport/faq/dpp-registry.md): FAQ on the ESPR Digital Product Passport registry: what it stores, who uploads data, how identifiers work, and what teams should avoid assuming.
- [Which products come first for the EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/which-products-come-first.md): FAQ on EU Digital Product Passport product priority: batteries have a separate passport rule, while ESPR product groups depend on the working plan and delegated acts.
- [Who must create an EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/who-must-create-a-digital-product-passport.md): DPP responsibility under the EU ESPR: how manufacturers, importers, distributors, suppliers, service providers, and delegated acts fit together.

*Recommended next step*

*Placement: after customs access section*

## Prepare DPP customs access without overbuilding customs data

Use this EU DPP FAQ to separate registry data, customs handoffs, public portal access, and restricted passport data before product teams design import workflows.

- [Open Research Copilot](/solutions/research-copilot.md): Check DPP customs, registry, and access-rights questions against cited source material.
- [Discuss DPP implementation](/contact.md): Review DPP registry data, portal access, and import handoffs with Sorena.


---

[Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us)

(c) 2026 Sorena AB (559573-7338). All rights reserved.

Source: https://www.sorena.io/artifacts/eu/digital-product-passport/faq/customs-access