Changes and gaps, with an owner.
ETA slips, missing documents, customs questions, and cost surprises are normal. Importcommand gives each one an owner, a next action, and a place in the attention list, so exceptions are handled rather than noticed.
What it does
Most import problems are not surprises to everyone; they are surprises to the wrong person. The forwarder knew the vessel was delayed, the supplier knew the packing list was late, the broker knew a question was pending. The gap is ownership: nobody on your side was clearly responsible for the next step.
In Importcommand an exception is raised on the record, from a milestone change, a document gap, a partner reply, or manually. It carries an owner, a next action, a due date, and a link to whatever caused it. It stays open until it is resolved, and its history remains on the record.
The dashboard's "what needs attention" view orders open exceptions by impact, so the morning check starts with the items that can still change today's outcome.
How it lives on the operational record
Every capability in Importcommand writes to the same shipment record. Nothing here is a separate module with its own list; it is a view of one record.
- Exceptions can be raised from milestones, documents, partner replies, or by a person.
- Each exception has an owner, a next action, a due date, and a cause.
- Resolution is recorded, including what changed on the record as a result.
- Exceptions roll up to "what needs attention" and are ordered by impact.
- High-impact operational and compliance decisions are flagged for human verification before they are treated as resolved.
In the workspace
Attention list
Open exceptions across all shipments, ordered by impact and age.
Ownership
Who is responsible for the next step, visible to everyone on the record.
Next action and due date
What happens next and by when, so nothing waits silently.
Cause and effect
The milestone, document, or reply that raised the exception, linked.
Resolution history
How past exceptions on this lane or supplier were resolved, for the next time.
Verification checkpoint
Decisions with compliance or cost impact require a person to confirm.
Boundary
Importcommand surfaces and organizes exceptions. It does not decide how to resolve them. Decisions with operational or compliance impact remain with your team and your broker.
Start with one representative shipment.
A controlled pilot maps your handoffs, checks fit and integrations, and shows what a single operational record changes for your team.