Hapag-Lloyd Feeds Live Container Positions Into SAP ERP, Cutting Supply Chain Blind Spots
Hapag-Lloyd has equipped 2 million shipping containers with IoT tracking devices. The devices transmit location data every 15 minutes on land and every six hours at sea. By mid-2024, the company had fitted trackers to 90% of its container fleet.
That data now moves beyond a customer-facing portal. SAP integrates the position data into SAP Business Network Global Track and Trace and embeds it in SAP S/4HANA. The result is automated delay alerts that surface inside the same back-end systems planners already use.
Why Milestone Tracking Was No Longer Enough
Before this change, ocean freight visibility was event-based. Carriers could confirm when a container left port or was loaded onto a ship, but gaps between milestones were opaque. If a container failed to arrive as planned, there was no way of knowing what had happened to it in transit.
Geopolitical disruption made that gap costly. Hostilities in the Strait of Hormuz are severely hindering shipping traffic today. During that pressure, 15,000 containers were held up in the Persian Gulf, and Hapag-Lloyd's phone lines could not handle the inquiry volume. The company gave all customers access to live positioning, including those who had not subscribed to it.
The episode clarified what continuous tracking enables that milestone tracking cannot: early warning while a shipment is still moving, not after it fails to arrive.
What the Integration Does Inside SAP
SAP Business Network Global Track and Trace offers transparent shipment information in real time along the entire supply chain. The data can be embedded natively in back-end systems such as SAP S/4HANA. It also connects to SAP Business Network for Logistics, which links shippers with carriers and logistics providers.
The practical effect: a production planner can see container position inside the same screen used to manage downstream scheduling. No portal switch, no manual lookup.
Looking ahead, SAP users will be able to ask their software what options are available when shipments are held up. If a ship misses a rail connection, the system will indicate whether onward truck transport is possible and how much longer the journey will take. Joule, SAP's AI assistant built into its cloud portfolio, is planned for this exception-handling workflow. These are forward-looking plans, not current released features.
What ERP and Operations Leaders Should Evaluate
The source is an SAP-published feature and reflects SAP and Hapag-Lloyd perspectives. Independent confirmation of integration depth or customer outcomes is not available from this source. The evidence does, however, point to three bounded questions worth addressing now.
First, connectivity. Is your SAP environment connected to SAP Business Network Global Track and Trace? If not, Hapag-Lloyd position data cannot reach your planners automatically.
Second, exception rules. Live data without defined thresholds creates noise. Decide which delay signals, vessel, port, or land-route deviations, should trigger a workflow versus a dashboard flag.
Third, governance. Warehouse planners, logistics managers, and production planners all benefit from tracking data, but each role needs different alert logic. Determine who owns rule maintenance before adding a continuous data feed.
Carriers, geopolitical disruption, and inventory cost are converging on the same problem. The question for your team is whether your ERP is set up to act on position data when it arrives.