When Busan Transshipment Misses the Connecting String | Dogwood Hub Field Notes

A house bill marked "on schedule" at origin can still miss the mother vessel at Busan by six hours — enough to slip an entire weekly string. Forwarders call us when the storage invoice arrives and the consignee asks for proof that the miss was operational, not documentation-related.

Separating feeder delay from terminal congestion

The first step is timestamp comparison: gate-out at origin feeder port, arrival at Busan feeder berth, discharge completion, and gate-in at the transshipment terminal for the connecting vessel. A gap between discharge and gate-in usually indicates terminal handling or customs examination, not ocean delay.

What we put in the memo

Our transshipment miss briefings include a timeline table with source tags (AIS, terminal gate, carrier event codes where available). We avoid blaming language — the goal is a factual sequence your desk can attach to a storage discussion.

Common surprise: documentation holds masked as congestion

If the carrier event log shows "documentation pending" before a transshipment miss, berth congestion charts alone will not explain the slip. We cross-check against customs publication cycles for the cargo type. Refrigerated seafood and certain chemical classes trigger examination rates that spike after holiday weeks.

Recommendation for standing imports

If you manage more than four transshipments through Busan monthly, a terminal queue retainer on the feeder berth group catches miss risks earlier than a post-incident delay report.