Run every route, store door, and merchandiser visit on one platform
Drivers, merchandisers, and planners work from one system, and every case a store refuses or returns reaches SAP the same day. Locus builds the SAP connection on your IT team’s schedule.
60 minutes with your DSD team.
TRUSTED BY
360+ Enterprises
to run complex transportation networks
Rated 4.5★ on G2 Read verified customer reviews Recognized by Gartner for 7 consecutive years
Backed by Ingka Group. Built for the long run.
Less spare stock in the branch means every change has to reach SAP right away
Mondelēz’s US DSD network and modernization timeline, per the Q1 2026 earnings call and the 2026 proxy statement.
Mondelēz is automating its DCs to cut the stock and cost in each branch. Each branch plans its next truck from the stock count in SAP, and every case a store refuses or returns changes that count. With little spare stock in each branch, a count that SAP updates late turns into wrong loads and empty shelves.
Three things to get right at the branch as the DCs automate
Record every refused or returned case at the store
Each refused or returned case changes the branch’s count and the store’s bill. Record it at the store with a photo, a signature, and the location, and a dispute weeks later takes one search by store and date.
Plan each day’s routes from that day’s orders
Each store gets the truck on the same days every week, but it orders a different amount each time. Keep the delivery days and build each day’s route from that day’s orders: which stores go on which truck, and in what order.
Give merchandisers a schedule of their own
When merchandisers start on the truck’s schedule, a truck an hour late is an hour of paid time spent waiting in the back room. Plan their visits from each store’s own rules: how often, which hours, and how long the work takes.
How Locus runs all three across your 55 branches
Every delivery in SAP the same day
Drivers record refused and returned cases in the Locus driver app, with a photo, signature, or PIN. Locus updates SAP when the truck is back, and the next truck is planned on the right count.
Stop 1 · Store A
Same delivery days, a new route every night
Each store keeps its delivery days. Locus rebuilds the route from each day’s orders and re-plans it when a truck runs late.
Truck 12 · Tuesday
Merchandisers get their own weekly plan
Locus plans merchandiser visits from each store’s visit frequency, hours, and task time, on a schedule separate from the delivery routes.
Merchandiser A
Planned from visit frequency, store hours, and task time
In production
60%
A leading Vietnamese beverage company captures proof of delivery and payment at every stop, with end-of-day reconciliation time down 60%.
Read the case study →
3 hrs → 5 min
A global FMCG leader plans delivery to 1.8M+ retail outlets in 10 countries, with plan run time down from 3 hours to 5 minutes.
Read the case study →
16.7%
Makro (CP Axtra) runs dispatch for 160+ stores on Locus, with logistics cost down 16.7%.
Read the case study →SAP stays your system of record. Locus connects to it on your IT team’s schedule.
One branch, planned on exported data
Locus re-plans one branch’s week from an export of orders and stores, with a merchandiser plan beside it. Nothing touches SAP.
One connection to SAP
Orders and store data come in from SAP, and every refused or returned case updates it. Locus builds it, or your SI does.
Branch by branch
Each branch compares Locus with its current route planning, and switches when Locus does better on its own routes.
“Locus TMS covered both the ends, the settlement and the dispatch planning. It integrated cleanly into SAP, a business critical system for us.”
What keeps running
Your telematics, merchandiser tracking, and freight planning stay as they are. Locus runs alongside them and reads the live signals they already produce.
Security
Your data sits in your own tenant, with SAML or ADFS single sign-on and an audit trail on every user action.
99.97% uptimeOne branch first, scored on idle time and fill rate
Your team picks the branch and the scorecard. The next branch waits until the numbers hold.
Recommend
Locus proposes each day’s routes, truck loads, and merchandiser visits. Your branch team approves them.
Shadow
Locus plans the same orders beside today’s routes, and your team compares miles, stops, and on-time arrivals.
Decide
Locus runs the branch’s routes and merchandiser plans inside your rules, and sends your team only the exceptions.
The scorecard also tracks cost per stop, miles per route, the time it takes to reconcile each truck once it’s back at the branch, and merchandiser hours lost to late trucks.