Follow-ups that keep their context.
Suppliers, forwarders, and customs brokers are part of every import. Importcommand keeps each request and reply tied to the shipment and order it concerns, so the conversation never drifts away from the record.
What it does
A typical import involves at least three external parties, each with its own communication channel. The supplier replies by email, the forwarder updates a portal, the broker asks a question in a chat. The answers exist, but they are attached to a person or an inbox rather than to the shipment.
Importcommand treats a follow-up as a first-class item on the record: who was asked, what was asked, when, and what came back. Requests can be raised from a document, a milestone, or an exception, and the reply lands in the same place.
The result is that "who needs to respond" becomes a dashboard view rather than a memory exercise, and that a colleague covering for someone can see the full exchange without forwarding emails.
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.
- A request is raised from the item it concerns: a document, a milestone, an exception, or a cost line.
- Each request has a recipient partner, an owner on your side, a due date, and an age.
- Replies attach to the request and update the underlying item's status.
- Open requests roll up to the dashboard's "who needs to respond" view.
- Partners with scoped access can answer directly in the workspace; others reply by email and the exchange is recorded on the record.
In the workspace
Open requests
Every outstanding ask, grouped by partner, with age and owner.
Partner view
What each supplier, forwarder, or broker currently owes across your shipments.
Aging and due dates
Requests waiting longer than expected surface in the attention list.
Attached context
The reply sits next to the document or milestone it answers.
Cross-shipment view
See all open items with one forwarder across every active shipment.
Scoped access
Partners see only the records and items they are involved in.
Boundary
Importcommand records and organizes exchanges with your partners. It does not act as your agent with them and does not replace the contractual relationship between you and your carriers, forwarders, or brokers.
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.