Transshipment: planned hub routing
Most global trade doesn't move on a single direct vessel. Cargo is fed into a major hub (Singapore, Rotterdam, Tanjung Pelepas, Colombo), discharged, and loaded onto a mainline or another feeder toward its destination. A single booking can involve two or three vessels. Transshipment is efficient — it lets carriers run dense hub-and-spoke networks — but each transfer adds transit time and a connection that can be missed, and it means the cargo's journey is only as reliable as its weakest link.
For a forwarder, the practical points are visibility and expectation-setting: a transshipment routing has a longer, more variable transit than a direct service, and tracking must follow the cargo across vessel changes. Customers quoted a direct-service transit who then experience a transshipment routing feel misled — so the routing type belongs in the quote, not the surprise.
Rollover: when your box doesn't make the ship
Rollover is the container-shipping equivalent of being bumped from an overbooked flight: your booked cargo doesn't load on its intended vessel and rolls to the next one — often a week later on weekly services. Causes include carrier overbooking (they sell more slots than space to hedge no-shows), vessel weight or capacity limits, a missed transshipment connection, late documentation, or port congestion. Rollover is disturbingly common on hot lanes and in peak season.
The damage is real: a week's delay, blown delivery commitments, and knock-on demurrage or storage. Mitigation is operational — book earlier against cutoffs, keep documentation clean and on time (late SI is a self-inflicted rollover cause), watch high-risk lanes and peak windows, and confirm loading rather than assuming it. Because so many rollover triggers are document- and deadline-driven, the desks that miss fewest are the ones that don't let cutoffs and confirmations get lost in the inbox.