Ocean freight transit time describes the scheduled or actual duration between specified departure and arrival milestones. Shipping time depends on the exact ports, carrier service, intermediate calls and any transshipment connections. Port-to-port transit time excludes inland collection and final delivery; cargo availability can also occur after vessel arrival.
These are port-to-port planning ranges (not guaranteed ETAs). Use them as a starting point, then confirm against the specific carrier schedule used for booking.
Use the routes below to identify the port pair you need to check. A broad trade lane does not have one fixed transit time: two services between the same ports can have different departure dates, intermediate calls and arrival dates.
Before using an estimate in a quote or inventory plan, confirm the exact origin port, destination port, carrier service, departure date and routing. Record when the schedule was checked, and distinguish vessel arrival from the date cargo is expected to become available for collection.
| Origin port | Destination port | What to verify before estimating shipping time |
|---|---|---|
| Shanghai, China | Los Angeles, United States | Selected service, intermediate calls and scheduled departure and arrival |
| Ningbo, China | Long Beach, United States | Port rotation, departure availability and destination terminal |
| Shanghai, China | New York/New Jersey, United States | Routing, intermediate calls and any transshipment connection |
| Yantian, China | Savannah, United States | Direct or connecting service, hub waiting time and destination call sequence |
| Shanghai, China | Rotterdam, Netherlands | Current routing, intermediate calls and schedule revisions |
| Ningbo, China | Barcelona, Spain | Direct or connecting service and any feeder connection |
| Shanghai, China | Jebel Ali, UAE | Service availability, routing and intermediate calls |
| Shanghai, China | Singapore | Selected departure, port rotation and arrival milestone |
| Rotterdam, Netherlands | New York/New Jersey, United States | Selected service, intermediate calls and departure date |
| Santos, Brazil | Rotterdam, Netherlands | Direct or connecting service and port rotation |
| Shanghai, China | Sydney, Australia | Service routing, intermediate calls and any transshipment connection |
Different disruptions affect different parts of the shipment timeline. Identify the affected milestone before adding a buffer.
| Factor | How it affects the shipment | What to check |
|---|---|---|
| Intermediate port calls | Adds time within the vessel’s scheduled rotation | Full service itinerary |
| Transshipment | Adds a connection and potentially a wait for another vessel | Connecting service and planned connection time |
| Blank sailing or rolled booking | Can postpone the shipment’s departure | Revised booking and departure confirmation |
| Weather or routing changes | Can change the voyage duration and arrival estimate | Carrier advisories and updated schedule |
| Congestion before berthing | Can delay berthing and discharge | Which arrival milestone the ETA represents |
| Terminal handling after arrival | Can postpone cargo availability | Discharge status and terminal availability |
| Documentation or customs holds | Can delay release even when the vessel arrives on schedule | Outstanding documents, inspections and release status |
| Inland transport availability | Can delay collection or final delivery | Haulage booking and delivery appointment |
The following example is hypothetical. It demonstrates how to calculate a shipment timeline and does not represent a current carrier schedule.
Assume a Shanghai–Los Angeles shipment follows this sequence:
| Shipment milestone | Illustrative day |
|---|---|
| Cargo ready at the supplier | Day 0 |
| Container collected | Day 2 |
| Container enters the origin terminal | Day 4 |
| Vessel departs Shanghai | Day 7 |
| Vessel arrives at Los Angeles | Day 23 |
| Cargo becomes available after discharge and required releases | Day 26 |
| Container delivered to the consignee | Day 28 |
In this example:
Quoting only the 16-day sea transit would leave out the time required before departure and after arrival. For inventory planning, specify the complete timeline and the assumptions behind it.
A reliable approach is to present transit time in three layers:
Capturing those assumptions consistently reduces dispute cycles and “but you said…” escalations. A governed workflow like quote management helps teams standardize service notes, inclusions, and lead-time assumptions across users and offices.
Transit-time decisions improve when the team compares options under consistent rules, with the same lane/service metadata used across quotes. Centralizing service and charge logic through rate management makes it easier to keep routing and pricing assumptions aligned.
Most “late shipments” start as a small miss: SI submitted late, cargo not gated-in, booking rolled, documents missing. An execution view like operations tower helps teams detect drift early, assign owners, and prevent a missed sailing.
If you want a single reference model for turning lane estimates into a repeatable quote-to-execution workflow, use how velocity works.
Compare ocean freight options using the same departure, arrival and delivery milestones. Record the exact ports, selected sailing, routing, connection points and schedule-check date. Keep inland transport, cargo release and delivery appointments separate from the vessel’s port-to-port transit time.
For an explanation of how systems organize rates, schedules and shipment milestones, see our guide to ocean freight software.
Related Articles

