eLogii + Webfleet: When to Add eLogii to Webfleet

Where each platform leads

Webfleet and eLogii do different jobs in the same field-service and distribution stack. Webfleet is the telematics platform: the system of record for vehicle GPS, tachograph compliance, OptiDrive 360 driver behavior, Webfleet Video dashcam footage, TPMS tyre data and asset trackers, with an A-to-B route planner and the Webfleet Work App sitting on top of the same hardware estate. eLogii is the routing engine for operations where the optimizer needs to do the heavy lifting across multi-day, multi-depot and constraint-heavy plans, and where the planner needs the engine to decide assignments rather than route them A-to-B with waypoints.

The combined deployment pattern: Webfleet stays the system of record for the GPS trail, OptiDrive 360 score, Tachograph Manager log, Webfleet Video record, TPMS data and the LINK and PRO Driver Terminal hardware estate. eLogii reads stops, vehicles, drivers and depots from the operational systems, runs the optimization across the routing horizons the WEBFLEET planner is not designed to lead on, and writes optimized routes and ETAs back over WEBFLEET.connect. The driver opens the Webfleet Work App or the PRO Driver Terminal in the cab; the route they take is the one eLogii planned. Webfleet keeps the telematics record, hardware estate and tachograph compliance log it owns end to end; eLogii owns the optimization decision layer.

What eLogii adds on top of Webfleet

Webfleet is the telematics platform. eLogii is the routing engine for the optimization-driven side of the problem. The table below isolates where each side leads.

Sources: WEBFLEET features, Webfleet route optimization glossary, Webfleet integration partner directory; eLogii optimization engines. Verified June 2026.

API surface and developer experience

Sources: eLogii API documentation; Webfleet developer resources, WEBFLEET.connect API documentation. Verified June 2026.

Scale, security and commercial

Sources: WEBFLEET features, Webfleet developer resources, Bridgestone EMEA press release: 1.2M+ connected vehicles, Bridgestone TomTom Telematics acquisition, Expertsure Webfleet review, G2 Webfleet reviews. Verified June 2026.

Route optimization, in detail

The WEBFLEET planner is built around the vehicle and the day’s stops, surfaced as an A-to-B route planner with waypoints, traffic-aware navigation and TomTom-heritage HGV routing (bridge heights, weight, hazardous-goods restrictions). What the public product page does not surface is constraint-based routing across time windows, capacity, skills, multi-depot and multi-day as a single solver input, recurring or template routes as a named capability, named multi-day or month-long horizons, or a public REST surface for the optimizer itself with named assignment and load-balancing modes. Webfleet’s own integration partner directory routes those jobs to third-party route optimization tools. eLogii’s optimizer covers exactly that side, callable over REST, plugged into the same WEBFLEET.connect API the partner integrations use.

eLogii’s routing scope

eLogii’s optimizer is built around two engines and six configurable modes, all callable via REST and exposed to the dispatcher as controls they can see and adjust.

• Two engines. The Default engine optimizes 100 tasks in under 10 seconds for high-throughput daily planning. The Advanced engine takes more factors into account and is the choice for multi-depot, multi-day, long-haul and constraint-heavy operations.
• Three assignment modes. Optimize Everything (creates fresh routes including all assignments), Add to Routes, Keep Existing Assignments (incorporates new tasks into existing routes while preserving driver assignments), and Add to Routes, Keep Existing Assignments and ETAs (inserts new tasks into available slots without modifying existing stop sequences or ETAs).
• Three load-balancing modes. Most Efficient Routes (fewest vehicles), Balance the Minimum Number of Routes (across load, time, distance or job count), and Use All Vehicles / Finish as Soon as Possible (maximize speed).

Beyond the modes, eLogii ships the operational surface the WEBFLEET planner isn’t designed to lead on: multi-day and long-haul routing (“plan a single day or an entire month in one run”), multi-depot (“route across multiple depots, branches, or home start locations in a single run”), recurring service patterns via task and route template groups (weekly, monthly, quarterly, bespoke cadences modeled as inputs to the optimizer), multi-technician crew jobs with skills, capacity and SLA constraints, and rule-based re-optimization the operator can see and steer.

What this means in practice

If the planner’s morning routine is “open the WEBFLEET planner, drop today’s stops as waypoints on an A-to-B route, send to the driver’s Work App, let traffic-aware HGV routing handle the rest”, Webfleet is the right tool and adding eLogii would be over-engineering. If the planner’s morning routine is “run the optimizer against today’s open jobs across three depots, balance against next week’s recurring service book, protect the SLA-locked priority bookings, route around the driver who’s off Tuesday”, the WEBFLEET planner is being asked to do a job it wasn’t built for and the integration-partner pattern (a third-party route optimization tool) adds a second commercial relationship and a second UI to manage. eLogii covers that side via REST API, plugged directly into the same WEBFLEET.connect; Webfleet stays in place for the GPS, OptiDrive 360 score, tachograph, Webfleet Video and Work App data.

When eLogii’s depth starts to matter

Webfleet covers the telematics-anchored fleet workflow well across European commercial, services and distribution. The signal that the routing problem has grown past what the WEBFLEET planner was designed for tends to be operational rather than headcount-based. Three patterns show up:

• Optimizer-driven assignment under heavy constraint. When the planner is spending the morning hand-balancing jobs across drivers, areas and skill sets, the optimizer should be making those calls. The WEBFLEET planner is designed as an A-to-B planner with waypoints and traffic-aware HGV routing; once the placement itself is the bottleneck and either the planner or the integration partner (a third-party route optimization tool) isn’t closing the gap with a single coherent decision layer, a dedicated routing engine plugged directly into WEBFLEET.connect makes more sense.
• Multi-depot rebalancing as a daily input. A regional service organization with three or four depots, or a distribution arm running parallel to the field-service business, needs the optimizer to see all depots as part of the same problem. The WEBFLEET planner product page does not document multi-depot as a supported constraint; cross-depot rebalancing as a single optimization input is left to the planner or a third-party tool.
• Recurring service programs at thousands of stops. Quarterly preventive cadences, monthly inspection rounds, contract-driven recurring visits across a large customer base. Recurring or template routes are not surfaced on the WEBFLEET planner page; the optimization across the recurring book, interacting with reactive break-fix work, is the part that needs the engine.

Where any of these is the dominant shape of the work, eLogii is the routing layer. Where none of them is, the WEBFLEET planner with the Webfleet Work App on top is the right tool and adding eLogii is over-engineering. The honest answer for many Webfleet customers is “you don’t need eLogii.” The honest answer for the operations where the optimizer is the bottleneck is that eLogii is built for exactly that.

What changes once eLogii is in place

Webfleet continues to do the telematics work it’s built for: GPS trail, OptiDrive 360 driver behavior scoring, Tachograph Manager HGV compliance, Webfleet Video dashcam, TPMS tyre data, LINK tracker and PRO Driver Terminal hardware estate. The difference shows up where the routing problem used to dominate. Brymec lifted productivity 30% and routing efficiency 20% on eLogii. ATS Building Products improved deliveries per route by ~98%. Porcelanosa runs eLogii with 95%+ ETA accuracy on daily distribution. Unimasters runs eLogii across a multi-country operation and achieved 50% less planning time and 49% fewer service calls. These are operational outcomes that come from moving the assignment problem from the planner’s morning into the optimizer:

• Slot booking co-pilot. When a customer is offered a time window, eLogii’s slot availability returns only slots that already fit the current optimized plan. Cuts failed visits ~35%. Plugs into whichever booking layer is in use over REST.
• Customer-driven rescheduling. Around 70% of reschedule requests handled without coordinator involvement. The customer picks a slot that already fits the plan and the route re-optimizes.
• Branded customer tracking pages. NPS surveys, safety briefings, access codes, treatment instructions, pushed onto the tracking page itself rather than handed off to a separate channel. Webfleet’s public product pages do not document branded tracking links as a named capability.
• Multi-brand tracking. Three brands run from one dispatch desk, each with its own logo, colors and layout.
• Map-native dispatch ops. Drag-and-drop reassignment with automatic ETA recalc on both routes; polygon, freehand and rectangle map selection; bulk actions on hundreds of stops; Gantt-style route timeline alongside the map; 13 historical segments refreshed overnight.
• Rule-based exception handling. Reroute a no-access visit to the nearest driver with the right skill, but don’t move any customer-confirmed bookings in the next 90 minutes. Visible to the planner, not buried in a black-box optimizer.
• Workflow analytics. Average time per step, skip rates, error patterns, completion data. Where driver hours actually went, not just where the vehicles went.

Running eLogii alongside Webfleet and the wider stack

The typical Webfleet-anchored stack: telematics for the vehicles (WEBFLEET for GPS, OptiDrive 360 for driver behavior scoring, Tachograph Manager for HGV compliance, Webfleet Video dashcams, TPMS, LINK trackers, PRO Driver Terminals), an FSM or operational system of record (Salesforce Field Service, ServiceTitan, BigChange, Joblogic, Microsoft Dynamics 365 Field Service, or an ERP-anchored operational module), an ERP for finance and customer master data (Microsoft Dynamics 365 Business Central, Microsoft Dynamics 365 Finance & Operations, SAP, NetSuite), and a routing decision layer alongside the WEBFLEET planner for operations where the optimizer is the bottleneck.

eLogii is built for that shape. It plugs into Webfleet, leaving the GPS trail, OptiDrive score, tachograph log, Webfleet Video record and Work App estate where they already are. The driver opens the Webfleet Work App or PRO Driver Terminal in the cab; eLogii plans the route they take to get there, surfaces the live ETAs, picks up GPS, and pushes completion back into the operational system. The common patterns:

• Webfleet + eLogii. Webfleet owns the GPS, OptiDrive, tachograph and Webfleet Video estate. eLogii owns the optimization layer where dispatch is dominated by multi-depot regional teams, recurring service programs at scale, or constraint-driven assignment across multi-day plans. Integration runs over WEBFLEET.connect (OAuth 2.0) and eLogii’s REST API; an iPaaS like Workato or MuleSoft is a common middleware choice.
• Webfleet + Work App + eLogii. The Webfleet Work App handles the driver-facing dispatch surface: order/task lists, ePOD, two-way messaging, working-hours logging, OptiDrive scoring, secure truck-parking booking. eLogii sits as the routing engine for the multi-depot, multi-day, recurring-program horizons, called via REST and writing back the optimized routes that the Work App then renders for the driver.
• Webfleet + FSM + eLogii. Salesforce Field Service, ServiceTitan, BigChange, Joblogic or Microsoft Dynamics 365 Field Service is the FSM. Webfleet provides the telematics. eLogii routes across the FSM’s jobs and the Webfleet fleet in one optimization run, replacing the need for a separate partner integration like a third-party route optimization tool in the routing layer.
• Webfleet + ERP + eLogii. When the financial system of record sits in Business Central, Finance & Operations, SAP or NetSuite, eLogii reads operational data from the ERP and runs the optimization, writing routes back for execution. The Webfleet integration stays where it is for telematics.

What makes the stack pattern straightforward:

• 70+ REST endpoints across Tasks, Routes, Drivers, Vehicles, Depots, Zones, Schedules, Forms and Optimization, designed for clean integration into a wider stack.
• Full-parity sandbox at api-sandbox.elogii.com so integration work can run in parallel with the existing telematics and FSM rollout.
• Webhooks with live driver GPS and ETA stream push real-time state back to the FSM, the dispatcher view or the customer-facing app. No polling, no cron jobs, no stale data.
• Bulk operations. POST /tasks/createOrUpdateMany handles hundreds of tasks per call, built for high-volume ingest from any FSM or ERP.
• Telematics, FSM and ERP independent. Customers running Webfleet, Samsara, Geotab, Verizon Connect or TomTom on the telematics side, and any FSM or ERP on the operational side, use eLogii for the optimization layer alongside whichever stack they already chose.

Webfleet exposes WEBFLEET.connect through its developer portal with OAuth 2.0 for downstream subscribers. The two APIs combine cleanly: eLogii reads stops, vehicles, drivers and depots from the operational source-of-truth (FSM, ERP or Webfleet directly), runs the optimization across the routing horizons the WEBFLEET planner is not designed to lead on, and writes optimized routes and ETAs back over WEBFLEET.connect. Webfleet picks up the in-cab GPS, OptiDrive, tachograph and Webfleet Video stream; the optimized route is what the driver follows. Completion data flows back into the operational system for the work record, asset history and reporting.

API surface, side by side

Both sides expose REST APIs. Webfleet’s is the integration surface for the telematics data model, reachable through WEBFLEET.connect with OAuth 2.0. eLogii’s is the integration surface for a routing and optimization engine, with the optimizer itself callable as REST endpoints.

eLogii API

• 70+ REST endpoints across Tasks, Routes, Drivers, Vehicles, Depots, Customers, Zones, Forms, Schedules and Optimization. Full reference.
• Authentication: ApiKey header, generated in Dashboard > Configuration > API Keys. Machine-to-machine without an OAuth round-trip.
• Sandbox: api-sandbox.elogii.com, full parity with production at api-35.elogii.com.
• Bulk operations: POST /tasks/createOrUpdateMany handles hundreds of tasks per call, built for high-volume ingest from any FSM or ERP.
• Optimization callable via REST: all six modes available programmatically; dispatchers can lock specific routes, manually reorder stops, or re-run with new constraints.
• Seven webhook event types, including Driver/Task Tracking Update with live GPS stream and Route ETAs Update. No polling, no cron jobs.
• Custom fields end-to-end through driver app, webhooks and reporting.
• FSM, ERP and telematics independent via REST API, including SAP, Oracle NetSuite, Microsoft Dynamics 365 Business Central, Sage, Acumatica, IFS, Infor, Joblogic, BigChange, Simpro, ServiceTitan, FieldRoutes, Salesforce Field Service, Samsara, Geotab, Verizon Connect and Webfleet.

Webfleet API (WEBFLEET.connect)

• REST API with OAuth 2.0 authentication, documented through the Webfleet developer portal.
• Documented endpoint surface: job dispatch, predefined routes over-the-air, message queues, driver safety data, vehicle and driver status, geofence events.
• Partner integration directory: Webfleet publishes a partner directory covering FSM, route optimization, fuel and tyre management, accounting and other ecosystem connectors.
• What’s not externally callable as named optimization modes: the WEBFLEET planner is positioned as a user-facing A-to-B planner with traffic-aware HGV routing. Constraint VRP (time windows, capacity, skills, multi-depot, multi-day) is delivered through partner integrations, not exposed as Webfleet REST endpoints with operator-visible modes.
• Documented per-device cap: third-party integration partner documentation reports a cap of 100 orders pushed to a single driver device.

For an integration team, the typical pattern when Webfleet and eLogii are both in the stack: Webfleet owns the system of record for GPS, OptiDrive 360, tachograph and Webfleet Video; the operational system (FSM or ERP) owns the work record; eLogii reads stops/vehicles/drivers/depots from the operational source-of-truth, runs the optimization across the horizons the WEBFLEET planner is not designed for, writes optimized routes and ETAs back over WEBFLEET.connect; Webfleet captures the in-cab stream; completion writes back to the operational system for the work record, asset history and reporting.

Pricing and time to live

eLogii runs alongside Webfleet; it does not replace what you’re paying Webfleet today. The question is what eLogii adds on top, and what it costs to add it.

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 Webfleet + eLogii rollouts complete in 3 to 5 weeks including the connector build.

Webfleet does not publish list pricing; the contract is per-vehicle, hardware-tied and quote-only, on multi-year terms for best rates. Pricing is tiered across Core, Pro and Premium bands, with Premium adding tachograph and driver coaching. The pricing models compose: Webfleet charges per vehicle for the telematics layer (with hardware fees), eLogii charges a platform fee for the routing layer. There is no per-seat or per-vehicle cost from eLogii.

When eLogii on top of Webfleet starts to pay off

Adding eLogii alongside Webfleet

Three steps for Webfleet customers whose planning problem has grown past what the WEBFLEET planner is designed to solve. Webfleet stays in place for the telematics; eLogii layers on as the routing engine.

Unimasters 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 pattern, in depth

The WEBFLEET planner is a useful A-to-B planner inside Webfleet. Five patterns where the optimization decision layer alongside it is the bottleneck, each with its own deep dive:

Frequently asked questions

Is eLogii a Webfleet alternative or a complement?

Complement, in most cases. Webfleet is the European telematics platform under Bridgestone Mobility Solutions, built from TomTom Telematics: the WEBFLEET console for tracking and dispatch, the Webfleet Work App for drivers, LINK series trackers, PRO Driver Terminals, Webfleet Video dashcams, TPMS, OptiDrive 360 driver behavior scoring and Tachograph Manager for HGV compliance, plus an A-to-B route planner with traffic-aware HGV routing. eLogii is the routing and optimization layer that runs alongside Webfleet when the planning problem starts to dominate: multi-depot field-service and distribution operations, dense same-day plans with hundreds of competing time-window constraints, optimizer-driven assignment across crews, recurring service programs at thousands of stops. Webfleet stays the system of record for the vehicle, GPS trail, OptiDrive score, tachograph and Work App data. integration runs over WEBFLEET.connect on one side and eLogii’s REST API on the other.

When does adding eLogii on top of Webfleet make sense?

When the WEBFLEET planner stops being the right place to solve the optimization problem and the Work App’s drag-and-drop dispatch is not closing the gap. The WEBFLEET planner is documented as A-to-B route planning with waypoints and traffic-aware HGV routing; constraint-based routing across time windows, capacity, skills, multi-depot and multi-day is not documented on the planner page and Webfleet’s own integration partner directory routes those jobs to third parties (third-party route optimization tools). eLogii layers on when the operation needs constraint-aware assignment across multi-day, multi-depot and recurring patterns in one optimization run, programmatic re-optimization with operator-visible rules, and slot booking that respects the current optimized plan.

Does Webfleet handle multi-resource crews, multi-day plans and multi-depot routing?

Partially. The WEBFLEET planner documents A-to-B route planning with waypoints, traffic-aware navigation and HGV restrictions (bridge heights, weight, hazardous-goods routing) drawn from the TomTom map heritage. Constraint-based routing across time windows, capacity, skills, multi-depot and multi-day is not native to the planner; Webfleet’s own integration partner directory lists third-party route optimization tools as the route-optimization partners that ship those constraints. Third-party integration documentation reports a 100-orders-per-device cap when pushing routes to a single driver. That’s the band where eLogii’s two engines and six configurable modes add depth, with Webfleet staying the system of record for the vehicle, GPS, OptiDrive score, tachograph and Work App data.

How does eLogii integrate with Webfleet?

Integration runs over WEBFLEET.connect (Webfleet’s REST API with OAuth 2.0 authentication) and eLogii’s REST API. WEBFLEET.connect documents endpoints for job dispatch, predefined routes over-the-air, message queues and driver safety data. eLogii’s REST API has 70+ endpoints, ApiKey auth, a full-parity sandbox at api-sandbox.elogii.com and seven webhook events including live driver GPS and Route ETAs Update. The typical pattern, Typically: eLogii reads stops, vehicles, drivers and depots from the operational systems; runs the optimization across the routing horizons the WEBFLEET planner is not designed to lead on; writes optimized routes and ETAs back over WEBFLEET.connect. Webfleet keeps the GPS trail, OptiDrive 360 score, tachograph log, Webfleet Video record and Work App job status.

How does pricing compare?

Webfleet prices per vehicle on multi-year hardware-tied contracts; pricing is quote-only and not publicly published. eLogii is a platform fee, banded by field staff, drivers, jobs per day and modules, from USD 3,000 per month. The pricing models compose: Webfleet charges per vehicle for the telematics layer, eLogii charges a platform fee for the routing layer. Customers typically report 3 to 4× return on investment within 6 months on eLogii.

How long does adding eLogii to a Webfleet stack take?

Typically 3 to 5 weeks from kickoff to a phased go-live, including building the custom connector against WEBFLEET.connect. eLogii reads stops, vehicles, drivers and depots from the operational systems; routes, ETAs and completion data flow back over WEBFLEET.connect. Most teams start with the business unit where the WEBFLEET planner is leaking the most: usually a multi-depot regional book, a recurring service program at scale, or the part of the operation where the planner is hand-rebalancing every morning. Webfleet stays in place for everything telematics-related: GPS trail, OptiDrive 360 score, tachograph, Webfleet Video, TPMS.

Where does Webfleet sit in the Bridgestone Mobility Solutions portfolio?

Webfleet is the European telematics brand under Bridgestone Mobility Solutions, built from TomTom Telematics. Azuga is the Bridgestone Americas sibling brand; the two run separately. Webfleet maintains an integration partner directory covering FSM, route optimization, fuel and tyre management, accounting and other ecosystem connectors. eLogii integrates against WEBFLEET.connect directly, not via the partner directory.

Why would a Webfleet customer add a routing engine instead of using the WEBFLEET planner and a partner integration?

Three reasons. First, the WEBFLEET planner is documented as A-to-B route planning with waypoints and traffic-aware HGV routing; constraint-based routing across time windows, capacity, skills, multi-depot and multi-day is not native to the planner and Webfleet’s own integration partner directory routes those jobs to third parties (third-party route optimization tools). Once the operation needs that depth as a daily input, the integration-partner pattern adds a second commercial relationship and a separate UI. Second, eLogii customers at scale report operational outcomes that go past what fleet routing alone delivers: Brymec 30% productivity and 20% routing efficiency; ATS Building Products 98% improvement in deliveries per route; Porcelanosa 60%+ planning time cut; Unimasters 50% less planning time and 49% fewer service calls. Third, eLogii exposes the optimizer itself as REST endpoints with seven webhook events, so the routing layer integrates cleanly into the Webfleet stack via WEBFLEET.connect, with a single commercial relationship.

Is eLogii enterprise-grade?

Yes. eLogii runs operations at scale: J-Club (9,000+ stores), NHS, Belfast City Council, Vergo Pest Management (400 technicians, Tyro Group), Bristow & Sutor (200+ enforcement agents, 200,000+ case visits routed annually), Porcelanosa, Caldic and Berkmann Wine Cellars. ISO 27001 and SOC 2 Type 2 certified.