Frequently asked questions.
Short answers about scope, boundaries, onboarding, and access.
What is Importcommand?
Import operations management software that consolidates orders, shipments, documents, partner follow-ups, tracking updates, exceptions, and landed-cost views into one operational record per shipment, with an overview dashboard as the source of truth.
Which import workflows are supported?
US ocean import (v1) and Mexico definitive ocean import (v1). Additional country workflows are available only when enabled for your workspace.
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.
Does it move cargo or book freight?
No. Importcommand does not transport cargo or act as a forwarder or carrier.
How does onboarding work?
Pilot first. We take one representative shipment process, map the handoffs (supplier, forwarder, broker, documents, tracking, customs, costs), run it on a single record, and evaluate fit, integrations, partner access, security and data controls, and migration needs.
Can external partners access the workspace?
Yes, with scoped access configured per workspace. A supplier can be limited to the documents it owes; a broker to the shipments it handles.
Who uses it day to day?
Importers, logistics teams, and purchasing teams, working from shared import information. Finance typically uses the landed-cost views.
Is pricing public?
No. Pricing is tailored per company based on volume, workflows, integrations, and pilot scope.
Does the software make decisions automatically?
It surfaces and organizes. High-impact operational and compliance decisions require human verification.
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.