STACK PATTERN
Geotab is the telematics, compliance and driver-safety layer for the vehicle and the driver: GPS, engine data, driver behavior, fuel, DVIR and HOS, exception events from the Geotab GO device. 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 is one-directional from Geotab into eLogii: MyGeotab API on one side, eLogii’s REST API on the other, typically delivered in 3 to 5 weeks alongside the eLogii rollout.
TRUSTED BY HUNDREDS OF HAPPY CUSTOMERS
Geotab and eLogii sit in different layers of the same stack. Geotab 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 Geotab-side work.
In the combined pattern, Geotab stays the system of record for vehicle telematics, HOS / ELD compliance and driver safety. Vehicle, driver and live-position data flows from Geotab into eLogii; 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 is one-directional on the Geotab side — nothing eLogii produces gets written into Geotab.
Three tables: where telematics & compliance data lives (Geotab leads), where routing and field execution lives (eLogii leads), and what the integration architecture looks like on both sides.
| Geotab | eLogii | |
|---|---|---|
| Vehicle GPS, trip history, engine data | Core. Streamed from the Geotab GO device into MyGeotab | Not in scope. Pulls vehicle locations via the MyGeotab API |
| Driver-behavior events (acceleration, braking, idling, harsh) | Core. Driver scorecards, risk and coaching | Not in scope |
| DVIR, HOS, ELD compliance, driver hours | Core. ELD-certified, FMCSA / DOT compliant via Geotab Drive | Not in scope |
| Geofencing, zones, exception rules | Core. Zone definitions and exception alerts inside MyGeotab | Not in scope. Reads zones / events via the API |
| Vehicle and driver master records | Core. The fleet roster lives in MyGeotab | Mirrors vehicles and drivers from Geotab for routing |
| 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 | Geotab 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 | Geotab Drive covers HOS / DVIR / ELD compliance in the cab; 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 inside MyGeotab; 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 |
| Geotab | eLogii | |
|---|---|---|
| API style | MyGeotab API: JSON over HTTPS, single endpoint with method-style calls | REST, JSON over SSL, ApiKey auth, predictable resource URLs |
| Authentication | Username / password / session ID; tokens via the Authenticate method | ApiKey header, generated in Dashboard > Configuration > API Keys |
| Resources covered | Vehicles, drivers, devices, trips, GPS history, exception events, DVIR, HOS, zones | Tasks, Routes, Drivers, Vehicles, Depots, Zones, Forms, Schedules, Optimization |
| Bulk reads / pagination | MultiCall and Feed methods for high-volume reads of GPS, status and exception data | createOrUpdateMany endpoints handle hundreds of tasks per call |
| Outbound events | Exception-event records and the Feed pattern for change streams | Seven event types including Driver/Task Tracking Update with live GPS stream |
| Optimization callable via API | No route optimization engine in Geotab | All six modes callable via REST; lock specific routes, manually reorder stops |
Sources: Geotab SDK documentation, 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 Geotab 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 Geotab device and driver IDs for telematics correlation.Variations on the same pattern: HOS-aware routing where each driver’s remaining hours from Geotab become a hard constraint; depot selection driven by the driver’s home base / assigned vehicle in Geotab; geofence and exception events from Geotab triggering eLogii re-optimization. None require special connector logic; they are normal mappings on top of one read-only feed from Geotab.
Geotab 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 scoping eLogii alongside Geotab:
Geotab’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: Geotab keeps the vehicle and driver layer, eLogii owns routes, ETAs, POD and customer tracking. The data feed is one-directional from Geotab into eLogii.
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 Geotab + eLogii deployment. The right one depends on what your Geotab 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 Geotab 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. Geotab owns the vehicle and driver layer: GPS, telematics, DVIR, HOS, exception events, Geotab Drive in the cab. 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 Geotab for work-order management. Geotab 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. Geotab feeds vehicle assignment, GPS and HOS hours into eLogii via the MyGeotab API. Bristow & Sutor runs 200+ enforcement agents and 200,000+ case visits routed annually on eLogii; Vergo runs 400 technicians.
eLogii runs alongside Geotab; nothing changes on the Geotab 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 Geotab + eLogii rollouts (including the integration) complete in 3 to 5 weeks. Geotab 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 Geotab’s built-in workflow covers, and who want to keep Geotab 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 the MyGeotab 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 both sides 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 Geotab. Approve the optimizer settings and the write-back fields on the order system.
Weeks 2–3Start with one business unit, depot or region. Drivers onboarded onto the eLogii app alongside Geotab Drive. 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 Geotab + upstream-ERP stack handles today, what the capability actually needs, where users land without it, and how eLogii covers it.
Geotab 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 MyGeotab API.
Geotab Drive is HOS / DVIR / ELD compliance in the cab. eLogii ships a native iOS / Android driver app for delivery and field-service execution: navigation, offline POD, photos, signatures, conditional steps and custom forms.
Geotab shows live vehicle GPS to the fleet operator inside MyGeotab. eLogii streams live driver GPS, real-time route ETAs and branded multi-brand end-customer tracking pages on top.
Through Geotab’s MyGeotab API and eLogii’s REST API. MyGeotab (JSON over HTTPS) exposes vehicles, drivers, devices, trips, GPS history, exception events, DVIR and HOS records. 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 Geotab to eLogii via MyGeotab; eLogii runs the optimization and dispatches the driver app; completion writes back to the upstream order system for invoicing. The integration is one-directional on the Geotab side. Most deployments are delivered in 3 to 5 weeks alongside the eLogii rollout.
No. Geotab Drive is the in-cab HOS / ELD / DVIR compliance app for the driver. eLogii’s driver app is the on-road delivery and field-execution surface: route, navigation, configurable POD, photos, signatures, custom forms. The two run side by side on the same phone. eLogii does not replace HOS / ELD / DVIR compliance; that stays in Geotab Drive.
Vehicle GPS coordinates and trip history, engine and fuel readings, driver-behavior events, DVIR and HOS status, exception alerts, geofence / zone events, and the vehicle and driver master records. That data is exposed via the MyGeotab API. Orders, items, customer addresses and delivery time windows come from the separate upstream order system, not from Geotab.
No. The integration is read-only on the Geotab side. eLogii pulls telematics, vehicle, driver and HOS data from Geotab to feed the optimizer and the live tracking surface. Completion data, POD references, timestamps and driver-collected payments write back to your upstream order system for invoicing and inventory, not into Geotab.
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 Geotab.
Typically 3 to 5 weeks from kickoff to a phased go-live, including the Geotab 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. Geotab 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 Geotab is drawn from Geotab’s public documentation, including the Geotab SDK and the MyGeotab 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 Geotab 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.