eLogii vs Spoke: Key Differences Explained

Which platform was built for which problem

Feature-by-feature

Spoke (formerly Circuit) is best-in-class for SMB courier teams: mobile-first driver app, simple sign-up, stop-based pricing that stays predictable as the team grows. eLogii goes deep on enterprise field service and distribution. The honest table below shows where each product is the depth leader. They do not target the same operations.

Capabilities (delivery + routing surface)

Scale & positioning

Developer & commercial

Sources: eLogii API documentation, Spoke public materials (spoke.com, formerly getcircuit.com). Verified June 2026.

Route optimization and scheduling

Both products optimize routes. The differences are in what shape the routing workload takes, and how much of the planning problem the optimizer is expected to model.

Spoke’s routing

Spoke Dispatch is built for day-of last-mile route optimization: take today’s parcels or deliveries, generate an efficient route per driver, push to the mobile driver app, expose tracking to recipients. For SMB courier teams this is the right shape and is genuinely well-executed. Spoke is mobile-first and consumer-grade simple. Where Spoke does not lead is multi-day routing, long-haul planning, multi-depot enterprise dispatch and recurring template-driven cadences.

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, multi-day long-haul routes 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

Both products re-plan within their 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.

SMB delivery dispatch vs enterprise dispatcher tooling

The choice usually turns on operation shape and scale. Spoke is purpose-built and best-loved at the SMB end of last-mile delivery. eLogii is purpose-built and best-loved for enterprise field service and distribution. These are not the same operation.

Spoke Dispatch is mobile-first, stop-based, and structured around how a small courier team operates day to day. Self-serve sign-up, predictable per-stop cost, a strong driver app, recipient tracking. The published Spoke Dispatch tiers cap at 12,000 stops per month, which is roughly 400 stops per day across the whole team. Above that volume, or with operational complexity that goes beyond daily-route dispatch, the product is operating outside the shape it was built for.

eLogii puts its entire roadmap into enterprise dispatcher tooling: recurring routes, multi-depot planning, multi-day and long-haul routes, 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. Pricing starts at $3,000 per month and is banded by field staff, drivers, jobs per day and the modules required.

eLogii is also 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. It also integrates with SAP, Oracle NetSuite, MS Dynamics 365 Business Central, Sage, Acumatica, IFS and Infor via the REST API.

Brymec 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 trialed five before choosing eLogii, citing flexibility and how quickly drivers could be onboarded. Crocus, a leading gardening services provider, runs deliveries on eLogii. These are exactly the evaluations where the buyer’s problem outgrows the SMB courier shape and lands in enterprise field service or distribution.

Dispatcher tooling depth

Spoke Dispatch ships a clean, focused interface for SMB courier teams. eLogii ships a deeper dispatch-desk surface for field operations, plus a deeper customer experience surface for field service flows, because at enterprise scale the dispatcher tooling is itself the product, not a thin layer over a routing engine.

• 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. ATS Building Products and Brymec run distribution on eLogii. For SMB courier teams Spoke Dispatch’s focused surface is the right tool. For enterprise operations at scale whose bottleneck is dispatcher tooling day to day, depth in a platform built for that scale is the bigger lever.

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.