STACK PATTERN
Motive is the telematics layer: vehicle GPS, engine data, driver behavior, fuel, maintenance, DVIR and HOS compliance, AI dashcam. eLogii is the routing and field execution layer that turns your delivery and field-service jobs into optimized routes, live ETAs, driver workflows and proof of delivery, then writes the completion data back to your upstream order system. Two systems, two jobs. The integration runs over Motive’s Fleet API on one 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
Motive and eLogii sit in different layers of the same stack. Motive is the telematics layer: vehicle GPS, engine data, driver behavior, fuel, maintenance and DVIR, HOS compliance. 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 Motive-side work.
In the combined pattern, Motive stays the system of record for vehicle telematics and driver compliance. Vehicle and driver data flows from Motive into eLogii; the optimized plan flows the other way; 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 your upstream order system for invoicing. The integration runs over both products’ REST APIs.
Three tables: where vehicle and driver data lives (Motive leads), where routing and field execution lives (eLogii leads), and what the integration architecture looks like on both sides.
| Motive | eLogii | |
|---|---|---|
| Vehicle GPS, engine data, idling, harsh events | Core. Streamed from the Motive Vehicle Gateway and dashcam | Not in scope. Reads vehicle locations via the Motive Fleet API |
| Driver behavior scoring, safety events, coaching | Core. Driver Safety Score, dashcam event review | Not in scope |
| DVIR, HOS, ELD compliance, driver hours | Core. ELD-certified, FMCSA / DOT compliant | Not in scope |
| Vehicle and driver master records | Core. The fleet roster lives in Motive | Mirrors vehicles and drivers from Motive for routing |
| Fuel cards, fleet maintenance schedules | Core. Motive Card, maintenance and inspection records | Not in scope |
| Item weight, cube, handling for capacity math | Not in scope. Lives on the upstream order / ERP | Reads from the upstream order system to feed optimizer constraints |
| Customer delivery address, time windows | Not in scope. Lives on the upstream order record | Reads from the upstream order system to feed optimizer constraints |
| eLogii | Motive native | |
|---|---|---|
| Multi-stop route optimization with constraints | Two engines, six configurable modes; vehicles, depots, capacities, time windows, skills, SLAs | No native constraint-aware route optimizer |
| Multi-day, 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 | Motive Driver app covers HOS/DVIR/messaging; not a delivery POD or stop-execution surface |
| Live GPS, route ETAs, branded customer tracking | Live driver GPS stream, route ETA updates, multi-brand tracking pages with embedded content | Live vehicle GPS for the fleet operator; no end-customer route ETA or branded delivery tracking |
| 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 |
| Motive | eLogii | |
|---|---|---|
| API style | Motive Fleet API: REST, JSON | REST, JSON over SSL, ApiKey auth, predictable resource URLs |
| Authentication | API token (created in the Motive Dashboard) or OAuth 2.0 for partner apps | ApiKey header, generated in Dashboard > Configuration > API Keys |
| Webhooks / events | Outbound webhooks for vehicle, driver, location, DVIR, HOS and safety events | Seven event types including Driver/Task Tracking Update with live GPS stream |
| Bulk reads / pagination | Paginated list endpoints for vehicles, drivers, locations and events | createOrUpdateMany endpoints handle hundreds of tasks per call |
| Optimization callable via API | No route optimization engine in Motive | All six modes callable via REST; lock specific routes, manually reorder stops |
Sources: Motive Developer Portal, eLogii API documentation. Verified June 2026.
End to end, how a delivery order moves from your upstream order system through eLogii to a completed POD, with Motive feeding the vehicle and driver layer alongside. 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 upstream order ID held as external_id so every eLogii object can be traced back to its source order. Vehicle and driver records are referenced by Motive vehicle and driver IDs for telematics correlation.Variations on the same pattern: depot selection driven by the driver’s assigned vehicle and home base in Motive; multi-day field-service jobs where one eLogii task represents each visit; HOS-aware planning that respects each driver’s remaining hours pulled from Motive. None of these require special connector logic; they are normal mappings across two REST APIs.
Motive is a deep telematics, compliance and driver-safety platform. Several of its modules feed the delivery problem at the edge, but none of them are route optimization or stop-by-stop execution. Drawing the line clearly matters when you are scoping eLogii alongside Motive:
Motive’s core was built to be a telematics, compliance and safety platform. The point of mapping the seam is so the integration with eLogii is clean: Motive keeps the vehicle and driver layer, eLogii owns routes, ETAs, POD and customer tracking.
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 Motive + eLogii deployment. The right one depends on what your Motive 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 Motive alongside eLogii. Same underlying pattern, different surface.
Wholesale food and drink, building materials, bathroom and kitchen, pharma, grocery. Items, customer master, delivery addresses and the order book live in the upstream ERP or order system. Motive owns the vehicle and driver layer: GPS, telematics, DVIR, HOS, fuel cards, dashcam. 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.
Most field-service operations run a dedicated FSM in front of Motive for work-order management. Motive sits at the vehicle and driver layer; the FSM (Simpro, Joblogic, ServiceTitan, Salesforce Field Service, MS Dynamics 365 Field Service) handles work-orders, jobs and invoicing; eLogii sits as the routing and dispatch layer, handling multi-day jobs, multi-technician crews, recurring service patterns and the driver mobile app for on-site execution. Motive feeds vehicle assignment, GPS and HOS hours into eLogii via the Fleet API. Bristow & Sutor runs 200+ enforcement agents and 200,000+ case visits routed annually on eLogii; Vergo runs 400 technicians.
eLogii runs alongside Motive; nothing changes on the Motive 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 Motive + eLogii rollouts (including the integration) complete in 3 to 5 weeks. Motive 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 Motive’s built-in workflow covers, and who want to keep Motive for items, customers, orders, inventory and financial close while adding eLogii for routing and execution on top.
Vehicles, drivers, HOS hours and live vehicle locations pulled from Motive’s Fleet API. Orders and customer master pulled from the upstream order system on a separate integration. Mapping to eLogii task fields documented end to end. Sandbox connectivity proven on Motive and on the upstream order system before any production data moves.
Weeks 1–2Custom data simulation against your historical order 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, using real vehicle and driver data from Motive. 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 alongside the existing Motive Driver app. Webhook stream wired to your integration layer. POD and completion data writing back to the upstream order system 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 stack-pattern detail, walks what the Motive + upstream-ERP stack handles today, what the capability actually needs, where users land without it, and how eLogii covers it.
Motive has no native constraint-aware route optimizer. eLogii is the routing layer on top: two engines, six modes, REST-callable, reads vehicles and drivers from the Motive Fleet API.
The Motive Driver app is HOS, DVIR and dashcam. eLogii ships a native iOS / Android driver app for delivery and field-service execution: navigation, offline POD, photos, signatures, conditional steps and custom forms.
Motive shows live vehicle GPS to the fleet operator. eLogii streams live driver GPS, real-time route ETAs and branded multi-brand end-customer tracking pages on top.
Through both products’ REST APIs. Motive’s Fleet API exposes vehicles, drivers, vehicle locations, driver-behavior events, DVIR and HOS records, and supports outbound webhooks. 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 your upstream order system to eLogii; vehicle, driver and live-GPS data flow from Motive to eLogii; eLogii runs the optimization and dispatches the driver app; completion data writes back to the upstream order system for invoicing. Most deployments are delivered in 3 to 5 weeks alongside the eLogii rollout.
No. The Motive Driver app is the compliance and safety surface (HOS, DVIR, dashcam, fuel cards, messaging). eLogii’s driver app is the on-road delivery surface (route, navigation, POD, photos, signatures, custom forms). They run side by side on the same phone.
From Motive: vehicle GPS, engine and fuel readings, driver behavior events, DVIR and HOS status, maintenance and exception alerts, vehicle and driver master records. That data is exposed via the Motive Fleet API. Orders, items, customer addresses and delivery time windows come from the separate upstream order system, not from Motive.
Vehicle GPS, engine and fuel readings, driver-behavior events, DVIR / HOS status, AI dashcam events and maintenance / exception alerts, plus the vehicle and driver master records and zones. eLogii uses this to plan routes against real vehicles, real drivers and their remaining HOS, and to surface live position into the dispatch desk and end-customer tracking page. The integration is one-directional: data flows from Motive into eLogii. Completion and POD write to the upstream order system, not into Motive.
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 Motive.
Typically 3 to 5 weeks from kickoff to a phased go-live, including the Motive integration. Most teams start with one business unit, depot or region, validate against historical order data, then expand. Heatleys evaluated 20 platforms and went live fast on eLogii, citing how quickly drivers could be onboarded.
It does not. Motive 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 Motive is drawn from Motive’s public documentation, including the Motive Developer Portal and the Fleet API reference. 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 Motive 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.