Cold Open
The exporter and importer both agree.
The shipment still cannot move.
Because a transit country on the route has not been notified, and Basel does not treat that as a minor detail.
Bilateral comfort is not chain-wide consent.
Article 6 Basel requires written consent from competent authorities before controlled waste movement begins.
The Scene
Part 1 built the file.
Now the file has to travel through governments.
The exporting country competent authority notifies. The importing country reviews. Transit countries may need to consent. Some countries have national forms, additional annexes, translation expectations, fee structures, or submission portals.
A team that prepared the right documents can still lose time by submitting them through the wrong path.
Submission is not clerical. It is route execution.
A Basel notification is only complete when every country in the movement chain is accounted for.
The Trap
Most operators focus on exporter and importer.
That feels logical.
But the route is larger than the buyer-seller relationship. A container may pass through ports, waters, or territories where transit notification applies. If that state is missing from the consent chain, the movement has a weak link.
The wrong competent authority creates the same problem.
The file may be prepared, but it is not moving through the right government door.
Field Warning: Submitting to the wrong authority is one of the most preventable causes of notification delay. Verify export, import, and transit contacts separately.
The Operator Moment
This is where timing gets expensive.
A recycler can lose days confirming contacts. A broker can lose credibility with a buyer. A port booking can age while the file waits for one country-specific requirement nobody checked.
This is why DeX treats country rules as part of the movement, not a footnote.
The route decides the consent map.
If the container crosses the country, the file has to respect the country.
The Field Rule
Map the authority chain before submission.
List the exporting country, importing country, and every transit country. Confirm the competent authority for each. Then identify country-specific submission rules, fees, language requirements, portals, response timelines, and additional documents.
Do not send a Basel file into the system blind.
Send it with a route map.
Confirm export, import, and transit countries before filing.
Verify the competent authority for each country separately.
Check country-specific forms, fees, portals, and language rules.
Track written consent status by country, not by shipment only.
Do not move until the required consent chain is complete.
Up Next
Once teams understand submission, the next shock is the size of the evidence package itself.
The notification form is not the full dossier.
Read next: DexMetal Field Notes — Episode 07: The 20-Annex Package Nobody Tells You About
DeX Sign-Off
DeX maps every country in the chain before quoting a timeline to any buyer.
Transit consent is not a formality. It is a government decision that moves at government speed.
The buyer does not see the transit problem until the shipment stops. By then the timeline is already broken.
Map the chain first. Quote the timeline second.
CTA: Use the Basel API to pull competent-authority contacts for every country in your route.
Related Reading
Basel notification documents and structure
20-annex supporting document package
Basel competent authority API lookup
Basel transit country notification requirements
Basel consent timelines by importing country
Episode 07: The notification was submitted. The annex package was missing one document. The kind no one thinks to ask for until the authority does.