Importcommand
Workflow · US ocean import v1

Ocean imports into the United States.

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

US ocean import is the first scope Importcommand supports. The workflow reflects how a typical US import actually runs: the supplier confirms the order, the forwarder books and ships, the broker files the Importer Security Filing before departure and the entry before or on arrival, and the cargo is released, picked up, and delivered.

Each of those handoffs produces information that usually lives in a different place. In Importcommand they land on one record, so the document set, the ISF confirmation, the vessel milestones, the entry status as your broker reports it, and the costs are visible together.

The connected workflow

How the record moves in this scope

Stage 1

Order readiness

Record created from the confirmed PO: supplier, incoterm, quantities, target arrival, owner.

Stage 2

Documents and ISF context

Commercial invoice, packing list, and B/L collected; ISF confirmation from the broker recorded against the shipment before departure.

Stage 3

Movement and entry context

Departure, transshipment, and arrival milestones; entry and release information as reported by the broker.

Stage 4

Exceptions and cost

ETA changes, holds, exams, and demurrage risk owned and actioned; landed-cost view moves from estimated to confirmed.

Document set

Typical required documents

A starting set for this scope. The pilot confirms the exact set for your products and lanes, and individual shipments can add documents.

DocumentWhy it mattersUsually owned by
Commercial invoiceBasis for valuation and classification by your broker; must match the order and packing list.Supplier
Packing listQuantities, weights, and packaging per line; needed for entry and for receiving.Supplier
Bill of ladingContract of carriage and title document; required for release.Forwarder / carrier
ISF (10+2) confirmationConfirmation that the Importer Security Filing was submitted before vessel departure.Broker
Arrival noticeCarrier notice with arrival details and charges due.Carrier / forwarder
Entry and release documentsEntry summary and release information as filed by your broker.Broker
Product-specific certificates or permitsDepends on the product (for example, FDA, USDA, or other agency requirements).Supplier / importer
Handoffs

Partners in this workflow

Supplier

Confirms the order and provides the commercial documents. Sees only the documents it owes on the shipments it supplies.

Forwarder and carrier

Books, ships, and reports movement. Provides the B/L and arrival notice; updates milestones.

Customs broker

Files ISF and entry, reports status, and advises on classification and requirements. Sees the shipments it handles.

Notes

Things to know

  • ISF must be filed before the vessel departs the foreign port; Importcommand records the confirmation from your broker and flags shipments approaching departure without one.
  • Entry, release, and any exam or hold are recorded as reported by your broker; Importcommand does not file or query CBP systems.
  • Landed-cost lines typically include ocean freight, duties and fees as determined at entry, broker fees, port and terminal charges, drayage, and any demurrage or detention.
  • Product-specific requirements (other government agencies) vary; the pilot maps which apply to your products so the required set is correct from the first shipment.

Boundary

Importcommand does not submit official customs filings, does not act as importer of record or customs broker, and does not transport cargo. Customs entries, classifications, valuations, and payments are handled by your licensed broker and by you as importer. Regulatory requirements change; verify current requirements with your broker and the relevant authorities.

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.