STACK PATTERN
ServiceTrade is the FSM for commercial service contractors: work orders, jobs and appointments, inspection workflows, deficiencies and quoting, recurring service contracts, the tech mobile app, the customer portal and the billing handoff. eLogii is the routing and dispatch layer on top: takes today’s ServiceTrade appointments and turns them into optimized multi-stop routes against vehicle capacity, time windows, skills and SLAs, with multi-day and multi-region planning, live tracking and configurable POD where you need it. Two systems, two jobs. The integration runs over both products’ REST APIs, typically delivered in 3 to 5 weeks alongside the eLogii rollout.
TRUSTED BY HUNDREDS OF HAPPY CUSTOMERS
ServiceTrade and eLogii sit at different layers of the same stack. ServiceTrade is the FSM and stays the system of record for jobs, appointments, inspections, deficiencies, quotes, recurring service contracts, the tech mobile app, the customer portal and billing handoff. eLogii is the routing and dispatch layer: the multi-stop optimizer, the route plan across the fleet, live tracking and, where the operation needs it, an additional driver mobile app surface. Both products expose REST APIs and webhook events, and the integration between them is a normal API integration.
In the combined pattern, ServiceTrade stays the system of record for the customer, the asset, the work order and the service contract. Open appointments flow into eLogii as routable tasks; eLogii optimizes against vehicles, depots, time windows, capacities, skills and SLAs; the tech navigates to the next stop in the eLogii app and switches to the ServiceTrade app on site to capture inspection results, deficiencies and the customer signature; completion timestamps and any route-side metadata write back to the ServiceTrade appointment. The work-order body lives in ServiceTrade where it was captured.
Three tables: where the work order and service contract live (ServiceTrade leads), where routing and dispatch live (eLogii leads), and what the integration architecture looks like on both sides.
| ServiceTrade | eLogii | |
|---|---|---|
| Customer, location, contact | Core. Customer record, multiple service locations per customer | Not in scope. References the ServiceTrade location ID via external_id |
| Jobs and appointments | Core. Job groups appointments; appointment carries window, tech and status | Reads appointments via the API and creates corresponding eLogii tasks |
| Assets and asset history at the location | Core. Assets, service history, inspection results, deficiencies linked to asset | Not in scope |
| Inspection workflows and forms | Core. Inspection templates per service line: fire alarm, sprinkler, mechanical PM | Not in scope. The inspection itself stays in the ServiceTrade tech app |
| Deficiencies and quote-from-deficiency | Core. Deficiency captured on inspection, quoted to the customer from the same record | Not in scope |
| Recurring service contracts | Core. Service line cadences, generates next-due appointments | Recurring routes / task templates pick up the appointments and route them |
| Customer portal and service reports | Core. End-customer logs in to see service history and reports | Not in scope |
| Invoicing handoff to accounting | Core. Invoice from completed job, push to QuickBooks / Sage Intacct / etc. | Not in scope |
| eLogii | ServiceTrade native | |
|---|---|---|
| Multi-stop route optimization with constraints | Two engines, six configurable modes; vehicles, depots, capacities, time windows, skills, SLAs, asset access requirements | Scheduling board and dispatch grid; not a constraint-aware multi-stop route optimizer |
| Multi-day, multi-region routing in one plan | Plan a single day or an entire month in one run; multi-depot, multi-day, overnight stops | Day-by-day scheduling, not whole-week route optimization |
| Recurring patterns as dedicated entities | Task and route templates: weekly, monthly, quarterly, bespoke cadences modeled at the data layer for the routing side | Recurring service contracts generate appointments; routing optimization across them is the gap eLogii fills |
| Live driver GPS, branded customer tracking | Live driver GPS stream, route ETA updates, branded multi-brand tracking pages with embedded content | ServiceTrade ships customer-facing tracking depending on tier; embedded content and multi-brand depth vary |
| Driver / technician on-road app surface | Native iOS and Android: navigation, configurable POD, photos, signatures, conditional outcomes, custom forms; offline-capable | ServiceTrade tech mobile app for the work-order body (inspection, deficiencies, customer signature) |
| Slot booking co-pilot – route-aware availability | Returns only slots that fit the current optimized plan; ~35% fewer failed visits | Not in scope |
| ServiceTrade | eLogii | |
|---|---|---|
| API style | ServiceTrade API: REST, JSON, OAuth 2.0 | REST, JSON over SSL, ApiKey auth, predictable resource URLs |
| Resources covered | Jobs, appointments, locations, assets, deficiencies, quotes, attachments, customers, invoices | Tasks, Routes, Drivers, Vehicles, Depots, Zones, Forms, Schedules, Optimization |
| Webhooks / outbound events | Event subscriptions on job and appointment lifecycle, deficiency and quote changes | Seven event types including Driver/Task Tracking Update with live GPS stream |
| Bulk operations | Per-resource calls; batched via the integration layer | createOrUpdateMany endpoints handle hundreds of tasks per call |
| Sandbox / test environment | Sandbox access via account setup with ServiceTrade | Full API parity at api-sandbox.elogii.com |
| Optimization callable via API | No route optimization engine in ServiceTrade | All six modes callable via REST; lock specific routes, manually reorder stops |
Sources: ServiceTrade public product and API documentation (api.servicetrade.com), eLogii API documentation. Verified June 2026.
End to end, how a ServiceTrade appointment gets routed, dispatched, completed and reconciled back to the job record. The exact wiring depends on your tenant and the iPaaS your team uses, but the shape is the same in every deployment.
POST /tasks/createOrUpdateMany, with the ServiceTrade job and appointment IDs held as external_id so every eLogii task can be traced back to the source records (and vice versa). Required skills, time windows, asset access constraints map to eLogii task fields.Variations on the same pattern: multi-day inspection projects modeled as one ServiceTrade job with multiple appointments routed across days in eLogii; emergency callouts triggering eLogii re-optimization while protecting customer-confirmed inspection windows; SLA-aware dispatch where the service contract’s response-time clause flows into eLogii as a hard constraint. None require special connector logic; they are normal mappings across two REST APIs.
ServiceTrade is a deep FSM for commercial service contractors. Several parts of it touch the routing problem at the edge, but it isn’t a constraint-aware route optimizer. Drawing the line clearly matters when scoping eLogii alongside ServiceTrade:
ServiceTrade was built to be the FSM for commercial service contractors; the point of mapping the seam is so the integration with eLogii is clean. ServiceTrade keeps the work order, the inspection workflow, the deficiency-to-quote flow and the service contract; eLogii owns the route plan, the multi-day scheduling and the live tracking.
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 ServiceTrade + eLogii deployment. The right one depends on what your ServiceTrade tenant already looks like 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 commercial service contractors running ServiceTrade alongside eLogii.
Fire and life safety, mechanical / HVAC, electrical, sprinkler / suppression: large operations with 100+ technicians across multiple branches and recurring service contracts on thousands of customer assets. ServiceTrade owns the service contract, the inspection workflow and the deficiency-to-quote flow. eLogii owns the routing layer: planning a whole week or month of inspections across branches, balancing tech skills against asset access requirements, surfacing SLA-aware re-optimization when emergency callouts land. Bristow & Sutor runs 200+ enforcement agents and 200,000+ case visits routed annually on eLogii; Vergo runs 400 technicians; the same routing depth applies to large ServiceTrade tenants.
The bulk of the appointment book is recurring service contracts firing on a cadence: quarterly fire alarm inspections, semi-annual mechanical PMs, monthly sprinkler tests. ServiceTrade generates the next-due appointments; eLogii’s recurring routes and task templates model the routing cadence and balance the load across techs and branches, week after week. Where the operation has a mix of inspection visits and reactive callouts, eLogii’s rule-based re-optimization protects the customer-confirmed inspection windows while reslotting the reactive work.
eLogii runs alongside ServiceTrade; nothing changes on the ServiceTrade 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 ServiceTrade + eLogii rollouts (including the integration) complete in 3 to 5 weeks. ServiceTrade pricing is its own thing and is not affected by adding eLogii.
30-minute custom simulation with a sample of recent ServiceTrade appointments, your branches, vehicles and tech skill matrix. Projected savings in drive time, planner hours and SLA breaches 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 dispatch and routing has outgrown what the ServiceTrade scheduling grid covers on its own, and who want to keep ServiceTrade as the FSM system of record while adding eLogii for the routing depth on top.
Service lines, tech skill matrix, branches as depots, recurring service contract cadences, asset access requirements. ServiceTrade API queries return the open appointment book; mapping to eLogii task fields documented end to end. ServiceTrade webhook subscriptions configured for the appointment lifecycle. Sandbox connectivity proven on both sides before any production data moves.
Weeks 1–2Custom data simulation against a recent sample of ServiceTrade appointments so you can validate the modeling and project savings before go-live. Side by side: how the work gets dispatched today vs. how eLogii would route it with the same constraints. Approve the optimizer settings, the trigger conditions and the write-back fields on the ServiceTrade appointment.
Weeks 2–3Start with one branch, region or service line. Techs onboarded onto the eLogii app alongside the existing ServiceTrade mobile app. ServiceTrade webhook live; eLogii webhook stream wired to your integration layer (or iPaaS) for the write-back. 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-region rollouts deploy in weeks, not quarters.
Through both products’ REST APIs. ServiceTrade exposes the ServiceTrade API (REST, JSON, OAuth 2.0) with endpoints for jobs, appointments, locations, assets, deficiencies, quotes, attachments and customer records, plus webhooks for event-driven integration. 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: a ServiceTrade webhook fires on appointment create / update, the integration calls eLogii to create or update a task, eLogii routes and dispatches; on completion, the eLogii webhook fires and the integration writes back to the ServiceTrade appointment. Most deployments are delivered in 3 to 5 weeks alongside the eLogii rollout.
No. ServiceTrade is the FSM and stays the system of record for work orders, jobs, appointments, inspections, deficiencies, quotes, recurring service contracts, customer records and invoicing handoff. eLogii is the routing and dispatch layer on top: multi-stop optimization across vehicle capacity, time windows, skills and SLAs; multi-day and multi-depot plans; live tracking; configurable POD. The two run alongside each other on the same operation.
Jobs (and the appointments inside them) in ServiceTrade carry the location, service line, requested window, asset references and tech requirements. The integration pulls open appointments via the ServiceTrade API (or subscribes to ServiceTrade webhooks) and creates corresponding eLogii tasks via POST /tasks/createOrUpdateMany, with the ServiceTrade job and appointment IDs held as external_id. eLogii then optimizes routes for the day, week or month against the wider plan.
Both, side by side, on the same phone. The eLogii driver app handles the route view, turn-by-turn navigation and any delivery-style POD or custom forms. The ServiceTrade mobile app stays the surface for the work order itself: inspection checklists, deficiencies, quoting on the fly, asset history, customer signature on the work order. Most operations use eLogii to get the tech to the right place at the right time and ServiceTrade to capture the service work.
Typically: appointment status (arrived, completed, partial, failed and the reason), arrival and completion timestamps, route-position metadata if needed, and any driver-collected payments or custom form data captured in the eLogii app. The write-back uses the ServiceTrade API against the matching appointment record. The work-order body (inspection results, deficiencies, attachments) remains in ServiceTrade where the tech captured it.
Recurring service contracts (the customer-facing agreement: quarterly fire alarm inspections, monthly sprinkler tests, semi-annual mechanical PMs) stay in ServiceTrade. eLogii’s recurring routes and task templates model the routing-side cadence: any frequency, any duration, modeled as dedicated entities. The two work together: ServiceTrade generates the next-due appointments off the service contract, eLogii routes them efficiently.
Typically 3 to 5 weeks from kickoff to a phased go-live, including the ServiceTrade integration. Most teams start with one branch, region or service line, validate against a sample of recent jobs, then expand. The integration is straightforward: ServiceTrade webhook or scheduled pull fires when an appointment is created or updated, eLogii creates a task and runs optimization, eLogii webhook fires on completion and the integration writes back to ServiceTrade.
ServiceTrade 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.
Commercial service contractors where ServiceTrade is already the FSM: fire and life safety, mechanical and HVAC, electrical, plumbing, sprinkler and suppression, security. The eLogii + ServiceTrade stack adds the most depth where the operation has 50+ technicians, multi-day or multi-region routing, recurring inspection cadences across thousands of assets, and SLA-driven service contracts.
Yes. eLogii runs operations at scale: J-Club (9,000+ stores), NHS, Belfast City Council, Vergo (400 technicians), 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.
Last updated: June 2026. Information about ServiceTrade is drawn from ServiceTrade’s public product pages and the ServiceTrade API documentation. 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 ServiceTrade appointments, your branches, vehicles, tech skills and SLA contracts, run them through the eLogii engine, and show you the projected delta against how you dispatch today. No slides, no generic benchmarks.