Maersk's U.S. Logistics Expansion: Test Whether One Provider Really Creates One Operating Record
Maersk's U.S. expansion makes a compelling promise: buy more of the journey from one provider and remove friction between ocean transport, inland moves, warehousing, fulfillment, air freight, and final delivery.
That promise deserves a rigorous test. A broad service portfolio can simplify procurement while leaving operations fragmented behind separate portals, identifiers, exception queues, and invoices. The question for a shipper is not merely whether one company can sell every leg. It is whether every leg creates one coherent operating record that people and systems can actually use.
The network grew through distinct capabilities
Supply Chain Dive's account of Maersk's U.S. buildout traces the strategy beyond ports into omnichannel fulfillment and e-commerce. Performance Team, acquired in 2020, strengthened warehousing and distribution. Visible Supply Chain Management added e-commerce fulfillment in 2021. Pilot Freight Services, acquired in 2022, expanded bulky B2B and B2C delivery. Ground freight and air services filled out more of the journey.
The scale is material. When the Visible deal was announced, its nine warehouses were positioned to reach 75% of the U.S. within 24 hours and 95% within 48 hours. Performance Team operated 24 sites covering 800,000 square meters when acquired, and the $1.7 billion Pilot transaction was expected to bring the U.S. network to roughly 150 facilities.
Those figures demonstrate reach. They do not, by themselves, demonstrate integration. Acquired operations often arrive with different systems, status vocabularies, shipment identifiers, billing practices, and escalation paths. A logo can change faster than an operating model.
Commercial bundling is not operational integration
A bundled proposal may offer one account team, one master agreement, or one rate package. Genuine integration reaches much deeper.
Start with the booking. Can an ocean booking, drayage move, warehouse receipt, parcel order, and air shipment be connected by a persistent customer reference? Then examine milestones. Does an ocean discharge event automatically create the expected inland and inventory consequences, or must staff reconcile files and portals?
Inventory is an equally revealing test. A container marked delivered is not the same as product available to promise. The record should show when freight reaches the facility, is unloaded, passes any inspection, is received into inventory, and becomes allocatable. If those events sit in separate systems without common timestamps and identifiers, the shipper still owns the integration work.
Finally, inspect exceptions. An integrated provider should transfer context when responsibility moves between services. A customs delay should not become a generic missed drayage appointment, and a late inbound trailer should not arrive at the warehouse as a surprise. The exception record needs its original cause, current owner, affected orders, revised plan, and next promised update.
Run a portability and handoff test before consolidating
Before awarding multiple modes, ask the provider to demonstrate a representative shipment from booking through invoice. Use real-looking complexity: a purchase order split across containers, one customs hold, a missed appointment, partial warehouse receipt, and expedited delivery for a priority order.
Score the demonstration against five requirements:
- Persistent identity. Every service must preserve the shipper's purchase order, SKU, customer order, and shipment references—not only the provider's internal job numbers.
- Event continuity. Milestones should appear in sequence with definitions, source systems, timestamps, and confidence levels. The next team should receive the event without rekeying it.
- Exception inheritance. Ownership, root cause, notes, documents, and revised commitments must follow the freight across organizational boundaries.
- Machine-readable access. The shipper should be able to export history through documented APIs or standard files at a useful frequency. A unified dashboard without portable data is visibility on lease.
- Invoice lineage. Each accessorial and service charge should trace back to the shipment, event, location, rate rule, and approval that produced it.
Also test exit conditions. Ask how quickly the provider can return complete operational history, in what format, and at what cost. Data portability matters even when the relationship is healthy because shippers need independent analytics, audit evidence, and continuity during system changes.
Put cross-service KPIs into the agreement
Traditional service-level agreements can hide weak handoffs by measuring each leg separately. Add metrics that expose what happens between legs.
Cross-service dwell measures elapsed time from one service's completion event to the next service's accepted event. Useful cuts include discharge-to-drayage pickup, gate-in-to-warehouse receipt, and pick completion-to-carrier acceptance. Publish medians and the 90th percentile; averages conceal the shipments causing customer pain.
Exception transfer time runs from detection to acknowledged ownership by the team that can act. Pair it with the percentage of transferred exceptions containing a cause code, affected order references, supporting documents, and a next-action deadline.
Invoice continuity tracks the share of charges that reconcile automatically to the contracted rate and operational event. Monitor first-pass match rate, disputed dollars, time to resolve, and duplicate-charge incidence across services.
End-to-end accountability should measure complete order journeys, not isolated transport legs. Track promised-versus-actual delivery, perfect-order rate, milestone completeness, and time to restore the plan after disruption. Assign one accountable owner for exceptions spanning two or more services.
Inbound Logistics notes that multimodal freight can pass through several handoffs and transit points. That is precisely why consolidation needs stronger evidence, not fewer controls. Fewer vendors may reduce contractual seams, but only shared data and explicit ownership remove operational seams.
Buy the record, not only the network
Maersk's expanded footprint can offer real value: broader physical coverage, fewer commercial relationships, and more opportunities to coordinate capacity. Shippers should capture those benefits without assuming that corporate ownership automatically produces end-to-end control.
Make the provider prove that bookings, milestones, inventory, exceptions, and invoices form one durable record. Then preserve that record in the shipper's own transportation management environment, where performance can be compared across providers and time.
CXTMS connects multimodal execution, shipment events, exceptions, documents, and freight costs in one auditable workspace. Request a CXTMS demo to see how a shipper-controlled operating record turns an integrated logistics promise into measurable accountability.
