Vehicles and Zones anchor field logistics — every delivery or service run maps to a vehicle and the geography it covers.
Please note:
- Deactivate vehicles during maintenance so auto-dispatch from Logistics and live map does not assign broken units.
- Zone changes affect recurring beats for Vendors and FMCG customers — update boundaries before the next planning cycle.
Register vehicles
- Open Vehicles
- Add unit ID, type, capacity, and default depot
- Set active/inactive for maintenance or seasonal fleet
- Assign drivers or crews when your tenant links HR profiles
Telematics or manual odometer readings can attach to trips when integrations are enabled.
Define zones
Zones partition cities, regions, or postcodes so planners do not cross incompatible routes.
| Zone type | Use case | Planning note |
|---|---|---|
| Delivery | FMCG drops | Cutoff times per zone |
| Service | Field repairs | Skill tags on vehicles |
| Restricted | Permits required | Block auto-assign |
| Overflow | Peak demand | Manual activation |
flowchart TB DEPOT[Depot] --> V1[Vehicle A] DEPOT --> V2[Vehicle B] V1 --> Z1[Zone North] V2 --> Z2[Zone South] Z1 --> STOPS[Stops / orders] Z2 --> STOPS STOPS --> LM[Live map visibility]
Route coherence
Assign orders to zones first, then vehicles with matching capacity and permits. Logistics and live map reflects active vehicles by zone when GPS or check-in events feed the map layer. Picked loads from Picking and orders attach here before departure.
Maintenance
Deactivate vehicles during service windows so auto-dispatch does not assign broken units. Update zone boundaries when territories change to keep SLA metrics honest.