Shanghai International Logistics Co., Ltd.
Worldwide Cargo Shipping: Trade Lanes, Services And Transit Planning
A carrier network is not a chain of shipments. It is a set of vessel rotations, each a loop of port calls that ends where it began, interlocked through shared transhipment ports. A cargo move is the sum of several loop segments plus one or more handoffs, and every handoff is a place where the schedule can slip. Three layers sit underneath each other: deep-sea mainline services crossing oceans on large vessels, regional and short-sea services feeding those mainlines, and coastal services moving boxes within one country or sub-region. Because the layers meet at specific ports, routing is a question of which hubs to pass through and how many vessel changes to accept.
Lane structure follows the geography of demand and navigable water. High-volume arteries run east to west between the manufacturing centres of East and Southeast Asia and the consumer markets of North America and Europe. North-south arteries connect those Asian origins with the Middle East, the Indian Subcontinent, Africa and South America. Inside each basin sit regional lanes that are shorter and more frequent.
The east-west arteries carry the bulk of containerised trade: Asia to North Europe and the Mediterranean, Asia to North America across the transpacific, and North America to Europe over the North Atlantic. These lanes serve few high-volume port pairs, so sailings are frequent and vessels are large. Because the lanes are long, a single delay can push later calls of the same loop back in sequence, so reliability depends as much on intermediate ports as on the crossing. North-south routes are long relative to their frequency, and a significant share still pass around the Cape of Good Hope or through the Red Sea and Suez corridor, so transit times spread widely.
| Trade lane | Cargo profile | Planning note |
|---|---|---|
| Asia to North Europe and Mediterranean | Consumer goods, machinery, components | Frequent mainline calls; arrival congestion adds days |
| Asia to North America, transpacific | Retail, e-commerce freight | Independent routings via northern and southern ocean |
| North America to North Europe | Vehicles, machinery, project cargo | Short, high-frequency, few transshipment options |
| Asia to Middle East and India | Project cargo, building materials | Feeder-heavy; transshipment at Jebel Ali or Colombo is common |
A direct service carries the container from origin to destination on one vessel. A transhipped routing discharges it at an intermediate port and loads it onto a second vessel, normally of different size and on a different rotation. No carrier calls every port in every ocean, so transshipment is unavoidable for many port pairs. The question is where the chain is allowed to break, and how much risk each connection carries.
The cost is not only extra freight. Transshipment adds a handling cycle, port charges, a documentation interface and a schedule that can fail independently. If each leg holds its schedule with probability p, the chain succeeds only if every leg succeeds, so reliability falls as leg count rises. The cargo also stands in a yard, exposed to weather, container moves and damage. The operational cost is dwell time, which the transit estimate must include; the commercial cost is extra freight and local handling.
| Dimension | Direct service | Transhipped service |
|---|---|---|
| Vessels involved | One | Two or more, plus yard handling |
| Schedule dependencies | A single vessel rotation | Each leg, plus the connection between them |
| Transit spread | Tighter, more predictable | Wider; the connection window dominates |
| Typical use | Major port pairs with a direct call | Minor ports, low volume, frequency mismatch |
A port pair is the origin and destination combination a service is sold on, and the unit at which schedules and rates are quoted. A hub is a port where several services converge so cargo can change vessels without changing carrier. Whether a port works as a hub depends on the number of independent rotations calling it, the terminal links between them, and free-time arrangements. Ports such as Singapore, Rotterdam and Jebel Ali are structural nodes for this reason: their importance is not cargo volume but the number of ways a shipment can pass. Where a hub offers two rotations for the same onward lane, a missed connection can be recovered on the next sailing; where it offers one, it means a roll.
A published schedule is a rotation: a numbered sequence of port calls with arrival and departure days, repeated on a cycle. To turn it into a transit estimate, number the calls in rotation order, locate the origin and destination calls, and count forward around the loop, not in a straight line. That gives the ocean leg. Then add the days between the delivery vessel's arrival at the transhipment hub and the outbound vessel's departure; that interval is the connection window and the largest source of variation in a transhipped itinerary. Finally add origin-side days for export clearance and gate-in, and destination days for import clearance, terminal handling and delivery.
A schedule is a plan; schedule performance is the gap between the published plan and what actually happened, measured across bookings and sailings rather than for one shipment. Three mechanisms open that gap. Blank sailings are deliberate carrier decisions to omit a call or cancel a sailing, used to align vessel deployment, manage capacity or react to demand shifts. Congestion is the accumulation of berth waiting, yard backlog and equipment or labour constraints at the ports the rotation calls. External interruption adds unplanned time: canal transits, weather routing, port strikes and inspection holds. Reliability figures need care, because a carrier's on-time figure is usually measured against the arrival time on the bill of lading, which may already include a buffer.
Frequency sets the granularity of any plan. A weekly service means a missed sailing costs about seven days; a port served every fourteen days makes the same miss cost a fortnight. Frequency is not the number of calls printed on the schedule, which is normally the cycle length of the rotation: a service advertised as weekly may publish a three or four week cycle across all its ports, and only part of that cycle serves any one port. Buffer time should sit on top of the published transit, not inside it. The recovery buffer covers the time needed to regain a missed connection at the tightest point in the chain. Also allow for cut-off slippage and customs variability, which is outside the carrier's control. Practical buffers on intercontinental moves are stated in days rather than a percentage, given as a range with a floor and a ceiling.
A usable transit plan is a chain of legs, each with an owner and a controllable or uncontrollable classification. The first leg runs from booking confirmation to terminal gate-in of the loaded container, including export clearance and inland delivery. The second is the port-to-port ocean leg on the named service and rotation. The third is the transhipment leg: discharge, yard handling, reloading and the connection window, a real dwell rather than a paperwork transfer. The fourth is arrival, discharge, import clearance and any inspection hold. The fifth is delivery to the consignee and proof of delivery. Controllable legs are those the shipper can influence: truck appointments, documents and packaging. The rest sit with the carrier and terminal.
Three cut-offs govern the origin leg. The documentation cut-off is the time by which shipping instructions, the VGM declaration and export declaration must be filed with the carrier. The VGM cut-off under SOLAS rules requires a verified gross mass for containerised cargo, submitted by the shipper or an authorised party, and is enforced separately because the carrier needs the figure before loading. The gate or CY cut-off is the latest time the container may be delivered to the terminal. In practice the VGM and documentation cut-offs fall earlier than the gate cut-off, sometimes by a day, and they most often cause a container to roll. Rolling is expensive in time: miss the cut-off and the chain re-times from a later origin call. The document set is unforgiving: commercial invoice, packing list, shipping instructions, HS code per line, certificates of origin, and a dangerous goods declaration where required.
Monitoring is only useful if it is milestone-based. The minimum set per booking is booking confirmation, gate-in at origin, vessel loaded, departure, arrival at each transhipment port, connection confirmed, arrival at destination, discharge, customs release and delivery. Alongside those timestamps, ask for the vessel name and voyage number, the current estimated arrival and departure, and the delay reason code. Also establish when the demurrage and detention clocks start, since that point determines the cost of lateness. For reefer cargo, treat the temperature log as a continuous record. Ask for the revision history of the estimated arrival: the pattern shows whether a delay is being absorbed or still growing. At the hub, confirm the container was actually loaded on the onward vessel, not merely booked onto it, and check whether the dwell exceeded the free time granted.
| Priority | Primary routing | Reason | Fallback |
|---|---|---|---|
| Speed against a fixed date | Direct service, highest frequency to destination | Removes a connection from the failure chain | Second direct routing with an earlier departure |
| Small volume to a minor port | Feeder plus mainline via nearest hub | Direct calls to minor ports are infrequent | Alternative feeder call order at same hub |
| Cost priority | Transhipped routing via hub with most feeders | More competing sailings, tighter space options | Direct service if rate gap is acceptable |
| Reliability-critical flow | Direct service, or routing with a wide connection window | A long window absorbs an inbound delay | Second hub with its own independent rotation |
Treat the published figure as the ocean leg only. Add origin days for cut-off, export clearance and gate-in, the connection wait at each hub, and destination days for import clearance and delivery. Then add a recovery buffer sized by the tightest connection and sailing frequency. State the result as a range, and confirm it against the booking rather than the schedule.
When there is no direct service, the destination is a minor port, or the direct frequency cannot meet the delivery date. It is rarely worth it when a direct service exists at workable frequency, because the connection window adds variability a single-vessel transit does not.
Treat it as a rotation. Number the port calls in order, find the origin and destination positions, and count forward around the loop to obtain the ocean leg. Read the interval between the arrival and departure calls at each transhipment port as the connection window, and check the cycle length to see how often each port is served. The schedule describes intention, not performance.
Milestone timestamps against schedule for booking, gate-in, load, departure, each transhipment arrival and connection, arrival, discharge, customs release and delivery. Alongside them, the estimated arrival revision history, the delay reason code, the start of the demurrage and detention clocks, and the reefer temperature log. Without the revision history, one estimate cannot separate an absorbed delay from a growing one.
Shanghai International Logistics Co., Ltd.