Container Status: Shipping Milestones and Next Steps

Quick answer: what container status entries mean

Container status describes reported events in a shipping container’s journey. A tracking history may include receipt at a facility, loading onto a vessel, discharge from a vessel, gate-out from a terminal and delivery to the destination. Read each label with its location, timestamp and estimated or actual flag. The label alone does not describe the whole shipment.

Three distinctions prevent common mistakes: a vessel arriving does not mean your container has been discharged; discharge does not mean it is available for collection; and gate-out does not mean the consignee has received it. A container can also be discharged at an intermediate port before another ocean leg.

Start with the container number and the carrier’s event history. Use a booking reference where that carrier supports it, and check which container the result describes if the booking contains several. Treat photographs and messages as optional documentation. When the next action depends on a milestone, ask the party responsible for that event to confirm it.

Received, loaded, discharged, gate-out and delivered

Received: a provider reports receipt at the named facility or stage. Check exactly what was received, where, and whether the equipment was full or empty. Do not automatically translate received into picked up or gate-in: pickup is collection, while gate-in describes entry into a facility. None of these labels alone establishes customs clearance or readiness for loading.

Loaded: a reported load event places the container on the named transport. In an ocean-vessel event, check the vessel, voyage and port. First confirm whether the entry is an actual event or a planned load. A booking confirmation and a scheduled vessel departure do not establish that this particular container was loaded.

Discharged: the container was unloaded from the vessel at the identified port when the event is marked actual. That port may be a transshipment stop rather than the final destination. Discharge is separate from customs release, carrier release and collection availability. Check those requirements with the parties handling your shipment before arranging pickup.

Gate-out: the container exited the named facility. Read the full or empty indicator and transport context; an empty container leaving an origin depot is a different event from a full import container leaving a destination terminal. A gate record documents that facility movement, not receipt by the final consignee.

Delivered: the provider reports delivery at the location or endpoint covered by its service. Confirm the recipient and delivery location, particularly if ocean transport and inland delivery were booked separately. For confirmation of receipt, ask the delivering operator for the appropriate proof of delivery. A terminal gate receipt and an arrival notice describe different events and do not substitute for final delivery confirmation.

Details that make a status update useful

Read a tracking entry as a group of fields: container number, event, location, transport reference, event time and source. Two updates can use the same word while referring to different ports or different stages. If one booking includes several containers, check the history of each rather than assuming the first result applies to all of them.

Keep the event time separate from the time you viewed or received the update. A recently refreshed screen can display an older event. Check the stated time zone before comparing records from two ports, and record the time zone with your notes. If the portal does not explain a field, ask the provider rather than silently treating it as local time.

For a concrete example of distinct event labels, Windward’s tracking documentation separates discharge at a transshipment port, discharge at the final port, gate-out and delivery to the consignee: https://developer.windward.ai/reference/eventdescriptions. Your carrier may use different wording; read its definitions and the shipment location together.

• Identity: confirm the container number and the booking or transport reference linked to it.
• Location: distinguish origin, intermediate port, destination terminal and delivery address.
• Timing: retain the actual or estimated label, event timestamp and stated time zone.
• Evidence: ask for the record relevant to the event, such as a gate movement record or delivery confirmation.

Step-by-step checks before planning the next move

Step 1: Start at the carrier’s tracking service with a supported identifier. Maersk’s tracking instructions, for example, describe searching with a bill of lading or container number to see previous movements and the expected schedule: https://www.maersk.com/support/faqs/2024/06/06/how-to-track-shipments. Other carriers may support different references. Confirm that the result belongs to the shipment you are handling.

Step 2: Find the most recent actual event and then read the future estimates separately. ETA means estimated time of arrival; ETD means estimated time of departure, not discharge. Maersk defines ETD this way in its LCL terms: https://terms.maersk.com/LCL. For loading and discharge, read the event’s full label instead of guessing an abbreviation. A forecast becoming overdue does not turn it into an actual event.

Step 3: Identify the next decision. If you are checking whether cargo sailed, request the container-specific load and vessel departure updates. If you are arranging collection, ask about availability and any outstanding release requirements. If a recipient says the shipment has not arrived, contact the inland operator about the delivery leg. These are different questions for different stages.

Step 4: Compare the tracking view with the responsible provider’s records when information conflicts. Save the exact event wording, time, location and reference, then ask which entry is current. A crane photograph or vessel AIS position does not establish that your container was on that vessel. You do not need photographs to follow the carrier’s identifier-based tracking workflow.

Step 5: Send a focused inquiry. Include the container number, relevant booking reference, last actual event and the action you need to arrange. For example: “The portal shows actual discharge at the destination terminal, but collection availability is blank. Please confirm availability, any outstanding release requirements and the next update.” This gives the operator a specific gap to investigate.

• For missing load confirmation, ask the carrier about that container and voyage.
• For collection questions, check with the carrier, terminal or forwarder handling release.
• For a gate-out discrepancy, ask the facility or inland operator for the movement record.
• For final receipt, ask the delivering operator for delivery details and the appropriate confirmation.

Examples: similar labels, different next steps

Example 1 — Discharge at an intermediate port. A hypothetical tracking history shows an actual discharge followed by a future loading estimate on a different vessel. The named port is a transshipment location. Read this as an intermediate transfer rather than final arrival. Ask the carrier to confirm the onward connection if that estimate changes or the next actual event is missing.

Example 2 — Vessel arrival without discharge. The vessel has an actual arrival time, but the container’s discharge is still estimated. Do not describe the container as unloaded or ready for collection. Ask about its discharge event and collection requirements. A vessel-level arrival cannot answer those container-level questions, and the missing event alone does not reveal the cause of the delay.

Example 3 — Gate-out without delivery. A full import container has left the destination terminal, but the recipient has not received it. Check the inland transport reference, intended delivery address and delivery appointment with the operator. The terminal’s gate-out record helps establish the facility departure; final receipt needs confirmation from the delivery leg.

Example 4 — A booking with mixed progress. Two containers share a booking, but only one has an actual load event. Preserve the separate histories and ask the carrier about the second container. Do not copy the first container’s status across the booking or infer that the missing entry means the second was left behind.

What a tracking screen cannot settle by itself

Updates may arrive later than the underlying movement, and different systems may display different event coverage. An unchanged screen does not by itself prove the container has stopped moving. Equally, a later vessel position does not fill a missing container event. Ask the source provider to reconcile the gap when it affects your next action.

A movement event is not a complete release checklist. Customs requirements, carrier release and terminal collection arrangements must be checked separately with the relevant operator or your forwarder. Avoid booking a truck solely because the word discharged appears. Ask what remains to be completed and who will confirm readiness.

The event history also does not determine charges, liability or contractual deadlines on its own. If a date affects a charge or dispute, retain the original records and ask the relevant carrier, terminal or forwarder which terms and timestamps apply. Do not infer a universal start or end date from a generic milestone guide.

Keep a short record of unresolved questions: the conflicting entries, the source you contacted, the answer received and the next agreed check. This makes follow-up easier if another person takes over. It also separates confirmed information from assumptions as the shipment progresses.

Related guides

• How to track a shipping container on iPhone
• Container tracking not updating: what to check
• Understanding equipment type in container tracking

Frequently asked questions