STACK PATTERN
NetSuite is the ERP and system of record: items, customers, sales orders, inventory, financial close. eLogii is the routing and field execution layer that turns NetSuite sales orders into optimized routes, live ETAs, driver workflows and proof of delivery, then writes the completion data back. Two systems, two jobs. The integration runs over SuiteTalk REST on the NetSuite side and eLogii’s REST API on the other, typically delivered in 3 to 5 weeks alongside the eLogii rollout.
TRUSTED BY HUNDREDS OF HAPPY CUSTOMERS
NetSuite and eLogii sit in different layers of the same stack. NetSuite is the ERP: items, customers, sales orders, inventory, financial close, multi-subsidiary reporting. eLogii is the routing and field execution layer: the route plan, the driver app, the live ETAs, the proof of delivery, the customer-facing tracking. Both products expose mature REST APIs, and the integration between them is a normal piece of NetSuite-side work.
In the combined pattern, NetSuite stays the system of record for items, customers, orders, inventory and financial close. Sales orders flow from NetSuite into eLogii as routable tasks; eLogii optimizes against vehicles, depots, time windows, capacities, skills and SLAs; the driver app captures POD, photos, signatures and any custom forms; completion writes back to NetSuite so AR can invoice and inventory can clear. The integration runs over both products’ REST APIs.
Three tables: where ERP and business data live (NetSuite leads), where routing and field execution live (eLogii leads), and what the integration architecture looks like on both sides.
| NetSuite | eLogii | |
|---|---|---|
| Item master / SKU catalog | Core. Item record, BOMs, lots, serials, pricing | Not in scope. Looks up items by external_id from the integration |
| Customer master, AR / AP | Core. Customer record, billing address, payment terms, AR/AP | Not in scope. Customer delivery info flows in via integration |
| Sales orders, invoices, GL | Core. Order capture, fulfilment, invoicing, multi-subsidiary close | Not in scope |
| Inventory levels, demand planning | Core. Advanced Inventory module covers forecasting and replenishment | Not in scope |
| Item weight, cube, handling for capacity math | Item record fields | Reads via integration to feed optimizer constraints |
| Customer delivery address, time windows | Customer + sales order record fields | Reads via integration to feed optimizer constraints |
| Multi-subsidiary, multi-currency, financial close | Core. OneWorld | Not in scope |
| eLogii | NetSuite native | |
|---|---|---|
| Multi-stop route optimization with constraints | Two engines, six configurable modes; vehicles, depots, capacities, time windows, skills, SLAs | Pick, Pack and Ship sequences stops within a wave; not a constraint-aware route optimizer |
| Multi-day, long-haul, multi-depot routing | Plan a single day or an entire month in one run; multi-depot, multi-day, overnight stops | Not in scope |
| Driver mobile app for on-road execution | Native iOS and Android: navigation, POD, photos, signatures, conditional outcomes, custom forms | Mobile Push and SuitePeople Mobile cover warehouse and HR; no on-road driver workflow |
| Live GPS, route ETAs, branded customer tracking | Live driver GPS stream, route ETA updates, multi-brand tracking pages with embedded content | Not in scope. Customer Center shows shipment status, not live ETAs |
| Slot booking co-pilot – route-aware availability | Returns only delivery slots that fit the current optimized plan; ~35% fewer failed visits | Not in scope |
| Customer self-reschedule on route-aware slots | ~70% of reschedule requests handled without coordinator involvement | Not in scope |
| Configurable POD forms and conditional outcomes | Configurable POD with photos, signatures, conditional steps, custom fields, custom forms | Not in scope |
| Parcel carrier rate-shop and label-print | Not in scope. Own-fleet routing only | Shipping integration covers UPS, FedEx, DHL, USPS rate-shop and labels |
| NetSuite | eLogii | |
|---|---|---|
| API style | SuiteTalk REST + SOAP, RESTlets, SuiteScript for server-side logic | REST, JSON over SSL, ApiKey auth, predictable resource URLs |
| Authentication | OAuth 2.0, Token-Based Authentication (TBA), or M2M | ApiKey header, generated in Dashboard > Configuration > API Keys |
| Sandbox environment | NetSuite Sandbox + Release Preview accounts for development and testing | Full API parity at api-sandbox.elogii.com |
| Bulk operations | Async record queries, SuiteScript Map/Reduce for high-volume batches | createOrUpdateMany endpoints handle hundreds of tasks per call |
| Webhooks / events | SuiteScript user-event scripts + Webhooks Plug-in for outbound events | Seven event types including Driver/Task Tracking Update with live GPS stream |
| Optimization callable via API | No route optimization engine in core NetSuite | All six modes callable via REST; lock specific routes, manually reorder stops |
Sources: Oracle NetSuite Help Center, NetSuite SuiteTalk REST API reference, eLogii API documentation. Verified June 2026.
End to end, how a delivery order moves from NetSuite to a completed POD and back into NetSuite for invoicing and inventory. The exact wiring depends on your tenant and the integration platform your team uses, but the shape is the same in every deployment.
POST /tasks/createOrUpdateMany, with the NetSuite internal ID held as external_id so every eLogii object can be traced back to its NetSuite source record.Variations on the same pattern: multi-depot picking where NetSuite Locations drive depot selection; multi-day jobs for field service where the eLogii task represents the visit and the NetSuite project represents the engagement; customer cancellations from NetSuite triggering eLogii re-optimization. None of these require special connector logic; they are normal mappings across two REST APIs.
NetSuite is a deep ERP and ships modules that touch the delivery problem, but none of them are route optimization. Drawing the line clearly matters when you are scoping eLogii alongside NetSuite:
This is not a criticism. NetSuite is an ERP and was never built to be a routing layer. The point is to be precise about where its features stop, so the integration with eLogii has a clean seam.
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 NetSuite + eLogii deployment. The right one depends on what your NetSuite team already has in place 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 customers running NetSuite alongside eLogii. Same underlying pattern, different surface.
Wholesale food and drink, building materials, bathroom and kitchen, pharma, grocery, parcel. NetSuite owns items, lots, batches, expiry, pricing, customer master, delivery addresses, sales orders, inventory and financial close. eLogii owns the route plan across the fleet, vehicle and capacity and time-window optimization, the driver mobile app for POD and pallet-level signing, the live customer tracking, and the slot booking on the storefront. Typical reach is own-fleet distribution operations with 50+ in the field, multi-depot picking and routing, and recurring weekly or monthly delivery patterns. Outcome shape from current customers: Brymec lifted productivity 30% and routing efficiency 20%; ATS Building Products improved deliveries per route by ~98%; Porcelanosa runs 95%+ ETA accuracy on daily distribution.
Less common pattern, because most field service operations run a dedicated FSM in front of NetSuite for work-order management. Where NetSuite is the financial backbone for field service, eLogii sits as the routing depth layer, often alongside an FSM in front (Simpro, Joblogic, ServiceTitan, Salesforce Field Service, MS Dynamics 365 Field Service). NetSuite handles service contracts, billable work, invoicing and parts inventory; the FSM (if present) handles work-order workflow; eLogii handles multi-day jobs, multi-technician crews, recurring service patterns and the driver mobile app. Bristow & Sutor runs 200+ enforcement agents and 200,000+ case visits routed annually on eLogii; Vergo runs 400 technicians.
eLogii runs alongside NetSuite; nothing changes on the NetSuite 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 NetSuite + eLogii rollouts (including the integration) complete in 3 to 5 weeks. NetSuite pricing is its own thing and is not affected by adding eLogii.
30-minute custom simulation with your real NetSuite delivery orders, depots and vehicles. Projected savings in drive time, fuel and planner hours 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 delivery or field execution problem has outgrown what NetSuite’s built-in workflow covers, and who want to keep NetSuite for items, customers, orders, inventory and financial close while adding eLogii for routing and execution on top.
Item master, customer addresses, sales orders, depots (NetSuite Locations) and vehicles inventoried. SuiteTalk REST queries return the open delivery book; mapping to eLogii task fields documented end to end. Custom NetSuite fields surfaced as eLogii custom fields. Sandbox connectivity proved out on both sides before any production data moves.
Weeks 1–2Custom data simulation against your historical NetSuite delivery book so you can validate the modeling and project savings before go-live. Side by side: what your planners produce today vs. what eLogii produces with the same orders. Approve the optimizer settings and the write-back fields.
Weeks 2–3Start with one business unit, depot or region. Drivers onboarded onto the eLogii app. Webhook stream wired to your integration layer. POD and completion data writing back to NetSuite for AR and inventory. 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-country rollouts deploy in weeks, not quarters.
Each of these takes one place where eLogii adds depth alongside NetSuite, walks what NetSuite handles today, what the capability actually needs, where users land without it, how eLogii covers it, and how it writes back to NetSuite via SuiteTalk REST.
NetSuite has no native constraint-aware route optimizer. eLogii is the routing layer on top: two engines, six modes, REST-callable, plugs into SuiteTalk.
NetSuite Mobile Push is warehouse-side. eLogii ships a native iOS / Android driver app with offline POD, photos, signatures, conditional steps and custom forms.
Item Fulfillment can hold notes and attachments. eLogii captures POD on the driver app: photos, e-signatures, conditional outcomes, custom forms, with REST write-back to NetSuite.
Customer Center shows shipment status. eLogii streams live driver GPS, real-time route ETAs and branded multi-brand customer tracking pages on top.
NetSuite’s date picker doesn’t check whether a date is achievable. eLogii’s slot booking co-pilot returns only slots that fit the optimized plan. ~35% fewer failed visits.
Through both products’ REST APIs. NetSuite exposes SuiteTalk REST plus SuiteScript, RESTlets and a Webhooks Plug-in for outbound events; 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: open delivery orders flow from NetSuite to eLogii (pulled on a schedule or pushed via a SuiteScript user-event on order approval); eLogii runs the optimization and dispatches the driver app; completion data writes back to NetSuite for AR invoicing and inventory clearance. Most deployments are delivered in 3 to 5 weeks alongside the eLogii rollout.
No. NetSuite WMS and Pick, Pack and Ship are warehouse-floor workflow: wave management, picking strategies, packing stations, shipment confirmation. They sit upstream of routing. eLogii is on the road: the route the truck takes once the load is built, the order each stop runs in, the driver app, the ETAs and the customer-facing tracking. If you already run NetSuite WMS, eLogii starts where the WMS hands off.
No. NetSuite’s shipping integration is rate-shop and label-print for parcel carriers (UPS, FedEx, DHL, USPS). It is for parcel handoff. eLogii is for own-fleet routing: your trucks, your drivers, your stops. If your delivery is all parcel through carriers, eLogii is not the right tool. If you run an own fleet for distribution or field service, eLogii is the layer NetSuite was never built to be.
Typically: open sales orders or delivery orders, the customer’s delivery address and geo, line items with weight and cube from the item record, any delivery time window, special-handling flags, the assigned depot or NetSuite Location, and any custom fields your operation depends on (access notes, gate codes, key handling). All of that is exposed via SuiteTalk REST today. The integration job either pulls on a schedule or pushes via a SuiteScript user-event on order approval.
Typically: delivery confirmation (delivered, refused, partial, failed and the reason), proof-of-delivery references (photo IDs, signature image references), timestamps (arrival, completion), driver-collected cash or payments where applicable, any custom form data captured in the driver app, and the final delivery status that triggers AR invoicing and inventory clearance. The write-back uses SuiteTalk REST or RESTlet endpoints from your integration layer.
Yes. eLogii has REST + JSON APIs, a sandbox at api-sandbox.elogii.com and publicly documented endpoints. Whichever iPaaS your team already uses can broker eLogii alongside NetSuite.
Typically 3 to 5 weeks from kickoff to a phased go-live, including the NetSuite integration. Most teams start with one business unit, depot or region, validate against historical NetSuite delivery data, then expand. Heatleys evaluated 20 platforms and went live fast on eLogii, citing how quickly drivers could be onboarded.
It does not. NetSuite 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.
Yes. eLogii runs operations at scale: J-Club (9,000+ stores), NHS, Belfast City Council, Vergo, Bristow & Sutor, Porcelanosa, Caldic and Berkmann Wine Cellars. ISO 27001 and SOC 2 Type 2 certified.
Last updated: June 2026. Information about NetSuite is drawn from Oracle’s public documentation: the NetSuite Help Center, SuiteTalk REST API reference, and SuiteScript and SuiteCloud platform docs. 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 NetSuite delivery orders, 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.