Skip to content

What actually happens to a passport at the EU border

The law contains two customs duties and they switched on at different times. One applies from the moment the registry became operational and puts a duty on the person declaring the goods. The other is the automated check everybody is describing, and it applies from the moment an interconnection exists that has not been built. Most published coverage collapses the two, and the gap between them is measured in years.

Sources as at
28 August 2026
Share
LinkedIn X Email
On this page

The short answer

The relevant provision is Article 15 of the Ecodesign for Sustainable Products Regulation, headed "Customs controls relating to the digital product passport". It has two operative limbs and each carries its own commencement.

Article 15(1) is live. Any person intending to place a product covered by a delegated act adopted under Article 4 under the customs procedure release for free circulation "shall provide or make available to customs authorities the unique registration identifier of that product", and the second subparagraph says that duty "shall apply from the moment the registry is operational". The registry became operational in July 2026.

Article 15(2) is not. Customs may release a product only after verifying that the registration identifier and the commodity code correspond to the data stored in the registry. But the second subparagraph of Article 15(2) says that verification "shall take place electronically and automatically via the interconnection referred to in paragraph 3", and that "it shall apply from the moment that interconnection is operational".

The interconnection in Article 15(3) is between the registry and the EU Customs Single Window Certificates Exchange System, and the same paragraph gives it a deadline of four years from the entry into force of the implementing act for the registry. That act entered into force on 6 August 2026. The arithmetic is four years from that date. We publish the arithmetic and not the year, because a date on which a duty applies belongs on the status record and not here.

One more clause deserves reading. Article 15(2) third subparagraph says release for free circulation "shall not be deemed to be proof of compliance with this Regulation or other Union law". The third time the same instrument family has declined to let a procedural event stand in for compliance.

The condition that is doing all the work

The duty in Article 15(1) is narrower than it looks, and the narrowing is in five words: "covered by a delegated act adopted pursuant to Article 4".

Article 4 is the ESPR power to set ecodesign requirements for product groups by delegated act, and what one of those acts decides is a subject in its own right. Where no such act has been adopted for a product group, nothing in Article 15(1) reaches goods in that group, however operational the registry is. The framework works by conferring powers rather than by creating product duties itself, which is why a live registry can coexist with very few mandatory users. Which acts exist, and what has been set rather than merely signalled, is maintained on the status record.

So the honest position for most readers is that neither limb reaches them yet, and the reason is upstream of customs entirely.

Why release for free circulation is not the same as the border

The scoping word in Article 15 is a customs term and it is not a synonym for importing.

Under the Union Customs Code, release for free circulation is the procedure that applies to non-Union goods intended to be put on the Union market or used within it. It collects import duty, applies commercial policy measures and prohibitions and restrictions, completes the other import formalities and confers on the goods the customs status of Union goods. Every other customs procedure leaves them as non-Union goods: transit across the Union to somewhere else, storage in a customs warehouse or free zone, temporary admission for a trade fair, inward processing for re-export.

That has a consequence people find surprising. The passport check is a market entry check, not a border crossing check. Goods moving in transit through the Union, or sitting under a storage procedure with duty suspended, are not within Article 15 at all. They come within it at the moment somebody declares them for free circulation, which may be later, elsewhere and by a different party.

For a business the practical read is that the obligation attaches to the declarant at the moment of market entry, and that whoever makes that declaration needs the registration identifier in hand. The role that carries this is usually the importer, and which role a business occupies is worked through at who carries the obligation.

What can actually stop your goods today

Because Article 15(2) is dormant, the question of what stops a consignment at the moment of release has a different answer, and it is a regime that has been running for years.

Article 15(5) says the whole article is without prejudice to the Union Customs Code and to Chapter VII of Regulation (EU) 2019/1020 on market surveillance. That chapter is headed "Products entering the Union market" and it contains the operative power.

Article 26 of that regulation requires the designated authorities to suspend release for free circulation on any of five grounds. The first is the one that matters here: the product is not accompanied by the documentation required by the Union law applicable to it, or there is a reasonable doubt as to the authenticity, accuracy or completeness of such documentation. The others cover marking and labelling, a falsely affixed conformity marking, an unidentifiable responsible operator, and a catch all where there is cause to believe the product does not comply or presents a serious risk.

What follows is worth knowing because it is a clock. Article 27 releases a suspended product where, within four working days of the suspension, the market surveillance authorities have not asked for the suspension to be maintained. Article 28 covers refusal, and requires customs to enter a specified notice in the customs data processing system where release is refused.

Two readings follow, and they point in opposite directions.

The reassuring one: there is no DPP specific border check operating today, and there will not be one until the interconnection exists.

The less reassuring one: ecodesign law is Union harmonisation legislation, so once a delegated act requires a passport for your product group, a missing or doubtful passport is already documentation missing or doubtful under Article 26(1)(a). The suspension power does not wait for the interconnection. It is the automation that waits.

The commodity code problem nobody has raised

Here is a question this research could not find addressed anywhere, and it is the sort of thing that produces a difficult morning three years from now.

The registry stores the commodity code as registration data, and Article 8(7)(d) of the implementing regulation has the Commission confirm the code's validity against the permitted ranges for the product group at the moment of registration. Article 15(2) of the framework then requires the code presented to customs to correspond to the data stored in the registry.

But a commodity code is not a stable value. The Combined Nomenclature is established under Council Regulation (EEC) No 2658/87, whose Article 12 requires the Commission to adopt a complete version each year, published by 31 October and applying from 1 January following. Codes are created, merged, split and withdrawn on that annual cycle.

So a value that is checked once at registration and then compared against a declaration years later is a value that a different Commission regulation rewrites every January. We did not find any source, at the Commission or elsewhere, addressing what happens to a registration whose stored commodity code has since been withdrawn or split. How this estate types a question in that state, rather than filling it with a confident guess, is set out at how we know.

The practical consequence is not alarming. It is a maintenance obligation nobody has named. Registration data has to be kept accurate and up to date at all times under Article 19(2), the code is registration data, and the code changes on somebody else's calendar.

What is being said, and what is worth ignoring

Three patterns are visible in current coverage and each is worth recognising.

Present tense customs checks. Several pages describe customs verifying passports as something happening now. The Commission's own registry page contributes to this, describing the customs function in the present tense without mentioning the Article 15(2) condition, and vendors are reproducing that sentence.

Confident dates with no arithmetic. Published estimates for when the automated check arrives range across several years. None that we read names the implementing act whose entry into force starts the four year clock, which is the only way to compute it.

Article numbers that do not check out. The one page we found that correctly identifies the interconnection dependency attributes the duty to the wrong article of the framework. Where a page cites an article number, it is worth spending the two minutes to look it up, and where it cites none, that is information too.

The general test is the one that applies across this whole subject. A provision that is written is not a provision that is operating, and a page that does not distinguish the two is not describing the law.

What to do now

  1. Establish whether a delegated act covers your product group. If none does, neither limb of Article 15 reaches you, and everything below is preparation rather than compliance.
  2. Find out who makes your customs declarations. The Article 15(1) duty falls on the person placing the goods under release for free circulation, which is frequently a broker or a forwarder acting for you rather than you.
  3. Decide how the registration identifier reaches that person. It is a value that has to travel from the registry to a customs declaration, and the two systems have no relationship. That is an internal process question and it is answerable now.
  4. Treat the commodity code as a maintained value. Put the annual nomenclature update on the same review cycle as anything else that decays.
  5. Do not buy against the automated check. It is years out on the instrument's own terms and nothing about it can be prepared for today beyond holding accurate data.

The architecture underneath all of this, including what the registry holds and what stays with you, is set out at where your passport data actually lives.

You might want to read next

Since you have read this, these may answer the questions that usually come next.

Sources

Worth sharing?

Help someone else make sense of product passports.

LinkedIn X Email