Documents, tracked per shipment.
Each import scope defines a required document set. Importcommand tracks that set per shipment, shows readiness at a glance, and keeps every request and reply tied to the document it concerns.
What it does
Document collection is where imports slow down quietly. A commercial invoice arrives with the wrong incoterm, a packing list is promised but never sent, a bill of lading copy is in someone's inbox but not where the broker can see it. None of these are dramatic; all of them delay clearance.
Importcommand gives each shipment a required document set based on its scope: for example commercial invoice, packing list, bill of lading, and the certificates or permits your products need. Each document has a status, an owner, and a history of who was asked, when, and what came back.
Document readiness rolls up to the record and to the dashboard, so purchasing sees what they still owe, logistics sees whether the set is complete before the vessel arrives, and the broker sees the same documents your team sees.
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.
- The required set is defined per scope and can be extended per shipment (for example, a specific certificate for a product category).
- Each document carries a status: required, requested, received, checked, or missing.
- Requests to suppliers and replies attach to the document and to the shipment.
- Readiness is visible on the record header and in the dashboard's "what is missing" view.
- Scoped partner access lets a supplier upload only the documents it owes.
In the workspace
Required set
The documents this shipment needs, with a status for each and the person responsible.
Request history
Every ask and answer per document, so nobody sends the third reminder for something already received.
Readiness roll-up
A single readiness state for the shipment that the dashboard and the broker can rely on.
Aging
How long each outstanding document has been waiting, and on whom.
Supplier access
A supplier sees only the documents it owes on the shipments it supplies.
Checked, not just received
A received document can be marked checked once someone has verified it, keeping a clear distinction.
Boundary
Importcommand tracks and organizes documents. It does not validate documents against customs regulations or submit them to authorities. Verification of compliance-critical documents remains with your team and your broker.
Common questions
Can the required set differ between the US and Mexico workflows?
Yes. Each scope carries its own required set, and individual shipments can add documents on top.
Does Importcommand store the documents themselves?
Documents can be attached to the record and are held within your workspace, subject to the access scopes you configure. Retention follows the customer agreement.
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.