Oracle OTM Live Delivery Tracking

What Oracle OTM shows about a delivery today

Oracle OTM covers the order and shipment-status view well, including the parcel-carrier handoff. The gap shows up when delivery is on your own fleet and the end customer wants to see where the truck is right now.

• Oracle's shipper view in OTM. Oracle OTM’s standard customer portal. End customers log in to see open orders, shipment status (created, picked, packed, shipped, delivered), invoice history, and support cases.
• OTM carrier execution carrier tracking. Once a shipment is handed to a parcel carrier and a label is generated, the tracking number flows into Oracle OTM and the customer can click through to UPS, FedEx, DHL or USPS to see the parcel’s status.
• Storefront order tracking. Storefront shows the order’s shipment status and any carrier tracking number.
• Shipment status update via OTM customization. Operations teams can fire OTM event rules when a fulfillment record updates, including sending an email or SMS to the customer.

All of that is shipment-status visibility, driven by warehouse milestones or parcel-carrier feeds. It is not live own-fleet driver GPS.

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 warehouse-driven shipment-status view Oracle OTM ships natively. The two complement each other.

Where Oracle OTM 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 Oracle OTM, 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 eLogii. A basic tracking widget is bolted onto the storefront, 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 Oracle OTM

The customer-facing tracking page is served by eLogii. Oracle OTM remains the system of record. Three integration shapes are common, and the choice depends on where you want the customer to land.

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 Oracle's shipper view in OTM work required.
2. Embedded in Oracle's shipper view in OTM. The eLogii tracking page embeds via iframe in the standard Oracle OTM Oracle's shipper view in OTM, so customers logging in to check an order see the live tracking inside their familiar portal.
3. Embedded in your storefront. Same iframe pattern but inside the your e-commerce storefront on the order details page.
4. Webhooks into Oracle OTM. If you want Oracle OTM to record key milestones (driver dispatched, arrival imminent, delivered) on a custom record or on shipment execution record, the eLogii Driver/Task Tracking Update webhook feeds the integration layer and a OTM event rule writes the state to Oracle OTM.

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

Frequently asked questions

Does Oracle OTM have live delivery tracking?

Oracle OTM Oracle's shipper view in OTM shows order and shipment status (created, picked, packed, shipped) and surfaces parcel-carrier tracking from the OTM carrier execution integration (UPS, FedEx, DHL, USPS). That works for parcel handoff. It does not surface live driver GPS for own-fleet deliveries, real-time route ETAs based on the current route plan, or branded customer-facing tracking pages with embedded content like NPS, safety briefings or access codes.

Why doesn’t Oracle OTM show live ETAs for own-fleet deliveries?

Because Oracle OTM was not built to be a routing or telematics layer. The shipment status in Oracle OTM comes from the carrier (for parcel) or from a manual shipment confirmation (for own fleet). There is no real-time driver-location feed feeding the customer-facing surface, because the routing layer that would generate that feed lives outside core Oracle OTM.

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 Oracle OTM Oracle's shipper view in OTM or your storefront via iframe, or sent to end customers via SMS / email links.

How is live driver GPS streamed to Oracle OTM?

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 Oracle OTM (typically as a custom record write or a OTM event rule), 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 OTM environment and a single own fleet.