Operations guide

Import shipment workflow: owned decisions from readiness to completion

A useful import workflow does more than display a vessel position. It shows the current milestone, the evidence required to complete it, the partner who owns the next response, and the fallback when that response does not arrive.

By Ayhan Karaca, Co-Founder · Updated: August 26, 2026

1. Readiness, booking, and stuffing

The importer creates the shipment and identifies the supplier, freight forwarder, and customs broker. The supplier confirms a readiness date. The forwarder then provides booking details such as stuffing date, port of loading, ETD, vessel, and shipping line when available.

At stuffing, the workflow records whether cargo was loaded, cancelled, or moved to a new date. A date change returns ownership to the booking/readiness step instead of pretending the old schedule remains valid.

  • Track the requested response, expiry, follow-up count, and last outcome.
  • Reset the relevant follow-up cycle when a partner supplies a valid pending or changed state.
  • Escalate to the importer when configured attempts are exhausted.
Original process map: evidence and ownership move forward together; an exception returns to the accountable decision instead of bypassing it.
Read the process map transcript

Stage one confirms readiness and ownership. Stage two records booking and stuffing evidence. Stage three collects shipping and customs documents. Stage four monitors sailing, ETA, and exceptions. Stage five completes clearance, cost evidence, and the operational handoff. Any missing or changed evidence routes back to its accountable owner before the next decision.

2. Shipping and customs documents

After stuffing, the working set can include HBL and ISF context, followed by commercial invoice and packing list collection. The customs broker remains the qualified party for filing and clearance decisions; Tyllus coordinates the request and stores the resulting evidence.

For US-bound ocean cargo, confirm current ISF requirements with CBP and your broker. A software milestone does not prove that a filing was timely, complete, or legally accepted.

3. Sailing, ETA, clearance, and completion

Once the shipment is sailing, teams monitor ETA and movement updates alongside documents and open actions. As arrival approaches, they review missing documents and the broker's clearance or hold status.

A released shipment may add CBP Form 7501 context, the customs broker invoice, and the freight forwarder invoice. Completion means the operating evidence is present and reviewed; it does not erase the need to retain records under the policy that applies to the importer.

Example decisions, supporting evidence, and operational limits near arrival
DecisionSupporting evidenceOwnerLimit
Respond to an ETA changeCarrier or forwarder update, previous ETA, and source timestampLogistics ownerETA is an estimate, not a delivery guarantee
Resolve clearance stateBroker response and applicable entry evidenceQualified customs ownerTyllus coordinates; it does not make the customs decision
Close the shipment workflowRequired handoffs, documents, and accepted cost recordsImporter operations ownerCompletion does not replace the applicable retention policy

Professional responsibility remains outside the workflow

Tyllus coordinates information and follow-ups. It does not transport cargo, file an ISF or entry, decide classification, calculate a binding duty, or replace a licensed customs broker.

Turn the sequence into an owned operating queue.

Compare this lifecycle with your actual partner handoffs and identify where the next action becomes invisible today.