COMPARISON
Both platforms handle enterprise route optimization. The real differences buyers act on are operational: how long it takes to go live, who configures and operates the system day to day, how deep the field-execution surface is (driver app, POD, branded tracking, self-service rescheduling), and the shape of the API integration into your existing FSM, ERP and telematics. This page maps out those differences against eLogii’s and Ortec’s published documentation, with the customer evidence behind each.
TRUSTED BY HUNDREDS OF HAPPY CUSTOMERS
Route optimization, dispatch, the driver mobile app, live customer tracking and operational analytics, shipped as one platform. Configuration is operator-facing: dispatchers and operations leads change skills, capacities, recurring patterns, SLAs and tracking-page brands from the UI. Named customers include J-Club (9,000+ stores), NHS, Belfast City Council, Vergo (400 technicians), Greenix, Bristow & Sutor, Porcelanosa, Caldic and City of Little Rock. ISO 27001 and SOC 2 Type 2 certified.
Long-running optimization business with several products in market. Routing is shipped as ORTEC Routing & Dispatch (standalone SaaS), ORTEC for SAP (SAP-certified, embedded in the SAP UI) and industry-specific bundles for foodservice, retail and CPG. Sold enterprise contact-sales with consulting-led implementations. Customer base spans retailers, manufacturers, 3PLs and foodservice distributors.
The comparison below covers what overlaps in scope between eLogii and ORTEC Routing & Dispatch (or ORTEC for SAP where SAP-embedded is the right comparison). Ortec also sells load building, workforce scheduling and inventory routing as separate products; those aren’t in scope for this comparison and stay in Ortec if you use them today.
| eLogii | Ortec | |
|---|---|---|
| Optimizer engines and modes | Two engines (Default and Advanced), six configurable modes: three assignment plus three load-balancing, all callable via REST | Native optimizer across ORTEC Routing & Dispatch and ORTEC for SAP |
| Recurring service patterns | Task and route template groups as dedicated entities: weekly, monthly, quarterly, bespoke cadences modeled at the data layer | Supported; recurring patterns are typically modeled through implementation patterns rather than as a first-class API entity |
| Multi-day, multi-depot routing | Plan a single day or an entire month in one run; multi-depot, multi-day, overnight stops | Native, long history in multi-depot distribution planning |
| Mid-execution re-optimization | Operator-visible rules; re-optimize on the fly while protecting locked SLAs and customer-confirmed slots | Re-planning within dispatch scope |
| SAP-embedded routing UI | Integrates with SAP via REST API; not embedded in the SAP UI | Available via ORTEC for SAP |
| eLogii | Ortec | |
|---|---|---|
| Native driver mobile app | Native iOS and Android: navigation, configurable POD, photos, signatures, conditional outcomes, custom forms, offline-capable | Driver-facing components exist; depth typically depends on the bundle and the implementation partner |
| Configurable POD per task type | Configured by the operator in the UI: photos, signatures, conditional steps, custom fields, custom forms | Supported through configuration / customization, typically scoped during implementation |
| Branded end-customer tracking | Multi-brand: each brand has its own logo, colors, layout; embedded NPS, access codes, safety briefings, treatment notes | Customer notifications and ETA visibility; multi-brand and embedded-content depth varies |
| Customer self-service rescheduling | Route-aware slot selection; ~70% of reschedule requests handled without coordinator involvement | Not a core component of the Ortec routing surface |
| Slot booking that fits the optimized plan | Returns only delivery slots that fit the current optimized plan; ~35% fewer failed visits | Not a core component of the Ortec routing surface |
| eLogii | Ortec | |
|---|---|---|
| REST API surface | 70+ endpoints across Tasks, Routes, Drivers, Vehicles, Depots, Zones, Forms, Schedules, Optimization | Web service APIs for the standalone SaaS; SAP-certified embedded integration for the SAP line; shape varies by product |
| Bulk operations | createOrUpdateMany endpoints handle hundreds per call | Bulk planning supported within SAP-embedded and standalone deployments |
| Optimizer callable via API | Run, re-optimize, lock routes, manually reorder; six modes via REST | Optimization typically invoked from SAP workflows or standalone UI; web-API exposure varies by product |
| Live driver GPS webhook | Seven event types including Driver/Task Tracking Update with live GPS stream | Telemetry available via integrations; live GPS webhook is not the primary integration path |
| Sandbox environment | Full API parity at api-sandbox.elogii.com | Sandbox / dev environments available; shape varies by deployment model |
| Typical time to live | 3 to 5 weeks including integrations to FSM, ERP, CRM and telematics | Typically measured in quarters; consulting-led implementations |
| Pricing model | Published platform fee, banded by field staff, drivers, jobs per day and modules from $3,000/mo | Enterprise contact-sales; scoped per product line with services on top; not publicly listed |
Sources: eLogii API documentation, ORTEC product pages for ORTEC Routing & Dispatch and ORTEC for SAP. Verified June 2026.
Both platforms handle enterprise route planning. The differences live in how the optimizer is exposed, how recurring patterns are modeled, and how re-optimization behaves on a live operation.
Two engines (Default for high-throughput single-day planning, Advanced for multi-depot, multi-day, constraint-heavy work) and six configurable modes: three assignment modes plus three load-balancing modes. Skills, vehicle capacity, time windows, depot start and end, SLA windows, customer-confirmed slots, HOS-style shift rules and business-specific constraints all flow into the same optimization run. Every mode is callable via REST.
Recurring patterns are first-class. Task and route templates carry the cadence (weekly, monthly, quarterly, bespoke) at the data layer, so 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.
ORTEC Routing & Dispatch is the standalone SaaS; ORTEC for SAP is the SAP-embedded line, certified to run inside the SAP UI; industry bundles cover foodservice, retail and CPG, often pairing routing with load building. The optimizer has a long history in distribution planning and remains a known choice when route planning sits inside an SAP-led estate.
eLogii exposes rule-based re-optimization to the operator: reroute a no-access visit to the nearest technician with the right 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. Ortec re-plans within its dispatch scope; depth of operator-facing rules varies by deployment.
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
Both platforms run at enterprise scale. The choice usually turns on how each one is bought, rolled out and operated.
eLogii rollouts are typically 3 to 5 weeks from kickoff to phased go-live, including integrations to your FSM, ERP (including SAP), CRM and telematics. Most teams start with one business unit, depot or region, validate on real historical data, then expand. Ortec implementations are typically measured in quarters and are consulting-led, with the heavier scope coming from where the optimizer sits in the wider SAP or industry-bundle setup.
On eLogii, the dispatcher or operations lead changes skills, capacities, recurring patterns, SLAs, custom forms, tracking-page brands and optimizer objectives from the UI. New configuration ships the same day it’s decided. On Ortec, deeper configuration changes typically route through an in-house solution engineer with Ortec experience or through the implementing partner. That shapes ongoing cost and how quickly operations can respond to a new requirement: a new pest licence type, a new SLA tier, a new depot.
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 trialled five before choosing eLogii, citing flexibility and how quickly drivers could be onboarded. Both evaluations turned on the operating-model questions above: time to value, day-to-day operability and the field-execution surface, not on the breadth of the underlying optimization stack.
Where the day-to-day workload lands. eLogii ships the customer experience surface and the dispatch desk as native components configured from the same UI as the optimizer.
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 (SAP, NetSuite, MS Dynamics 365 BC, Sage, Acumatica), telematics for the vehicles (Samsara, Geotab, TomTom, Motive), and a routing layer.
eLogii is built for that shape. It plugs into your existing FSM and ERP as the routing and dispatch layer, leaving field execution paperwork in the FSM where your 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, streams GPS to the customer-facing tracking page, and pushes completion back into the FSM / ERP for invoicing.
api-sandbox.elogii.com so integration work can run in parallel with the existing FSM / ERP rollout.POST /tasks/createOrUpdateMany handles hundreds of tasks per call, built for high-volume ingest from any FSM or ERP.Custom simulation
A 30-minute working session with our solutions team. We take a sample of your real jobs, 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.