Treat a border hold like a production incident. You need the error message, the owning team, an escalation path and a post mortem. Skipping the first step is the most common mistake, because teams start phoning suppliers before they know which check failed.
Step 1: Get the error, in writing
Contact the border control post or your customs agent and request the hold reason in writing. Verbal reasons get misremembered and misrouted. The written reason tells you whether this is documentary, identity or physical, and that determines everything downstream.
Step 2: Route to the correct owner
| Failure | Owner |
|---|---|
| Delisted establishment code | Supplier and their competent authority |
| Invalid or incorrect code | Importer or customs agent |
| CHED error or late submission | Importer or agent at the border control post |
| Certificate mismatch | Exporting country's competent authority |
| Seal or identity failure | Carrier or exporter |
| Physical check finding | Exporter or producer |
A structured approach to troubleshooting a held EU consignment starts with routing, not with phone calls.
Step 3: Set expectations on time
Simple queries clear in hours. Certificate replacements routinely take days. Communicate the realistic window to commercial stakeholders early rather than optimistically.
Step 4: Track the cost while it runs
Log demurrage, storage and temperature risk as the hold continues. This is your business case for prevention.
Step 5: Post mortem
Run a root cause review after resolution. Refusals are recorded in TRACES and visible across the EU, which can raise inspection frequency on future loads.
FAQ
What if the code cannot be listed?
The consignment cannot clear, and unresolved cases can end in re-export or destruction.
Watch a demo to see how a compliance dashboard turns border exceptions into tracked, owned incidents.
Top comments (0)