What the latest US container import report says
In its 11 November release, Descartes reported 2,674,808 TEUs of US containerised imports in October 2026, a monthly record in its data. It also said there were no signs of broad-based port congestion. Read those findings together before turning a volume headline into a delay forecast.
TEU means twenty-foot equivalent unit, a measure of container capacity rather than a count of physical boxes. A 40-foot container represents two TEUs. Keep the unit visible when discussing the headline with colleagues, especially when your shipment register counts individual containers.
Use national volume as context for local checks
Before you add a delay allowance to a booking, identify the affected port, terminal, vessel call and inland leg. A national total does not establish the waiting time or collection status of a particular container.
Import volume, vessel queues and container dwell answer different questions
An import volume figure describes the amount of cargo within a reporting period and coverage area. A vessel queue describes ships waiting for service at a particular location. Container dwell describes time spent at a defined stage, such as between discharge and terminal gate-out. Check which question a metric answers before using it to explain a late shipment.
A busy gateway can move cargo efficiently, while an individual container faces a documentation problem or misses an inland connection. Equally, a national monthly total can hide a local disruption. Investigate the movement and handover that affect your goods instead of assigning the same cause to every late box.
Our port congestion guide explains the wider operational problem. For a current shipment decision, obtain the latest local information and distinguish a reported backlog from a delay confirmed against your container reference.
Check the definition behind a port transit delay number
The Descartes report's methodology uses an initial release of U.S. Customs and Border Protection (CBP) bill-of-lading data that can later be revised. Its port transit delay runs from the ETA first declared on the bill of lading to Descartes' receipt of the processed data. That interval differs from physical discharge-to-gate-out dwell.
Before you compare two published delay figures, record their start event, end event, coverage and reporting period. Ask whether each value is an average, a median or a snapshot. Avoid combining unlike measures into one number labelled port congestion. If a report provides a regional average, do not assume that every terminal shares it.
For your own operational review, choose an event pair that answers the actual question. To examine terminal dwell, request discharge and gate-out evidence. To examine inland rail performance, request the relevant rail departure and destination availability events. Preserve the event source and time zone so a later comparison uses the same basis.
A seven-field readiness check for US-bound containers
Use this record when a port-volume headline prompts a shipment review. It is a practical handover checklist, not a prediction of how long a terminal will take to process your cargo. Keep one record per container when boxes on the same booking have different movements.
- 1. Identity and destination: Record the container number, booking or bill of lading, discharge terminal and final delivery location. Confirm that the latest itinerary still matches those details.
- 2. Maritime movement: Keep the planned port arrival separate from any reported actual arrival and container discharge. Record the carrying vessel and voyage where available.
- 3. Release and availability: Ask the responsible parties to confirm any outstanding carrier, customs or terminal requirements and whether the box is available for collection. Discharge alone does not answer that question.
- 4. Onward transport: Record whether the next movement is by truck, rail or another vessel, who arranges it and which connection or appointment is confirmed.
- 5. Receiving window: Confirm the warehouse's receiving date, opening hours and any appointment requirements. Identify the latest delivery time that still meets the inventory need.
- 6. Free time and return: Obtain the applicable last free day and empty-return instructions from the responsible provider. Keep confirmed terms separate from planning estimates.
- 7. Next action: Name the person responsible for each missing confirmation, record when they will follow up and state which customer commitment depends on the answer.
A useful review ends with a specific action, such as confirming a rail connection or resolving a release requirement. A note that says only busy port leaves the receiving team without an owner, a decision or a reliable next update. Keep the unresolved point visible until someone confirms the handover.
Give rail-bound imports their own delivery timeline
If your booking includes inland rail, a seaport milestone is only one part of the journey. Ask who is responsible for the transfer, whether an onward rail movement is assigned and what evidence will confirm departure. At the destination ramp, check availability and the final collection plan before promising warehouse delivery.
If an expected rail event is missing, ask the carrier or forwarder to reconcile the status. The absence of a tracking update is a reason to investigate, not proof that a container has missed its train. Also confirm whether the booking covers the inland move or whether your team must arrange it separately.
Use a single shipment record to connect the ocean, inland and warehouse dates. Keep each planned estimate labelled and replace it with an actual event only when supporting evidence arrives. Our guide to AIS versus container milestones explains why a vessel's position cannot establish every subsequent container movement.
Worked example: a port ETA with an unconfirmed handover
Suppose a container has a planned port arrival on 16 November and your warehouse needs the goods on 20 November. The receiving sheet shows delivery on 18 November, but no one has confirmed collection availability or the inland appointment. These dates are an illustrative planning example, not a reported shipment or a transit-time benchmark.
Keep the port ETA as an estimate. Mark the warehouse delivery date provisional, identify the missing confirmations and ask the transport provider for a supported delivery plan. If actual discharge is reported, update that milestone without automatically treating the container as released or ready to leave the terminal.
If the confirmed handover no longer meets the warehouse requirement, discuss the available alternatives with your forwarder and receiving team. The decision should follow the shipment evidence. Adding an arbitrary national delay average to the port ETA would still leave the missing appointment and release questions unanswered.
Compare alternative gateways on the complete journey
Before changing a routing guide, compare the full delivery plan: ocean departure, any transhipment, discharge terminal, inland connection and final receiving window. A port that looks attractive in a national summary may not provide the right service for your origin, cargo-ready date or delivery destination.
Use sailing schedule search to compare available itineraries, then confirm space, cut-offs and commercial terms with your carrier or forwarder. Ask for an onward transport plan on the same delivery basis for each option. Keep possible savings or time improvements as proposals until the relevant providers confirm them.
An alternative gateway needs an inland plan
Before you switch ports, establish how the container reaches its final destination and who owns each handover. A shorter ocean itinerary does not by itself establish an earlier warehouse delivery.
Keep pickup deadlines and cost assumptions current
When an arrival or connection changes, revisit collection appointments, free time and empty-return arrangements. Use the container release checklist to organise the destination checks, and confirm the applicable dates rather than calculating a universal deadline from the vessel ETA.
If your quote contains a provisional policy-related charge, review its basis separately from the congestion discussion. Our US Section 301 port fee suspension checklist provides a dated notice summary and quote-review record. High import volume alone cannot determine whether a particular invoice line applies.
Use container tracking to maintain the handover record
Use Panvaya container tracking to review available carrier-reported milestones against the booked plan. Details depend on the carrier and reference, so obtain missing release, terminal or inland confirmations from the responsible provider. Share an update that identifies the latest confirmed event, the next planned handover and the question still awaiting an answer.
The bottom line
Treat the import record as a prompt to review your receiving plan. Check the definition behind any delay number, follow the individual container through its onward handovers and assign an owner to missing confirmations. Your warehouse needs a supported delivery plan, not a national statistic applied to every shipment.