The manual tracking process on Evergreen
Evergreen tracking spans ShipmentLink, the DCSA Track & Trace v2.2 API, EDI IFTSTA via INTTRA, and several third-party aggregators with their own refresh cadences. Ocean Alliance vessel sharing means an Evergreen booking may execute on an Evergreen, CMA CGM, COSCO, or OOCL vessel, each with different tracking-feed characteristics.
- 01
Identify tracking reference
Track by container number, BL number (EGLV prefix), or booking reference via ShipmentLink. Evergreen-owned container prefixes include EMCU, EGHU, EGSU, and EITU, plus HMCU registered to Evergreen Marine (UK) and UGMU for U-class containers. IMT U-class LTIU and IMTU prefixes query under EGLV carrier context where post-consolidation routing has been confirmed; this is not confirmed in public sources at the per-shipment level. OOCL-owned containers (OOLU) route under the separate OOCL tracking system, not Evergreen's, even when the booking is on Evergreen.
- 02
Access ShipmentLink tracking
Log into shipmentlink.com or use the ShipmentLink mobile app for shipment-level and container-level visibility. Primary customer-facing platform for Evergreen shipments.
Pain pointShipmentLink is the primary customer-facing platform but the actual native refresh cadence for container milestones has not been published by Evergreen. Forwarders relying only on ShipmentLink may miss short-window exceptions between polls.
- 03
Review container milestones
Standard events: gate-in origin, loaded on vessel, vessel departed origin, vessel arrived at transhipment (if applicable), vessel arrived destination, discharged from vessel, gate-out destination. Refresh cadence varies by channel: TrackCargo 90 min, TRADLINX 12x daily, JSONCargo on-demand API, GoComet near-real-time. Whether Evergreen reports customs clearance milestones (US CBP release, EU customs release) is not confirmed in public sources.
- 04
Identify the operating carrier
The booking confirmation and vessel schedule specify the operating carrier. An 'Evergreen booking' may physically sail on an Evergreen, CMA CGM, COSCO, or OOCL vessel depending on the Ocean Alliance service string rotation. Tracking feed source depends on the operating carrier.
Pain pointOn alliance-partner tonnage (CMA CGM, COSCO, or OOCL vessels), milestone events originate from the operating carrier's system before flowing into ShipmentLink. Data lag is possible. COSCO's DCSA T&T conformance is not confirmed in public sources; cross-polling SynCon Hub and COP portal may be required on COSCO-operated legs for completeness.
- 05
Evaluate ETA against Ocean Alliance reliability
Ocean Alliance schedule reliability: 67.6% (April 2026, Sea-Intelligence GLP #177, ALL arrivals), a modest improvement from 64.0% in January 2026 (GLP #174). March/April 2026 peer context: Gemini Cooperation 85.0%, MSC standalone 73.4%, Premier Alliance 54.2%. Build schedule buffers calibrated to the most recent alliance-level figure.
Pain point~68% reliability means 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. Customer-facing tracking should consolidate connected legs into a single shipment view.
- 07
Handle exceptions
Detect deviations: late gate-in, missed vessel loading (common failure modes tied to 'No VGM, No Gate-in' and 'No MRN, No Load'), transhipment dwell, weather delays, and Cape of Good Hope routing deltas on Asia-Europe / Asia-Mediterranean trades. At ~64% alliance reliability, exception management is a material share of the tracking workload.
Ocean Alliance network and operating-carrier tracking
Ocean Alliance members are Evergreen, CMA CGM, COSCO, and OOCL. The alliance was extended to 2032 via an MOU signed on 27 February 2024 in Shanghai. The Day 10 Product (live from April 2026) deploys approximately 390 vessels across 41 weekly loops covering 520+ direct port pairs.
Operating-carrier tracking patterns. Evergreen-operated sailings feed direct tracking through ShipmentLink, the DCSA T&T v2.2 API via the ShipmentLink Developer Portal, and EDI IFTSTA via INTTRA. CMA CGM-operated sailings produce milestone events in CMA CGM systems before they appear in ShipmentLink, with potential data lag on alliance-partner legs. COSCO-operated sailings carry an additional caveat: COSCO's DCSA T&T v2.2 conformance is not confirmed in public sources, so data lag and milestone granularity may differ; cross-polling SynCon Hub (synconhub.coscoshipping.com) and the COP portal may be necessary for completeness. OOCL-operated sailings sit on separate IT systems with their own SCAC (OOLU) and customer portal (MyOOCL); OOLU container prefixes are tracked under OOCL carrier context, not EGLV.
Transatlantic cooperation. Three loops / 18 ships with ONE tonnage under a separate VSA (not Ocean Alliance membership) was reduced in early 2026 to two loops with 14 vessels. Tracking on ONE-operated Transatlantic legs requires awareness of ONE's milestone conventions.
Intra-Asia CIX7 service (launched 20 April 2025) is joint with Wan Hai, RCL Feeder, and Bengal Tiger Line. Evergreen contributes 1 of 4 vessels. Non-Evergreen operating carriers on CIX7 sail outside Ocean Alliance visibility; tracking milestones source from each partner's system.
Reliability per Sea-Intelligence GLP #177 (April 2026, ALL arrivals): Ocean Alliance 67.6%, a modest improvement from 64.0% in January 2026 (GLP #174). Sea-Intelligence publishes alliance-level aggregates; no Evergreen-specific carrier-level reliability figure is published.
DCSA conformance. Maersk, CMA CGM, Hapag-Lloyd, MSC, ONE, and Evergreen all have DCSA T&T v2.2 live on their published developer portals. COSCO's conformance is NOT confirmed in public sources. Evergreen's Developer Portal lists v2.2 as live alongside OVS 3.0, Booking 2.0 Beta, Shipping Instruction, Transport Document, BL 3.0 Beta, Commercial Schedules 1.0, and JIT Port Call 1.2 Beta 1.
Where Evergreen tracking errors happen
Common tracking failure patterns on Evergreen, drawn from observed operational patterns and the operating-carrier variability inherent in Ocean Alliance bookings.
Operating-carrier milestone lag on COSCO legs
CommonEvergreen booking on a COSCO vessel. COSCO's DCSA T&T conformance is not confirmed in public sources; milestones may lag or be incomplete compared to Evergreen-operated services. Remediation: poll COSCO's SynCon Hub and COP portal in parallel on COSCO-operated legs until COSCO's DCSA conformance is verified.
OOCL vessel container-prefix confusion
OccasionalEvergreen booking on OOCL tonnage with OOLU-prefix equipment. Tracking query defaults to EGLV carrier context, returns no results. Remediation: detect OOLU-prefix containers and route tracking queries to OOCL's systems.
IMT container-prefix routing gap
OccasionalIMT U-class (LTIU) or B-type (IMTU) container on a Mediterranean leg. Post-consolidation routing to EGLV carrier context is not confirmed in public sources at the per-shipment level. Remediation: carry IMT party identifiers from booking confirmation through into tracking queries; do not force EGLV identifiers on IMT-confirmed shipments without operator confirmation.
Alliance-partner milestone lag on CMA CGM/OOCL legs
CommonMilestone events delayed or incomplete compared to Evergreen-operated services. TMS shows stale data. Remediation: poll the operating carrier's tracking feed in parallel with Evergreen's to ensure milestone completeness.
Ocean Alliance reliability overestimate
CommonETA committed using Gemini (85.0% March/April 2026) or industry average. Actual Ocean Alliance reliability is 67.6% (March/April 2026 GLP #177). Wider delay variance. 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; generate synthetic transhipment events when the carrier feed is silent.
Customs clearance milestone assumption
OccasionalOps staff assumes Evergreen 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 Evergreen 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 API cost. Remediation: align polling to source cadence (TrackCargo 90 min, TRADLINX 12x daily, JSONCargo on-demand, GoComet near-real-time).
DCSA Beta endpoint over-reliance
OccasionalIntegration team builds business-critical flows against DCSA BL 3.0 Beta or Booking 2.0 Beta endpoints and encounters beta-stage instability. Remediation: treat the Beta endpoints as Beta until Evergreen announces GA; keep ShipmentLink web forms and INTTRA EDI as production fallbacks.
How Expedion agents handle Evergreen tracking
Expedion agents consolidate Evergreen tracking across primary, EDI, and third-party channels with operating-carrier-aware polling, Ocean Alliance reliability calibration, transhipment consolidation, and exception detection handled automatically.
Consume Evergreen tracking through ShipmentLink and the DCSA T&T v2.2 API via the ShipmentLink Developer 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 and with EDI IFTSTA via INTTRA for TMS-integrated forwarders.
Identify the operating carrier (Evergreen, CMA CGM, COSCO, or OOCL) per booking from the booking confirmation and vessel schedule. Poll the operating carrier's tracking feed in parallel with Evergreen's to reduce the data-lag window on alliance-partner legs. For COSCO-operated legs, cross-poll SynCon Hub and the COP portal because COSCO's DCSA conformance is not confirmed.
Calibrate ETA commitments to Ocean Alliance's 67.6% (March/April 2026 GLP #177) reliability baseline. 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 alone.
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 Evergreen 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 Evergreen container prefixes (EMCU, EGHU, EGSU, EITU, HMCU, UGMU) to EGLV carrier context for tracking queries. Detect OOLU-prefix containers and route to OOCL's systems. Carry IMT party identifiers (LTIU, IMTU prefixes) through from booking confirmation into tracking rather than defaulting to EGLV without confirmation.
Recognise when an Evergreen Asia-Europe or Asia-Mediterranean sailing is on Cape of Good Hope routing and adjust expected transit times accordingly. Do not assume CMA CGM's January 2026 partial Suez return applies to Evergreen.
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 min source) while maintaining real-time posture through JSONCargo on-demand for high-priority shipments.
Agent capability availability
*Capability availability: AIS cross-referencing, parallel alliance-partner tracking, and synthetic transhipment event generation are on the agent roadmap. Confirm with your Expedion contact which items are live in production today versus on the near-term build roadmap before relying on any specific item.*
Evergreen tracking channels and reliability
Reference data for ops teams managing Evergreen tracking. Refresh cadences and DCSA conformance figures are sourced from Evergreen's published Developer Portal and third-party integration documentation.
| Channel | Access | Coverage | Notes |
|---|---|---|---|
| ShipmentLink | shipmentlink.com + mobile app | Container tracking, BL tracking, booking-reference queries, document downloads. | Primary customer-facing platform. Native refresh cadence for container milestones not published. |
| DCSA Track & Trace v2.2 API | ShipmentLink API Developer Portal (shipmentlink.com/_ec/APIPORTAL_Home) | Standard DCSA T&T v2.2 endpoints (release date 26 October 2021). | Live on the Developer Portal (carrier self-attestation). |
| Additional DCSA APIs | ShipmentLink Developer Portal | OVS 3.0, Booking 2.0 Beta, Shipping Instruction, Transport Document, BL 3.0 Beta, Commercial Schedules 1.0, JIT Port Call 1.2 Beta 1. | Beta endpoints where labelled Beta; treat as such until Evergreen announces GA. |
| 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/evergreen-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% (Mar/Apr 2026) | N/A | Sea-Intelligence GLP #177, ALL arrivals. Up modestly from 64.0% in January 2026 (GLP #174). Comparators March/April 2026: Gemini 85.0%, MSC 73.4%, Premier Alliance 54.2%. |
Schedule reliability comparison
Per Sea-Intelligence Global Liner Performance #177 (April 2026, ALL arrivals):
- Gemini Cooperation (Maersk + Hapag-Lloyd): 85.0% - MSC standalone: 73.4% - Ocean Alliance (Evergreen + CMA CGM + COSCO + OOCL): 67.6% - Premier Alliance (ONE + HMM + Yang Ming): 54.2%
Ocean Alliance ranked third among the four groupings in that window: below Gemini and MSC standalone, above Premier Alliance.
Trajectory. Ocean Alliance reliability moved from 64.0% in January 2026 (GLP #174) to 67.6% by April 2026 (GLP #177), a modest improvement within a stable band. No Evergreen-specific carrier-level reliability figure is published by Sea-Intelligence; the alliance-level number is the working reference for forwarders. Operators should track Sea-Intelligence monthly releases for updated alliance data.
Sea-Intelligence typically publishes alliance-level aggregates. Individual carrier-level reliability for Evergreen separate from the Ocean Alliance aggregate is not consistently published.
Related pages
Evergreen 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 · COSCO tracking
Ocean Alliance context: CMA CGM · COSCO · OOCL — OOCL is a wholly-owned COSCO subsidiary with separate IT systems, SCAC (OOLU), and customer portal (MyOOCL).
Solutions: Tracking automation
Frequently asked questions
Does Evergreen implement the DCSA Track & Trace v2.2 API?
Yes. DCSA Track & Trace v2.2 is live on the ShipmentLink API Developer Portal (shipmentlink.com/_ec/APIPORTAL_Home), as carrier self-attested. The canonical DCSA T&T v2.2 release date is 26 October 2021. Evergreen's posture matches the other Tier 1 carriers where public conformance is confirmed (Maersk, CMA CGM, Hapag-Lloyd, MSC, ONE all live on v2.2). This contrasts with COSCO, whose DCSA T&T conformance is not confirmed in public sources.
How does Ocean Alliance operating-carrier affect tracking quality?
Ocean Alliance vessel sharing means an Evergreen booking may execute on an Evergreen, CMA CGM, COSCO, or OOCL vessel under the Day 10 Product (approximately 390 vessels across 41 weekly service loops covering 520+ direct port pairs). Tracking feed source depends on the operating carrier. Evergreen-operated sailings feed direct through ShipmentLink and the DCSA T&T v2.2 API. CMA CGM-operated sailings produce milestones in CMA CGM systems before flowing into ShipmentLink, with potential data lag. COSCO-operated sailings carry an additional caveat — COSCO's DCSA conformance is not confirmed in public sources, so cross-polling SynCon Hub and the COP portal may be required. OOCL-operated sailings sit on separate IT systems with their own SCAC (OOLU) and portal (MyOOCL). Expedion agents identify the operating carrier from the booking confirmation and poll the appropriate feed in parallel with Evergreen's.
What is Evergreen's schedule reliability?
Sea-Intelligence does not publish an Evergreen-specific carrier-level reliability figure; the working reference is the Ocean Alliance aggregate. Per GLP #177 (April 2026, ALL arrivals), Ocean Alliance reliability is 67.6%, a modest improvement from 64.0% in January 2026 (GLP #174). March/April 2026 peer context: Gemini Cooperation 85.0%, MSC standalone 73.4%, Premier Alliance 54.2%. Forwarders should calibrate ETA commitments against the Ocean Alliance baseline and build larger schedule buffers on Evergreen bookings.
What refresh cadence do third-party tracking integrations offer for Evergreen?
Cadences vary by provider: TrackCargo 90 minutes, TRADLINX 12x daily, JSONCargo on-demand (pay-per-query), GoComet near-real-time. ShipmentLink's own native container-milestone refresh cadence is not published in public sources. Expedion agents poll each channel at its native cadence rather than forcing a uniform interval, avoiding wasted API calls on lower-frequency sources while maintaining real-time posture through JSONCargo on-demand for high-priority shipments.
How should forwarders handle tracking on COSCO-operated or OOCL-operated legs of an Evergreen booking?
For COSCO-operated legs, cross-poll COSCO's SynCon Hub (synconhub.coscoshipping.com) and the COP portal in parallel with ShipmentLink — COSCO's DCSA T&T conformance is not confirmed in public sources, so milestone granularity may differ from Evergreen-operated services. For OOCL-operated legs, route OOLU-prefix container queries to OOCL's tracking system (separate IT and SCAC OOLU under MyOOCL); querying under EGLV will return no results. Expedion agents detect the operating carrier from the booking confirmation and route tracking queries accordingly without requiring manual reviewer intervention per shipment.
Does Evergreen report customs clearance milestones?
Not confirmed in public sources. Evergreen's standard milestone events cover physical container movements (gate-in origin, loaded on vessel, vessel departed, vessel arrived at transhipment if applicable, vessel arrived destination, discharged from vessel, gate-out destination). Whether Evergreen reports US CBP release or EU customs release as separate milestones via ShipmentLink or the DCSA T&T API is not confirmed in public sources. Pending operator confirmation, forwarders should source customs clearance milestones from the customs broker system rather than from Evergreen's tracking feed.
Which other DCSA APIs does Evergreen expose on its Developer Portal?
The ShipmentLink API Developer Portal (shipmentlink.com/_ec/APIPORTAL_Home) lists DCSA OVS 3.0, Booking 2.0 Beta, Shipping Instruction, Transport Document, BL 3.0 Beta, Commercial Schedules 1.0, and JIT Port Call 1.2 Beta 1, alongside Track & Trace v2.2 (live). Endpoints labelled Beta should be treated as Beta until Evergreen announces GA — keep ShipmentLink web forms and INTTRA EDI as production fallbacks for business-critical flows.