Oracle OTM Driver Mobile App

What Oracle OTM’s mobile apps cover today

Oracle OTM’s mobile surface targets long-haul driver status, shipper-side visibility and office approvals. It does not target last-mile multi-stop execution.

• OTM's driver tracking surface. Lets a contracted carrier driver mark loads picked, in transit and delivered, with timestamps. Geared to long-haul status updates rather than multi-stop delivery with POD per stop.
• OTM's mobile companion. Office surface for shippers and planners: approvals, dashboards, record lookup.

None of those is the working surface a delivery driver opens at every stop. For own-fleet last-mile, the routing-plus-execution layer sits outside Oracle OTM.

What an on-road driver app actually needs to do

The driver workflow on the road is a different problem from warehouse scanning or ERP record access. The app has to be the driver’s whole working surface for the day.

• Turn-by-turn navigation. Native or integrated with Apple Maps, Google Maps and Waze. The driver shouldn’t need a second device.
• Route view with live re-sequencing. The day’s plan laid out by stop, with the next stop highlighted. If dispatch adds or cancels a stop, the app updates in place.
• Proof of delivery capture. Photos, e-signatures, configurable form fields per stop or task type.
• Conditional outcomes. Delivered, refused, partial, failed and the reason. Different outcomes trigger different follow-ups.
• Offline operation. Captures, photos, signatures all queue locally and sync when signal returns. A basement, a rural route or a dead zone can’t block the workflow.
• Barcode and asset scanning. Camera-based scanning for items, pallets, serial numbers, asset tags.
• Vehicle inspections. Start-of-shift pre-trip checklist; end-of-shift sign-off.
• Live GPS. Streams back to dispatch and to the customer-facing tracking page so ETAs stay accurate.

That’s the working surface for a delivery driver or field service technician. None of it is what OTM's driver tracking surface (a long-haul status app) was built to do.

Where Oracle OTM users land today without a driver app

Two patterns are common in Oracle OTM customers that haven’t yet added a dedicated driver app. Both create friction at scale.

• Paper route sheets plus phone camera and signature. Driver prints the route at the depot, drives stops, captures photos and signatures on a personal phone or a basic camera. Manual reconciliation at the end of the day; POD evidence sits in someone’s camera roll, not against the Oracle OTM record. Cycle-time on AR invoicing stretches because POD takes a day or two to arrive.
• Third-party driver app, manual sync. A generic delivery app captures POD, but data flow back into Oracle OTM is manual: a CSV export, a copy-paste, sometimes a scheduled OTM customization pull. The driver workflow works, the data flow doesn’t, and the AR team waits.

The path forward is a driver app that lives in the same data flow as the route plan: same source for the route, same destination for the captures.

How eLogii’s driver app works

Native iOS and Android, built specifically for delivery and field-service execution. The driver opens the app at the start of their shift and lives in it for the day.

• Daily route view. Today’s plan laid out by stop, with the next stop highlighted, ETA shown, and contact details for the customer.
• Turn-by-turn navigation. Native handoff to Apple Maps, Google Maps or Waze; or in-app navigation depending on configuration.
• Configurable POD per stop. Photos, e-signature, conditional outcomes, custom form fields. Configured at the route or task-type level so different stops capture the right evidence.
• Offline-first. Drivers can complete the whole day with no signal. Captures queue on the device and sync automatically when connectivity returns.
• Barcode scan. Camera-based scanning for items, pallets, asset serials.
• Custom forms. Temperature checks for cold-chain, gate access codes, hazmat handling forms, safety attestations, NPS micro-surveys, vehicle inspections.
• Live GPS. Streams back to dispatch and to the customer-facing tracking page so ETAs update live.
• Multi-language. Interface localized so drivers work in their own language.

How the integration sits with Oracle OTM

The driver app reads from eLogii and writes back to eLogii. eLogii reads orders from Oracle OTM and writes execution data back. The driver never sees Oracle OTM directly; the app is built for the road.

1. Route from Oracle OTM to driver. Open sales orders pulled from Oracle OTM via OTM REST API become routable tasks in eLogii. Optimization runs. The driver’s daily route lands in the app at the start of their shift.
2. Driver completes stops. Navigation, POD capture, photos, signatures, custom forms, conditional outcomes. All offline-capable.
3. Sync to eLogii. Captures land in eLogii in real time when signal is available, or on the next sync when it returns. Live GPS streams via webhook (Driver/Task Tracking Update) for dispatch and customer-facing visibility.
4. Write back to Oracle OTM. Completion status, POD references (photo IDs, signature image references), timestamps, driver-collected payments and custom form data write back to Oracle OTM via OTM REST API, typically against the linked shipment execution record. OTM closes the load; freight invoicing runs.

End to end: driver experience is built for the road, Oracle OTM stays the TMS and freight-execution system of record, OTM and the upstream ERP receive the POD reference the moment the driver completes the stop.

Frequently asked questions

Does Oracle OTM have a driver mobile app?

Not in the on-road delivery sense. Oracle OTM ships OTM's driver tracking surface for long-haul driver status updates, OTM's mobile companion for approvals, and a OTM's mobile companion for approvals (look up a customer, approve a transaction, see a dashboard). None of those is built for the driver workflow on the road: turn-by-turn navigation, offline-capable proof of delivery, photos, e-signatures, conditional outcomes for failed visits, custom forms per job type.

What does an on-road driver app actually need to do?

The driver gets a daily route, drives between stops, completes the work and captures the evidence. The app has to handle: turn-by-turn navigation to each stop; the route view with the day’s plan and live re-sequencing if a stop is added or canceled; proof of delivery capture (photos, signatures, configurable form fields); conditional outcomes (delivered, refused, partial, failed and the reason); offline operation so the driver isn’t blocked by patchy signal; barcode scanning for items or assets; vehicle inspection checks; live GPS streaming back to dispatch so ETAs can update; secure handoff of the captures back into the system of record.

How does the eLogii driver app integrate with Oracle OTM?

The driver app reads the day’s route from eLogii (which got the orders from Oracle OTM via OTM REST API in the first place). When the driver completes a stop, the app captures the POD evidence and writes it to eLogii. From eLogii, the completion data, photo and signature references, timestamps and any custom form data flow back to the upstream ERP via the integration. Vehicle assignment updates can flow to Oracle OTM via OTM REST API, typically against the linked shipment execution record so OTM can close the load and trigger freight invoicing. The driver never sees Oracle OTM directly; the app is built for the road, not for ERP record entry.

Is the eLogii driver app offline-capable?

Yes. Drivers can complete stops, capture POD, photos and signatures with no signal. Captures queue on the device and sync automatically when connectivity returns. Built for rural routes, basement deliveries and dead zones.

Can the driver app capture custom forms per job type?

Yes. Form fields are configurable per route, per stop or per task type: temperature checks for cold-chain, gate access codes, asset serials, hazmat handling forms, safety attestations, NPS micro-surveys. Custom field data flows through to Oracle OTM via OTM REST API against the matching record.