Customs compliance doesn’t stop at filing the declaration. The real challenge is keeping visibility across where your entry stands—has the number been assigned, has Customs received it, is it cleared, or is it stuck?
CargoWise solves this with status events—system-driven milestones that can also power workflows. By linking workflows to status codes, you can turn compliance updates into action, automation, and visibility across your business.
Let’s walk through some key examples.
1. CEN – Customs Number Entered
This event is triggered when the entry number is allocated.
💡 How to use it:
- Trigger an internal notification to let operations know the declaration has been registered.
- Start the “clock” on measuring clearance times.
2. ECM – Export Customs Commenced
This event is added when the export declaration is first sent to Customs (e.g., Taiwan Customs).
💡 How to use it:
- Trigger workflow tasks to confirm export docs are complete.
- Update milestones for visibility on the export filing.
3. ECC – Export Customs Cleared
This event is added when export clearance is received from Customs.
💡 How to use it:
- Automatically update the shipment milestone to “Cleared for Export.”
- Trigger customer notifications confirming the export release.
4. CCC – Customs Commenced
This event is triggered when the import declaration is first sent to Customs.
💡 How to use it:
- Create a workflow task to validate entry data matches invoice values.
- Kick off any importer-specific checks before clearance comes back.
5. CLR – Customs Cleared
This event is triggered when Customs clearance is received on an import declaration.
💡 How to use it:
- Update milestones to show cargo is cleared and ready for delivery.
- Trigger billing workflows (e.g., duty, brokerage fees).
- Send client-facing “Cleared” notifications automatically.
6. CES – Customs Entry Status
This event updates when the status of the import or export declaration changes.
💡 How to use it:
- Use CES as a “catch-all” event to trigger reports.
- Drive exception management workflows when statuses move from “Filed” to “Held” or “Queried.”
Workflows: Turning Events into Action
The real power of CargoWise events comes when you link them into workflows:
- Automate tasks: clearance = create delivery order.
- Trigger notifications: entry number assigned = customer update.
- Drive visibility: events feed dashboards and reports so management sees real-time clearance performance.
⚡ Pro tip: Use milestones to trigger email notifications. For example, if a declaration hits DCR (Declaration Rejected), CargoWise can automatically send an alert email to your team or even directly to your client. No more manually checking declaration status, and no more manually sending follow-up emails—CargoWise handles it for you.
Instead of treating events as just system stamps, they become operational drivers that cut down on emails, manual follow-ups, and delays.
The Takeaway
CargoWise status events aren’t just markers in the customs process—they’re levers for automation, visibility, and efficiency.
By building workflows around events like CEN, CCC, CLR, CES, and even DCR, you reduce manual work, improve communication, and set your business up for smoother compliance.
✨ At ALL2S Consulting LLC, we help brokers and importers configure CargoWise events and workflows so compliance runs smoother, customers stay informed, and teams spend less time chasing updates.
📌 Coming Next (Article 7): We’ll explore exception management in CargoWise—how to handle RFIs, holds, and exams efficiently.
ALL2S CONSULTING LLC 