The manual tracking process on COSCO
Tracking a COSCO shipment involves Ocean Alliance operating-carrier variability, a DCSA T&T v2.2 conformance gap versus other Tier 1 carriers, and the 67.6% March/April 2026 alliance reliability baseline.
- 01
Identify tracking reference
Track by container number, BL number (COSU prefix), or booking reference. Legacy-prefix containers (CCLU, CSLU, CBHU, COCU from the February 2016 China Shipping merger; CICU for leased equipment) should be queried under the COSU carrier context. OOCL-owned containers (OOLU) route under the separate OOCL tracking system, not COSCO's, even when the booking is on COSCO.
- 02
Access SynCon Hub tracking
Log into synconhub.coscoshipping.com for shipment-level and container-level visibility. Tracking is integrated with the booking platform. Real-time updates are stated, but the native refresh cadence for container milestones is not published.
Pain pointSynCon Hub is the primary customer-facing platform, but the actual refresh cadence for container milestones has not been published by COSCO. Forwarders relying only on SynCon Hub may miss short-window exceptions.
- 03
Review container milestones
Standard events: gate-in at origin terminal; loaded on vessel; vessel departed origin port; vessel arrived at transhipment port (if applicable); vessel arrived destination port; discharged from vessel; gate-out at destination terminal. Refresh cadence varies by channel: TrackCargo 90 minutes, TRADLINX 12x daily, JSONCargo on-demand API, GoComet near-real-time.
- 04
Identify the operating carrier
Booking confirmation and vessel schedule specify the operating carrier. A COSCO booking may physically sail on a COSCO, CMA CGM, OOCL, or Evergreen vessel depending on the Ocean Alliance service string rotation. Tracking feed source depends on the operating carrier.
Pain pointOn alliance-partner tonnage (CMA CGM, OOCL, or Evergreen vessels), milestone events originate from the operating carrier's system before flowing into COSCO's visibility platform. Data lag is possible. Partner carriers may also report a different set of intermediate milestones.
- 05
Evaluate ETA against Ocean Alliance reliability
Ocean Alliance schedule reliability was 67.6% in March/April 2026 (Sea-Intelligence GLP #177, ALL arrivals). For context in the same window: Gemini Cooperation 85.0%, MSC standalone 73.4%, Ocean Alliance 67.6%, Premier Alliance 54.2%. Global reliability was 62.4% in April 2026, the highest figure of the year. Build schedule buffers calibrated to the 67.6% baseline.
Pain pointAt approximately 68% reliability, roughly 3 in 10 arrivals are delayed. Proactive tracking (continuous ETA recalibration against AIS vessel positions) outperforms passive milestone polling.
- 06
Factor in Day 10 Product (April 2026)
The Ocean Alliance's Day 10 Product deploys approximately 390 vessels across 41 weekly service loops covering 520+ direct port pairs. More port pairs per loop can mean more intermediate transhipment events on a given shipment. Customer-facing tracking should consolidate connected legs into a single shipment view rather than exposing every intermediate vessel change.
- 07
Handle exceptions
Detect deviations: late gate-in; missed vessel loading (common failure mode tied to 'No VGM, No Gate-in' and 'No MRN, No Load' blocks); transhipment dwell; weather delays. At roughly 64% alliance reliability, exception management is a material share of the tracking workload rather than an edge case.
Ocean Alliance network and operating-carrier tracking
Ocean Alliance members are COSCO, CMA CGM, OOCL, and Evergreen. The alliance was extended to 2032 in an agreement signed on 27 February 2024. The Day 10 Product launched in April 2026 with approximately 390 vessels across 41 weekly loops and 520+ direct port pairs.
Operating-carrier tracking patterns differ per alliance member. COSCO-operated sailings feed directly through SynCon Hub, the COP portal, and EDI IFTSTA. CMA CGM-operated sailings have milestone events that originate from CMA CGM's systems before flowing into COSCO's visibility platform; data lag on alliance-partner legs is possible and milestone granularity may differ. OOCL-operated sailings are the trickiest case: OOCL is a wholly-owned COSCO subsidiary (acquired July 2018 for approximately USD 6.3 billion) but runs separate IT systems and uses its own SCAC (OOLU). OOLU-prefix containers are tracked under the OOCL carrier context, not COSU, and data lag or milestone granularity may differ. Evergreen-operated sailings go through an alliance-partner feed rather than a subsidiary, with its own data-lag and milestone-reporting characteristics.
Three Transatlantic services include ONE tonnage under a separate cooperation agreement — not Ocean Alliance membership. That cooperation was reduced in early 2026 to two loops with 14 vessels (a 37% capacity cut on the North Atlantic). Tracking on ONE-operated Transatlantic legs requires awareness of ONE's milestone conventions, which differ from Ocean Alliance partner conventions.
Ocean Alliance schedule reliability was 67.6% in March/April 2026 (Sea-Intelligence GLP #177, ALL arrivals). Global reliability was 62.4% in April 2026, the highest figure of the year. No COSCO-specific carrier-level reliability data is published; the 67.6% figure is alliance-level.
The DCSA conformance picture is the largest documented standards gap among Tier 1 carriers in the Expedion roster. Maersk, CMA CGM, Hapag-Lloyd, MSC, and ONE all have DCSA Track & Trace v2.2 live. COSCO's DCSA T&T v2.2 conformance is not confirmed from public sources. The COP portal's open API is referenced by COSCO marketing as a developer entry point, but whether it implements the DCSA T&T standard or is proprietary is unconfirmed.
Where COSCO tracking errors happen
Common COSCO tracking rework and data-quality triggers, drawn from Ocean Alliance operating-carrier variability, the DCSA conformance gap, and third-party refresh cadence behaviour.
Operating-carrier milestone lag
CommonCOSCO booking on a CMA CGM, OOCL, or Evergreen vessel. Milestones delayed or incomplete compared to COSCO-operated services. TMS shows stale data. Remediation: poll the operating carrier's tracking feed in parallel with COSCO's to ensure milestone completeness.
OOCL vessel container-prefix confusion
OccasionalCOSCO booking on OOCL tonnage with OOLU-prefix equipment. Tracking query defaults to COSU carrier context, returns no results. Remediation: detect OOLU-prefix containers and route tracking queries to OOCL's systems.
Legacy prefix tracking failure
CommonCCLU, CSLU, CBHU, COCU, or CICU-prefixed container queried without COSU carrier context. Tracking returns no results. Remediation: map all legacy-prefix containers to COSU for API and portal queries.
DCSA conformance assumption
CommonIntegration team assumes COSCO has DCSA T&T v2.2 live (as all other Tier 1 carriers do). Builds the pipeline to DCSA v2.2 endpoints, encounters the conformance gap, and breaks the integration. Remediation: treat COSCO as non-DCSA-confirmed; fall back to SynCon Hub feeds, COP portal, third-party aggregators, and EDI IFTSTA until conformance is verified.
Ocean Alliance reliability overestimate
CommonETA committed to consignees using Gemini (~85.0% March/April 2026) or industry-average benchmarks. Actual Ocean Alliance reliability is 67.6% (Sea-Intelligence GLP #177, April 2026, ALL arrivals). Wider delay variance than expected. Remediation: calibrate ETAs to the Ocean Alliance baseline and build larger buffers.
Transhipment event gap
OccasionalMulti-leg shipment on alliance-partner tonnage misses discharge/reload events at the transhipment port. Consignee ETA mis-calibrated. Remediation: cross-reference AIS vessel position data against the published schedule and generate synthetic transhipment events when the carrier feed is silent.
Customs clearance milestone absence
OccasionalOps staff assume COSCO reports US CBP release or EU customs release as a milestone event. This is not confirmed in public sources. Consignee expectation mismatch. Remediation: pending confirmation, do not surface customs release through COSCO tracking; source from the customs broker system instead.
Third-party aggregator cadence misuse
OccasionalTMS configured to poll TrackCargo every 15 minutes when the source refresh is 90 minutes. No additional data; just wasted API cost. Remediation: align polling to source cadence (TrackCargo 90 min, TRADLINX 12x daily, JSONCargo on-demand).
How Expedion agents handle COSCO tracking
Expedion agents consolidate COSCO tracking across SynCon Hub, the COP portal, third-party aggregators, and EDI IFTSTA, with operating-carrier awareness and ETA calibration to the Ocean Alliance reliability baseline.
Consume COSCO tracking through SynCon Hub and the COP portal as primary feeds. Supplement with third-party aggregators (TrackCargo 90 min, TRADLINX 12x daily, JSONCargo on-demand, GoComet near-real-time) to close refresh-cadence gaps, especially where SynCon Hub's native cadence is unpublished.
Identify the operating carrier (COSCO, CMA CGM, OOCL, or Evergreen) per booking from the booking confirmation and vessel schedule. Poll the operating carrier's tracking feed in parallel with COSCO's to reduce the data-lag window on alliance-partner legs.
Calibrate ETA commitments to Ocean Alliance's 67.6% March/April 2026 reliability baseline (Sea-Intelligence GLP #177, ALL arrivals). Tighter buffers than Premier Alliance (54.2% March/April 2026), wider than Gemini (85.0% March/April 2026). Continuous ETA recalibration from AIS vessel positions rather than published schedules.
Consolidate connected legs from the Day 10 Product's 41 weekly loops into a single on-transit status for consignee-facing views. Surface individual transhipment events only when an exception (missed connection, hub dwell) needs explanation.
Validate COSCO milestone data against AIS vessel position data for ETA sanity-checking and synthetic event generation when the carrier feed is silent on a transhipment leg.
Auto-map CCLU, CSLU, CBHU, COCU, and CICU container queries to COSU carrier context. Detect OOLU-prefix containers and route those tracking queries to OOCL's systems instead of COSCO's.
Until COSCO's DCSA T&T v2.2 conformance is verified, route all programmatic tracking queries through SynCon Hub, COP portal open API, third-party aggregators, and EDI IFTSTA rather than DCSA v2.2 endpoints.
Detect deviations from expected milestone timing against the Ocean Alliance reliability baseline. Monitor 'No VGM, No Gate-in' and 'No MRN, No Load' holds and escalate immediately. Generate consignee-facing updates with delay context.
Poll each channel at its native refresh cadence rather than forcing a uniform polling interval. Avoids wasted API calls on TrackCargo (90-minute source) while maintaining real-time posture through JSONCargo on-demand for high-priority shipments.
COSCO tracking channels and reliability
Available tracking channels, refresh cadence, and the canonical Ocean Alliance reliability baseline.
| Channel | Access | Coverage | Notes |
|---|---|---|---|
| SynCon Hub | synconhub.coscoshipping.com | Container tracking, BL tracking, shipment status, document downloads. | Primary customer-facing platform. Native refresh cadence for container milestones not published. |
| COP portal | cop.lines.coscoshipping.com | Customer operations platform. Open API referenced. | Whether the open API implements DCSA T&T or is proprietary is unconfirmed. |
| DCSA T&T v2.2 API | Not confirmed | Container, BL, booking reference queries (if live). | Conformance not confirmed from public sources. Maersk, CMA CGM, Hapag-Lloyd, MSC, and ONE all have v2.2 live. |
| TrackCargo (3rd-party) | trackcargo.net / API | Container and BL tracking aggregation. | 90-minute refresh cadence. |
| TRADLINX (3rd-party) | tradlinx.com / API | Container and BL tracking aggregation. | 12x daily refresh. |
| JSONCargo API (3rd-party) | jsoncargo.com/cosco-container-tracking-api | On-demand container tracking API. | Pay-per-query on-demand model. |
| GoComet (3rd-party) | gocomet.com | Container tracking and visibility. | Near-real-time refresh cadence. |
| EDI IFTSTA | Direct and via INTTRA | Milestone status event messages. | Standard for TMS-integrated forwarders. |
| Ocean Alliance reliability | 67.6% (March/April 2026) | N/A | Sea-Intelligence GLP #177, ALL arrivals. Comparators same window: Gemini 85.0%, MSC 73.4%, Premier Alliance 54.2%. |
Schedule reliability comparison
Canonical alliance-level reliability figures per Sea-Intelligence GLP #177 (April 2026, ALL arrivals):
- Gemini Cooperation (Maersk + Hapag-Lloyd): 85.0% - MSC standalone: 73.4% - Ocean Alliance (COSCO + CMA CGM + OOCL + Evergreen): 67.6% - Premier Alliance (ONE + HMM + Yang Ming): 54.2% - Source: Sea-Intelligence GLP #177 (April 2026, ALL arrivals)
Ocean Alliance ranked third among the four groupings in that window: well below Gemini and MSC standalone, but above Premier Alliance.
Sea-Intelligence published global on-time reliability at 62.4% for April 2026, the highest figure of the year. GLP #177 (April 2026, ALL arrivals) is the canonical alliance-level reference used on this page.
Sea-Intelligence typically publishes alliance-level aggregates. Individual carrier-level reliability for COSCO separate from the Ocean Alliance aggregate is not consistently published, so the alliance-level number is the working reference for forwarders.
Related pages
COSCO carrier pages: Overview · Booking · Shipping instructions · Bill of lading · Documentation
Tracking across carriers: Maersk tracking · MSC tracking · CMA CGM tracking · Hapag-Lloyd tracking · ONE tracking · Evergreen tracking
Ocean Alliance context: OOCL — COSCO subsidiary with separate IT systems, SCAC (OOLU), and customer portal (MyOOCL).
Solutions: Tracking automation
Frequently asked questions
Does COSCO implement the DCSA Track & Trace v2.2 API?
Not confirmed from public sources. COSCO's DCSA T&T v2.2 conformance was not verifiable during research, which is a material gap versus Maersk, CMA CGM, Hapag-Lloyd, MSC, and ONE — all of which have v2.2 live. Verification is pending operator confirmation. The COP portal's open API is referenced by COSCO marketing as a developer entry point, but whether it implements the DCSA T&T standard or is proprietary is also unconfirmed. Expedion agents treat COSCO as non-DCSA-confirmed and route programmatic tracking through SynCon Hub, the COP portal, third-party aggregators, and EDI IFTSTA via INTTRA until conformance is verified.
How does Ocean Alliance operating-carrier affect tracking quality?
A COSCO booking may physically sail on a COSCO, CMA CGM, OOCL, or Evergreen vessel depending on the Day 10 Product service string rotation. Operating carrier determines the tracking feed source. On COSCO-operated sailings, milestones feed directly through SynCon Hub and the COP portal. On alliance-partner tonnage, milestones originate from the operating carrier's system before flowing into COSCO's visibility platform — potential data lag and different milestone granularity. OOCL-operated sailings are the trickiest case: OOCL runs separate IT systems and uses its own SCAC (OOLU), so OOLU-prefix container queries must route to OOCL's tracking rather than COSCO's. Expedion agents identify the operating carrier per booking and poll the relevant system in parallel.
What is COSCO's schedule reliability?
COSCO-specific carrier-level reliability is not published. Sea-Intelligence publishes Ocean Alliance aggregate reliability rather than a COSCO-only breakdown. The alliance-level figure is 67.6% in March/April 2026 (Sea-Intelligence GLP #177, ALL arrivals). For context in the same window: Gemini Cooperation 85.0%, MSC standalone 73.4%, Ocean Alliance 67.6%, Premier Alliance 54.2%. Global reliability was 62.4% in April 2026, the highest figure of the year.
What refresh cadence do third-party tracking integrations offer for COSCO?
TrackCargo refreshes every 90 minutes. TRADLINX refreshes 12 times daily. JSONCargo offers an on-demand pay-per-query API. GoComet provides near-real-time updates. SynCon Hub's own native refresh cadence for container milestones is not published by COSCO, which is why third-party aggregators are often used to close refresh-cadence gaps. Expedion agents align polling to each channel's native cadence rather than forcing a uniform polling interval, avoiding wasted API calls on slower-refresh sources while maintaining real-time posture for high-priority shipments through JSONCargo on-demand.
How should forwarders handle tracking on OOCL-operated legs of a COSCO booking?
Route OOLU-prefix container queries to OOCL's tracking system, not COSCO's. OOCL is a wholly-owned COSCO subsidiary (acquired July 2018 for approximately USD 6.3 billion) but runs separate IT systems and uses its own SCAC (OOLU). A COSCO booking on OOCL tonnage will produce OOLU-prefix equipment, which returns no results if queried under the COSU carrier context. Whether ops teams query OOCL in parallel or rely on COSCO consolidation for OOCL-operated legs is not confirmed in public sources. Expedion agents detect OOLU-prefix containers and route tracking queries to OOCL's systems automatically.
Does COSCO report customs clearance milestones?
It is not confirmed in public sources that COSCO reports US CBP release, EU customs release, or equivalent customs-clearance milestones as standard events in SynCon Hub or the COP portal. Container movement events (gate-in, loaded, departed, arrived, discharged, gate-out) are the confirmed milestone set. Pending operator confirmation, Expedion agents do not surface customs release through COSCO tracking and source customs-clearance status from the customs broker system instead.
How does COSCO's reliability compare to other alliance groupings?
Using the canonical Sea-Intelligence GLP #177 figures (April 2026, ALL arrivals), Ocean Alliance ranked third among the four major groupings: Gemini Cooperation 85.0%, MSC standalone 73.4%, Ocean Alliance 67.6%, Premier Alliance 54.2%. Ocean Alliance sits well below Gemini and MSC standalone but above Premier Alliance. Forwarders should calibrate COSCO ETA commitments to the Ocean Alliance baseline and build wider buffers than for Gemini or MSC bookings. Global reliability was 62.4% in April 2026, the highest figure of the year.