One operational record for every import.
Importcommand brings orders, shipments, documents, partner follow-ups, tracking updates, exceptions, and landed-cost views into a single connected workspace, so your team knows what is moving, what is missing, and who needs to respond.
What Importcommand really is
An import operations management platform that consolidates scattered import information into a single operational record per shipment. From order readiness to arrival, every document, partner reply, milestone, exception, and cost stays on the record it belongs to.
Request a pilotOne operational record
Orders, shipments, documents, partner follow-ups, tracking updates, exceptions, and landed-cost views in one connected workspace.
A source of truth
The overview dashboard shows what is moving, what is missing, who needs to respond, and what requires attention, together.
Clearly bounded
US ocean import and Mexico definitive ocean import. It does not file customs, move cargo, or replace brokers, forwarders, or carriers.
You won’t need to open five tools to know where a shipment stands. The record is quiet. The dashboard is sharp. Scattered means slow. One connected record means your team acts on what needs attention today.
One connected record for every import
Spend less time reconstructing and more time executing. The operational record works quietly underneath the day: every document, partner reply, milestone, exception, and cost line lands on the shipment it belongs to, and the dashboard reads from the same place your team works.
What is the operational record? +
It is the single record Importcommand keeps for one shipment, from order readiness to arrival. Six structured layers, one owner, and a full history, shared by importers, logistics, purchasing, finance, and the partners you grant scoped access to.
Import information is scattered by default.
Spreadsheets, inboxes, carrier portals, and chat threads each hold a piece of the picture. Importcommand replaces that fragmentation with one record per shipment that everyone works from.
From order readiness to arrival, in one line.
Each stage writes to the same record, so a document collected at stage two is already visible when an exception surfaces at stage four.
Create the record
Start from the order: supplier, terms, expected quantities, and target arrival.
- Order readiness
- Linked purchase order
- Assigned owner
Collect documents
Request, receive, and check the required document set against the record.
- Invoice, packing list, B/L
- Follow-ups keep context
- Readiness at a glance
Track milestones
Departure, transshipment, arrival, and customs context tied to the shipment.
- ETA changes logged
- Partner updates attached
- Who needs to respond
Manage cost & exceptions
Exceptions gain an owner and a next action. Landed-cost views stay current.
- Gaps and delays
- Customs context
- Clear next step
A source of truth for the daily questions.
The dashboard shows shipment status, document readiness, open items, and attention priorities together, so the morning check-in takes minutes, not a tour of every inbox.
What is moving?
Every shipment with its current milestone and expected arrival.
What is missing?
Documents and confirmations still outstanding per record.
Who needs to respond?
Open requests to suppliers, forwarders, and brokers, with age.
What needs attention?
Exceptions with an owner and a next action, ranked by impact.
What one record replaces.
Figures drawn from how the workflow is structured: one record per shipment, four daily questions, seven handoffs.
Two workflows. Every milestone on the record.
Ocean shipments into US ports and definitive ocean imports into Mexico. Each lane produces the same kinds of events, from booking to release, and each event lands on the shipment record with its source and timestamp.
Six layers, one shipment.
A record is not a folder of attachments. Each layer is structured, has an owner, and updates the others. A milestone change can open an exception; an exception can change a cost line; a received document changes readiness on the dashboard.
- Order readiness: supplier, incoterm, quantities, target arrival, owner
- Documents: the required set, status per document, request history
- Partner follow-ups: every ask and answer, tied to the item it concerns
- Milestones: movement and customs context with source and timestamp
- Exceptions: owner, next action, due date, cause, resolution
- Landed cost: estimated versus confirmed lines, totals on the header
Seven parties. One place they meet.
An import passes through the supplier, the forwarder, the carrier, the broker, the customs authority, your warehouse, and finance. Each is responsible for its own step, and Importcommand does not take any of those steps over. What it does is give every handoff a place on the record, with scoped access for the partners who need it, so context is never rebuilt from an inbox.
Your partners stay in charge
Brokers file, forwarders arrange, carriers move. Importcommand never submits a customs filing or acts on your behalf. It marks every record with what it is: organized by software, verified by people.
What changes on a Tuesday.
The value of one record shows in ordinary days, not in demos. This is what the same morning looks like for a team working from the operational record.
Dashboard scan
Three shipments moving, two missing documents, four partners yet to answer, one item needing attention. Ordered by impact, before the first email is opened.
One request, in context
Purchasing asks the supplier for the packing list from the document itself. The request carries the shipment, the order, and the due date. No forwarded thread.
An ETA slips
The forwarder reports arrival moved three days. The milestone updates, the previous ETA is kept, and the warehouse contact on the record is identified.
An exception with an owner
The slip opens an exception: owner logistics, next action to confirm the receiving slot, due today. Demurrage risk is linked to the cost view.
Costs, current
The broker confirms duties. The landed-cost line moves from estimated to confirmed and finance sees the same total operations does.
The same import, two ways of working.
Scattered
- Tracking spreadsheet updated by one person, read by nobody else in time
- Packing list "sent" in an email thread the broker was never on
- ETA change noticed when the arrival notice arrives
- Landed cost assembled weeks after delivery
- Exceptions handled by whoever saw the message first
- Status meetings to rebuild a picture that existed in pieces
One operational record
- One record per shipment that every role works from
- Documents tracked per shipment with readiness the broker can see
- ETA revisions logged with who reported them and who was told
- Landed-cost lines moving from estimated to confirmed as the shipment moves
- Exceptions with an owner, a next action, and a due date
- A dashboard that answers the four daily questions
Shared import information across the team.
Importers
See every inbound order and shipment as one record, from the first supplier confirmation to arrival at the warehouse.
Logistics teams
Track milestones and partner responses without re-keying carrier updates into a sheet nobody else can find.
Purchasing teams
Know which documents are outstanding from which supplier and keep every request tied to the right order.
Specific import workflows, clearly bounded.
Importcommand is built for named import scopes rather than a generic "supply chain" promise. Additional country workflows are only available when enabled for your workspace.
Ocean imports into the United States
Order readiness, document collection, milestone tracking, ISF and entry context, and landed-cost views for FCL and LCL ocean shipments.
Mexico definitive ocean import · v1Definitive ocean imports into Mexico
The same connected record adapted for definitive import into Mexico: document set, broker (agente aduanal) handoffs, and port milestones.
What Importcommand does not do
It does not transport cargo, does not submit official customs filings, and does not replace carriers, forwarders, or customs brokers. It organizes the work around them. High-impact operational and compliance decisions still require human verification.
We start with one shipment, not a migration.
A controlled pilot takes one representative shipment process and maps every handoff. It evaluates fit, integrations, partner access, security and data controls, and what migration would actually require, before anyone commits.
Pick one representative shipment
A real order with a real supplier, forwarder, and broker.
Map the handoffs
Who sends what, when, and where it currently gets lost.
Run it in Importcommand
Documents, tracking, exceptions, and costs on one record.
Decide with evidence
Fit, access, security, and migration needs, written down.
Does Importcommand file customs entries?
No. It does not submit official customs filings and does not replace customs brokers, forwarders, or carriers. It organizes the documents, follow-ups, and context around them.
How long is a pilot?
One representative shipment, end to end. The scoping call sets the exact scope; the evaluation is written down so the decision has evidence behind it.
Can our broker and forwarder use it?
Yes, with scoped access configured per workspace: a broker sees the shipments it handles, a supplier the documents it owes.
Is pricing public?
No. Pricing is tailored per company based on volume, workflows, integrations, and pilot scope, and shared after the pilot.
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.