Port of Oakland Volume Fell 10%: Rebuild the Gateway Forecast From Vessel Calls Up

The Port of Oakland handled 173,818 twenty-foot equivalent units (TEUs) in August, down nearly 10% from a year earlier. The headline looks like a demand warning, but the operational story is more complicated. Vessel calls also fell 9% year over year, according to SupplyChainBrain. When ship arrivals and throughput decline at almost the same rate, planners should not assume that every missing container represents lost customer demand.

That distinction matters. A shipper that reads the result only as weak demand may cut drayage, warehouse labor, and rail allocations too aggressively. One that dismisses the decline as a sailing-calendar quirk may retain expensive capacity that goes unused. The better response is to rebuild the gateway forecast from vessel calls up, then test it against ship size, import demand, export mix, and inland execution.

Start with calls, not the monthly total

Monthly TEU is the output of several variables: the number of vessel calls, deployed ship capacity, vessel utilization, and the balance of loaded and empty containers. Begin by calculating TEU per call for the current month and comparable periods. If calls fall 9% while total volume falls nearly 10%, average throughput per call is roughly stable. That points first toward fewer arrivals, although exact call-level capacity and utilization data are still needed.

Do not treat every call as interchangeable. One omitted 4,000-TEU vessel and one omitted 12,000-TEU vessel create radically different capacity gaps. Match each scheduled and actual call to the service, nominal ship capacity, arrival date, terminal, and prior call history. Record blank sailings, port omissions, late arrivals that crossed the month boundary, and service changes. A vessel arriving September 1 instead of August 31 lowers August's total without necessarily changing the underlying cargo book.

The year-to-date view provides a useful guardrail. Through August, Oakland processed more than 1.4 million TEUs, 4.5% below the same period in 2025. Loaded cargo was down 2.5%, less severe than the headline monthly decline. This suggests a softer gateway, but not a simple 10% collapse in recurring loaded demand.

Separate four competing explanations

After normalizing for calls, test four explanations rather than forcing one narrative.

Fewer vessel calls. Compare scheduled, actual, omitted, and delayed calls by service. A lower call count can reflect carrier network design or timing, not lost shipper demand. Calculate the capacity removed by the missing ships and identify whether booked cargo rolled, rerouted, or never materialized.

Different ship size or utilization. Track nominal capacity and estimated loaded exchange per vessel. Stable calls with smaller ships indicate a capacity decision; stable deployed capacity with lower exchanges points more directly to utilization or demand. TEU per call should be segmented by service because averages can hide a large-vessel substitution.

Import demand. Oakland imports through August were down 4.6% year over year. Yet the national market moved the other way in August: U.S. containerized imports reached 2,603,709 TEUs, up 3.3% year over year and the third-highest monthly total on record, FreightWaves reported. Oakland's import decline therefore may reflect gateway share, routing, or customer mix as well as aggregate consumption.

Export and empty mix. Oakland exports were 0.2% ahead of last year through August. That modest growth can coexist with falling total TEU if imports or empty repositioning decline. Forecast loaded imports, loaded exports, inbound empties, and outbound empties separately. Each has different implications for revenue, equipment availability, trucking, and warehouse workload.

Translate the forecast into inland scenarios

A useful gateway forecast should produce capacity decisions, not merely a chart. Build three rolling scenarios for the next six to eight weeks.

The call-recovery case assumes delayed or omitted services return and cargo rolls forward. Preserve flexible drayage blocks, receiving appointments, and rail allocations around the resulting arrival banks. The soft-demand case assumes calls remain lower and loaded imports continue below baseline. Reduce discretionary capacity gradually while protecting contracted coverage for priority customers. The share-shift case assumes U.S. demand remains healthy but cargo favors other gateways. Review origin routings, carrier services, inland cost, and customer commitments before deciding whether to compete for volume or reposition resources.

Port-to-inland design belongs in this analysis. Shippers are using diversified inland routes to reduce concentration risk, and shorter dray moves paired with rail can reduce empty miles, Supply Chain Dive reported. For Oakland, each scenario should therefore project container availability by discharge week, local dray moves, rail lifts, warehouse receipts, chassis demand, and empty returns. Monthly TEU alone cannot reveal where an inland bottleneck will form.

Set triggers that resist one-month overreaction

Use explicit triggers to move between scenarios. Consider shifting allocations only when at least two independent signal groups agree for two consecutive reporting periods:

• Vessel calls or deployed capacity remain materially below the service baseline.
• Forward bookings and purchase orders weaken beyond the current sailing window.
• Loaded import volume loses share while comparable U.S. gateways grow.
• Rail reservations, dray tenders, or warehouse appointments confirm lower physical demand.
• Rollover, dwell, and equipment shortages indicate deferred cargo rather than cancellation.

Define actions in advance. A confirmed call-recovery signal might release temporary drayage and weekend receiving capacity. Persistent soft-demand signals might reduce reserved warehouse labor by a preset band. Evidence of a gateway share shift should trigger a lane-level landed-cost review rather than an automatic Oakland exit.

Every decision should carry an expiry date. Reassess temporary capacity changes after the next two vessel cycles or the next monthly port release. Keep the forecast version, source data, assumption, decision owner, and actual outcome so the team can learn whether it reacted to demand, network design, or calendar noise.

Oakland's August result is meaningful, but its value lies in the questions it prompts. When teams connect vessel schedules, container mix, bookings, and inland milestones, they can distinguish a structurally weaker gateway from a temporary change in the sailing calendar—and allocate capacity accordingly.

CXTMS brings bookings, vessel milestones, drayage, rail moves, warehouse appointments, and exceptions into one operating view. Request a CXTMS demo to build gateway forecasts that translate port signals into timely execution decisions.