The DIWASS checklist for carriers: what to fix before the border.
DIWASS lands differently on carriers than on producers or processors. You are the one at the border. You are the one a roadside check stops first when a status does not match reality. This checklist covers what a carrier needs in order to stay ahead of DIWASS rather than react to it.
Six checks before the next cross-border run
None of these are complicated. All of them are the kind of thing that only becomes visible once a truck is already at a barrier.
Confirm registration - not just awareness
Knowing about the DIWASS obligation is not the same as being registered in it. Only registration lets a carrier be named on a notification, so if registration is not complete, it blocks everything else on this list.
Know what you are carrying: Orange or Green List
Registration does not change with the classification, but operational responsibility does. Orange List runs live with no grace period. Green List still has a paper transition, and it ends on 31 December 2026.
Put the DIWASS notification ID on the CMR
The detail carriers miss most often. The notification ID has to travel with the shipment on the CMR for border checks. A correct DIWASS file still causes problems on the road if the number is missing or wrong.
Set the status before the border, not after
The status must be live before the truck crosses - not corrected afterwards. Enforcement runs on live plate recognition, so a mismatch at the moment of scanning stops the truck at the barrier.
Do not assume the rest of the chain is registered
A fully compliant carrier can still be blocked because the producer, processor or broker on that shipment is not registered. Check the chain on fixed routes and long-standing customers, not only on new ones.
Plan for scale, not only for compliance
A handful of cross-border runs a month, and manual portal use is fine. Daily, across several drivers and routes, manual entry becomes a dispatch bottleneck rather than a compliance task.
How a border check actually plays out
Orange List enforcement is not a periodic spot-check. It runs on live database lookups, and that changes what "in order" has to mean.
None of this is discretionary at the moment of the check. Either the record matches the truck, or it does not.
Registration is now a commercial requirement
There is a commercial side to this that has nothing to do with enforcement. Shippers can only select DIWASS-registered carriers when they build a chain, because the system will not let them name a party that does not exist in it.
So an unregistered carrier is not simply delayed - it is off the shortlist entirely. The slot goes to a competitor who registered first, and it usually goes quietly, without anyone explaining why the work stopped coming.
Carrier timing that is not negotiable
Build the status update into the dispatch procedure itself, not into whatever the person on shift remembers to do.
DIWASS for carriers, in short
What does a carrier need to be DIWASS-compliant?
Registration in DIWASS, the notification ID on the CMR, and a status that is live and accurate before the border crossing. Registration alone is not enough - the status timing is what a roadside check actually looks at.
Does the carrier or the notifier get fined?
At a border check, the carrier is fined first. The notification may have been filed by the producer or a broker, but the transport in front of the officer is the carrier's.
Where does the DIWASS notification number go?
On the CMR that travels with the shipment. Border checks match it against the DIWASS record, so a missing or mistyped ID can stop a shipment whose digital file is perfectly correct.
Do Green List shipments need a live status too?
Digital submission is already required, but a transitional arrangement allows paper without sanctions until 31 December 2026. From 1 January 2027 that fallback disappears, so it is worth operating now as if it is already gone.
Can a carrier be blocked by someone else's mistake?
Yes. If the producer, processor or broker on a shipment is not registered, the notification cannot be completed and the shipment does not move - regardless of how compliant the carrier is.
Related DIWASS resources
DIWASS for carriers →
How carriers register, automate status updates, and get the notification ID onto the CMR.
The chain dependency risk →
Why one unregistered partner anywhere in the chain stops a shipment you did everything right on.
Orange List vs Green List →
Which classification applies, and what each one changes about deadlines, documents and lead time.
DIWASS compliance →
Obligations per party, how enforcement works, and a practical compliance checklist.
Keep the fleet moving, not explaining.
Evreka syncs DIWASS statuses straight from dispatch through to the border crossing, so the digital file and the CMR always say the same thing.