STACK PATTERN
SAP EWM is the warehouse management system: inbound, internal, outbound, yard and labor processes. eLogii is the routing and field execution layer that turns SAP EWM outbound deliveries 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 EWM OData services on the SAP EWM 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
SAP EWM and eLogii sit in different layers of the same stack. SAP EWM runs the warehouse floor: inbound, internal, outbound, yard and labor processes. 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 SAP-side work.
In the combined pattern, SAP EWM stays the system of record for warehouse processes. Outbound deliveries flow from EWM 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 SAP EWM so EWM can post Goods Issue and the upstream S/4HANA or SAP ECC system can invoice. The integration runs over both products’ REST APIs.
Three tables: where ERP and business data live (SAP EWM leads), where routing and field execution live (eLogii leads), and what the integration architecture looks like on both sides.
| SAP EWM | eLogii | |
|---|---|---|
| Inbound delivery and putaway | Core. Item record, BOMs, lots, serials, pricing | Not in scope. Looks up items by external_id from the integration |
| Picking, packing, staging | Core. Customer record, billing address, payment terms, AR/AP | Not in scope. Customer delivery info flows in via integration |
| Outbound deliveries, EWM shipping flows | Core. Order capture, fulfilment, invoicing, multi-subsidiary close | Not in scope |
| Warehouse stock and slotting | Core. EWM internal warehouse process covers slotting 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-warehouse, multi-plant, automation control | Core. multi-warehouse, multi-org and multi-plant | Not in scope |
| eLogii | SAP EWM native | |
|---|---|---|
| Multi-stop route optimization with constraints | Two engines, six configurable modes; vehicles, depots, capacities, time windows, skills, SLAs | EWM picking, packing and staging 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 | EWM RF and mobile UI and SAP Fiori companion 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. your storefront or B2B portal 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 |
| SAP EWM | eLogii | |
|---|---|---|
| API style | OData services and SAP's extension framework for server-side logic | REST, JSON over SSL, ApiKey auth, predictable resource URLs |
| Authentication | OAuth 2.0, OAuth 2.0 or X.509 client certificates, or M2M | ApiKey header, generated in Dashboard > Configuration > API Keys |
| Sandbox environment | SAP EWM development and quality systems accounts for development and testing | Full API parity at api-sandbox.elogii.com |
| Bulk operations | Async record queries, SAP background job for high-volume batches | createOrUpdateMany endpoints handle hundreds of tasks per call |
| Webhooks / events | SAP enhancement spot scripts + SAP eventing 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 SAP EWM | All six modes callable via REST; lock specific routes, manually reorder stops |
Sources: SAP Help Portal, SAP EWM OData services reference, eLogii API documentation. Verified June 2026.
End to end, how a delivery order moves from SAP EWM to a completed POD and back into SAP EWM 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 SAP EWM document number held as external_id so every eLogii object can be traced back to its SAP EWM source record.Variations on the same pattern: multi-depot picking where EWM warehouse numbers and storage bins drive depot selection; multi-day jobs for field service where the eLogii task represents the visit and the SAP EWM project represents the engagement; customer cancellations from SAP EWM triggering eLogii re-optimization. None of these require special connector logic; they are normal mappings across two REST APIs.
SAP EWM is a deep warehouse management system 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 SAP EWM:
This is not a criticism. SAP EWM is a WMS 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 SAP EWM + eLogii deployment. The right one depends on what your SAP EWM 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 SAP EWM alongside eLogii. Same underlying pattern, different surface.
Wholesale food and drink, building materials, bathroom and kitchen, pharma, grocery, parcel. SAP EWM 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 SAP EWM for work-order management. Where SAP EWM 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). SAP EWM 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 SAP EWM; nothing changes on the SAP EWM 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 SAP EWM + eLogii rollouts (including the integration) complete in 3 to 5 weeks. SAP EWM pricing is its own thing and is not affected by adding eLogii.
30-minute custom simulation with your real SAP EWM 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 SAP EWM’s built-in workflow covers, and who want to keep SAP EWM for items, customers, orders, inventory and financial close while adding eLogii for routing and execution on top.
Item master, customer addresses, sales orders, depots (EWM warehouse numbers and storage bins) and vehicles inventoried. EWM OData services queries return the open delivery book; mapping to eLogii task fields documented end to end. Custom SAP EWM 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 SAP EWM 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 SAP EWM 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 SAP EWM, walks what SAP EWM handles today, what the capability actually needs, where users land without it, how eLogii covers it, and how it writes back to SAP EWM via EWM OData services.
SAP EWM has no native constraint-aware route optimizer. eLogii is the routing layer on top: two engines, six modes, REST-callable, plugs into EWM API surface.
SAP EWM radio frequency (RF) and mobile app is warehouse-side. eLogii ships a native iOS / Android driver app with offline POD, photos, signatures, conditional steps and custom forms.
outbound delivery can hold notes and attachments. eLogii captures POD on the driver app: photos, e-signatures, conditional outcomes, custom forms, with REST write-back to SAP EWM.
your storefront or B2B portal shows shipment status. eLogii streams live driver GPS, real-time route ETAs and branded multi-brand customer tracking pages on top.
Through both products’ REST APIs. SAP EWM exposes EWM OData services plus SAP extension, OData entity sets and a SAP eventing 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 SAP EWM to eLogii (pulled on a schedule or pushed via a SAP enhancement spot on order approval); eLogii runs the optimization and dispatches the driver app; completion data writes back to SAP EWM for AR invoicing and inventory clearance. Most deployments are delivered in 3 to 5 weeks alongside the eLogii rollout.
No. SAP EWM picking, packing and shipping 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. eLogii starts where EWM hands off: the load is staged, the EWM shipping flow is closed, the truck pulls away from the dock.
No. EWM’s EWM shipping flow 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 SAP EWM 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 SAP EWM Location, and any custom fields your operation depends on (access notes, gate codes, key handling). All of that is exposed via EWM OData services today. The integration job either pulls on a schedule or pushes via a SAP enhancement spot 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 EWM OData services or OData entity set 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 SAP EWM.
Typically 3 to 5 weeks from kickoff to a phased go-live, including the SAP EWM integration. Most teams start with one business unit, depot or region, validate against historical SAP EWM delivery data, then expand. Heatleys evaluated 20 platforms and went live fast on eLogii, citing how quickly drivers could be onboarded.
It does not. SAP EWM 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 SAP EWM is drawn from SAP’s public documentation: SAP Help Portal, EWM OData services API reference, and SAP extension and SAP's integration 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 SAP EWM 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.