The manual MSC tracking workflow
Tracking an MSC shipment manually runs through four channels with different authentication models and event-delivery mechanics. The ops-desk workflow below reflects the typical integrated forwarder's path from channel selection through customer-facing status narrative.
- 01
Identify the correct tracking channel
Four options: myMSC portal (manual, adequate for one-off queries), MSC Track & Trace API (via the MSC Developer Portal at developerportal.msc.com, designed to DCSA standards), MSC EDI (IFTSTA milestones, COPARN bookings, APERAK acknowledgements, via INTTRA, GT Nexus, or CargoSmart), and RSS/web services (legacy, being migrated to API).
Pain pointUnlike carriers with self-serve developer portals, MSC's Track & Trace API onboarding requires submission of the Direct Integration Request Form and may carry fees. Sandbox and test data is in development per MSC's own page.
- 02
Query the chosen channel by BL, booking, or container number
All three identifier types work on myMSC. API queries are authenticated via credentials issued through Direct Integration onboarding.
Pain pointFor shipments booked on Premier Alliance slot-exchange services, the MSC tracking feed may have different coverage than the operating carrier's (ONE, HMM, Yang Ming). Operators should check both feeds where the partner API is available. See the MSC booking page for the booking-side context on slot-exchange services.
- 03
Parse the returned 10 DCSA-standard milestones
Gate-in (origin), load, vessel departure, transshipment hub arrival, discharge at hub, load onto onward vessel, departure from hub, vessel arrival (destination), discharge, and gate-out. Each event has an ACT (actual), EST (estimated), or PLN (planned) qualifier.
Pain pointTransshipment count on MSC is typically lower than on hub-and-spoke alliance services because MSC's standalone network has more direct calls. A Shanghai-Rotterdam shipment on MSC may have fewer events than the same route on a Gemini service, which changes what normal looks like for ops-desk exception detection.
- 04
Compare ACT against PLN to detect delays
Standard DCSA pattern. Current DCSA T&T standard is version 2.2, released October 2021, which added subscription callbacks, enhanced security, and document events. v3.0 beta exists but MSC's specific v3.0 conformance status is not publicly confirmed.
Pain pointMSC does not publish refresh cadence targets. Third-party visibility providers typically poll 4-12 times per day. For forwarders whose TMS supports webhooks, the DCSA 2.2 subscription callback pattern is better than polling, but MSC-specific subscription callback availability should be confirmed at onboarding.
- 05
Calibrate delay thresholds to MSC's reliability tier
Sea-Intelligence GLP 2025 data shows MSC standalone at 70-80% across the year, peaking near 80% in August and September 2025. Gemini ran at 88-92%; Premier Alliance at 52-58%.
Pain pointForwarders applying a 48-hour normal delay threshold from Gemini experience to MSC over-alert on weak lanes (too many exceptions) and under-alert on strong lanes (missed real exceptions). MSC needs its own threshold tuning. See the MSC booking page for the booking-side ETA-calibration context; this step is about tracking-side threshold tuning.
- 06
Translate raw milestones into customer-facing status updates
Absorb multi-leg transshipment events into plain-language status narratives. For TIL-owned hub terminals (Gioia Tauro, Le Havre, Sines, Lome, and Asian terminals), tracking event generation tends to be more consistent than at independently-operated hubs.
Pain pointCustomer inquiries about transshipment hub events are less common on MSC direct services (fewer hub events to explain) but more complex on Premier Alliance slot-exchange shipments where the customer sees MSC branding but the vessel is operated by a different carrier.
- 07
Handle where is my shipment inquiries
Parse customer emails, match to shipment via container, BL, or booking number, respond with current status, last milestone, predicted ETA, and any delays.
Pain pointInbound volume on MSC scales with customer count the same way it does on other carriers, but MSC-specific status narrative generation is thinner because the underlying data SLAs are thinner.
Network structure and tracking coverage
MSC's independent East-West network launched on 1 February 2025, following the dissolution of the 2M alliance with Maersk. The standalone network offers 1,900+ direct port pairs via the Suez Canal and 1,800+ via the Cape of Good Hope. For tracking, the structural difference is fewer transshipment events per shipment on direct services: a Shanghai-Rotterdam shipment on MSC may reach destination with fewer hub events than the same route on a hub-and-spoke alliance service like Gemini. This changes what normal tracking looks like for ops-desk exception detection — fewer milestones does not mean data is missing; it means the ship sailed direct.
Where MSC does transship, it tends to route through its own TIL-operated terminals (Terminal Investment Limited owns facilities at Gioia Tauro, Le Havre, Antwerp, Sines, Lome, and several Asian ports). Event generation from TIL-owned terminals is typically more consistent than at independently-operated hubs, enabling tighter status updates on transshipment legs.
Schedule reliability data from Sea-Intelligence GLP 2025 shows MSC's standalone network averaging 70-80% across 2025, peaking near 80% in August and September 2025. For comparison, Gemini consistently ran at 88-92%, Premier Alliance ran at 52-58%, and Ocean Alliance ran at 60-69%. MSC sits 12-18 percentage points behind Gemini but materially above both Premier and Ocean. The implication for tracking: exception-detection thresholds must be calibrated to MSC's mid-70s baseline, not to higher-reliability carriers.
For 9 Asia-Europe services, MSC bookings sail on Premier Alliance partner tonnage (ONE, HMM, Yang Ming) via slot exchange. On these specific services, the operating carrier's schedule performance applies, not MSC's standalone performance, and MSC's native tracking feed may have different coverage than the operating carrier's feed. Exception-detection logic should reconcile both feeds where available. MSC also has a vessel service agreement with ZIM covering Asia/US East Coast and Asia/US Gulf routes, effective 1 February 2025. Suez vs Cape routing optionality at booking time changes what on schedule means for a given shipment — transit time baselines and threshold tuning must account for which routing was selected. Booking-side routing selection is covered on the MSC booking page; this page covers the tracking-side implications.
Where MSC tracking errors happen
Applying higher-reliability carrier baselines to MSC shipments
CommonForwarders extrapolating 88%+ Gemini reliability to MSC over-alert on weak lanes and miss real exceptions on strong lanes. MSC's 70-80% baseline per Sea-Intelligence GLP 2025 requires its own threshold tuning, not a borrowed benchmark from a structurally different alliance-based service.
Missing operating carrier on Premier Alliance slot-exchange shipments
FrequentFor 9 Asia-Europe services, MSC bookings sail on ONE, HMM, or Yang Ming tonnage. Whether MSC's tracking feed cleanly covers the partner leg is not publicly documented. Operators relying on MSC's feed alone may see data gaps at slot-exchange handover points where the physical vessel operator changes but MSC's tracking system treats it as a single booking.
MSC API onboarding barrier for mid-market forwarders
OccasionalUnlike carriers with self-serve developer portals, MSC requires the Direct Integration Request Form and may charge fees. Mid-market forwarders often defer MSC API integration and fall back to browser-based myMSC tracking, which does not scale to portfolio-wide visibility and leaves MSC shipments with lower automation coverage than other carriers in the same forwarder's portfolio.
Transshipment hub events on direct services surprising customers
OccasionalMSC's standalone network has more direct services than hub-and-spoke alliance models. On the lanes where MSC does transship (via TIL-owned terminals at Gioia Tauro, Le Havre, Sines, Lome, and several Asian ports), the customer sees unexpected hub events and questions the routing. Requires a customer-facing narrative trained on MSC's network shape to explain why the transshipment was scheduled and that TIL-operated hubs typically generate more consistent event data than independent hubs.
DCSA v3.0 conformance uncertainty
OccasionalMSC is a founding DCSA member and adopted the Commercial Schedules API in June 2025, but MSC-specific v3.0 Track & Trace conformance status is not on DCSA's public dashboard. Forwarders planning v3.0-specific integrations (enhanced subscription callbacks, richer document events, stricter schema validation) cannot confirm MSC's readiness and may delay MSC integration projects pending clarity.
Costa Rica document-side tracking required in addition to physical milestones
OccasionalFor MSC cargo to Costa Rica and similar destinations where Original BL is mandatory (per MSC's Bill of Lading management rules), agents must track Original BL courier status alongside physical container milestones. Missing one side creates delivery delays despite on-schedule physical tracking. See the MSC bill of lading page for the BL-side Costa Rica Original BL rule.
How Expedion agents handle MSC tracking
Expedion agents consume MSC tracking data from the right channel per shipment lifecycle, calibrate exception detection to MSC's standalone-network reliability tier, and reconcile data across Premier Alliance slot-exchange partners where applicable. Every capability below addresses an MSC-specific operational difference from higher-reliability alliance-based carriers.
Pull milestone data via MSC's Track & Trace API (or direct EDI where that is the forwarder's integration mode) for active shipments. Polling cadence tightened near cut-off and port arrival, loosened in mid-transit. Where MSC's DCSA 2.2 subscription callback path is available at the forwarder's TMS, agents subscribe to push events rather than polling.
Compare actual-vs-planned timestamps against MSC's standalone-network reliability baseline (mid-70s per Sea-Intelligence GLP 2025), not a generic carrier average or higher-reliability benchmarks. A 24-hour variance on an MSC mainliner is less alarming than the same variance on a higher-reliability service, and agents' alert logic reflects that difference.
For Asia-Europe bookings where MSC slot-exchanges with Premier Alliance, reconcile tracking data from both MSC and the partner carrier where both feeds are available. Avoid the gap that can form when a booking sails on ONE, HMM, or Yang Ming tonnage and MSC's native tracking feed is thinner than the operating carrier's.
Translate raw DCSA milestones into customer-facing updates in the forwarder's communication style. Absorb multi-leg transshipment events into clear status narratives. For TIL-operated hubs, leverage the more consistent event generation to give tighter status updates than independent-hub shipments allow.
For MSC shipments to destinations where Original BLs are mandatory (Costa Rica and similar), agents track Original BL courier status, receipt confirmation at destination agent, and any local clearance milestones alongside physical container milestones. Cargo cannot be released on the vessel arrival event alone, and the customer-facing status must reflect both sides of the release gate. See the MSC bill of lading page for the BL-side Original BL workflow.
MSC tracking details
Key reference data for ops teams tracking MSC shipments across the Track & Trace API, EDI channels, and myMSC portal.
| Detail | Value |
|---|---|
| Primary tracking API | MSC Track & Trace (via Developer Portal at developerportal.msc.com) |
| API onboarding | Direct Integration Request Form required (fees may apply) |
| EDI messaging set | IFTSTA (milestones), COPARN (bookings), APERAK (acknowledgements) |
| EDI channels | Direct, INTTRA, InforNexus (GT Nexus), CargoSmart |
| Manual tracking | myMSC portal by BL, booking, or container number |
| DCSA T&T standard version | v2.2 (released October 2021; v3.0 beta exists; MSC v3.0 conformance status not publicly confirmed) |
| DCSA Commercial Schedules API | Adopted by MSC June 2025 |
| DCSA membership | Founding member; Global CDIO Andre Simha chairs DCSA Supervisory Board |
| Standard milestone count | 10 events for typical transshipment shipment |
| Milestone qualifiers | ACT (actual), EST (estimated), PLN (planned) |
| Refresh cadence | Not published; third-party providers poll 4-12 times/day |
| Network structure | Independent East-West since 1 February 2025 |
| Key hub terminals (TIL-operated) | Gioia Tauro, Le Havre, Antwerp, Sines, Lome, and several Asian ports |
| Schedule reliability (Sea-Intelligence GLP 2025) | MSC 70-80%; Gemini 88-92%; Premier 52-58%; Ocean 60-69% |
| Premier Alliance slot exchange | 9 Asia-Europe services (MSC bookings may sail on ONE/HMM/Yang Ming tonnage) |
| ZIM vessel service agreement | Asia/US East Coast and Asia/US Gulf (effective 1 February 2025) |
TMS compatibility for MSC tracking
Expedion agents consume MSC tracking from within your existing TMS. For CargoWise users, agents read shipment state via eAdaptor and consume milestones through either MSC's Track & Trace API or IFTSTA EDI via INTTRA, whichever the forwarder has set up. For GoFreight and Magaya, agents use the respective APIs for internal state and MSC's Track & Trace API for carrier-side milestones. Full TMS compatibility details are on the MSC overview page.
Related pages
MSC carrier pages: MSC overview · Shipping instructions · Bill of lading · Booking · Documentation
Tracking across carriers: Container tracking automation · Maersk tracking · CMA CGM tracking · Hapag-Lloyd tracking · ONE tracking · COSCO tracking · Evergreen tracking
Frequently asked questions
How does Expedion handle the MSC Track & Trace API's onboarding process?
MSC's Track & Trace API requires submission of a Direct Integration Request Form through the MSC Developer Portal, unlike carriers with self-serve developer portal sign-ups. Fees may apply and sandbox/test data is still in development. Expedion handles the integration setup on behalf of the forwarder, including the Direct Integration Request Form submission, credential management, and fallback to EDI (IFTSTA via INTTRA) or myMSC portal queries during the onboarding period. Once API access is live, agents switch to the Track & Trace API as the primary milestone source.
What does MSC's 70-80% reliability baseline mean for exception-detection thresholds?
Sea-Intelligence GLP 2025 data shows MSC's standalone network averaging 70-80% schedule reliability across 2025, compared to Gemini at 88-92%, Premier Alliance at 52-58%, and Ocean Alliance at 60-69%. Forwarders who apply Gemini-calibrated thresholds (where a 24-hour delay is unusual) to MSC will generate excessive false alerts on weak lanes and miss genuine exceptions on strong lanes. Expedion agents calibrate delay thresholds to MSC's mid-70s baseline so alerts reflect real operational variance, not carrier-tier mismatch. For the booking-side ETA-calibration context, see the MSC booking page.
How does Expedion track shipments on Premier Alliance partner tonnage?
For 9 Asia-Europe services, MSC bookings may sail on ONE, HMM, or Yang Ming vessels via Premier Alliance slot exchange. MSC's native tracking feed may have different coverage than the operating carrier's feed at slot-exchange handover points. Where both the MSC and partner carrier APIs are available, Expedion agents reconcile data from both feeds to close the gap that can form when the physical vessel operator's tracking data is richer than MSC's. The reconciliation runs automatically for active shipments on known slot-exchange services.
How does Expedion handle Costa Rica-bound MSC cargo where Original BLs are mandatory?
For MSC shipments to Costa Rica and similar restricted-release destinations, cargo cannot be released on the vessel arrival event alone because the consignee must present the Original BL. Expedion agents track both physical container milestones (via MSC's Track & Trace API) and document-side milestones (Original BL courier status, receipt confirmation at destination agent, local clearance steps). The customer-facing status reflects both sides of the release gate, so the forwarder and consignee see whether the document chain is keeping pace with the physical shipment.