SAP Live Delivery Tracking

What SAP shows about a delivery today

SAP covers the ledger and freight-event view well at the back-office level. The gap shows up when delivery is on your own fleet and the end customer wants to see where the truck is right now.

• Outbound delivery status in S/4HANA. The standard SD outbound delivery moves through statuses (created, picked, packed, posted-goods-issue, POD set) driven by warehouse and SD postings. Visible in Fiori back-office apps and via OData.
• SAP TM freight events. Where TM is licensed, freight events fire at loading, dispatch, arrival at destination, intermediate stops on long-haul. Designed for B2B freight visibility and carrier orchestration.
• SAP customer portals. SAP Commerce Cloud, SAP Customer Activity Repository and various SAP-based self-service portals can surface order and shipment status to end customers. The live data they show comes from the underlying SAP records, which are warehouse-milestone or freight-event level.
• SAP S/4HANA Cloud notifications. Operations teams can configure event-driven notifications to customers via SAP Event Mesh and downstream messaging tools.

All of that is shipment-status visibility, driven by warehouse milestones, ledger postings, or carrier-event feeds. It is not live own-fleet driver GPS that an end customer can open and watch in real time.

What live delivery tracking actually means

For own-fleet operations, the customer-facing tracking experience that drives repeat orders and reduces support load looks like this:

• Live driver GPS on a map. The customer sees where the truck is right now and what stop number they are on the route.
• Real-time ETA. Recalculated as the driver moves and as the plan changes; not a static morning estimate that’s out of date by lunchtime.
• Driver name and contact. Customer knows who’s coming and can call if access changes.
• Branded. The page carries the operator’s branding (logo, colors, layout), not a generic delivery widget. Multi-brand support for operators running multiple consumer brands.
• Embedded content. NPS micro-survey at the end. Safety briefings before a hazmat delivery. Access codes for a gated community. Care instructions for a piece of equipment.
• Self-service rescheduling. If the customer can’t take the delivery, the page offers a route-aware reschedule that already fits the optimized plan.

This is a separate surface from the ledger and freight-event view S/4HANA ships natively. The two complement each other.

Where S/4HANA users land today

Three patterns are common before a live-tracking layer is added.

• Customer support absorbs the “where’s my order” calls. The customer phones in. The CSR opens S/4HANA, sees a shipment status from yesterday, calls the driver, calls back the customer. Cycle time per call: 4 to 8 minutes. Aggregate cost at scale: significant.
• Generic SMS templates. Driver sends a manual SMS at start of day with an estimated window. No live tracking, no map, no self-reschedule. Works until a customer asks a follow-up.
• Third-party tracking widget, no live driver feed. A basic tracking widget is bolted onto the customer portal, but it has no real connection to the live driver position or to the optimized plan. The ETA is a guess.

The fix is a tracking page driven by the same live GPS and route data the dispatcher is looking at, branded to match the operator, surfaced wherever the customer expects to find it.

How eLogii’s live tracking works

The driver app streams GPS as the driver moves. eLogii recalculates ETAs continuously as drivers progress and as the plan changes. The customer-facing tracking page shows the live state.

• Live driver GPS stream. From the driver app to eLogii in real time.
• Real-time ETA. Recalculated against the current plan and current driver position.
• Branded tracking pages. Configurable logo, colors and layout per brand. Multi-brand support for operators running several consumer brands from one fleet.
• Embedded content. NPS, safety briefings, access codes, care instructions, treatment notes – configured per task type or per customer segment.
• Self-service rescheduling. Customer can pick a route-aware slot if they can’t take the delivery. Around 70% of reschedule requests get handled without coordinator involvement.
• Notification triggers. SMS or email when the driver is N minutes out, when arrival is imminent, when the delivery is complete.

How live tracking fits with S/4HANA

The customer-facing tracking page is served by eLogii. S/4HANA remains the system of record. Four integration shapes are common, and the choice depends on where you want the customer to land and what you want SAP to record.

1. SMS / email link. Customer gets a link via SMS or email at key moments (booked, driver en route, N minutes out). Link opens the eLogii tracking page directly. Simplest integration; no SAP portal work required.
2. Embedded in your SAP customer portal. The eLogii tracking page embeds via iframe in your SAP-based customer self-service surface (SAP Commerce Cloud, SAP Customer Activity Repository, or a custom portal), so customers logging in to check an order see the live tracking inside their familiar portal.
3. Embedded in SAP Commerce Cloud storefront. Same iframe pattern but inside the SAP Commerce storefront on the order details page.
4. Webhooks into S/4HANA. If you want S/4HANA to record key milestones (driver dispatched, arrival imminent, delivered) on a custom Z-field on the outbound delivery, the eLogii Driver/Task Tracking Update webhook feeds the integration layer and an OData call writes the state to SAP.

The first three are display-side: where the customer sees the page. The fourth is data-side: where the live state lands in S/4HANA. They are independent; pick the combination that matches your workflow.

Frequently asked questions

Does SAP S/4HANA have live delivery tracking?

Core S/4HANA tracks outbound delivery status (created, picked, packed, posted-goods-issue). SAP TM, where licensed, adds freight shipment events (loading, dispatch, arrival at destination) for B2B freight workflows including third-party carrier tracking integration. Neither surfaces own-fleet live driver GPS to end customers, real-time route ETAs based on current vehicle position, or branded customer-facing tracking pages with embedded content like NPS, safety briefings or access codes. SAP’s tracking surface is shipment-status and freight-event-level; end-customer-facing live tracking is a separate problem.

Why doesn’t S/4HANA show live driver ETAs for own-fleet deliveries?

Because SAP was not built to be a last-mile telematics layer. Shipment status in S/4HANA comes from goods movement postings (warehouse) or freight events (TM). There is no real-time own-fleet driver-location feed driving an end-customer-facing surface, because the last-mile routing and execution layer that would generate that feed lives outside core S/4HANA.

How does eLogii’s live tracking work?

The eLogii driver app streams live GPS coordinates as the driver moves. eLogii recalculates route ETAs in real time as drivers progress and as the plan changes. Customer-facing tracking pages, branded per customer, show the live map, the next-stop ETA, the driver name and contact, and any embedded content the operator configured (NPS, access codes, safety briefings, treatment notes). Pages can be embedded in your customer portal or SAP-based self-service surface via iframe, or sent to end customers via SMS / email links.

How is live driver GPS streamed to S/4HANA?

Via webhooks. eLogii’s Driver/Task Tracking Update webhook fires with live driver coordinates and updated ETAs; the integration layer can route those events to S/4HANA (typically as a custom record write via OData, or a SAP Event Mesh inbound event), to your own dispatch screens, or directly to a customer-facing endpoint. No polling, no cron jobs, no manual sync.

Can the tracking page be branded per customer?

Yes. Multi-brand tracking is supported. Run three brands from one dispatch desk, each with its own logo, colors, layout and embedded content. Useful for operators running multiple consumer brands off a single S/4HANA tenant and a single own fleet.