Movement and customs context on the record.
Departure, transshipment, arrival, and customs context are recorded against the shipment as it moves. ETA changes are logged, and the people who need to know are identified.
What it does
Tracking updates are easy to get and hard to use. A carrier portal shows a vessel's position; a forwarder emails a revised ETA; a broker mentions that entry is filed. Each update is accurate at the moment it is sent and disconnected from everything else.
Importcommand records milestones on the shipment record: booked, departed, transshipped, arrived, customs context as reported by your broker, and released or delivered. Each milestone has a source, a timestamp, and, where relevant, a change history, so an ETA that moved three times is visible as such.
Because milestones sit next to documents and costs, a delay is immediately seen in context: is the document set complete for the new arrival date, does demurrage risk change, and who should be told.
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.
- Milestones are recorded per shipment with source and timestamp.
- ETA changes are logged with the previous value, so drift is visible.
- Customs context (for example, entry filed or released) is recorded as reported by your broker.
- A milestone change can raise an exception with an owner when it affects readiness, cost, or downstream plans.
- Milestone status rolls up to the dashboard's "what is moving" view.
In the workspace
Movement timeline
Booked, departed, transshipped, arrived, released: the shipment's path in one line.
ETA history
Every revision with when it changed and who reported it.
Customs context
Entry and release information as your broker reports it, alongside the documents it depends on.
Linked exceptions
An ETA slip that matters becomes an owned item, not a note.
Who to tell
The warehouse, purchasing, or finance contact attached to the shipment is identified when a milestone changes.
Lane view
All shipments on a lane or with a carrier, side by side.
Boundary
Importcommand records milestones as reported by your carriers, forwarders, and brokers. It does not operate vessels, book freight, or determine customs status; it organizes the information those partners provide.
Common questions
Where do milestone updates come from?
From your partners and, where integrations are in scope, from their systems. The pilot maps which updates arrive how, so nobody re-keys them.
Are updates automatic?
Where an integration is agreed during the pilot, updates can flow automatically. Otherwise they are recorded by your team or by partners with scoped access.
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.