STACK PATTERN
project44 is the multi-carrier, multi-modal visibility platform for shipments moving across carriers: OTR ELD feeds, ocean AIS, rail, air, parcel. eLogii is the routing and field execution layer for the part of the operation you run on your own fleet: optimized routes, live ETAs, a driver mobile app and proof of delivery. The two solve different problems and coexist via the ERP / TMS / order system; eLogii does not write tasks, milestones or POD into project44.
TRUSTED BY HUNDREDS OF HAPPY CUSTOMERS
project44 and eLogii sit in different layers of the same stack. project44 is the visibility platform: multi-modal in-transit visibility across OTR, ocean, rail, air and parcel carriers. 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 project44-side work.
In the combined stack, project44 stays the visibility system for carrier shipments on its side. Your own-fleet delivery orders flow from your order system into eLogii; 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 the upstream order system for invoicing. The two products don’t exchange data directly; the order system in the middle is the seam.
Two tables: where visibility data lives on the project44 side, and where routing and field execution live on the eLogii side. Each side is a system of record for what it owns; they don’t integrate directly.
| project44 | eLogii | |
|---|---|---|
| Multi-carrier OTR tracking via ELD feeds | Core. Live status on truckload and LTL shipments | Not in scope. Own-fleet routing only |
| Ocean, rail and air tracking | Core. AIS feeds, rail and air-cargo status | Not in scope |
| Multi-modal milestones and predictive ETAs | Core. Milestone events across modes, predictive ETA | Not in scope |
| Yard and dock visibility, OS&D | Core. Yard moves, dock scheduling, OS&D exception management | Not in scope |
| Inbound carrier ETA into your depots | Predictive ETA on inbound carrier loads | Can optionally read inbound ETA from project44 to phase outbound own-fleet plans |
| Order book, item master, customer master | Not in scope. Lives in the upstream ERP / TMS | Not in scope. Lives in the upstream ERP / TMS |
| eLogii | project44 native | |
|---|---|---|
| Multi-stop route optimization with constraints | Two engines, six configurable modes; vehicles, depots, capacities, time windows, skills, SLAs | Not in scope. project44 is visibility, not a route optimizer |
| Multi-day, 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 | project44 is shipper-facing visibility; not a driver app for own-fleet stop execution |
| Live driver GPS, route ETAs, branded end-customer tracking | Live driver GPS stream, route ETA updates, multi-brand tracking pages with embedded content | project44 surfaces carrier ETA to the shipper; not a branded end-customer tracking page for own-fleet deliveries |
| 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 |
| project44 | eLogii | |
|---|---|---|
| API style | REST endpoints and webhooks for downstream consumers | REST, JSON over SSL, ApiKey auth, predictable resource URLs |
| Authentication | OAuth 2.0 (client credentials) for partner / customer apps | ApiKey header, generated in Dashboard > Configuration > API Keys |
| Sandbox environment | project44 sandbox tenants for development and testing | Full API parity at api-sandbox.elogii.com |
| Outbound events | Webhook subscriptions on shipment-status and milestone events | Seven event types including Driver/Task Tracking Update with live GPS stream |
| Bulk reads | Paginated reads of shipments, milestones and exceptions | createOrUpdateMany endpoints handle hundreds of tasks per call |
| Direct write from eLogii into project44 | Not used. eLogii does not write into project44 | Not used |
Sources: project44 developer documentation, eLogii API documentation. Verified June 2026.
End to end, how a delivery order moves from the order system, through eLogii, to a completed POD. project44 continues to capture multi-carrier visibility on its side of the stack. The two products don’t exchange data directly.
POST /tasks/createOrUpdateMany, with the upstream order ID held as external_id.The seam is the order system in the middle. eLogii and project44 each integrate with it on their own side; they don’t chain to each other.
project44 is a deep multi-carrier visibility platform on the carrier side of the stack. For the part of the operation you run on your own drivers and vehicles, several project44 surfaces touch the problem at the edge, but none of them are own-fleet routing or stop-by-stop execution.
project44 was built to be a multi-carrier visibility platform; the point of mapping the seam is so eLogii fits cleanly alongside it. The two solve different problems and the order system in the middle holds the integration together.
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
Two shapes cover almost every rollout where project44 and eLogii both sit in the stack. They don’t integrate with each other directly; each connects to the order system in the middle.
api-sandbox.elogii.com and publicly documented endpoints. The project44 side typically stays as it is.Large shippers and distributors running an own fleet for some of their volume and carrier shipments for the rest.
Wholesale food and drink, building materials, bathroom and kitchen, pharma, grocery. The order book lives in the ERP or order system. project44 covers in-transit visibility on the carrier shipments (inbound to depots, outbound to customers via 3PLs). eLogii covers the own-fleet last-mile: 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.
A useful but optional pattern: eLogii reads project44’s predictive ETA on inbound carrier shipments feeding a depot so the outbound own-fleet plan can phase against them. If the inbound load is running late, the outbound route plan adjusts. The read is from project44’s REST API on the eLogii side; nothing flows back the other way.
eLogii runs alongside project44; nothing changes on the project44 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 project44 + eLogii rollouts (including the integration) complete in 3 to 5 weeks. project44 pricing is its own thing and is not affected by adding eLogii.
30-minute custom simulation with your real 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 project44’s built-in workflow covers, and who want to keep project44 for items, customers, orders, inventory and financial close while adding eLogii for routing and execution on top.
Item master, customer addresses, sales orders, depots and vehicles inventoried in the order system. Order-system queries return the open delivery book; mapping to eLogii task fields documented end to end. Sandbox connectivity proven on the order-system side and on eLogii before any production data moves. The project44 side stays as it is.
Weeks 1–2Custom data simulation against your historical order 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 on the order system.
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 the upstream order system 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 capability eLogii covers for own-fleet operations alongside project44’s carrier visibility. eLogii’s side connects to the order system; the project44 side stays as it is.
project44 is multi-carrier visibility, not own-fleet routing. eLogii is the routing layer for own-fleet operations: two engines, six modes, REST-callable, connects to the order system in the middle.
project44’s shipper view shows carrier-shipment status. eLogii streams live driver GPS, real-time route ETAs and branded multi-brand end-customer tracking pages for own-fleet deliveries.
Not directly. project44 and eLogii sit on different sides of the same supply-chain stack: project44 for multi-carrier, multi-mode in-transit visibility; eLogii for own-fleet routing, dispatch and field execution. They coexist via the ERP / TMS / order system in the middle, which carries the order book and the customer master. eLogii reads open delivery orders from the order system, optimizes, dispatches the driver app and writes completion back to the order system. project44 continues to capture multi-carrier visibility on its side. eLogii does not write tasks, milestones or POD into project44. Typical eLogii rollout 3 to 5 weeks.
No. project44 is the multi-modal in-transit visibility platform for shipments moving across carriers, modes and yards. eLogii is the own-fleet routing and execution layer for the deliveries and field visits you run on your own drivers and vehicles. Different scopes; both have a place in a large operation that runs own-fleet last-mile alongside carrier shipments.
For customers with inbound carrier shipments feeding their own depots, project44’s predictive ETAs and exception events on inbound loads can be read by eLogii (via project44’s REST API) so the outbound own-fleet plan can react when an inbound shipment runs late. This is an optional read on the eLogii side; many deployments don’t need it. eLogii does not write back to project44.
No. The two systems coexist via the ERP / TMS / order system, not by writing into each other. eLogii’s completion data, POD references, timestamps and driver-collected payments write back to your upstream order system for invoicing and inventory. project44 continues to capture its multi-carrier visibility from the same carriers and yards.
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 the rest of the stack.
Typically 3 to 5 weeks from kickoff to a phased go-live for the eLogii rollout itself. Most teams start with one business unit, depot or region for own-fleet operations, validate against historical order data, then expand. Heatleys evaluated 20 platforms and went live fast on eLogii, citing how quickly drivers could be onboarded.
It does not. project44 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 project44 is drawn from project44’s public documentation, including the project44 documentation and the project44 API reference. 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 project44 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.