eLogii vs Locus: Key Differences Explained

Which platform was built for which problem

Feature-by-feature

Locus is an enterprise dispatch and last-mile platform with AI-led positioning across dispatch planning, real-time tracking, multi-carrier allocation (ShipFlex), field workforce and network design. eLogii goes deep on field service and distribution. On the advanced routing surface where they overlap, the differences are in operator-controllable optimization depth, recurring routes, and modernity of the developer surface.

Capabilities (advanced routing surface)

Scale & positioning

Developer & commercial

Sources: eLogii API documentation, Locus public materials (locus.sh). Verified May 2026.

Route optimization and scheduling

Both products handle enterprise route planning. The differences are in how the optimization surface is exposed to operators, and how much of the planning logic stays in the planner’s hands rather than behind an AI black box.

Locus’s routing

Locus markets a constraint-aware AI dispatch engine that optimizes across more than 180 variables. The strength is real at dispatch scale across retail, FMCG, 3PL and e-commerce. If your problem is high-volume AI-led dispatch with multi-carrier allocation (Locus ShipFlex) and sortation or network design alongside last-mile, Locus’s platform breadth is genuine.

eLogii’s routing

eLogii’s optimizer is exposed across five distinct modes: a single data set, one or more specific dates, existing routes (re-optimization), a date range, and recurring patterns with varying intervals. Skills, capabilities, vehicle capacity, SLA windows, business rules and time constraints are all considered together, with configurable objectives the planner can see and adjust.

For field service and distribution, eLogii models recurring cadences natively via routes, task template groups and route template groups. Quarterly residential treatments, monthly commercial accounts, weekly compliance visits, daily distribution drops and reactive callouts can all sit in the same plan. This is the engine J-Club (9,000+ stores) and Vergo (400 technicians) run their operations on.

Dynamic re-optimization

Locus re-plans within its dispatch scope. eLogii exposes rule-based re-optimization to operators directly. For example, reroute a no-access visit to the nearest technician with the right pest license, but don’t move any quarterly accounts with a customer-confirmed window in the next 90 minutes. At enterprise scale, rule-based re-optimization is how planners stop chasing exceptions one at a time.

Routing depth vs dispatch-platform breadth

Both are enterprise-credible. The choice usually turns on this.

Locus is a broad enterprise dispatch and last-mile platform. One vendor across dispatch planning, real-time tracking, multi-carrier allocation (ShipFlex), field workforce, sortation and network design, with deep AI/ML positioning and 350+ deployments across 30+ countries. The track record is real in retail, FMCG, 3PL and e-commerce. The trade-off is that the dispatch engine sits inside a wider platform with multiple modules, and the operator surface is shaped by AI-led automation rather than configurable, planner-visible logic.

eLogii puts its entire roadmap into advanced routing and field execution: recurring routes, multi-depot planning, mid-execution re-optimization, the driver app, the analytics surface. The data model treats recurring template groups, configurable Forms, skills-based assignment and custom fields as dedicated API entities rather than configuration layered on top of a generic dispatch object.

Either product can be embedded in your wider stack:

• eLogii is FSM and ERP independent: it integrates with FieldRoutes, Simpro, Samsara, and ServiceTitan, Salesforce Field Service, ServiceMax, ServiceNow, MS Dynamics 365 Field Service, Joblogic, Jobber and Housecall Pro via the REST API.
• eLogii also integrates with SAP, Oracle NetSuite, MS Dynamics 365 Business Central, Sage, Acumatica, IFS and Infor via the REST API.
• Locus integrates broadly across ERPs, WMSs and dispatch surfaces; specifics best confirmed directly per module.

Brymec (UK HVAC and building services distribution) evaluated 15 logistics platforms before picking eLogii, with Transport Manager Tom Maddison calling it the clear winner after narrowing to three. Heatleys (~200 deliveries per day, MRO and safety distribution) evaluated 20+ options and trailed five before choosing eLogii, citing flexibility and how quickly drivers could be onboarded. These are exactly the evaluations where focused depth wins when the buyer’s problem is advanced routing and field execution rather than a broader AI-dispatch-plus-multi-carrier mandate.

Customer experience and dispatch-desk depth

Locus ships customer-facing tracking and dispatch tooling across its platform. eLogii ships a deeper customer experience surface and dispatch-desk surface because both are the core product, not modules sharing a wider dispatch roadmap.

• Slot booking co-pilot. Customers only see slots that fit current routes. Cuts failed visits 35%.
• 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.
• Embedded tracking content. Push NPS surveys, safety briefings, access codes or treatment instructions onto the tracking page itself.
• Multi-brand tracking. Run three brands from one dispatch desk, each with its own logo, colors and layout.
• Map-native dispatch ops. Drag-and-drop reassignment with auto 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.
• Workflow analytics. Average time per step, skip rates, error patterns, completion data. Tells you where the technician hours actually landed, not just where the routes went.

Porcelanosa runs eLogii with 95%+ ETA accuracy on their daily routes. For field teams whose bottleneck is this layer day to day, depth in this layer is the bigger lever than dispatch-platform breadth.

Running eLogii alongside your FSM, ERP and telematics

Enterprise operations at scale rarely run on a single packaged product. The common shape is a stack: an FSM for field execution and paperwork (ServiceTitan, FieldRoutes, Simpro, Joblogic, Salesforce FS, MS D365 FS), an ERP for finance, inventory and customer master data (SAP, NetSuite, MS Dynamics 365 BC, Sage, Acumatica), telematics for the vehicles (Samsara, Geotab, TomTom), and a routing layer on top.

eLogii is built for that shape. It plugs into your existing FSM and ERP as the advanced optimization layer, leaving field execution and paperwork in the FSM where your drivers and technicians already work day to day. The technician opens the FSM’s field app on site; eLogii plans the route they take to get there, surfaces the live ETAs, picks up GPS, and pushes completion back into the FSM.

• 50+ REST endpoints across Tasks, Routes, Drivers, Vehicles, Depots, Zones, Schedules 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 FSM/ERP rollout.
• Webhooks with live driver GPS and ETA stream push real-time state back to your FSM, dispatcher view or customer-facing app.
• Bulk operations. POST /tasks/createOrUpdateMany handles hundreds of tasks per call, built for high-volume ingest from any FSM or ERP.
• FSM and ERP independent. Customers running FieldRoutes, Simpro, Salesforce FS or MS D365 FS use eLogii for advanced optimization alongside the FSM they already chose.