Settings
How ZetDeliver books, attempts, collects and tells customers. Every change is audited.
ZetDeliver isn't part of your company's suite
E-commerce and scheduled delivery: runs, slots, POD, COD and returns. It runs on its own and reuses your existing vehicles, drivers and customers.
You don't have access to this page
Your ZetDeliver role is Member. This page is for other roles.
You don't use ZetDeliver
Your ZetDeliver role is No access. Your admin decides who gets ZetDeliver and with which role.
Your work is in the ZetMove Driver app
Your ZetDeliver role is Delivery rider, so you don't use ZetDeliver 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 deliveries
Stations
Where parcels are sorted and runs start
| Station | Cut-off | Hours | Riders | Capacity / day | Manager |
|---|---|---|---|---|---|
Andheri station Micro-hub · 4 zones | 08:30 | 06:30–22:00 | 38 | 1,300 | Asha Menon |
Thane station Delivery station · 3 zones | 08:00 | 07:00–21:30 | 29 | 950 | Nitin Desai |
Vashi station Delivery station · 3 zones | 08:00 | 07:00–21:30 | 24 | 800 | Pooja Iyer |
Bhiwandi sort centre Sort centre · 2 zones | 05:30 | 24 hours | 12 | 400 | Riya Kapoor |
What Zed may do on its own
Every action is in the rescue log with its reason and an undo
- Message customers after a failed attempt and book their answer
- Re-sequence a run when a rider falls behind
- Ask high RTO-risk COD customers to pay by UPI first
- Move a delivery to another run in the same zone
- Approve return to origin without a manager
- Approve POD photos it is unsure about
Recent changes
Audit log for ZetDeliver settings
- Today 09:12Evening slot capacity Andheri 320 → 360Riya Kapoor
- Mon 17:40UPI-first for RTO risk over 70Zed (suggested), Riya approved
- Fri 10:02Changed failed-attempt WhatsApp templateRiya Kapoor
Delivery windows
What customers can pick at checkout and on the tracking page
| Window | Default capacity per zone | Fee | Days | On |
|---|---|---|---|---|
| 07:00–10:00 | <input class="rs-in" style="width:90px" value="60" aria-label="Capacity" /> | Free | Mon – Sun | |
| 10:00–14:00 | <input class="rs-in" style="width:90px" value="140" aria-label="Capacity" /> | Free | Mon – Sun | |
| 14:00–18:00 | <input class="rs-in" style="width:90px" value="120" aria-label="Capacity" /> | Free | Mon – Sun | |
| 18:00–21:00 | <input class="rs-in" style="width:90px" value="70" aria-label="Capacity" /> | ₹29 | Mon – Sun |
Day-by-day capacity lives on Delivery slots.
Cut-offs
Orders after the cut-off move to the next window
- Same-day (Mumbai)Andheri, Thane, Vashi
- Next-day (MMR)All stations
- Evening slot 18:00–21:00Andheri, Thane
- Bhiwandi & KalyanBhiwandi sort centre
When a window fills up
Applied per zone
- Close the window at
- Warn dispatch at
- Let Zed open an overflow run when over 95%
- Charge a surge fee for the last 10%
Attempts and returns
What happens when a delivery fails
- Max attempts before RTO
- Gap between attempts
- Hold at station before RTO
- RTO charge to merchant
- Reattempts billed as new deliveries
Failed-attempt rescue
Zed contacts the customer within minutes of a failed attempt
- First message on
- If no answer in 30 min
- Book the slot the customer picks without asking dispatch
- Offer self-collect at the station
- Ask riders for a photo of the door on every failed attempt
- Flag fake attempts (rider not within 200 m of the address)
Proof of delivery
What a rider must capture at the door
| Parcel | Photo | OTP | Signature | Open-box | Geofence 150 m |
|---|---|---|---|---|---|
| Prepaid | |||||
| COD | |||||
| High value (over ₹10,000) | |||||
| Electronics |
Cash on delivery
What riders may collect, and how cash gets back to the merchant
- Max COD per shipment
- Max cash a rider may carry
- Accept UPI at the door
- Hand-in at the station
- Variance that needs a manager
- Bank deposit
- Merchant remittance
- Hold remittance while a COD dispute is open
ZetBill
Delivery charges and remittances flow to ZetBill
- Invoice merchants for delivery charges
- Net delivery charges off the remittance
- Return charge per shipment
Customer messages
Sent automatically at each step. {name}, {merchant}, {slot} and {link} are filled in.
- Out for deliveryWhatsApp
- Failed attemptWhatsApp + voice
- DeliveredSMS
Channels
Where customers hear from you
- WhatsApp Business
- SMS
- Voice call (IVR)
- Survey after delivery
General
Defaults for new deliveries
Depots
Where parcels are sorted and runs start
| Depot | Cut-off | Hours | Couriers | Capacity / day | Manager |
|---|---|---|---|---|---|
Amsterdam depot Depot · Westpoort · 3 zones | 14:00 | 05:30–22:00 | 34 | 1,600 | Sanne Bakker |
Utrecht depot Depot · Lage Weide · 4 zones | 14:00 | 05:30–22:00 | 31 | 1,500 | Joost van Dam |
Rotterdam depot Depot · Waalhaven · 3 zones | 14:30 | 06:00–21:30 | 22 | 1,000 | Thijs Visser |
Nieuwegein hub City hub · 2 zones | 15:00 | 07:00–21:00 | 9 | 420 | Joost van Dam |
Hilversum hub Cargo-bike hub · 2 zones | 13:00 | 07:30–20:00 | 7 | 260 | Sanne Bakker |
What Zed may do on its own
Every action is in the rescue log with its reason and an undo
- Message customers after a failed attempt and book their answer
- Re-sequence a run when a rider falls behind
- Offer a pickup point after the first failed attempt
- Move a delivery to another run in the same zone
- Approve return to origin without a manager
- Approve POD photos it is unsure about
Recent changes
Audit log for ZetDeliver settings
- Today 09:12Evening window capacity Utrecht 180 → 220Riya Kapoor
- Mon 17:40Offer pickup point after attempt 1Zed (suggested), Riya approved
- Fri 10:02Changed failed-attempt WhatsApp templateRiya Kapoor
Delivery windows
What customers can pick at checkout and on the tracking page
| Window | Default capacity per zone | Fee | Days | On |
|---|---|---|---|---|
| 08:30–13:00 | <input class="rs-in" style="width:90px" value="220" aria-label="Capacity" /> | Free | Mon – Sat | |
| 13:00–17:00 | <input class="rs-in" style="width:90px" value="180" aria-label="Capacity" /> | Free | Mon – Sat | |
| 17:00–21:00 | <input class="rs-in" style="width:90px" value="160" aria-label="Capacity" /> | €1,95 | Mon – Sat |
Day-by-day capacity lives on Delivery slots.
Cut-offs
Orders after the cut-off move to the next window
- Same day (flowers, cheese)Utrecht, Amsterdam
- Next dayAll depots
- Evening 17:00–21:00All depots
- Cargo bike (Hilversum)Hilversum hub
When a window fills up
Applied per zone
- Close the window at
- Warn dispatch at
- Let Zed open an overflow run when over 95%
- Charge a surge fee for the last 10%
Attempts and returns
What happens when a delivery fails
- Max attempts before return
- Gap between attempts
- Hold at pickup point
- Return charge to merchant
- Reattempts billed as new deliveries
Failed-attempt rescue
Zed contacts the customer within minutes of a failed attempt
- First message on
- If no answer in 30 min
- Book the slot the customer picks without asking dispatch
- Offer neighbour or pickup point
- Ask riders for a photo of the door on every failed attempt
- Flag fake attempts (rider not within 200 m of the address)
Proof of delivery
What a rider must capture at the door
| Parcel | Photo | OTP | Signature | ID check 18+ | Geofence 150 m |
|---|---|---|---|---|---|
| Standard | |||||
| High value (over €250) | |||||
| Wine & spirits | |||||
| Card at door |
Card at door and payment links
Couriers carry a Betaalbox terminal; customers can also pay from a link
- Payment provider
- Accept at the doorDebit card, credit card, Apple Pay, iDEAL QR
- Send a payment link the evening before
- Settlement from Betaalbox
- Merchant payout
ZetBill
Delivery charges and remittances flow to ZetBill
- Invoice merchants for delivery charges
- Net delivery charges off the remittance
- Return charge per shipment
Customer messages
Sent automatically at each step. {name}, {merchant}, {slot} and {link} are filled in.
- Out for deliveryEmail + SMS
- Failed attemptWhatsApp
- DeliveredEmail
Channels
Where customers hear from you
- SMS
- Survey after delivery
Add a delivery window
Customers can pick it from tomorrow