STACK PATTERN
SAP S/4HANA is the ERP and system of record: material master, business partners, sales orders, inventory, financial close. eLogii is the last-mile routing and field execution layer that turns S/4HANA outbound deliveries into optimized own-fleet routes, live ETAs, driver workflows and proof of delivery, then writes completion data back. Two systems, two jobs. Where SAP TM is in play, TM keeps the freight and long-haul planning; eLogii handles the own-fleet last-mile execution. The integration runs over S/4HANA OData APIs (BAPIs and IDocs on on-prem tenants) and eLogii’s REST API, typically delivered in 3 to 5 weeks alongside the eLogii rollout.
TRUSTED BY HUNDREDS OF HAPPY CUSTOMERS
SAP S/4HANA and eLogii sit in different layers of the same stack. S/4HANA is the ERP: material master, business partners, sales orders, outbound deliveries, inventory, financial close, multi-company consolidation. eLogii is the last-mile routing and field execution layer: the own-fleet route plan, the driver app, the live ETAs, the proof of delivery, the customer-facing tracking. Where SAP TM is licensed, TM keeps freight and long-haul transportation planning; eLogii covers the own-fleet last-mile workflow TM was not built to be. Both products expose mature APIs, and the integration between them is a normal piece of SAP-side work.
In the combined pattern, S/4HANA stays the system of record for material master, business partners, sales orders, outbound deliveries, inventory and financial close. Outbound deliveries flow from S/4HANA 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 S/4HANA so SD can post goods issue and trigger billing. The integration runs over S/4HANA OData APIs (BAPIs and IDocs on on-prem tenants) and eLogii’s REST API.
Three tables: where ERP and business data live (S/4HANA leads), where last-mile own-fleet routing and field execution live (eLogii leads), and what the integration architecture looks like on both sides.
| SAP S/4HANA | eLogii | |
|---|---|---|
| Material master / SKU catalog | Core. Material record, BOMs, batches, serials, pricing conditions | Not in scope. Looks up materials by external_id from the integration |
| Business Partner master, AR / AP | Core. BP record (customer / vendor roles), billing address, payment terms, AR/AP | Not in scope. Delivery info flows in via integration |
| Sales orders, outbound deliveries, GL | Core. SD order capture, outbound delivery, goods issue, billing, multi-company close | Not in scope |
| Inventory levels, demand planning | Core. MM-IM, MRP, IBP for advanced planning | Not in scope |
| Material weight, volume, handling for capacity math | Material master fields | Reads via integration to feed optimizer constraints |
| Customer delivery address, time windows | Business Partner + outbound delivery record fields | Reads via integration to feed optimizer constraints |
| Multi-company, multi-currency, financial close | Core. Group Reporting, multiple ledgers | Not in scope |
| eLogii | SAP native (S/4HANA + optional TM) | |
|---|---|---|
| Own-fleet last-mile multi-stop route optimization | Two engines, six configurable modes; vehicles, depots, capacities, time windows, skills, SLAs | SAP TM handles freight and long-haul planning at enterprise scale; not focused on own-fleet last-mile constraint optimization |
| Multi-day, long-haul, multi-depot routing | Plan a single day or an entire month in one run; multi-depot, multi-day, overnight stops | TM models long-haul freight legs; own-fleet daily route planning typically not in TM scope |
| Driver mobile app for on-road execution | Native iOS and Android: navigation, POD, photos, signatures, conditional outcomes, custom forms | SAP Fiori, SAP Mobile Start and SAP Asset Manager cover warehouse, asset and field-service workflows; no on-road last-mile driver app |
| Live GPS, route ETAs, branded customer tracking | Live driver GPS stream, route ETA updates, multi-brand tracking pages with embedded content | Not in scope. TM tracks shipment events, not live own-fleet driver GPS to end customers |
| Slot booking co-pilot – route-aware availability | Returns only delivery slots that fit the current optimized plan; ~35% fewer failed visits | aATP confirms inventory availability; route-aware slot calculation is separate |
| Customer self-reschedule on route-aware slots | ~70% of reschedule requests handled without coordinator involvement | Not in scope |
| Configurable POD forms and conditional outcomes on the device | Configurable POD with photos, signatures, conditional steps, custom fields, custom forms | POD function in SD records the result on the outbound delivery; capture surface is not a driver app |
| Goods issue posting and billing trigger | Not in scope. eLogii feeds the trigger; SAP posts | Core. PGI, billing, AR all in SD |
| SAP S/4HANA | eLogii | |
|---|---|---|
| API style | OData services (whitelisted on S/4HANA Cloud Public, broader on Private and on-prem) + BAPIs, IDocs, RFCs | REST, JSON over SSL, ApiKey auth, predictable resource URLs |
| Authentication | OAuth 2.0, SAML, mTLS, communication users / arrangements | ApiKey header, generated in Dashboard > Configuration > API Keys |
| Sandbox environment | SAP S/4HANA Cloud test tenant; sandbox client on on-prem; SAP API Business Hub for API exploration | Full API parity at api-sandbox.elogii.com |
| Bulk operations | OData $batch, IDoc inbound and outbound, ABAP background jobs for high-volume batches | createOrUpdateMany endpoints handle hundreds of tasks per call |
| Events / webhooks | SAP Event Mesh and Enterprise Event Enablement publish business events for outbound; BAdIs and workflow on the inbound side | Seven event types including Driver/Task Tracking Update with live GPS stream |
| Last-mile optimization callable via API | No own-fleet last-mile route optimization engine in core S/4HANA; SAP TM covers freight | All six modes callable via REST; lock specific routes, manually reorder stops |
Sources: SAP Help Portal for S/4HANA Cloud, SAP API Business Hub, SAP TM and SAP EWM documentation, eLogii API documentation. Verified June 2026.
End to end, how an outbound delivery moves from S/4HANA to a completed POD and back into S/4HANA for goods issue posting, billing and inventory clearance. The exact wiring depends on the tenant (Cloud Public vs Private vs on-prem) and the integration platform your team uses, but the shape is the same in every deployment.
POST /tasks/createOrUpdateMany, with the SAP delivery number held as external_id so every eLogii object can be traced back to its SAP source record.Variations on the same pattern: multi-plant picking where SAP plants and shipping points drive depot selection in eLogii; multi-day field-service jobs where the eLogii task represents the visit and an SAP service order represents the engagement; customer cancellations from S/4HANA triggering eLogii re-optimization. None of these require bespoke connector logic; they are normal mappings across two API surfaces.
S/4HANA is a deep ERP and ships modules that touch the delivery problem. Drawing the line clearly matters when you are scoping eLogii alongside S/4HANA:
This is not a criticism. SAP’s job is ERP, finance and enterprise-scale supply chain. 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 S/4HANA + eLogii deployment. The right one depends on what your SAP team already has in place and which side of the seam you want the orchestration logic to live on.
BAPI_OUTB_DELIVERY_CONFIRM_DEC). Typical time: 3 to 5 weeks alongside the rest of an eLogii rollout.api-sandbox.elogii.com and publicly documented endpoints.Two common shapes for customers running SAP S/4HANA alongside eLogii. Same underlying pattern, different surface.
Wholesale food and drink, building materials, bathroom and kitchen, pharma, grocery, parcel. S/4HANA owns material master (with batches, expiry, BOMs), business partners, sales orders, outbound deliveries, inventory and financial close. eLogii owns the own-fleet route plan, 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-plant 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.
Service-heavy operations on S/4HANA often run SAP Field Service Management (acquired from Coresystems) or a third-party FSM in front of the ERP for work-order management. Where S/4HANA 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). S/4HANA handles service contracts, billable work, billing 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 S/4HANA; nothing changes on the SAP 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 S/4HANA + eLogii rollouts (including the integration) complete in 3 to 5 weeks. SAP licensing is its own thing and is not affected by adding eLogii.
30-minute custom simulation with your real S/4HANA outbound deliveries, plants 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 last-mile own-fleet delivery or field execution problem has outgrown what S/4HANA’s built-in workflow covers, and who want to keep S/4HANA for material master, business partners, sales orders, inventory and financial close while adding eLogii for routing and execution on top.
Material master, business partner delivery addresses, outbound deliveries, depots (mapped from SAP plants and shipping points) and vehicles inventoried. OData queries (or BAPI / IDoc on on-prem) return the open delivery book; mapping to eLogii task fields documented end to end. Custom SAP 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 S/4HANA outbound 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, plant or region. Drivers onboarded onto the eLogii app. Webhook stream wired to your integration layer (CPI / iPaaS / custom). POD and completion data writing back to S/4HANA for goods issue posting and billing. 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 S/4HANA for own-fleet last-mile, walks what S/4HANA (and SAP TM where relevant) handles today, what the capability actually needs, where users land without it, how eLogii covers it, and how it writes back to S/4HANA via OData or BAPI.
SAP TM handles freight planning; core S/4HANA has no own-fleet last-mile optimizer. eLogii is the last-mile layer: two engines, six modes, REST-callable, plugs into OData.
SAP Fiori, Mobile Start and Asset Manager cover warehouse and field-service workflows. eLogii ships a native iOS / Android driver app for on-road last-mile execution.
SAP’s POD function in SD records the result on the outbound delivery. eLogii captures POD on the driver app: photos, e-signatures, conditional outcomes, custom forms, with write-back via OData / BAPI.
SAP TM tracks freight shipment events. eLogii streams live own-fleet driver GPS, real-time route ETAs and branded multi-brand customer-facing tracking pages on top.
SAP aATP confirms inventory availability, not route-aware delivery slots. eLogii’s slot booking co-pilot returns only slots that fit the optimized plan. ~35% fewer failed visits.
Through both products’ APIs. S/4HANA exposes OData services (whitelisted on S/4HANA Cloud Public, broader on Private and on-prem) plus BAPIs, IDocs and Remote Function Calls (RFCs). SAP Cloud Platform Integration (now SAP Integration Suite) sits in the middle for many tenants. 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 outbound deliveries flow from S/4HANA to eLogii (pulled on a schedule or pushed via an event published on outbound delivery creation); eLogii runs the optimization and dispatches the driver app; completion data writes back to S/4HANA via OData or BAPI for goods issue posting, billing and inventory clearance. Most deployments are delivered in 3 to 5 weeks alongside the eLogii rollout.
No. SAP EWM (Extended Warehouse Management) and SAP MM Inventory Management handle warehouse-floor workflow: putaway, wave picking, packing, goods issue, inventory postings. 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 EWM, eLogii starts at the goods issue handoff.
No. SAP Transportation Management is enterprise-scale freight and transportation planning: multi-modal (rail, ocean, road TL/LTL), freight cost allocation, carrier orchestration, customs and trade integration. It is heavyweight and designed for shippers and 3PLs at scale. eLogii is the own-fleet last-mile execution layer: constraint-aware multi-stop routing, driver mobile app, POD capture, live ETAs and branded customer-facing tracking. Many TM customers run eLogii alongside for the last-mile own-fleet workflow that TM was not built to be. Customers that do not license TM run eLogii on top of S/4HANA’s standard SD outbound delivery flow.
Typically: open outbound deliveries or sales orders ready to ship, business partner delivery address and geo, line items with weight, volume and pallet count from the material master, any delivery time window or SLA from the customer master, special-handling flags, the assigned plant / shipping point / storage location, and any custom fields the operation depends on (access notes, gate codes, hazmat). All exposed via OData services or BAPIs / IDocs depending on the tenant. The integration job either pulls on a schedule or pushes via a workflow event when the outbound delivery is created or released.
Typically: delivery confirmation (delivered, refused, partial, failed and the reason), proof-of-delivery references (photo IDs, signature image references), timestamps (arrival, completion) used to set POD status on the outbound delivery, any driver-collected cash or payments, custom form data captured in the driver app, and the final delivery status that triggers SAP goods issue posting (PGI), billing and AR. The write-back uses OData updates or BAPI calls (e.g. BAPI_OUTB_DELIVERY_CONFIRM_DEC) from the integration layer.
Yes. 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 S/4HANA.
Typically 3 to 5 weeks from kickoff to a phased go-live, including the S/4HANA integration. SAP integrations skew slightly longer than NetSuite or D365 BC because the OData / BAPI surface area is bigger and SAP tenants are typically more customized. Most teams start with one business unit, plant or region, validate against historical S/4HANA outbound delivery data, then expand.
It does not. SAP licensing 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 S/4HANA is drawn from SAP’s public documentation: the SAP Help Portal for S/4HANA Cloud, the SAP API Business Hub, and SAP TM, EWM and Integration Suite 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 S/4HANA outbound deliveries, plants, 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.