STACK PATTERN
Oracle OTM is the transportation management system: carrier selection, freight rating, multi-modal planning, freight invoicing. eLogii is the routing and field execution layer that turns Oracle OTM-planned loads into optimized last-mile routes, live ETAs, driver workflows and proof of delivery, then writes the completion data back. Two systems, two jobs. The integration runs over OTM REST API on the Oracle OTM side and eLogii’s REST API on the other, typically delivered in 3 to 5 weeks alongside the eLogii rollout.
TRUSTED BY HUNDREDS OF HAPPY CUSTOMERS
Oracle OTM and eLogii sit in different layers of the same stack. Oracle OTM runs transportation execution: carrier selection, freight rating, multi-modal planning, freight invoicing, claims. eLogii is the routing and field execution layer: the route plan, the driver app, the live ETAs, the proof of delivery, the customer-facing tracking. Both products expose mature REST APIs, and the integration between them is a normal piece of OTM-side work.
In the combined pattern, Oracle OTM stays the system of record for multi-carrier freight execution. Loads handed off to own-fleet flow from OTM into eLogii as routable tasks; eLogii optimizes against vehicles, depots, time windows, capacities, skills and SLAs; the driver app captures POD, photos, signatures and any custom forms; completion writes back to Oracle OTM so OTM can close the load and trigger freight invoicing. The integration runs over both products’ REST APIs.
Three tables: where ERP and business data live (Oracle OTM leads), where routing and field execution live (eLogii leads), and what the integration architecture looks like on both sides.
| Oracle OTM | eLogii | |
|---|---|---|
| Carrier master and contracts | Core. Item record, BOMs, lots, serials, pricing | Not in scope. Looks up items by external_id from the integration |
| Freight rating and rate-shop | Core. Customer record, billing address, payment terms, AR/AP | Not in scope. Customer delivery info flows in via integration |
| Multi-modal loads and BOLs | Core. Order capture, fulfilment, invoicing, multi-subsidiary close | Not in scope |
| Carrier tendering and acceptance | Core. Inventory feeds come from upstream ERP, not OTM | Not in scope |
| Item weight, cube, handling for capacity math | Item record fields | Reads via integration to feed optimizer constraints |
| Customer delivery address, time windows | Customer + sales order record fields | Reads via integration to feed optimizer constraints |
| Multi-modal, multi-region freight invoicing | Core. multi-org and multi-region | Not in scope |
| eLogii | Oracle OTM native | |
|---|---|---|
| Multi-stop route optimization with constraints | Two engines, six configurable modes; vehicles, depots, capacities, time windows, skills, SLAs | pick/pack/ship at the warehouse sequences stops within a wave; not a constraint-aware route optimizer |
| Multi-day, long-haul, multi-depot routing | Plan a single day or an entire month in one run; multi-depot, multi-day, overnight stops | Not in scope |
| Driver mobile app for on-road execution | Native iOS and Android: navigation, POD, photos, signatures, conditional outcomes, custom forms | OTM's driver tracking surface and OTM's mobile companion cover warehouse and HR; no on-road driver workflow |
| Live GPS, route ETAs, branded customer tracking | Live driver GPS stream, route ETA updates, multi-brand tracking pages with embedded content | Not in scope. Oracle's shipper view in OTM shows shipment status, not live ETAs |
| Slot booking co-pilot – route-aware availability | Returns only delivery slots that fit the current optimized plan; ~35% fewer failed visits | Not in scope |
| Customer self-reschedule on route-aware slots | ~70% of reschedule requests handled without coordinator involvement | Not in scope |
| Configurable POD forms and conditional outcomes | Configurable POD with photos, signatures, conditional steps, custom fields, custom forms | Not in scope |
| Parcel carrier rate-shop and label-print | Not in scope. Own-fleet routing only | Shipping integration covers UPS, FedEx, DHL, USPS rate-shop and labels |
| Oracle OTM | eLogii | |
|---|---|---|
| API style | OTM REST APIs and SOAP services for server-side logic | REST, JSON over SSL, ApiKey auth, predictable resource URLs |
| Authentication | OAuth 2.0, OAuth 2.0 (Oracle Identity Cloud Service), or M2M | ApiKey header, generated in Dashboard > Configuration > API Keys |
| Sandbox environment | Oracle OTM test and stage environments accounts for development and testing | Full API parity at api-sandbox.elogii.com |
| Bulk operations | Async record queries, OTM background process for high-volume batches | createOrUpdateMany endpoints handle hundreds of tasks per call |
| Webhooks / events | OTM event rule scripts + OTM event publishing for outbound events | Seven event types including Driver/Task Tracking Update with live GPS stream |
| Optimization callable via API | No route optimization engine in core Oracle OTM | All six modes callable via REST; lock specific routes, manually reorder stops |
Sources: Oracle Transportation Management documentation, Oracle OTM REST API reference, eLogii API documentation. Verified June 2026.
End to end, how a delivery order moves from Oracle OTM to a completed POD and back into Oracle OTM for invoicing and inventory. The exact wiring depends on your tenant and the integration platform your team uses, but the shape is the same in every deployment.
POST /tasks/createOrUpdateMany, with the OTM shipment ID held as external_id so every eLogii object can be traced back to its Oracle OTM source record.Variations on the same pattern: multi-depot picking where OTM locations and lanes drive depot selection; multi-day jobs for field service where the eLogii task represents the visit and the Oracle OTM project represents the engagement; customer cancellations from Oracle OTM triggering eLogii re-optimization. None of these require special connector logic; they are normal mappings across two REST APIs.
Oracle OTM is a deep transportation management system and ships modules that touch the delivery problem, but none of them are route optimization. Drawing the line clearly matters when you are scoping eLogii alongside Oracle OTM:
This is not a criticism. Oracle OTM is a multi-carrier TMS and was never built to be a constraint-aware own-fleet last-mile routing engine. The point is to be precise about where its features stop, so the integration with eLogii has a clean seam.
We’d never go back to the way we were planning before. eLogii is the backbone as well as the brain of our planning operations, translating actively to our bottom line.
Jord Van Dijk, IT Director, J-Club · 9,000+ stores routed on eLogii
Three shapes cover almost every Oracle OTM + eLogii deployment. The right one depends on what your Oracle OTM team already has in place and which side of the seam you want the orchestration logic to live on.
api-sandbox.elogii.com and publicly documented endpoints.Two common shapes for customers running Oracle OTM alongside eLogii. Same underlying pattern, different surface.
Wholesale food and drink, building materials, bathroom and kitchen, pharma, grocery, parcel. Oracle OTM owns items, lots, batches, expiry, pricing, customer master, delivery addresses, sales orders, inventory and financial close. eLogii owns the route plan across the fleet, vehicle and capacity and time-window optimization, the driver mobile app for POD and pallet-level signing, the live customer tracking, and the slot booking on the storefront. Typical reach is own-fleet distribution operations with 50+ in the field, multi-depot picking and routing, and recurring weekly or monthly delivery patterns. Outcome shape from current customers: Brymec lifted productivity 30% and routing efficiency 20%; ATS Building Products improved deliveries per route by ~98%; Porcelanosa runs 95%+ ETA accuracy on daily distribution.
Less common pattern, because most field service operations run a dedicated FSM in front of Oracle OTM for work-order management. Where Oracle OTM is the financial backbone for field service, eLogii sits as the routing depth layer, often alongside an FSM in front (Simpro, Joblogic, ServiceTitan, Salesforce Field Service, MS Dynamics 365 Field Service). Oracle OTM handles service contracts, billable work, invoicing and parts inventory; the FSM (if present) handles work-order workflow; eLogii handles multi-day jobs, multi-technician crews, recurring service patterns and the driver mobile app. Bristow & Sutor runs 200+ enforcement agents and 200,000+ case visits routed annually on eLogii; Vergo runs 400 technicians.
eLogii runs alongside Oracle OTM; nothing changes on the Oracle OTM side. eLogii pricing starts from $3,000 per month as a platform fee, banded by field staff, drivers, jobs per day and the modules required. Each band includes a quota; cost steps up when the operation crosses a band, not when you add an individual seat. Customers typically report 3 to 4× return on investment within 6 months, and combined Oracle OTM + eLogii rollouts (including the integration) complete in 3 to 5 weeks. Oracle OTM pricing is its own thing and is not affected by adding eLogii.
30-minute custom simulation with your real delivery orders, depots and vehicles. Projected savings in drive time, fuel and planner hours from adding eLogii on top.
We have been extremely impressed with the results from eLogii so far. The solution is powerful and the team have found it extremely intuitive and easy to get going with. We signed a multi-year agreement with eLogii and are looking forward to deepening our relationship with them over the next years.
Anthony O’Keeffe, CEO, Bristow & Sutor · 200+ enforcement agents, 200,000+ case visits routed annually
Three steps for teams whose delivery or field execution problem has outgrown what Oracle OTM’s built-in workflow covers, and who want to keep Oracle OTM for items, customers, orders, inventory and financial close while adding eLogii for routing and execution on top.
Item master, customer addresses, sales orders, depots (OTM locations and lanes) and vehicles inventoried. OTM REST API queries return the open delivery book; mapping to eLogii task fields documented end to end. Custom Oracle OTM fields surfaced as eLogii custom fields. Sandbox connectivity proved out on both sides before any production data moves.
Weeks 1–2Custom data simulation against your historical Oracle OTM delivery book so you can validate the modeling and project savings before go-live. Side by side: what your planners produce today vs. what eLogii produces with the same orders. Approve the optimizer settings and the write-back fields.
Weeks 2–3Start with one business unit, depot or region. Drivers onboarded onto the eLogii app. Webhook stream wired to your integration layer. POD and completion data writing back to Oracle OTM for AR and inventory. Expand to the rest of the operation once the first cohort is steady. Most teams complete the transition in 3 to 5 weeks total.
Weeks 3–5Unimasters runs eLogii across a multi-country operation and achieved 50% less planning time and 49% fewer service calls. Multi-country rollouts deploy in weeks, not quarters.
Each of these takes one place where eLogii adds depth alongside Oracle OTM, walks what Oracle OTM handles today, what the capability actually needs, where users land without it, how eLogii covers it, and how it writes back to Oracle OTM via OTM REST API.
Oracle OTM has no native constraint-aware route optimizer. eLogii is the routing layer on top: two engines, six modes, REST-callable, plugs into OTM API surface.
OTM's driver tracking surface is warehouse-side. eLogii ships a native iOS / Android driver app with offline POD, photos, signatures, conditional steps and custom forms.
shipment execution record can hold notes and attachments. eLogii captures POD on the driver app: photos, e-signatures, conditional outcomes, custom forms, with REST write-back to Oracle OTM.
Oracle's shipper view in OTM shows shipment status. eLogii streams live driver GPS, real-time route ETAs and branded multi-brand customer tracking pages on top.
Through both products’ REST APIs. Oracle OTM exposes OTM REST API plus OTM customization, OTM REST endpoints and a OTM event publishing for outbound events; eLogii’s REST API has 70+ endpoints, ApiKey auth, a full-parity sandbox at api-sandbox.elogii.com and seven webhook event types including Driver/Task Tracking Update with live GPS. Typical pattern: open delivery orders flow from Oracle OTM to eLogii (pulled on a schedule or pushed via a OTM event rule on order approval); eLogii runs the optimization and dispatches the driver app; completion data writes back to Oracle OTM for OTM load closure and freight invoicing. Most deployments are delivered in 3 to 5 weeks alongside the eLogii rollout.
No. Warehouse pick/pack/ship sits upstream at the WMS. OTM tenders freight and runs invoicing. eLogii owns the constraint-aware own-fleet last-mile route plan once the load is allocated to your own fleet.
No. OTM’s carrier execution is rate-shop and label-print for parcel carriers (UPS, FedEx, DHL, USPS). It is for parcel handoff. eLogii is for own-fleet routing: your trucks, your drivers, your stops. If your delivery is all parcel through carriers, eLogii is not the right tool. If you run an own fleet for distribution or field service, eLogii is the layer Oracle OTM was never built to be.
Typically: open sales orders or delivery orders, the customer’s delivery address and geo, line items with weight and cube from the item record, any delivery time window, special-handling flags, the assigned depot or Oracle OTM Location, and any custom fields your operation depends on (access notes, gate codes, key handling). All of that is exposed via OTM REST API today. The integration job either pulls on a schedule or pushes via a OTM event rule on order approval.
Typically: delivery confirmation (delivered, refused, partial, failed and the reason), proof-of-delivery references (photo IDs, signature image references), timestamps (arrival, completion), driver-collected cash or payments where applicable, any custom form data captured in the driver app, and the final delivery status that triggers OTM load closure and freight invoicing. The write-back uses OTM REST API or OTM REST endpoint endpoints from your integration layer.
Yes. eLogii has REST + JSON APIs, a sandbox at api-sandbox.elogii.com and publicly documented endpoints. Whichever iPaaS your team already uses can broker eLogii alongside Oracle OTM.
Typically 3 to 5 weeks from kickoff to a phased go-live, including the Oracle OTM integration. Most teams start with one business unit, depot or region, validate against historical Oracle OTM delivery data, then expand. Heatleys evaluated 20 platforms and went live fast on eLogii, citing how quickly drivers could be onboarded.
It does not. Oracle OTM pricing stays as-is, eLogii is added on top. eLogii pricing is a platform fee, banded by field staff, drivers, jobs per day and modules, from $3,000 per month. Customers typically report 3 to 4× return on investment within 6 months on eLogii.
Yes. eLogii runs operations at scale: J-Club (9,000+ stores), NHS, Belfast City Council, Vergo, Bristow & Sutor, Porcelanosa, Caldic and Berkmann Wine Cellars. ISO 27001 and SOC 2 Type 2 certified.
Last updated: June 2026. Information about Oracle OTM is drawn from Oracle’s public documentation: Oracle Transportation Management documentation, OTM REST API API reference, and OTM customization and Oracle's integration platform docs. Information about eLogii is drawn from elogii.com and the eLogii API documentation.
Custom simulation
A 30-minute working session with our solutions team. We take a sample of your real Oracle OTM delivery orders, depots, vehicles and SLAs, run them through the eLogii engine, and show you the projected delta against how you plan today. No slides, no generic benchmarks.