The manual tracking workflow on Maersk
Tracking a Maersk shipment manually is the workflow where forwarders spend the most time per shipment relative to the value delivered. The four available channels have different cost, coverage, and authentication models, and picking the wrong one for a given use case wastes operator time. The steps below describe the typical ops-desk workflow for an integrated forwarder with a Maersk account.
- 01
Identify the correct tracking channel for the use case
Four options: Maersk.com portal for one-off queries, Track & Trace Plus API for programmatic access, Legacy Tracking API for older TMS integrations, EDI IFTSTA for enterprise messaging. Portal is adequate for a single customer query; API is required for an ops desk running more than a handful of shipments.
Pain pointForwarders whose TMS only speaks the legacy XML API get PII masking on shipments they don't own — consignee names and addresses are redacted — which makes reconciliation harder for shipments where the forwarder is not the bill-to party.
- 02
Query the chosen channel with container, BL, or booking reference
Each channel accepts different identifier types. Portal accepts all three; the legacy API is username/password authenticated; Track & Trace Plus requires developer portal credentials.
Pain pointOperators used to querying by container number miss shipments when the container isn't yet stuffed or hasn't been assigned — early-stage shipments are only findable by booking reference.
- 03
Parse the returned milestone events
Maersk returns DCSA-standard milestones with ACT/EST/PLN qualifiers. A typical transshipment shipment generates 10 events from origin gate-in through destination gate-out.
Pain pointCustomers don't expect the extra hub events (transshipment hub arrival, discharge, onward load, departure) and get confused when the status jumps from 'departed port of loading' to 'arrived at Tangier' instead of the final destination.
- 04
Compare actual timestamps against planned timestamps
Each event carries a qualifier. ACT is the confirmed actual time, EST is the current best estimate, PLN is the original planned time. Delays surface as ACT drifting from PLN, or as EST updating progressively as the shipment nears each port.
Pain pointRaw delay detection treats a 2-day variance on a pre-Gemini trade the same as on a Gemini service with 85.0% reliability (Sea-Intelligence GLP #177, April 2026, ALL arrivals). A 2-day delay on Gemini is a significant exception; on a less reliable lane it's within baseline noise.
- 05
Refresh the tracking data on a schedule appropriate to the shipment lifecycle stage
Maersk doesn't publish a refresh cadence. Third-party visibility providers consolidating Maersk data poll between 4 and 12 times per day, with tighter intervals near cut-off and port arrival.
Pain pointPolling wastes API quota mid-voyage when the shipment is stable but the customer may still be asking for updates. The DCSA 2.2 subscription callback pattern (push instead of poll) solves this but requires the forwarder's TMS to support webhook ingestion.
- 06
Translate raw milestones into customer-facing status updates
Raw DCSA events are not customer-friendly. 'Gate-in at CNSHA' or 'Discharge at MAES' needs to become 'Container arrived at Shanghai port terminal' or 'In transshipment at Tangier, on schedule for onward connection to Rotterdam on [date].'
Pain pointThis translation is manual ops work repeated for every customer inquiry. Ops staff often build informal cheat sheets or macro templates; forwarders without that infrastructure rewrite the same explanation from scratch.
- 07
Respond to 'where is my shipment?' customer inquiries
Customer emails asking for status get parsed, matched to the correct shipment, checked against current milestone data, and responded to with plain-language status. Industry baseline is 2-4 hours during business hours only.
Pain pointInbound volume scales with customer count. An ops desk handling 200 active shipments might receive 15-30 status inquiries per day, each requiring a tracking check and a custom response.
- 08
Handle exception escalations when a shipment misses a planned event
Missed events (gate-in not received, vessel departure late, discharge delayed) require escalation decisions — who to notify, when, and with what level of detail.
Pain pointMost forwarders don't have an exception escalation framework; decisions get made per-shipment based on senior ops judgment, which creates inconsistency and delays customer notification.
Gemini network and reliability
Since 1 February 2025, Maersk operates the East-West trade lanes jointly with Hapag-Lloyd under the Gemini Cooperation \u2014 29 mainliner services plus 29 shuttle services covering Asia/US West Coast, Asia/US East Coast, Asia/Middle East, Asia/Mediterranean, Asia/North Europe, Middle East\u2013India/Europe, and Transatlantic. The network is built on a hub-and-spoke model that deliberately trades direct calls for transshipment reliability. For tracking, this means more milestone events per shipment: a shipment from Shanghai to Rotterdam that was previously a direct mainliner call now typically involves a hub-port transshipment, generating additional discharge, storage, and load events that customers don't always expect.
Most Gemini hubs are owned or managed by APM Terminals (Maersk) or Hanseatic Global Terminals (Hapag-Lloyd), which gives the cooperation direct operational control over hub turnaround times. Key East-West hubs include Tangier, Salalah, Algeciras, and SCCT (Suez Canal Container Terminal) \u2014 all running digital twins for real-time hub performance modelling. Port Said East and the new Damietta hub terminal come into the SE3 service rotation from April 2026.
Schedule reliability has materially improved under Gemini, and this directly affects how tracking exception detection should work. Sea-Intelligence measured Gemini at 91.2% on-time schedule reliability between February and May 2025, roughly 35 percentage points above the market average over the same period. Current Sea-Intelligence GLP #177 (April 2026, ALL arrivals) shows Gemini at 85.0%, the figure used in the frontmatter facts and exception detection sections of this page. Separately, Gemini reported 92% schedule reliability across its first year of operation. These are distinct measurements from distinct sources covering distinct time periods. All represent the highest sustained reliability in the container shipping industry, and they meaningfully change ETA prediction accuracy for Maersk shipments compared to pre-Gemini baselines. A delay threshold calibrated to an industry averaging 55\u201360% reliability will miss real exceptions on a network averaging ~85%.
Gemini routing and 2026 schedule changes
Gemini launched with a Cape Network design routing most services via the Cape of Good Hope. The first Gemini service to return to Red Sea routing is the ME11 service (India/Middle East to Mediterranean), from mid-February 2026. Other services (SE1, SE3) may follow. Transit times and ETA baselines shift when routing changes \u2014 ops teams need to refresh planning assumptions each time a service transitions, and tracking exception thresholds need to update in parallel.
Effective April 2026, four service adjustments change port rotations that affect tracking baseline assumptions: NE2 adds a direct Antwerp call; NE3 gains a Baltic rotation via Aarhus and Gothenburg with Southampton as the final outbound European call to Asia, and NE3 replaces Ningbo with Yantian in South China; NE4 reverts to its pre-Baltic rotation; and SE3 upgrades to 20,000 TEU vessels with a simplified rotation and a new Damietta hub call. Each change shifts the expected milestone sequence and transit time for shipments on those services. Forwarders whose tracking dashboards or customer ETA commitments are anchored to pre-April 2026 port rotations will see false-positive delay alerts until their baselines update.
Where Maersk tracking errors happen
Tracking failures are less about carrier-side data quality and more about how the forwarder consumes and translates the data. Maersk's underlying feed is one of the better carrier feeds in the industry; the failure modes below describe where ops desks lose time or customer trust on top of a working feed.
Missed DCSA 2.2 subscription opportunities
CommonForwarders whose TMS can't receive webhook callbacks stay on polling, which wastes API quota mid-voyage when shipments are stable and misses near-real-time events when they matter. The fix requires TMS webhook capability, which most mid-market forwarders lack.
PII masking on legacy API confusing reconciliation
OccasionalForwarders querying the legacy tracking API for shipments where they are not the bill-to party or shipper see consignee names and addresses redacted. This is a compliance feature, not a bug, but it catches operators used to unmasked data and breaks automated reconciliation scripts that key off consignee fields.
Transshipment hub events confusing customer-facing status
FrequentGemini's hub-and-spoke design generates extra events at hub ports (arrival, discharge, onward load, departure) that don't appear on direct-call shipments. Customers who expect a straight-line progression from origin to destination see the hub events as anomalies. Ops staff get status inquiries from customers worried their cargo is stuck in Tangier or Salalah when the shipment is actually on schedule.
Generic delay thresholds missing Gemini-scale exceptions
FrequentException detection rules set to 'alert if ETA slips more than 48 hours' work on most trade lanes but under-report on Gemini services. A 24-hour slip on a service averaging 85.0% reliability (Sea-Intelligence GLP #177, April 2026, ALL arrivals) is a meaningful exception worth surfacing; the same slip on a less reliable lane is within normal variance. Forwarders running one threshold across all lanes either get alert fatigue on weak lanes or miss real exceptions on strong lanes.
Polling cadence mismatched to shipment lifecycle stage
CommonA shipment mid-ocean between Shanghai and Rotterdam generates no new milestones for 10-15 days, but ops desks often poll the API at a constant cadence regardless of expected activity. The result is wasted API calls during quiet periods and sometimes insufficient polling near cut-offs when events are actually happening.
Milestone-to-customer-language translation done manually per inquiry
CommonRaw DCSA milestones ('Gate-in at CNSHA', 'Discharge at MAES') are not customer-friendly. Without automation, ops staff rewrite the same status explanation for every customer inquiry, and phrasing drifts between operators and across shipments. Customer trust degrades when the same shipment gets three different status explanations from three different ops staff.
How Expedion agents handle Maersk tracking
Expedion agents consume Maersk's tracking feed through the Track & Trace Plus API and DCSA 2.2 subscription callbacks where the forwarder's TMS supports webhook ingestion. Every capability below is built to reduce the per-shipment operator time on tracking from minutes to near-zero while preserving the customer-facing quality bar.
Agents pull milestone data via Track & Trace Plus API for active shipments and subscribe to DCSA 2.2 callback events where the customer's TMS supports webhook ingestion. For forwarders on legacy TMS systems that only speak the older XML API, agents handle PII masking by reconciling against the forwarder's internal shipment master rather than relying on carrier-returned consignee fields.
Polling intervals are configurable per lifecycle stage: tighter cadence near cut-off and port arrival (every 30-60 minutes), looser cadence in mid-transit (every 4-6 hours). This reduces API quota consumption during quiet periods while maintaining near-real-time awareness at the stages when events actually happen.
Agents compare actual-versus-planned timestamps against Gemini service reliability benchmarks, not a generic 'N-day delay equals exception' rule. A small variance on a Gemini mainliner averaging 85.0% reliability (Sea-Intelligence GLP #177, April 2026, ALL arrivals) surfaces as a meaningful exception because the baseline is tight; the same variance on a less reliable trade lane falls within normal variance. Thresholds are configurable per trade lane and per service.
Agents translate raw DCSA milestones into customer-facing updates that absorb the extra hub events from Gemini's hub-and-spoke design. Instead of a confusing sequence of 'Tangier arrival / Tangier discharge / Tangier onward load / Tangier departure,' the customer sees 'in transshipment at Tangier, on schedule for onward connection to Rotterdam on [date].' The narrative is generated per hub and per destination pair, not hardcoded.
Inbound customer tracking queries arriving by email are parsed, matched to the correct shipment via container, BL, or booking number, and responded to with current status, last milestone, predicted ETA, and any scheduled delay. Response time target: under 5 minutes, 24/7. Industry baseline is 2-4 hours during business hours only. Responses are sent from the forwarder's email domain in the forwarder's voice.
When a shipment slips against its Gemini reliability baseline, agents notify the consignee proactively rather than waiting for the customer to ask. Notifications include the specific milestone that slipped, the updated ETA, the reason where known (transshipment hub congestion, vessel schedule change, Red Sea routing transition), and the forwarder's recommended next action. Forwarder brand voice and notification channel (email, SMS, TMS notification) are configured per customer.
Maersk tracking details
Published Maersk tracking channels, APIs, and milestone standards at a glance. Full Gemini network impact is covered in the sections above. Operator-experience details (real-world refresh cadences, hub-specific quality issues) are in the operator knowledge gap block.
| Detail | Value |
|---|---|
| Primary tracking API | Track & Trace Plus (developer.maersk.com) |
| Legacy tracking API | XML API (delivers.maersk.com/developer/apis/tracking), username/password auth |
| Legacy API PII masking | Consignee names and addresses redacted for non-bill-to requesters |
| EDI messaging set | IFTSTA (milestones), COPARN (booking), APERAK (acknowledgements) |
| Manual tracking | Maersk.com portal, by container / BL / booking reference |
| DCSA standard version | v2.2 (released October 2021) |
| DCSA 2.2 new capabilities | Subscription callbacks (push), enhanced security, document event support |
| Standard milestone count | 10 events for typical transshipment shipment |
| Milestone qualifiers | ACT (actual), EST (estimated), PLN (planned) |
| Third-party refresh cadence | 4-12 polls per day (Maersk does not publish official cadence) |
| Gemini network launch | 1 February 2025 |
| Gemini service count | 29 mainliner + 29 shuttle services |
| Gemini reliability (Sea-Intelligence, Feb-May 2025) | 91.2% |
| Gemini reliability (Sea-Intelligence GLP #177, Mar/Apr 2026, ALL arrivals) | 85.0% |
| Gemini key hubs | Tangier, Salalah, Algeciras, SCCT (APMT/HGT-managed) |
| Red Sea routing return | ME11 service from mid-February 2026; SE1/SE3 may follow |
TMS compatibility for Maersk tracking
Expedion agents consume Maersk tracking from within your existing TMS. For CargoWise users, agents read shipment state via the eAdaptor API and consume milestones through either Maersk's Track & Trace Plus API or IFTSTA EDI, whichever the forwarder is already set up for. For GoFreight and Magaya, agents use the respective REST and Open APIs for internal shipment state and Track & Trace Plus API for carrier-side milestones. Full TMS compatibility details are on the Maersk overview page.
Related pages
Maersk carrier pages: Maersk overview · Shipping instructions · Bill of lading · Booking · Documentation
Tracking across carriers: Container tracking automation · MSC tracking · CMA CGM tracking · Hapag-Lloyd tracking · ONE tracking · COSCO tracking · Evergreen tracking
Frequently asked questions
How does Expedion handle DCSA 2.2 subscription callbacks vs traditional polling?
Agents use DCSA 2.2 subscription callbacks (push) where the forwarder's TMS supports webhook ingestion, which provides near-real-time milestone updates without consuming API quota. For forwarders on older TMS platforms without webhook capability, agents fall back to polling via the Track & Trace Plus API with lifecycle-aware intervals: tighter near port events, looser mid-ocean.
What does Gemini's schedule reliability mean for ETA prediction accuracy on Maersk shipments?
Sea-Intelligence GLP #177 (April 2026, ALL arrivals) reports Gemini at 85.0% schedule reliability; Sea-Intelligence also measured Gemini at 91.2% between February and May 2025, roughly 35 percentage points above the market average over that period. For ETA prediction, this means Maersk shipments on Gemini services have a tighter expected variance window than other networks. Agents use this tighter baseline for exception detection: a small delay on a Gemini service is a meaningful exception, while the same delay on a less reliable lane is within normal variance.
How does the legacy tracking API's PII masking affect forwarders querying shipments they don't own?
Maersk's legacy XML tracking API redacts consignee names and addresses when the requester is not the bill-to party or shipper. This breaks automated reconciliation scripts that key off consignee fields. Agents handle this by reconciling against the forwarder's internal shipment master rather than relying on carrier-returned consignee data.
How does Expedion translate raw hub transshipment events into customer-facing updates?
Gemini's hub-and-spoke design generates extra events at hub ports that confuse customers expecting a direct origin-to-destination progression. Agents collapse hub events (arrival, discharge, onward load, departure) into a single customer-facing narrative like 'in transshipment at Tangier, on schedule for onward connection to Rotterdam on [date],' generated per hub and destination pair.