The manual tracking process on Hapag-Lloyd
Tracking a Hapag-Lloyd shipment involves navigating Gemini's hub-and-spoke milestone pattern, Cape routing transit adjustments, and multiple tracking channels.
- 01
Identify tracking reference
Track by container number (HLCU prefix), BL number (HLCU prefix), or booking reference. The DCSA T&T v2.2 API supports all three query types: Equipment Reference, Carrier Booking Reference, and Transport Document Reference. UACU-prefixed containers from the UASC-era fleet also resolve under HLCU carrier context.
- 02
Log into Navigator 2.0
Access the Online Business Suite shipment overview at www.hapag-lloyd.com. Navigator 2.0 provides shipment-level and container-level visibility, document downloads (booking confirmation, invoice, BL, ICS2 MRN), and milestone events in a timeline view.
- 03
Review container milestones
Standard DCSA 2.2 events on a typical East-West Hapag-Lloyd shipment: origin gate-in, origin terminal load, vessel departure, transshipment hub discharge, transshipment hub load, vessel arrival at destination, destination terminal discharge, and destination gate-out. On Gemini-routed services, the hub-and-spoke design generates additional shuttle-to-mainliner and mainliner-to-shuttle transshipment events at each hub.
Pain pointA Gemini-routed shipment generates more milestone events than a direct service on the same trade. Each hub transit (Tangier, Salalah, Algeciras, SCCT, Damietta) adds a transshipment discharge and a transshipment load event. The event count can confuse ops staff accustomed to THE Alliance's point-to-point milestone pattern.
- 04
Evaluate ETA accuracy against Gemini reliability
Gemini averaged ~90% schedule reliability in 2025 (Sea-Intelligence GLP), with Asia-North Europe and Transatlantic exceeding 95%. This is materially higher than the other groupings per Sea-Intelligence GLP #177 (April 2026, ALL arrivals): Ocean Alliance 67.6%, MSC standalone 73.4%, Premier Alliance 54.2%, against Gemini 85.0% in the same window. Use the Gemini baseline for ETA commitments to consignees, not a generic industry average.
Pain pointReliability is a Gemini Cooperation figure, not Hapag-Lloyd-specific. Pre-Gemini (under THE Alliance), Hapag-Lloyd's reliability was consistent with THE Alliance's lower performance range. The ~90% only applies to Gemini-routed services.
- 05
Factor Cape routing into ETAs
Most Asia-Europe and Mediterranean Gemini services route via the Cape of Good Hope, adding approximately 10–14 days compared to Suez transit times. A full Suez return remains calibrated to security conditions, not a fixed date. Each booking's routing should be checked individually.
- 06
Communicate status to consignee
Translate the shuttle-mainliner-shuttle event chain into a single customer-facing 'in transit' status rather than a confusing list of hub port stops. Surface individual hub transshipment events only when an exception (late shuttle, missed mainliner connection, port congestion) needs explanation.
- 07
Handle exceptions
Detect deviations from expected milestone timing: late shuttle, missed mainliner connection, port congestion, weather delays. Factor in April 2026 service changes (NE2 Antwerp, NE3 Baltic rotation with Aarhus/Gothenburg and Yantian replacing Ningbo, SE3 Damietta hub) when routing assumptions shift.
Gemini network and hub-and-spoke tracking
Hapag-Lloyd tracking operates within the Gemini Cooperation network — a hub-and-spoke vessel-sharing arrangement with Maersk, effective 1 February 2025. Gemini runs 29 mainliner services and 29 shuttle services. Hub ports include Tangier (primary call at APM Terminals MedPort Tangier; HGT participates in TC3 within the same complex), Salalah, Algeciras, SCCT at Port Said, and — from February 2026 — Damietta (DACT, operated by Hanseatic Global Terminals).
The hub-and-spoke design generates a distinctive milestone pattern: a Gemini-routed East-West shipment produces shuttle-to-mainliner and mainliner-to-shuttle transshipment events at each hub port. This is intrinsic to the network design, not a sign of mis-routing. Customer-facing tracking should consolidate the shuttle-mainliner-shuttle event chain into a single on-transit status rather than surfacing every hub stop.
April 2026 service changes impact tracking waypoints directly: NE2 adds Antwerp (new tracking waypoint for Benelux-bound cargo), NE3 adds a Baltic rotation with Aarhus and Gothenburg and replaces Ningbo with Yantian (remap waypoint assumptions for Pearl River Delta), SE3 calls Port Said and the new Damietta hub with Istanbul and Izmit shifted to dedicated shuttles.
Most Asia-Europe and Mediterranean services route via the Cape of Good Hope, adding approximately 10–14 days compared to Suez. A full Suez return remains calibrated to security conditions.
On the terminal side, DACT Damietta is the cleanest example of a Hapag-Lloyd-managed Gemini hub terminal (directly operated by HGT). At Tanger Med, the primary Gemini call is at APM Terminals MedPort Tangier, but HGT's stake in TC3 (Tanger Alliance) sits within the same complex. On most other Gemini hubs, APM Terminals is the operator. Forwarders may observe slightly different event emission patterns between HGT-operated and APM Terminals-operated hubs during the DACT ramp-up period, though the DCSA-standardised event set is the same.
Where Hapag-Lloyd tracking errors happen
The most common Hapag-Lloyd tracking errors, based on the Gemini network structure, routing patterns, and API integration.
Hub-and-spoke milestone confusion
CommonConsignee or ops staff interprets the shuttle-mainliner-shuttle event chain as cargo mis-routing or repeated unnecessary transshipments. The hub-and-spoke pattern is intrinsic to Gemini's design. Remediation: consolidate hub events into a single on-transit status for customer-facing updates. Surface individual hub events only when an exception needs explanation.
Pre-Gemini reliability assumption
CommonETA committed using THE Alliance-era reliability or a generic industry average. Gemini's ~90% baseline is materially higher than THE Alliance's pre-transition performance. Using a lower baseline sets unnecessarily wide delay windows and undermines consignee confidence. Remediation: calibrate ETAs to Gemini reliability on the specific trade.
Cape routing ETA mismatch
CommonTransit time estimate uses Suez-era benchmarks. Actual Gemini routing is Cape of Good Hope on most Asia-Europe and Mediterranean services, adding 10–14 days. Remediation: default to Cape transit times for affected trades unless the specific service has confirmed Suez routing.
Service change routing lag
OccasionalApril 2026 changes (NE2 Antwerp, NE3 Yantian replacing Ningbo, SE3 Damietta hub) not yet reflected in tracking assumptions or TMS waypoint configuration. Consignee pre-alerts reference outdated routing. Remediation: update routing logic and waypoint configuration from the effective date.
DACT Damietta event timing uncertainty
OccasionalDACT is a new HGT-operated hub terminal (commercial operations from February 2026). Event emission patterns may differ from established APM Terminals-managed hubs during the ramp-up period. Remediation: monitor DACT event timing through 2026 and adjust milestone expectations as the terminal stabilises.
UACU container tracking confusion
OccasionalUACU-prefixed container from the UASC-era fleet. TMS or API queries using UACU as the carrier context may not return results — queries must use HLCU. Remediation: map all UACU containers to HLCU carrier context for all tracking API queries.
Competitor reliability conflation
OccasionalUsing Ocean Alliance's 67.6% or MSC standalone's 73.4% (Sea-Intelligence GLP #177, April 2026, ALL arrivals) as the baseline for a Gemini-routed Hapag-Lloyd shipment. Gemini's 85.0% in the same window is the correct baseline for both Hapag-Lloyd and Maersk East-West services. Remediation: always use the Gemini figure for Gemini-routed services.
How Expedion agents handle Hapag-Lloyd tracking
Expedion agents automate Hapag-Lloyd tracking with Gemini-aware milestone consolidation and reliability-calibrated ETA management.
Agents consume Hapag-Lloyd's DCSA T&T v2.2 API at api-portal.hlag.com as the primary tracking feed. All three query types are supported: Equipment Reference (HLCU-prefix container), Carrier Booking Reference, and Transport Document Reference (HLCU-prefix BL). EDI IFTSTA is the fallback for legacy integrations, with Navigator 2.0 scraping as a last resort.
Agents consolidate the shuttle-mainliner-shuttle event chain into a single on-transit status for the consignee-facing view. Individual hub transshipment events (Tangier, Salalah, Algeciras, SCCT, Damietta) are surfaced only when an exception — late shuttle, missed mainliner connection — needs explanation.
Agents calibrate ETA commitments to Gemini reliability (~90% mainliner, 95%+ on Asia-North Europe and Transatlantic) rather than a generic East-West average or pre-Gemini THE Alliance figure. Asia-North Europe shipments carry a narrower delay threshold than other sub-trades.
Agents update routing logic for April 2026 changes automatically: NE2 bookings factor the Antwerp call, NE3 bookings factor the Baltic rotation and Yantian-over-Ningbo switch, SE3 bookings factor the Damietta hub entry. Customer-facing pre-alerts reflect new routing from the effective date.
Agents track which Gemini services are on Cape versus Suez routing and adjust transit time calculations per service string. Time-sensitive cargo on traditionally-Suez lanes is flagged with the Cape routing transit-time delta before booking confirmation.
Agents detect deviations from expected milestone timing, surface delays when they exceed the Gemini reliability-calibrated threshold, and generate customer-facing updates with delay context rather than simply reporting the shipment as delayed.
Agents auto-map UACU-prefixed container queries to HLCU carrier context for API resolution. Tracking results are returned under the HLCU carrier identity regardless of the physical container prefix.
Hapag-Lloyd tracking channels and reliability
Available tracking channels, access methods, and reliability context for Hapag-Lloyd shipments.
| Channel | Access | Coverage | Notes |
|---|---|---|---|
| DCSA T&T v2.2 API | api-portal.hlag.com | Equipment, Booking, Transport Document queries. Shipment, Equipment, Transport events. | Self-serve OAuth. DCSA founding member. v3.0 in beta. |
| DCSA Commercial Schedules API | api-portal.hlag.com | Port-to-port and inland pre/on-carriage schedules. | Live June 2025. DCSA-compliant. |
| Navigator 2.0 | www.hapag-lloyd.com (OBS) | Shipment overview, container tracking, document downloads, milestones. | Web UI for non-API customers. |
| EDI (IFTSTA) | Direct and via INTTRA / Infor Nexus / CargoSmart | Milestone event messages, booking confirmations (COPARN). | Standard for TMS-integrated forwarders. |
| Live Position (add-on) | OBS + API | IoT GPS per-container near-real-time tracking. | Per-container fee. Consignee subscription available in selected countries. |
| Gemini reliability | ~90% 2025 average (Mar/Apr 2026: 85.0%) | N/A | Sea-Intelligence GLP #177 (April 2026, ALL arrivals). Ocean Alliance ~68%, MSC ~73%, Premier ~54%. |
Schedule reliability comparison
Schedule reliability determines the variance window that ops teams should apply when making ETA commitments to consignees. Sea-Intelligence GLP #177 (April 2026, ALL arrivals) provides the baseline:
Gemini Cooperation (Hapag-Lloyd + Maersk): ~85% (85.0%, March/April 2026): the highest sustained reliability in the industry. Asia-North Europe and Transatlantic lanes exceeded 95% in 2025. Hapag-Lloyd's own Customer Value Proposition deck showed 92% mainliner reliability in November 2025 on a 21-day-pre-arrival methodology (methodologically distinct from Sea-Intelligence ALL-arrivals).
MSC standalone: ~73% (73.4%, March/April 2026): operating a standalone East-West network with dual Suez/Cape routing options post-2M dissolution.
Ocean Alliance (CMA CGM, COSCO, OOCL, Evergreen): ~68% (67.6%, March/April 2026): Cape of Good Hope routing on most Asia-Europe/Med compresses schedule buffers.
Premier Alliance (ONE, HMM, Yang Ming): ~54% (54.2%, March/April 2026): the lowest of the four groupings.
These are cooperation/alliance-level figures. Neither Hapag-Lloyd's nor Maersk's individual carrier reliability is separately reported in public Sea-Intelligence data. Pre-Gemini, Hapag-Lloyd's reliability under THE Alliance was consistent with THE Alliance's lower performance range. The ~85% reflects the Gemini Cooperation's hub design, not either partner's standalone historical performance.
Related pages
Hapag-Lloyd carrier pages: Overview · Booking · Shipping instructions · Bill of lading · Documentation
Tracking across carriers: Maersk tracking · MSC tracking · CMA CGM tracking · ONE tracking · COSCO tracking · Evergreen tracking
Solutions: Tracking automation
Frequently asked questions
What DCSA API version does Hapag-Lloyd support?
Hapag-Lloyd's tracking API conforms to DCSA Track & Trace v2.2, the current production standard (released October 2021). The API is hosted at api-portal.hlag.com with self-serve OAuth registration. It supports three query types: Equipment Reference (HLCU-prefix container number), Carrier Booking Reference, and Transport Document Reference (HLCU-prefix BL number). Hapag-Lloyd is a DCSA founding member. DCSA v3.0 exists in beta but v2.2 remains the production standard.
How does Gemini's hub-and-spoke affect tracking milestones?
Gemini's hub-and-spoke design routes shipments through hub ports (Tangier, Salalah, Algeciras, SCCT, Damietta from 2026) via shuttle-mainliner-shuttle connections. Each hub transit generates a transshipment discharge and a transshipment load event, so a Gemini-routed shipment produces more milestone events than a direct service on the same trade. This is intrinsic to the network design, not a sign of mis-routing. Expedion agents consolidate hub events into a single on-transit status for consignee-facing updates.
What is Hapag-Lloyd's schedule reliability?
Gemini Cooperation (Hapag-Lloyd + Maersk) averaged approximately 90% schedule reliability in 2025, with Asia-North Europe and Transatlantic exceeding 95%. Sea-Intelligence GLP #177 (April 2026, ALL arrivals) shows Gemini at 85.0%. For comparison: Ocean Alliance ~68% (67.6% point), MSC standalone ~73% (73.4% point), Premier Alliance ~54% (54.2% point). The ~90% is a Gemini Cooperation figure, not Hapag-Lloyd-specific; both partners' mainliners contribute to the same reliability pool.
Does Hapag-Lloyd offer push-based tracking notifications?
Hapag-Lloyd's DCSA T&T v2.2 API emits events as they occur at each terminal and vessel operation rather than on a fixed polling interval. API subscribers receive events via the query model. Hapag-Lloyd is a member of DCSA working groups driving push/subscription models for v3.0. For near-real-time tracking on a per-container basis, the Live Position add-on provides IoT GPS tracking through OBS and API.
How does Cape of Good Hope routing affect Hapag-Lloyd ETAs?
Most Asia-Europe and Mediterranean Gemini services route via the Cape of Good Hope, adding approximately 10–14 days compared to Suez transit times. A full Suez return remains calibrated to security conditions, not a fixed date. Expedion agents check per-service routing rather than applying a carrier-level assumption and adjust ETA calculations accordingly.
What is the Commercial Schedules API?
Hapag-Lloyd launched a DCSA-compliant Commercial Schedules API in June 2025, hosted at api-portal.hlag.com alongside the T&T API. It provides port-to-port and inland (pre/on-carriage) sailing schedules. This is useful for combining schedule and tracking data in the same integration layer — for example, comparing an actual ETA milestone against the planned schedule baseline.
What is Live Position?
Live Position is an IoT-based near-real-time GPS tracking add-on available on a per-container basis for shipments where the container is fitted with a Hapag-Lloyd remote monitoring device. It is subscribed at booking or post-booking through OBS and accessible to both shipper and consignee (consignee subscription gated to a defined country list including India, EU member states, UK, and others). A Live Position API is also available through the Developer Portal for TMS integration.