Delivery Routes
Delivery routes are reusable pickup/dropoff patterns. Dispatchers use routes when the same movement path, schedule, or driver responsibility repeats.
Route List
The routes table shows:
- Route name.
- Pickup origin.
- Dropoff destination.
- Assigned driver.
- Schedule.
- Assignment status.
- Active/inactive state.
- Active order count.
- Start date.
- Created and updated dates.
Use search, filters, and sorting to find route records quickly.
Route Setup
A route includes:
| Field | Meaning |
|---|---|
| Route name | Name used by dispatchers to identify the route. |
| Pickup type | Warehouse or address origin. |
| Dropoff type | Warehouse or address destination. |
| Driver | Optional assigned driver. |
| Start date | Date the route becomes relevant. |
| Schedule time and days | Repeating route schedule. |
| Notes | Operational notes for dispatchers. |
Drivers must be active/available and have a vehicle when the route requires one.
Route Detail
The route detail modal shows:
- Route information.
- Pickup and dropoff points.
- Schedule.
- Driver and vehicle.
- Switch driver action.
- Session status summary.
- Route sessions table.
Route Sessions
A route session is one execution of the route. The route can have many sessions over time.
Session statuses include:
- Open.
- Started.
- Picked up.
- In transit.
- Completed.
- Cancelled.
Dispatchers can create a session only when the route has an assigned driver and does not already have an open session.
Add Orders to a Route
Eligible deliveries can be added to a route session from the route detail flow or from table route assignment.
Use route assignment when:
- The deliveries match the route pattern.
- A route driver will handle the work.
- Orders should be grouped under route execution.
Do not use a route as a general bucket for unrelated deliveries. Routes are meant for repeatable pickup/dropoff operations.