The manual tracking process on ONE
Tracking an ONE shipment involves navigating Premier Alliance vessel assignments, operating-carrier data feeds, hub-and-spoke transshipment events, and a ~54% reliability baseline.
- 01
Identify tracking reference
Track by container number, BL number (ONEY prefix), or booking reference. Legacy-prefix containers (NYKU, MOLU, KKLU) should be queried under ONEY carrier context.
- 02
Access ONE eCommerce tracking
Log into ecomm.one-line.com for shipment-level and container-level visibility. Real-time milestone events, document access (booking confirmation, BL), and status updates.
- 03
Review container milestones
Standard DCSA 2.2 events: origin gate-in, terminal load, vessel departure, transshipment discharge/load, vessel arrival, destination discharge, gate-out. On Premier Alliance bookings, milestones originate from the operating carrier's systems (ONE, HMM, Yang Ming, or MSC).
Pain pointPremier Alliance cross-carrier tracking quality depends on the inter-carrier data exchange. ONE bookings on HMM or Yang Ming tonnage receive consolidated milestones through ONE's platform, but the underlying source is the operating carrier's infrastructure. Latency and granularity may differ from ONE-operated services.
- 04
Identify the operating carrier
Booking confirmation specifies the operating carrier. An 'ONE booking' may physically sail on an HMM, Yang Ming, or MSC slot exchange vessel. Tracking feed source depends on the operating carrier.
Pain pointOn MSC slot exchange tonnage (9 Asia-Europe services), milestone naming conventions reflect MSC's tracking standard, not ONE's. This can confuse TMS systems expecting ONE-standard event codes.
- 05
Evaluate ETA against Premier Alliance reliability
Premier Alliance schedule reliability: 54.2% (April 2026, Sea-Intelligence GLP #177), down from 58.8% in January 2026 (GLP #174). For comparison: Gemini 85.0%, MSC standalone 73.4%, Ocean Alliance 67.6%. Build wider schedule buffers than other alliance groupings.
Pain point~54% reliability means nearly half of arrivals are delayed. Proactive tracking (continuous ETA recalibration from vessel positions) is essential, not passive milestone polling.
- 06
Factor in April 2026 hub-and-spoke
The restructure adds shuttle-to-mainliner transshipment events at Busan and Shanghai hubs on Asia-Europe lanes. Fewer direct port calls, more intermediate events. Customer-facing tracking should consolidate shuttle and mainliner legs.
- 07
Handle exceptions
Detect deviations: late shuttle to hub, missed mainliner connection, hub port congestion, weather delays. At this reliability baseline, exception management is a larger share of tracking workload than for higher-reliability carriers.
Premier Alliance network and operating-carrier tracking
ONE tracking operates within the Premier Alliance network — a 5-year vessel-sharing agreement with HMM and Yang Ming, effective 9 February 2025. Post-Hapag-Lloyd restructuring expanded service counts across all major trade lanes. Separately, ONE has a slot exchange with MSC on 9 Asia-Europe services — not an alliance membership but a capacity cooperation.
Operating-carrier tracking patterns determine the data source for each booking:
- ONE-operated: Direct T&T feed, full DCSA event set. - HMM-operated: Consolidated milestones through ONE's platform. Source is HMM's infrastructure. Latency and granularity may differ. - Yang Ming-operated: Similar consolidation pattern to HMM. - MSC slot exchange: Consolidated from MSC's tracking platform. Milestone naming reflects MSC's standard, not ONE's. Event richness reflects MSC's tracking quality.
The April 2026 hub-and-spoke restructure uses Busan and Shanghai as primary Asian hubs. Fewer direct China calls. More shuttle-to-mainliner transshipment events on Asia-Europe lanes. Customer-facing tracking should consolidate shuttle and mainliner legs into a single shipment view rather than presenting two separate tracking streams.
Most East-West services route via the Cape of Good Hope. Transit times are materially longer than Suez-era benchmarks. The Red Sea-China Service is the only confirmed Suez product.
ONE is a founding DCSA member (established April 2019) with broader standards implementation than most Tier 1 carriers: T&T v2.2, OVS 3.0, BOL 3.0 (ISS), Commercial Schedule 1.0, Booking 2.0 Beta. The developer portal at developers.one-line.com requires registration to access full documentation — this limits public visibility compared to Maersk's or CMA CGM's openly documented API portals.
Reliability trajectory: Premier Alliance slipped from 58.8% in January 2026 (GLP #174) to 54.2% by April 2026 (GLP #177). The April 2026 restructure is explicitly aimed at improvement through fewer port calls per rotation.
Where ONE tracking errors happen
The most common ONE tracking errors, driven by the Premier Alliance multi-carrier structure, hub-and-spoke routing, and reliability baseline.
Operating-carrier milestone lag
ONE booking on HMM or Yang Ming vessel. Milestones delayed or incomplete compared to ONE-operated services. TMS shows stale data. Remediation: poll operating carrier's tracking feed in parallel with ONE's to ensure milestone completeness.
MSC event code mismatch
ONE booking on MSC slot exchange tonnage. MSC milestone naming conventions don't match ONE's standard event codes. TMS mapping breaks. Remediation: configure TMS to handle both ONE and MSC event taxonomies for Premier Alliance bookings.
Premier Alliance reliability overestimate
ETA committed using Gemini (~85%) or industry average. Actual Premier Alliance: ~54%. Wider delay variance. Remediation: calibrate ETAs to Premier Alliance baseline and build larger buffers.
Hub-and-spoke event confusion
April 2026 restructure generates shuttle-to-mainliner transshipment events at Busan and Shanghai. Ops staff interprets intermediate hub events as mis-routing. Remediation: consolidate hub events into single on-transit status for customer-facing view.
Legacy container tracking failure
NYKU, MOLU, or KKLU-prefixed container queried without ONEY carrier context. Tracking returns no results. Remediation: map all legacy-prefix containers to ONEY for API queries.
Cape routing ETA mismatch
Transit time based on Suez-era benchmarks. Actual routing via Cape of Good Hope. Remediation: default to Cape transit times for affected trades.
Developer portal access barrier
Integration team cannot access API documentation without registration. Delays tracking integration setup. Remediation: register on developers.one-line.com early in the integration timeline.
How Expedion agents handle ONE tracking
Expedion agents automate ONE tracking with operating-carrier-aware milestone consolidation and Premier Alliance reliability-calibrated ETA management.
Consume ONE's DCSA T&T v2.2 API as primary tracking feed. Support container, BL, and booking reference queries. Implement polling alongside any subscription-based feed.
Identify the operating carrier (ONE, HMM, Yang Ming, MSC slot exchange) per booking from the booking confirmation. Poll the operating carrier's tracking feed in parallel with ONE's to ensure milestone completeness and timeliness.
Calibrate ETA commitments to Premier Alliance's ~54% reliability baseline. Wider delay buffers than Gemini or Ocean Alliance. Continuous ETA recalibration from actual vessel positions rather than published schedules.
Consolidate shuttle-mainliner transshipment events at Busan/Shanghai hubs into single on-transit status for consignee-facing view. Surface individual hub events only when an exception (missed connection, hub congestion) needs explanation.
For bookings on MSC slot exchange tonnage, translate MSC milestone naming conventions to ONE-consistent event codes for the forwarder's TMS.
Detect deviations from expected milestone timing against the Premier Alliance reliability baseline. At ~54%, exception management is a larger share of tracking workload. Generate customer-facing updates with delay context.
Auto-map NYKU, MOLU, KKLU container queries to ONEY carrier context for API resolution.
Track which services route via Cape vs Suez (Red Sea-China Service is the only confirmed Suez product). Adjust transit time calculations per service string.
ONE tracking channels and reliability
Available tracking channels, access methods, and reliability context for ONE shipments.
| Channel | Access | Coverage | Notes |
|---|---|---|---|
| DCSA T&T v2.2 API | developers.one-line.com | Container, BL, booking reference queries. Shipment, Equipment, Transport events. | Founding DCSA member. Documentation gated behind registration. v3.0 in beta. |
| DCSA OVS 3.0 | developers.one-line.com | Operational Vessel Schedules. | DCSA-compliant. |
| DCSA BOL 3.0 (ISS) | developers.one-line.com | Bill of Lading standard. | DCSA-compliant. |
| DCSA Commercial Schedule 1.0 | developers.one-line.com | Port-to-port schedules. | DCSA-compliant. |
| DCSA Booking 2.0 Beta | developers.one-line.com | Booking standard. | Beta. |
| eCommerce portal | ecomm.one-line.com | Container tracking, BL info, shipment status, document downloads. | Web UI for non-API customers. |
| Mobile app | ONE Container Tracking (iOS/Android) | Booking status, SI status, BL info. | -- |
| EDI | Direct and via INTTRA/Infor Nexus/CargoSmart | Milestone event messages. | Standard for TMS-integrated forwarders. |
| Premier Alliance reliability | 54.2% (Mar/Apr 2026) | N/A | Sea-Intelligence GLP #177. Gemini 85.0%, MSC 73.4%, Ocean Alliance 67.6%. |
Schedule reliability comparison
Carrier and alliance schedule reliability determines the variance window that ops teams should apply when making ETA commitments. Sea-Intelligence Global Liner Performance #177 (April 2026) provides the baseline:
Gemini Cooperation (Maersk + Hapag-Lloyd): 85.0%: the highest sustained reliability in the industry.
MSC standalone: 73.4%: post-2M dissolution, operating a standalone East-West network.
Ocean Alliance (CMA CGM + COSCO + Evergreen): 67.6%
Premier Alliance (ONE + HMM + Yang Ming): 54.2%
Trajectory: Premier Alliance slipped from 58.8% in January 2026 (GLP #174) to 54.2% by April 2026 (GLP #177). The April 2026 hub-and-spoke restructure is explicitly aimed at improving this through fewer port calls per rotation.
Sea-Intelligence does not consistently publish ONE-specific figures separately from the Premier Alliance aggregate. ONE individual carrier: 55.1% (May 2025). The alliance-level number is the working reference for forwarders.
Related pages
All ONE pages: Overview · Booking · Shipping instructions · Bill of lading · Documentation
Tracking across carriers: Maersk tracking · MSC tracking · CMA CGM tracking · Hapag-Lloyd tracking · COSCO tracking · Evergreen tracking
Solutions: Tracking automation
Frequently asked questions
What DCSA API standards does ONE implement?
ONE is a founding DCSA member (established April 2019) and implements Track & Trace v2.2, Operational Vessel Schedule 3.0, Bill of Lading 3.0 (ISS), Commercial Schedule 1.0, and Booking 2.0 Beta. This is one of the broader DCSA portfolios among Tier 1 carriers. The APIs are accessible through the developer portal at developers.one-line.com, though documentation requires registration.
How does Premier Alliance operating-carrier affect tracking quality?
Premier Alliance bookings may sail on ONE, HMM, Yang Ming, or MSC slot exchange vessels. ONE-operated services provide direct T&T feed with full DCSA events. HMM and Yang Ming-operated services deliver consolidated milestones through ONE's platform, but the source is the partner's infrastructure — latency and granularity may differ. MSC slot exchange tonnage uses MSC's milestone naming conventions, which can cause TMS event mapping issues.
What is ONE's schedule reliability?
Premier Alliance schedule reliability was 54.2% in March/April 2026 (Sea-Intelligence GLP #177), down from 58.8% in January 2026 (GLP #174). ONE individual carrier: 55.1% (May 2025, not consistently reported separately from the alliance). For context: Gemini 85.0%, MSC 73.4%, Ocean Alliance 67.6% in March/April 2026.
How does the April 2026 hub-and-spoke restructure affect tracking?
The restructure uses Busan and Shanghai as primary Asian hubs, replacing some direct port calls with shuttle-to-mainliner connections. This generates additional transshipment events in the tracking timeline. Customer-facing tracking should consolidate shuttle and mainliner legs into a single shipment view. Expedion agents handle this consolidation automatically, surfacing individual hub events only when an exception needs explanation.
Does ONE offer push-based tracking notifications?
The DCSA T&T v2.2 standard supports subscription callbacks for push-based event notifications. ONE's specific implementation of subscriptions and webhooks requires developer portal access to verify. Expedion agents implement polling alongside any subscription-based feed to ensure no milestones are missed.
Is ONE's API documentation publicly accessible?
No. ONE's developer portal at developers.one-line.com requires registration to access full API documentation. The public-facing pages describe available products but do not expose detailed endpoint specifications, rate limits, or data schemas. This contrasts with Maersk's and CMA CGM's openly documented API portals.
How does ONE's reliability compare to other alliance groupings?
March/April 2026 (Sea-Intelligence GLP #177): Gemini 85.0%, MSC standalone 73.4%, Ocean Alliance 67.6%, Premier Alliance 54.2%. Premier Alliance is the lowest of the four groupings, slipping from 58.8% in January 2026 (GLP #174). The April 2026 hub-and-spoke restructure is aimed at improvement through fewer port calls per rotation.