The Fleet section is the operator's control room for deliveries. If your store runs its own drivers (or participates in the open delivery network), this is where you monitor bookings, manage drivers, fund their wallets, and reward performance.
Fleet Dashboard
Navigate to Fleet → Dashboard. It shows your own store's bookings plus network bookings within 20 km that your drivers could serve (or inside your territory, if KukuExpress has drawn one for your fleet — see below), with status filters, quick date ranges, and sortable columns. From here you can:
- Track drivers live on a map centered on your store, with each driver's current status.
- See cancellation reasons and reopen cancelled bookings back into dispatch.
- Spot returning customers via the trust hint on their bookings.
Managing Drivers
Fleet → Drivers lists your drivers with their pay rate, city, canonical wallet balance, and an inline auto-assign toggle. Bulk actions let you suspend drivers, set rates, or toggle auto-assign for many at once. Each driver can register multiple vehicles; every vehicle is approved individually against a 7-document verification checklist (selfie, license front/back, vehicle photos, OR/CR).
Operator Wallet & Top-Ups
Your operator wallet at Fleet → Wallet funds your drivers. Drivers submit top-up requests with a proof-of-payment image; approving a request debits your operator wallet and credits the driver. Approvals are blocked if your wallet lacks funds, and dispatch is suspended while an operator wallet is negative — keep it funded.
Driver Rewards
Define completion rewards — e.g. complete N bookings in a day to earn a flat bonus plus a per-trip amount — with schedule windows and claim limits. Rewards pay from your operator wallet to the driver's wallet automatically at completion.
Support Tickets
Drivers can open support tickets from their app. Handle them in Fleet → Support, an inbox with per-ticket chat.
Driver App 4.1.8: Customer Trust Profile & Pabili Receipts
Customer Trust Profile
Drivers can tap a customer's name on any available booking — or on the booking detail — to open a quick trust snapshot before accepting: the customer's profile photo, their star rating from past driver ratings, a gold returning-customer badge with completed-order count, and the date of their last successful booking. Customer profile photos and the delivery notes entered at checkout also now show directly on the accept popup, the Available Pickups cards, and the booking detail.
Note: the star rating only fills in as drivers rate customers after trips, and the profile photo shows only when the customer has set one in their app.
Receipt Photos Required on Pabili Orders
For bookings from pabili stores, the driver must photograph the store receipt from their purchase. The app asks for the photo at Picked Up — while the driver is still at the store — and again before Complete Booking if it is still missing. The server enforces this too: a pabili completion without a receipt photo, a subtotal-adjustment proof, or a kukurier pabili receipt is rejected. Captured receipts appear in the booking's Photo Proof strip next to the pickup and delivery photos, so operators can audit what the driver actually paid.
Driver App 4.1.9: Booking Alerts Overhaul
Alerts That Ring and Open the Trip
When a booking is auto-assigned to a driver — or handed to them from your Fleet board — their phone rings with the KukuExpress tone and the app jumps straight to the booking's details, even if the app was already open on screen. There is no dialog to tap through: the driver lands on the pickup and drop-off information immediately. Customer chat messages on a live transaction behave the same way — the phone rings and the conversation opens by itself, unless the driver is already reading that chat.
The app also double-checks for assignments in the background while it is open, so even if the phone's system dropped the push notification (battery saver, weak signal), the trip still rings within seconds instead of sitting silently in the list.
One Phone at a Time
Each driver's booking alerts ring on exactly one phone: the one they signed in on most recently. When a driver signs in on a different device, alerts move there and the previous phone receives a notice that it went quiet ("Booking alerts moved to another phone"). That old phone then shows an amber card — Booking alerts are on another phone — with a one-tap option to switch alerts back. Merely reopening the app on the old phone does not switch alerts back; moving them is always a deliberate tap, so a forgotten phone at home can never silently swallow bookings.
The "Booking Alerts are OFF" Warning
If a driver's phone cannot receive alerts at all — notifications blocked in the phone's settings, or the device failed to register — the app's home screen pins a red Booking alerts are OFF card. Tapping it opens the phone's notification settings (when notifications are blocked) or retries the registration, and reports clearly whether it worked. The card disappears on its own once alerts are healthy.
For operators: dispatch now prefers drivers whose phones can actually ring. A driver showing the red card is not only missing alerts — auto-assign will pass over them in favor of a reachable driver whenever one is available nearby. If a driver reports not getting bookings, the first thing to check is whether this card is showing on their home screen.
Scheduled Deliveries: When Riders See Them
Customers can schedule deliveries for a future time slot (pre-orders). Here is exactly how those bookings reach drivers:
- Before the lead-time window: the booking is held in a scheduled state — it does not appear in any driver's available-bookings list and no phones ring. Drivers cannot see it at all yet.
- Inside the window: the platform automatically promotes the booking into the normal flow — it enters the available list and eligible drivers get the usual booking alert. The window is your store's dispatch lead time (30 minutes before the slot by default; adjustable per store).
- Merchant prep still applies: for restaurant-type stores the booking additionally waits for the merchant to mark the order as being prepared — riders never get called for an order the kitchen hasn't started.
- In the driver app: a promoted scheduled booking looks like any other request but carries its scheduled time — the list's Scheduled sort shows soonest-slot-first with a clock icon, so drivers can tell a "deliver at 6:30 PM" job from an ASAP one before accepting.
Operator Territories (Map Fences)
Some operators are given exclusivity over an area. Instead of a distance radius, KukuExpress draws a territory for your fleet on the map — a town, a city, a whole province, or any custom shape, and more than one if you serve several places. Territories are set by KukuExpress, not from the portal; contact support to request one or to change it.
What your drivers receive
- Inside your territory: network deliveries whose pickup or drop-off is inside one of your fences are offered to your drivers as usual.
- Outside your territory: your drivers do not receive network deliveries that neither start nor end inside your fences — those go to the fleets that serve that area, or to the open network when no territory covers either end. This applies the moment a territory exists for your fleet.
- Your own store's orders always reach your own drivers, wherever the pickup is.
- Deliveries paid with a coupon your fleet sponsored stay with your fleet, as before.
The pickup decides who gets a delivery first: an exclusive fence reserves deliveries picked up inside it. The drop-off decides who else may take it: if a parcel is picked up in a town nobody covers and delivered into your territory, your drivers receive it right away; if it is picked up inside another operator's exclusive fence and delivered into yours, their fleet has the first window and your drivers can take it once that lapses. Everything else about who can take a booking is unchanged: the merchant must still allow outside drivers (or be a pabili store), locked drivers still need Fleet-Operator Mode for other stores' orders, wallet minimums still apply, and each driver's own distance preference still limits how far from their phone a pickup can be.
Exclusive vs shared fences
- Exclusive: deliveries picked up inside are reserved for your fleet first. If nobody in your fleet accepts within the fence's window (10 minutes by default), the delivery opens to the whole network. Where two operators' exclusive fences overlap, both fleets share the deliveries in the overlap.
- Shared: the area bounds your drivers as above, but other fleets may take deliveries inside it too. Nothing is reserved.
On your Fleet board
Once your fleet has a territory, Fleet → Dashboard shows a Your territory card with each fence, its mode and its window, and a map of the outlines. The board lists network bookings inside your territory at any distance (the 20 km limit no longer applies) and hides bookings outside it. Rows reserved for your fleet carry a Your territory badge; bookings reserved for another operator's territory stay hidden until their window lapses.
Taking Local Orders Before the Store Accepts Them
A delivery from an ordinary (non-pabili) store normally waits for the kitchen to accept the order and start preparing it before the platform involves drivers. Whether your fleet may jump in earlier is now a setting:
- Fleet level: Bookings → Pricing → Driver Network → Let my drivers take local orders before the store accepts them. On by default.
- Driver level: the Early orders switch on each driver's row under Fleet → Drivers. On by default; only matters while the fleet setting is on.
When both are on, your drivers see these orders the moment the customer places them, and auto-assign can hand one to your fleet straight away. Use this for local stores you know will accept. When either is off, that driver only sees the order once the store has accepted and marked it preparing, so nobody rides to a kitchen that hasn't said yes. Pabili orders and Kukurier parcels are never held — there is nothing to prepare.
Turning the fleet setting off does not cancel anything: the order simply appears for your drivers when the store accepts it. The platform's own auto-cancel for orders nobody takes still applies, so a store that never accepts still ends with a cancelled order.
Driver Availability and "Why Isn't My Driver Getting Bookings?"
The Fleet board's bookings card now starts with your driver headcount: available now (online, free, and with a GPS fix inside your store's freshness window), on a trip, available but stale GPS (the app says available, but the phone hasn't reported a position recently — usually backgrounded or dozed), offline, and, if you have a territory, how many available drivers are physically inside it. "Available now" is about the driver's phone and status, not their location: a driver outside the territory can still take a pickup inside it within their radius.
Click any pill to open GPS Tracking. Each driver there carries a verdict — Can receive bookings, On a trip, or Blocked: … naming the first thing in the way — and expands to the full checklist: online, fresh GPS, wallet above your floor, operator wallet funded, allowed to take other stores' orders, an approved active vehicle, and push alerts reachable, followed by the driver's own app settings (pickup radius, max trip length, minimum fare, cash on hand, auto-assign, early orders, inside territory). The Fleet booking gates card shows the store-level settings behind those checks, and your territory is drawn on the map.