Overview
Pepper uses Route Tracking to bring delivery visibility directly into the operator experience. Route Tracking provides operators with clear and proactive insight into when their orders will arrive. Instead of relying on phone calls, texts, or manual updates, operators can simply open their Pepper app to see an accurate arrival window for each order.
The feature displays easy to understand delivery time windows and sends smart notifications when a truck leaves the warehouse, when an operator is the next stop, and when a delivery is running significantly behind schedule. By connecting directly to routing systems such as Samsara and Omnitracs, Pepper turns live routing data into simple delivery information operators can depend on.
Viewing delivery timing in Pepper
Route Tracking is fully integrated into the ordering experience, and users do not need a separate portal or login. Delivery visibility appears exactly where they already manage and review their orders.
On the Upcoming orders screen, users can see:
A list of orders that are on the way
An arrival window for each order
Automatically updated windows when the ETA changes significantly
On the Past orders screen, users can see:
A record of delivery times for their own reference
How delivery updates are communicated
Route Tracking also sends proactive notifications so operators do not need to keep refreshing the app. Only operators receive these messages, and this can be set up through the notifications tab.
Order is on its way
An approximate window sent when Pepper first receives a delivery estimate for an order, usually when the truck leaves the warehouse. This tells the operator to know when to expect it.
Order delayed or arrives earlier than expected
Sent when the estimated delivery time moves outside the previously communicated window. This usually happens due to traffic, route changes, or longer than usual unloads.
You are the next stop
Sent when the operator is the next scheduled stop on the route, along with approximate minutes to arrival. This is especially useful for busy kitchens and docks that need a short heads up to get ready.
Order has been delivered
Sent when Pepper detects that the delivery is completed at the operator location. This gives operators a clear confirmation that the order has arrived.
Operators can turn notifications off for their own account if they prefer not to receive them.
How the feature works with routing systems
Route Tracking is designed to work with the routing software that is already trusted by a distributor.
We commonly integrate with
Samsara
Omnitracs
Other 3rd party fleet management vendors
Here's how it works:
The current routing system plans the route and trucks.
Dispatchers create routes, assign vehicles and drivers, and define stop sequences in the routing software, just as they normally would.
As the truck moves, the routing system updates arrival estimates
Live GPS data, traffic conditions, and stop completion times feed into the routing platform’s ETA model. The system continually updates the expected arrival time for each stop.
Pepper reads those estimates and converts them into a clear delivery window.
Operators see predictable, easy to understand time windows in the Pepper app.
When the estimate changes significantly, Pepper updates the window and sends new notifications to operators.
Distributors do not need to replace their routing platform. Route Tracking simply connects to it and brings the relevant information into Pepper.
Additional notes
Route Tracking is intentionally focused on clarity and practicality:
It shows realistic delivery windows
Arrival times appear as simple windows rather than exact minutes, since small variations in traffic, unloading, or stop duration naturally shift timing throughout the day. Route Tracking also avoids live map views, since map level detail often creates unnecessary questions about nearby truck movements, stop order, and routing choices. A window sets realistic expectations and avoids frustration when timing moves by a few minutes, or route changes.
It does not override routing decisions.
Dispatchers retain full control over how routes are planned, sequenced, and managed. Route Tracking simply reflects the delivery timing generated by the existing routing system.It does not require new hardware or new routing workflows.
Route Tracking works with the systems already in place, enhancing visibility rather than replacing core operational tools.
Route Tracking setup for Samsara
Step 1: Create an API access token
In Samsara:
Follow these instructions to create a new Bearer API token. Only the “Read Routes” scope under the Driver Workflow category is required.
Give it a clear name, such as “Pepper Route Tracking”.
Share the token with your Pepper contact.
The token does not expire and does not need to be refreshed once generated.
Step 2: Import Pepper Order IDs from ERP to Samsara
Pepper order ids are six character ids that appear on orders sent from Pepper into your ERP. These ids must be added to the stops in Samsara so Pepper can connect route events back to the correct orders.
Generally, there are at least two ways of doing this.
Option 1: Using the Samsara API (recommended)
If your team manages routes through the Samsara API:
Add the Order IDs into the “externalIds” attribute as illustrated in the API documentation
Use a single key to store them, suggested key name: "pepperIds"
If a stop contains several Pepper orders, the Pepper Order IDs should be packed into one key-value pair using a delimiter, such as:
“externalIds”: {
{
“pepperIds”: “123ABC.234BCD.345CDE”,
}
}In the above example, three Pepper Order IDs are compressed into one external ID key-value pair.
Option 2: Using CSV upload to Samsara
If your team uploads routes using CSV:
Add a new column called pepperIds, as illustrated in instructions here.
For each stop row, enter the Pepper order id or ids.
If there are several orders on the same stop, combine them in one cell with a delimiter, for example:
123ABC.234BCD.345CDEunder “pepperIds” header.
Step 3: Notify Pepper Staff
Once the token is created and Pepper order ids are flowing into Samsara, let your Pepper contact know. Pepper will complete the remaining configuration on their side.
Route Tracking setup for Omnitracs
Step 1: Create an event subscriber
In the Omnitracs web portal:
1. Go to Administration.
2. Open Event Subscriptions and click Add.
3. Choose a clear subscriber name, such as “PEPPER-TMT”. Add a short description. Check the Stop Departed subscription, then click Save
Step 2: Create a web service integration user
Still in the Administration portal:
Go to Users and click Add.
Create a user with an email in this format: [email protected]
For example “[email protected]"
Set any first and last name.
Check the box for Web Service Integration User.
Choose a secure password and save the user.
5. Next, go to the User Groups and Roles tab, give the user the ADMIN role, then click Save.
Once created, share the subscriber name, username, and password with Pepper.
Step 3: Import Pepper Order IDs from ERP to Omnitracs
Pepper order ids are six character ids that appear on orders sent from Pepper into your ERP. These ids must be added to the stops in Omnitracs so Pepper can connect route events back to the correct orders.
Generally, there are at least two ways of doing this.
Option 1: Using the Omnitracs API (recommended)
If your team manages routes through the Omnitracs API:
Add the Order IDs into the “customProperties” attribute as illustrated in the API documentation
This will appear as a key-value pair, such as:
“customProperties”: [
{
“key”: “pepperId”,
“value”: “123ABC”
}
]The suggested custom property name is “pepperId”.
Option 2: Manual upload inside Omnitracs
If your team uploads routes manually:
Add a custom property field named "pepperId".
Enter the six character Pepper order id for each order attached to that stop.
This ensures the order can be matched to the correct updates in Pepper.
Step 4: Notify Pepper
Once the event subscriber is created, the integration user is set up, and Pepper order ids are flowing into Omnitracs, let your Pepper contact know. Pepper will handle the remaining configuration on their side.