How CMA CGM Container Tracking Actually Works: What the Portal Shows, What It Doesn't, and What the Events Mean

Key Takeaways

Data lag averages 6-12 hours. CMA CGM has stated that data is usually transmitted about 8 working hours after the vessel sails, with backend updates running 2-4 times per day.
Searching by B/L gives you more data than searching by container number. Container-number searches may not surface all event updates.
CMA CGM offers a two-tier API at api-portal.cma-cgm.com — a free public tier with an API key, and a private OAuth2 tier that adds rail, ramp, and inland move data.
APL, ANL, CNC, and Containerships all share CMA CGM’s backend. APLU-prefix containers are trackable through the same portal.
Schedule reliability runs 50-60%, below the global average in several months of 2025. ETA shifts are common, especially on multi-leg routings.
Trustpilot complaints consistently cite stale data and changing dates as the biggest tracking frustrations.

Who This Is For

This guide is for operations teams, freight forwarders, and importers who track shipments on CMA CGM — including APL and ANL bookings — and need to understand what the portal data means, why it lags, and how to get better results through the API. It pairs with our event naming comparison for teams tracking across multiple carriers.

What the Portal Shows You

The basic view is public. No account is needed to look up a single container. Registered users get additional features: an interactive map showing vessel position, email notifications for milestone events, and a tracking dashboard for managing multiple shipments.

APL runs on the same backend. Since CMA CGM’s full integration of APL, the apl.com tracking portal shares the same data pipeline. APLU-prefix containers are trackable on CMA CGM’s portal, and vice versa. The same applies to ANL, CNC, and Containerships — all are part of the CMA CGM Group and share tracking infrastructure.

Container prefixes you will encounter: CMAU (primary), APLU, CGMU, CGHU, CGTU, CMNU, and CNCU. All are searchable through the same portal. If you are tracking a legacy APL booking, use the APLU container number for the most complete results.

Event Names and What They Mean

CMA CGM’s event labels are relatively straightforward compared to some carriers, but there are nuances worth flagging. The table below maps each label to what actually happened and the corresponding DCSA code.

CMA CGM Event Label	What Actually Happened	DCSA Code
Gate In Full	Laden container entered the origin terminal	GTIN
Loaded at POL	Container was lifted onto the vessel at port of loading	LOAD
Departure from POL	Vessel left the port of loading	DEPA
Transshipment	Container is being transferred between vessels at an intermediate port	—
Arrival at POD	Vessel arrived at the destination port	ARRI
Discharged at POD	Container was unloaded from the vessel at destination	DISC
Gate Out Full	Container left the destination terminal	GTOT
Empty Released	Empty container has been returned to the carrier	—
Delivered	Container delivered to consignee’s location (carrier haulage)	DLVD

The “Transshipment” label is vague by design. CMA CGM rolls the transshipment leg into a single label rather than breaking it into discharge-at-hub, dwell, and reload-at-hub like some carriers do. If you need to know whether the container has been unloaded at the transshipment port, loaded onto the feeder, or is still sitting in the hub yard, the portal will not tell you. You will see “Transshipment” and then nothing until the next leg fires.

The B/L vs container number data gap is real and confirmed. CMA CGM has acknowledged that searching by container number may not surface all event updates. If you search by B/L, you typically get a more complete timeline — especially for events at origin and during transshipment. This is not a bug; it reflects how CMA CGM’s system indexes events differently depending on the identifier type. Our guide on which identifier to track with covers this pattern across carriers.

Update Cadence: How Fresh Is the Data?

CMA CGM’s 6-12 hour data lag is among the longest of the major carriers. The company has stated that tracking data is usually transmitted about 8 working hours after the vessel sails. Backend systems sync 2-4 times per day. This means the portal is showing you events that happened roughly half a working day ago.

What this means operationally: if a vessel departs Shanghai at 06:00 local time, the “Departure from POL” event might not appear until 14:00-18:00 — or the next business day if the departure happens in the evening. For departure events, this lag is rarely consequential. For destination events — discharge, gate out — it can mean the difference between dispatching a trucker on time or missing a pickup window.

Known Gaps and Quirks

Transshipment visibility is thin. As noted in the event table, CMA CGM compresses the transshipment leg into a single label. You will not see when the container was discharged at the hub, how long it sat in the yard, or when it was loaded onto the feeder. For shipments routing through major Ocean Alliance hubs, this creates a visibility gap that can last anywhere from two days to two weeks.

Schedule reliability runs below the global average. CMA CGM’s monthly reliability in 2025 hovered in the 50-60% range, falling below the global carrier average in several months. This means roughly 4-5 out of every 10 arrivals deviate from the published schedule. ETAs in the portal should be treated as estimates, not commitments — and they will change, sometimes multiple times during a voyage.

No “Available for Pickup” event. Like most carriers, CMA CGM does not publish a single event that confirms a container is cleared by customs, released by freight, and available in the terminal yard. The gap between “Discharged at POD” and “Gate Out Full” is operationally opaque on the portal.

Ocean Alliance routing complexity. CMA CGM is part of the Ocean Alliance alongside COSCO, OOCL, and Evergreen. Containers booked on CMA CGM may physically move on partner vessels. Tracking data for alliance-operated legs can lag behind CMA CGM’s own-vessel data, and the event labels may not be perfectly consistent when the underlying data comes from a partner carrier’s system. If you track by B/L and notice events that seem to fire later than expected on certain legs, the container may be on a partner-operated vessel where data flows through an additional synchronization layer.

Empty return tracking is limited. CMA CGM publishes an “Empty Released” event, but the level of detail varies. At some terminals, the event fires when the empty container crosses the terminal gate. At others, it fires when the carrier’s system registers the return from the depot. If you are managing detention charges and need to prove timely empty return, the Equipment Interchange Receipt (EIR) from the depot is a more reliable record than the portal event. The portal event confirms that CMA CGM’s system registered the return, but the EIR confirms the physical handoff with a timestamp and condition inspection.

What to Do When Tracking Breaks

Scenario 1: Container number search returns fewer events than expected. Switch to B/L search. CMA CGM has confirmed that container-number lookups may not surface all event updates. If you have the B/L number, use it — it consistently returns a more complete timeline.

Scenario 2: ETA has changed three times in a week. This is common on CMA CGM, especially for multi-leg routings through Ocean Alliance hubs. Check whether the vessel name has changed (indicating a feeder connection was rebooked) or whether the same vessel is simply running behind schedule. If the vessel name has changed, the container was likely rolled at the transshipment hub.

Scenario 3: Tracking page loads but shows no data. CMA CGM’s JavaScript-based portal can fail silently in some browser configurations. Disable ad blockers, ensure JavaScript is enabled, and try a different browser. If the issue persists, the tracking system itself may be experiencing intermittent issues — CMA CGM does not publish a status page for its tracking portal.

Scenario 4: APL container not found on CMA CGM portal. While APL is fully integrated, some older booking references may not resolve. Try searching by the APLU container number instead of the booking reference. If you are looking for a shipment booked before the full APL integration, the data may still be indexed under APL’s legacy system.

Scenario 5: “Discharged at POD” posted but terminal says not ready. The 6-12 hour lag means the discharge event may post before the terminal has completed all processing. Alternatively, the container may be discharged physically but held by customs or freight. Contact your customs broker or check the terminal’s website for availability status.

API and Integration Options

CMA CGM offers a two-tier API through its developer portal at api-portal.cma-cgm.com. The structure is more nuanced than most carriers, and the tier you get determines what data you see.

The Public tier is available with an API key and includes a free trial. It provides equipment moves (container milestones), transshipment events, and planned vessel dates. Authentication is straightforward — register, get a key, start making calls. This tier covers the same data you see on the portal, plus some structured fields that are easier to parse programmatically.

The Private tier requires OAuth2 authentication and booking party identification — CMA CGM needs to verify that you are a party to the shipment before granting access. This tier adds rail and ramp moves, inland move dates, and more granular event data. If you are a freight forwarder managing CMA CGM bookings directly, the private tier is the level you want.

Both tiers are built on DCSA v2.2.0. CMA CGM is a DCSA founding member, and the API output follows the DCSA event structure. This makes CMA CGM’s data relatively straightforward to normalize alongside Maersk, Hapag-Lloyd, and ONE in multi-carrier integrations.

Schedule reliability figures, update cadence estimates, and carrier performance data referenced in this guide are based on third-party industry reports and may reflect specific monthly snapshots rather than sustained averages. Carrier systems and capabilities are subject to change.