Guide · Operations

Exception Management in Shipping

Most shipments run themselves. Operations teams exist for the ones that don't — and how fast you catch those defines how expensive they get.

An exception is any shipment deviating from plan: a rolled container, a missed connection, a customs hold, an ETA sliding past the promised delivery week. Exception management is the working system for catching those deviations early and acting on them — and it's the practical payoff of all the visibility infrastructure described in our RTTV guide.

The exceptions that matter most

The workflow: detect → alert → act

Detect: exceptions surface as event gaps or plan-versus-actual divergence — a load event that didn't happen, an AIS position inconsistent with the schedule, an ETA past the delivery commitment. Detection has to be automatic; nobody re-checks 80 shipments daily.

Alert: the deviation goes to the person who owns the shipment — email or dashboard — with enough context to act: what changed, the new ETA, the affected reference.

Act: rebook, expedite, pre-clear, or simply re-promise the customer early. Almost every response is cheaper the earlier it starts; the same missed connection costs an email on day one and a demurrage invoice on day ten.

Making it stick

Teams that do this well keep it simple: one dashboard everyone trusts, alerts wired to the few events that matter (departed, transshipped, discharged, ETA moved, gone silent), and a habit of working the exception list instead of the full shipment list. That's the design behind Shyppy — statuses, ETAs and alerts across ocean, air and courier, so the exceptions find you instead of the other way round.

Frequently asked questions

What is an exception in shipping?

Any deviation from the planned journey: rolled cargo, a missed transshipment connection, a customs hold, a significant ETA change, or a shipment that has gone silent (no events when events are expected).

What is rolled cargo?

A container that didn't ship on the vessel it was booked on — usually due to overbooking, weight restrictions or schedule changes. It normally moves on the next sailing, adding days to weeks; the tell-tale sign is a missing 'loaded' event.

What is exception management?

The workflow of automatically detecting shipments that deviate from plan, alerting the owner with context, and acting early — rebooking, expediting, pre-clearing, or resetting customer expectations.

How do you detect exceptions automatically?

By comparing plan to reality continuously: expected milestones that never arrive, AIS positions inconsistent with schedules, ETAs crossing delivery commitments, and event silence beyond a threshold. Tracking platforms raise these as alerts.

Why act early on exceptions?

Costs compound: the same problem answered on day one with a rebooking email becomes storage fees, demurrage and a missed customer commitment by day ten. Early detection is the entire economic case for visibility.

See every shipment in one place

Ocean containers, air cargo, courier parcels and live vessel positions — tracked in a single dashboard with automatic alerts. Free plan, no credit card.