Settings
How ZetRoute plans and assigns work: assignment rules, depots and zones, SLAs and alerts. Every change is audited.
ZetRoute isn't part of your company's suite
Dispatch and route optimisation: assign, schedule and replan live. It runs on its own and reuses your existing vehicles, drivers and customers.
You don't have access to this page
Your ZetRoute role is Member. This page is for other roles.
You don't use ZetRoute
Your ZetRoute role is No access. Your admin decides who gets ZetRoute and with which role.
Your work is in the ZetMove Driver app
Your ZetRoute role is Driver, so you don't use ZetRoute on the web. Trips, stops, proof of delivery, cash, shifts and documents live in the ZetMove Driver app on your phone.
General
Defaults for new jobs and plans
Route planning
Zed builds the next day's plan every evening
- Build tomorrow's plan at
- Optimise for
- Publish without approval if savings under
- Keep the same driver on recurring lanes
- Allow carriers in plans
- Use live traffic (Google Maps)
Recent changes
Audit log for ZetRoute settings
- Today 09:40Changed auto-assign radius 20 → 25 kmRiya Kapoor
- Mon 18:12Added SLA rule: Nirmal Foods · reeferRiya Kapoor
- Fri 11:05Max jobs per driver-day 8 → 9 on Pune laneZed (suggested), Riya approved
Auto-assign strategy
How a new job finds a driver. Applies to jobs Zed doesn't plan the evening before.
What matters when ranking drivers
Zed weighs these for nearest, one by one and batch
What Zed may do on its own
Shown in the live log with reasons and undo
- Re-sequence a driver's own stops
- Send new ETAs to customers when a trip is over 45 min late
- Reassign a job to another driver if the SLA is safe
- Book a carrier up to ₹15,000 without asking
- Change a customer's delivery slot
Dispatcher scope
What dispatchers see on the board, jobs and live pages
- Dispatchers see only jobs in their depot's zones
- Hide the global unassigned pool from dispatchers
- Dispatchers can take jobs from a neighbouring zone
Depots
Where trucks start and end; docks come from here
| Depot | Type | Docks | Hours | Serves zones |
|---|---|---|---|---|
Bhiwandi hub · BHW Rahnal village, Bhiwandi 421302 | Hub | 8 | 24 × 7 | Mumbai MMR, Gujarat, Nashik |
Taloja yard · TLJ Plot 12, Taloja MIDC 410208 | Yard | 4 | 05:00–23:00 | Mumbai MMR, Pune, South Konkan |
Pune Chakan cross-dock · PNQ Chakan Phase II, Pune 410501 | Cross-dock | 3 | 06:00–22:00 | Pune |
Zones
Group pickups and drops; dispatchers are scoped to zones
- Mumbai MMR42 jobs/dayDispatcher: Riya KapoorPin codes: 400xxx, 421xxx
- Pune31 jobs/dayDispatcher: Sunil Kale (lead)Pin codes: 410xxx, 411xxx
- Nashik12 jobs/dayDispatcher: Riya KapoorPin codes: 422xxx
- Gujarat18 jobs/dayDispatcher: Meena Rao (lead)Pin codes: 394xxx, 380xxx
- South Konkan7 jobs/dayDispatcher: Riya KapoorPin codes: 416xxx, 403xxx
SLA rules
The most specific rule wins: customer and type, then customer, then default
| Applies to | Window | Grace | Penalty | Alert |
|---|---|---|---|---|
| Deccan Pharma · all jobs | 2 h delivery window | 15 min | ₹2,500 per hour late | 60 min before |
| Exetron Pvt Ltd · FTL | Dock slot ± 30 min | 30 min | ₹2,500 per missed slot | 90 min before |
| Nirmal Foods · reefer | 2–5 °C, 2 h window | 0 min | Stock value if > 8 °C for 30 min | Any reading > 5 °C |
| Default · FTL | 4 h window | 30 min | None | 60 min before |
| Default · PTL | 2 h window | 15 min | None | 45 min before |
Alert rules
Who hears about what, and how
| When | Tell | Driver app | In-app | ||
|---|---|---|---|---|---|
| Job assigned to a driver | Driver app | ||||
| Trip running late (ETA past window) | Customer contact | ||||
| Exception opened | Dispatcher on shift | ||||
| Route plan ready to publish | Operations manager | ||||
| Capacity gap over 2 trucks | Operations manager | ||||
| Delivered with POD | Customer contact |
Message templates
Fields in braces are filled in for each job
New alert rule
Build it from a trigger, a condition and who to tell
Add SLA rule
Applies to new jobs from now on
Add depot
Trucks and docks can then be assigned to it