Solutions
Who We Serve
Our Solutions
Who We Serve
🏭 Waste Producers

Every shipment needs a DIWASS notification before the truck leaves.

Your Eural code must match your processor's permit - validated in real-time by DIWASS before departure. One mismatch, one missing pre-notification, and the truck stays at your gate.

Your DIWASS readiness
DIWASS notification filed before departure
For Orange List (Annex IA/IB): mandatory digital before departure. For Green List (Annex VII): transitional period until Dec 31, 2026, but DIWASS registration required now.
Eural code matches processor permit
DIWASS validates this in real-time - mismatch = blocked
Carrier has active DIWASS account
You cannot select an unregistered carrier in your notification
Processor registered in DIWASS
Processor's DIWASS ID required to complete notification
DIWASS status = Announced
Confirmation that DIWASS accepted your document
Chain partner DIWASS IDs verified
All regular partners verified for DIWASS registration
0 / 6 items completed
Your specific risks

What DIWASS means for producers

🚫
Shipment blocked at gate

If DIWASS hasn't confirmed your Annex VII as "Announced" before loading begins, the truck legally cannot depart. No override.

⚠️
Eural/permit mismatch

DIWASS checks your waste code against your processor's permit in real-time. An incorrect code blocks the notification before departure.

🔗
Chain dependency

Your carrier and processor must both be DIWASS-registered. You cannot name an unregistered party in your notification.

⏱️
2-day pre-notification window

Annex VII must be in DIWASS at least 2 working days before departure. Your current same-day process does not comply.

How Evreka helps

Remove every blocker

📄

Wasteform for producers

Create and submit Annex VII documents from your existing transport records. DIWASS ID returned automatically. No portal.

✅

Eural validation at source

Waste code validated against processor permit before your team confirms any transport. Catch mismatches at your desk.

🔗

Chain verification

All your regular carriers and processors verified for DIWASS registration at booking stage. No surprises on departure day.

🔔

2-day alert system

Automatic reminder 2 working days before departure if DIWASS document is not yet filed. Nothing slips through.

Your compliance load

How many DIWASS notifications does your operation generate?

Every outbound cross-border shipment is a notification. Every notification is a deadline. Calculate your monthly compliance load.

15
Annex VII notifications
(Green List)
10
Orange List notifications
(mandatory since May 21, 2026)
25
Total notifications
to manage per month
Each notification requires: pre-notification filing (2+ working days before departure), status updates at departure, chain party verification, and receipt tracking on arrival.

Every cross-border hazardous shipment now needs DIWASS.

Every day without a DIWASS-ready process is a day of compliance risk. Let's close that gap.

On this page