Guide

U.S. import container exception management.

U.S. import operations break down when teams cannot tell which containers changed, which shipments need action, and which customers need a new update.

Reviewed July 3, 2026

Container tracking

Track a container while this is fresh.

Use the same workflow after the guide: enter a container number and work email, then create the trial workspace that saves the shipment.

30-day free trialNo credit card requiredContainer-number firstCoverage caveats shown

Track one container free. Your 30-day trial starts when you create the account.

The real problem is exception volume

Most import teams are not struggling because they cannot check a single container. They struggle because dozens or hundreds of containers require review, and only a few actually changed in a way that matters. The work is identifying the exceptions before they become warehouse, dispatch, or customer-service problems.

What to classify daily

Separate containers into simple operating groups: unchanged and on plan, ETA changed, discharged or available, held or missing an expected event, inland move pending, customer update needed, and free-time risk. This gives the team a shared language for deciding what gets attention first.

  • Changed ETA
  • Hold or missing milestone
  • Drayage or warehouse impact
  • Customer update required

Why this matters for U.S. gateways

U.S. imports often move from vessel arrival into terminal availability, rail, truck pickup, distribution-center appointments, and empty return. A delay at one step can create a scheduling problem two steps later, especially when the team is still working from yesterday's status.

How to make the workflow stick

Assign daily ownership, review changed containers first, document what was communicated to customers, and keep the container record visible to everyone involved in freight operations. CargoScope supports this by centralizing container status and alert context.

Example workflow

A logistics team adds a container number, watches milestone and ETA changes in CargoScope, receives a delay alert, and uses the dashboard to prioritize the next customer or operations update. The workflow is intentionally practical: start with the container, identify what changed, decide whether the shipment needs action, and keep the team aligned on the same record.

Operational checklist

Use the guide to define what your team should review daily: active containers with changed ETAs, shipments approaching port availability or last-free-day risk, containers with holds or missing milestones, and customers waiting on updated delivery timing. A good container visibility process should reduce repeated manual checks, not create another inbox for status noise.

  • Review changed ETAs before customer update meetings
  • Flag containers that may affect drayage, warehouse labor, or delivery appointments
  • Keep unsupported workflows, such as B/L tracking, clearly marked as coming soon

How CargoScope supports the work

CargoScope is built for container-number tracking today. It helps teams centralize available milestones, ETA changes, delay signals, and exception context so operators can spend less time switching between carrier portals and more time acting on containers that need attention.

FAQ

What teams ask first.

Who is this guide for?

It is written for freight forwarders, shippers, importers, exporters, logistics managers, and operations teams improving ocean container visibility.

Can CargoScope track by Bill of Lading today?

Not yet. Bill of Lading tracking is coming soon. CargoScope currently focuses public tracking on container numbers.

What problem should this workflow solve?

The goal is to reduce repetitive status checks, catch shipment changes earlier, and help freight teams prioritize containers that affect customers, drayage, warehouses, or avoidable accessorial cost exposure.

Start tracking containers with CargoScope.

Track a container free, review open pricing, or create an account when you are ready to save shipments.