Maersk freight operations, handled by AI agents.

The state of Maersk operations in 2026

Maersk is the world's second-largest container carrier and part of the Gemini Cooperation with Hapag-Lloyd, effective February 2025. The alliance restructuring replaced the former 2M partnership with MSC, reorganizing vessel sharing, port rotations, and schedule structures across major trade lanes.

For freight forwarder ops desks, Maersk's February 2025 transition introduced real operational friction. Hub-and-spoke routing through hubs like Tanjung Pelepas and Tangier increased the number of transshipment legs per shipment, making tracking more complex and ETA predictions less reliable.

Maersk operates under three SCAC codes: MAEU (Maersk Line), MSKU (Safmarine, integrated), and SEAU (Sealand, now a Maersk brand). Container prefixes across all three codes are accepted on the Maersk.com portal, but BL numbers and booking references follow different formatting conventions depending on the origin entity.

What experienced ops teams watch for on Maersk

Maersk.com is one of the most mature carrier portals in the industry, and the DCSA v2.2 track-and-trace feed runs live. That maturity cuts both ways at the SI desk. The portal is stable and well-documented, but its validation layer is correspondingly strict: HS code formatting, party-detail consistency across shipper, consignee, and notify blocks, and VGM reconciliation against the booked weight all get checked upfront. Submissions that would clear a younger carrier portal and get corrected downstream tend to bounce on Maersk at first pass. The trade is fewer surprises later in exchange for more upfront care, which only pays off when the upfront care is consistent.

The three-SCAC legacy (MAEU, MSKU, SEAU) has always meant that a Safmarine-originated or Sealand-originated booking carries a different reference format into SI submission. Pre-Gemini, that was a one-point mapping problem. Under Gemini's hub-and-spoke routing, the same booking now moves through more operational touchpoints — SI submission, draft BL review, amendment routing if anything changes at the hub — and each hop is another place the legacy reference has to survive intact. A mis-mapped MSKU booking that would have caused one correction on a direct service can cascade into two or three on a Tanjung Pelepas-routed shipment.

The less visible consequence of Gemini is that the effective amendment window has compressed structurally, not just administratively. On direct services, the "last safe edit" moment for a draft BL was anchored to the mother vessel's cut-off at the load port. On feeder-then-trunk strings, every additional hub between the load port and destination is a point at which an in-flight amendment has to chase a container already in motion across carrier operational boundaries. Carrier turnaround on the amendment request itself may be unchanged, but the internal deadline an ops desk should actually be working to has moved earlier. Teams still anchoring SI lock-downs to pre-Gemini cut-off assumptions are the ones getting caught.

What Expedion handles for Maersk

Five operational workflows are fully supported on Maersk shipments today. Each one is documented in detail on its own page.

TMS compatibility

Expedion agents operate Maersk workflows on top of your existing TMS. We connect via API where available and authenticated browser sessions where not. Your system of record stays intact.

Frequently asked questions