espr-regulations

DPP and EU Customs: How Border Checks Will Work

What is already confirmed about DPP at the EU border, what remains open, and how importers should prepare now.

3/30/2026 · 11 min read · InfoDPP

Editorial update, 22 July 2026: the Commission describes the production DPP Registry as operational, with registration available through a secure interface or API and a separate testing environment. This is not the customs interconnection. ESPR Article 15 still requires the Registry’s interconnection with the EU Single Window Environment for Customs by 6 August 2030; product-specific obligations and operational customs procedures remain separate.

Why Customs Is Becoming Part of the DPP Story

A Digital Product Passport is more than a product page reached through a QR code. It also connects structured product information with identifiers and, where required, the EU Registry.

The EU is also developing its use in enforcement. The DPP is also being positioned as part of the enforcement infrastructure around products entering and circulating in the Single Market.

That matters because customs checks change the practical meaning of compliance. A missing or weak product record is no longer just a theoretical risk for later market-surveillance action. It can become a logistics, clearance, and border-readiness issue.

Battery passports and customs declarations

For products covered by ESPR, Article 15 provides for the unique registration identifier to be supplied when the product is declared for release for free circulation. The product obligation and the technical customs connection must both be checked before treating this as an operational procedure.

Battery passports follow a different rule. The September 2026 FAQ for batteries, question 4.1, explains that the passport must be registered in the EU DPP Registry, but its registration identifier does not have to be entered in the electronic customs declaration. This exception concerns the regime under Regulation (EU) 2023/1542. It does not remove the battery passport, registration or other import obligations.

An importer should therefore identify the applicable product law before adding a DPP identifier to its customs process. The battery clarification is not evidence that the same exception applies to toys, detergents or future ESPR product groups.

What Is Already Confirmed

Update (26.03.2026): Political Agreement on EU Customs Reform

Status, 20 September 2026: Parliament approved the customs reform at second reading and the final act was signed on 16 September. OEIL lists procedure 2023/0156(COD) as completed, awaiting publication in the Official Journal. This does not bring forward DPP obligations or the Registry-to-customs interconnection deadline of 6 August 2030. European Parliament procedure. The reform provides for an EU Customs Authority in Lille and a phased Customs Data Hub. Its adoption is a separate legislative step from the product-specific DPP rules and the technical interconnection required by ESPR Article 15.

Several elements are already clear enough to form a reliable preparation baseline.

1. The DPP is expected to support customs and market surveillance

In a written answer published on 17 March 2026, the European Commission confirmed to the European Parliament that DPP data will be integrated into EU customs control systems.

2. The EU Single Window is part of the enforcement architecture

The EU Single Window Environment for Customs already exists as legal infrastructure. Its role is to streamline how customs authorities verify non-customs formalities through one digital environment, rather than forcing repeated submission and fragmented checks.

For DPP, this matters because the border-enforcement model is moving toward data access and cross-checking through connected systems, not ad hoc manual document review only.

3. The Registry now has a customs-relevant data baseline

The adopted Registry regulation requires the registration record to contain the product identifier and, where relevant for the product and customs procedure, the commodity code. Before accepting a registration, the system checks the validity of that code where relevant and issues a unique registration identifier. This does not turn the Registry into a complete customs declaration or prove product compliance, but it gives the future connection a defined reference point.

4. Customs and market surveillance are being brought closer together

Customs and market surveillance authorities increasingly share data and coordinate their inspections. This cooperation covers both border checks and supervision of products already on the market.

5. E-commerce imports are under special pressure

The Commission has explicitly pointed to high non-compliance rates in online-import channels. Importers selling through digital marketplaces should therefore prepare for closer scrutiny of product information.

What This Does Not Mean

The planned interconnection does not mean that all products and procedures are already covered.

It does not mean every customs officer will scan every QR code

The likely model is risk-based and system-driven, not universal one-by-one scanning of product labels.

It does not mean all products face DPP border checks immediately

Only product categories covered by applicable DPP obligations under delegated acts or standalone sectoral laws can be checked on that basis.

It does not mean the full operational rulebook is already published

The registry is to be connected to customs systems. The detailed inspection procedures, criteria for selecting products and arrangements for authorities to access the data still need to be specified.

How Border Checks Are Likely to Work

Border checks involve several distinct elements.

1. Product category

First, the product must belong to a category for which a DPP obligation applies. No customs workflow can enforce a DPP obligation that does not yet exist for that category.

2. Product identification

The product must be linkable to a unique product identifier and, where required, to a data carrier or digital record that customs-related systems can verify.

3. Registry and system access

The relevant authorities must be able to access or cross-check the record through the appropriate infrastructure. Regulation 2026/1778 now supplies the Registry-side identifiers and commodity-code checks; ESPR Article 15 requires the Registry-to-Single-Window interconnection to be operational by 6 August 2030. The product-specific obligation and actual customs workflow still determine what is checked.

The same identification logic is now appearing outside the ESPR. The Commission’s guidelines on the Forced Labour Regulation (OJ C/2026/4637, 3 September 2026) list the unique identifier of the digital product passport among the product-identification data an investigating authority may gather, next to HS and CN codes, batch or serial numbers and chain-of-custody evidence. Read more: DPP Beyond ESPR: Forced Labour Guidelines and Public Procurement.

4. Risk assessment and verification

Checks are likely to be triggered by risk factors such as:

product category
route of import
online-marketplace sales pattern
prior non-compliance history
missing or inconsistent operator data
discrepancies between declarations and structured records

5. Enforcement response

If the check reveals missing or inconsistent information, the response may range from additional documentation requests to shipment delays, stronger scrutiny, or refusal to place the product on the market.

Customs and Market Surveillance: Who Does What?

This distinction is important.

Customs authorities

Customs focuses on products at the point of entry and on border-related control functions. In a DPP context, that means customs may increasingly rely on connected systems to verify whether the relevant product information exists and matches the declared product.

Market-surveillance authorities

Market-surveillance authorities focus on compliance inside the market, including investigation, corrective measures, withdrawal, recall, and cooperation with other authorities.

Why the distinction matters less than before

For companies, the practical answer is that the two functions increasingly reinforce each other. Better coordination means the same weak product-data foundation can create problems both at the border and after market entry.

What Importers Will Need to Be Ready For

Importers should not approach this as a pure customs-broker issue. The key challenge is data quality and record structure.

1. Clear product identity

The imported product must be linked to the correct identifier and the correct record. If the identifier logic is inconsistent across supplier, importer, and declared product data, enforcement becomes harder and risk rises.

2. Accessible compliance evidence

If a product category requires DPP-linked information, the importer must be in a position to demonstrate that the record exists, is accessible, and is tied to the right product.

3. Usable operator data

Authorities need to identify the operator responsible for the product. Weak or fragmented operator information makes both customs and market-surveillance checks harder.

4. Better supplier-data discipline

Importers depending on non-EU suppliers often receive evidence in unstructured form: PDFs, declarations by email, fragmented certificates, or incomplete factory information. Importers may need to organise and link this evidence before it can be used reliably in digital checks.

What Is Still Open

Several operational details still need to be settled.

1. The exact border-check workflow is not yet fully published

We know the legal connection deadline and the Registry-side data baseline. We do not yet have the full step-by-step operational manual for DPP-related border enforcement, including risk-selection and user-facing customs procedures.

2. The intensity of checks will vary by product group

Some sectors will face stronger enforcement pressure earlier than others, especially where safety, traceability, or online-import risk is higher.

3. The relationship between DPP records and other customs formalities will continue to evolve

The EU enforcement environment is becoming more integrated, but companies should not assume every system link is already technically complete.

What Companies Can Do Now Without Guessing the Final Rulebook

You do not need every final procedural detail to improve product records and supplier-data processes.

1. Build structured product records, not PDF archives

Border enforcement becomes much easier for authorities when product data is structured, searchable, and linked to identifiers. It becomes much harder when data exists only in attachments and email exchanges.

2. Map which products may face DPP obligations first

Not all products will be checked on the same timeline. Prioritize categories where DPP obligations are confirmed or where preparatory work is already advanced.

3. Fix identifier logic across your supply chain

Make sure the identifiers used internally, by suppliers, and in compliance workflows can be reconciled in a consistent way.

4. Treat importer readiness as a data project

DPP border enforcement is not mainly about label printing. It is about whether the product record behind the label is coherent, accessible, and defensible.

The Strategic Takeaway

The EU is building an enforcement model in which structured product data will matter more at the border than it used to.

Companies that prepare by improving product records, identifiers, and supplier-data workflows are making progress that remains valuable even if the final technical workflow changes.

Improving data quality is useful preparation even while the final enforcement procedures are being developed.

Official Sources

Want to organise product data and supplier documents? Try OriginPass.eu and start preparing your digital product passport.

Continue Reading

Related guides