How to Track Multiple Containers Across Carriers in One Place

Quick answer: You do not need ten tabs. Pull every BL and container into one shared view, normalize times, and set alerts on the milestones that matter. Anchor plans to Loaded and Transport Departure. Use a simple ETA policy so everyone acts on the same signal.

Why multi carrier tracking feels messy

Planned versus actual: Portals often show planned legs until the first actual event posts. ETAs move when that cutover happens.
Different handoffs: Terminals, feeders, and mainline systems post on different clocks. Your view updates after those handoffs.
Transshipment naming: Outbound vessels can be pending until assignment is firm. Names appear after loading is confirmed.
Time zone mix: Local time on one page and UTC on another creates false drift if you do not normalize.

You can tame this with one shared view and clear rules. The event logic is standardized across lines even if the labels differ.

What a unified view must include

Inputs: BL number, container number, booking number, carrier name.
Core milestones: Gate In, Loaded, Transport Departure, Discharged, Gate Out.
Two clocks: Event time in local port time and UTC in ISO 8601 format. Include IANA time zone labels.
ETA rule: Accept the most recent ETA only after Loaded on the outbound vessel, or after Transport Departure if rolling risk is high.
Evidence link: Link each event to a screenshot or export. No guesswork.

Three setup paths that work

1) No code baseline

Create a sheet with columns for BL, container, carrier, milestone, event time local, event time UTC, first seen, ETA now, evidence link.
Collect events from carrier portals. Paste links to each capture. Use data validation for milestone names.
Share the sheet. Decisions use this as the source of truth.

2) Portal plus alerts

Turn on carrier notifications for status and ETA change. Send to a shared mailbox or chat channel.
Use the alerts to drive updates in the shared view. Cut manual refresh to near zero.

3) Unified platform

Load BLs and containers from every line into one dashboard. Map events to the standard names so labels match across carriers.
Wire milestone alerts to the planning channel. Everyone sees the same flip from plan to actual at the same time.

Tip: If a transshipment is involved, defer internal ETA updates until you see Loaded on the outbound vessel. That is the moment the connection is real.

Daily workflow to keep teams aligned

Start of day: filter the unified view for any new Loaded, Departure, or Discharged actuals. Post one update to the team channel.
Midday: check only exceptions. Use alerts to catch firsts. Do not recheck every record.
End of day: refresh ETAs that qualify under your rule. Log changes once. Add evidence links.

Playbooks for common pain points

Feeder not yet assigned: Keep the plan provisional. Watch for Loaded at the hub. Update ETA only after that event appears.
Rolling risk: If the cut off is tight, wait for Transport Departure to confirm the leg. Avoid early promises.
Blank sailing or port omission: Use schedule tools to confirm the next viable rotation. Set a temporary internal ETA and tag the shipment as exception until a new Loaded appears.
Customs or doc hold: Do not change ocean leg ETA. Add a separate inland or release column and keep timelines independent.

Methods and sources

DCSA Track and Trace: standard documentation, overview, and the shipping glossary.
Time normalization best practice: ISO 8601 and the IANA time zone database.
Location coding for ports and ramps: UN/LOCODE and current code lists.

Do it in a dedicated platform

A shared sheet works to start. A dedicated dashboard removes repeat work and prevents drift as volume grows.

Upload once: Load BLs and containers from every carrier. The platform keeps them in one list and maps labels to standard milestones.
Wire alerts: Send status and ETA change notifications to a shared mailbox or channel so the team sees firsts in time.
Keep the trail: Every ETA change stores timestamp and evidence link. Reviews take minutes, not hours.
Share safely: Give customers a limited view without exposing internal notes.

A simple setup in TRADLINX

Paste your BL list and containers. Confirm carriers.
Add alert recipients. Use a shared mailbox for ops and a channel for sales.
Share the dashboard link. Use the same view in daily standups.

Prefer a guided setup with your live shipments. Talk to us.

Prefer email? Contact us directly at min.so@tradlinx.com (Americas), sondre.lyndon@tradlinx.com (Europe) or henry.jo@tradlinx.com (EMEA/Asia)