Field notes
Visibility handoffs that survive partner changes
Shipment visibility fails most often at the seam between organisations, not inside a single system. When a feeder carrier joins a lane, the status vocabulary rarely matches what your customer portal already shows.
Write a one-page handoff sheet for each partner: the event names they use, the earliest moment they can confirm an event, and who owns corrections when a scan arrives late. Share that sheet when onboarding, not after the first missed update.
Prefer fewer, reliable events over a long list of optional scans. Customers tolerate a short status trail that arrives on time more than a rich trail that stalls for two days.
In Hong Kong air–ocean combinations, treat the airport freighter arrival and the bonded warehouse receipt as separate commitments. Collapsing them into one “arrived” status creates disputes when cargo sits overnight.
Rehearse a partner switch with a dry-run file before go-live. Send three historical shipments through the new handoff sheet and confirm that exception codes still map to your customer language.