Importcommand
Scope & boundaries

Named import scopes, explicit limits.

Importcommand is positioned for two workflows today. It organizes the work around your partners; it does not replace them.

US ocean import · v1

Ocean imports into the United States

FCL and LCL ocean shipments arriving at US ports: order readiness, document collection, milestone tracking, ISF and entry context from your broker, and landed-cost views.

Mexico definitive ocean import · v1

Definitive ocean imports into Mexico

Definitive import (importación definitiva) by ocean: document set, agente aduanal handoffs, port milestones, and cost views on the same connected record.

Additional country workflows are available only when enabled for your workspace. If your imports fall outside these scopes, tell us during the pilot request and we will say plainly whether there is a fit.

Boundaries

What Importcommand does not do

Being clear about limits is part of being a reliable source of truth.

  • Does not transport cargo
  • Does not submit official customs filings
  • Does not replace carriers, forwarders, or customs brokers
  • Does not make high-impact operational or compliance decisions for you; those require human verification

Not sure your workflow fits?

Describe your import process in a pilot request. If the scope does not match, we will tell you directly.