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.
Stale GPS, Locked Phones, and Why a Rider Missed an Offer
Driver App 4.3.0 and newer: while a rider is online, KUKU Driver keeps sharing their location from the background — phone locked, in another app, or on a call — under a persistent "You're online" notification in the tray. Going offline in the app stops it. Riders on older builds only report their position while the app is on screen and the phone is unlocked, so they go to Stale GPS about ten minutes after locking the phone. If a rider keeps going stale, check their app version first and ask them to update.
The "Keep GPS on while your phone is locked" card. Some Android phones (Xiaomi, Realme, Vivo, Oppo and others) kill background services unless the app is allowed to run unrestricted. When an online rider's phone has not granted that, the app's home screen shows an amber card; tapping it opens the system dialog, and the card clears once allowed. If the dialog does not appear, the manual path is Settings → Apps → KUKU Driver → Battery → Unrestricted (the wording varies by brand).
What you see on the Fleet dashboard:
- Stale GPS appears once the rider's last fix is older than your Location Stale After window (Bookings → Pricing; 0 means 15 minutes). It clears the instant a fresh fix arrives. The dashboard and the driver app use the same window.
- While the fix is stale, the rider's app only lists your own store's orders. Pabili and other stores' orders are hidden until the fix refreshes, because the platform cannot tell where the rider actually is.
- Open offers (the ones every eligible rider can grab) are shown in the app itself, not pushed to the phone. A rider whose app is off-screen will not see or hear them, even with fresh GPS. If nobody takes the order, it is cancelled after 15 minutes.
How riders get bookings while the phone is in their pocket
Assign the booking to them. A booking assigned to a specific rider — by auto-assign (per rider under Fleet → Drivers) or by you from the Fleet board — sends a push notification with sound that rings with the app in the background or even closed. Push alerts reachable on the GPS Tracking page tells you the rider's phone is registered for exactly these alerts.
For a fleet whose riders wait with the phone locked, put every rider on auto-assign and keep manual assignment for when you want to choose. Auto-assign picks the nearest available rider and prefers riders with a recent GPS fix — which, on 4.3.0, means every rider whose phone is on and online.
Riders who want open offers still need the app on screen while waiting.
Letting Drivers Join Your Fleet From the App
Instead of registering every rider yourself, hand them your fleet join code. It sits at the top of Fleet → Drivers in the partner portal and on the Drivers tab of the operator app: six characters, no confusing letters, easy to read out over the phone or paste into a group chat.
A rider uses it in the KUKU Driver app in one of two places:
- At signup — an optional "Operator join code" field. The app shows your fleet's name before they finish.
- Later — a rider who signed up without a code sees a Join an operator card on their home screen and can enter it there.
Either way the rider lands under your Drivers as pending, exactly as if you had registered them. Nothing about approval changes: you still review their documents and approve a vehicle before they can go online, and the driver-seat limit still applies at approval.
Managing the code
- Regenerate mints a new code and retires the old one at once. Do this if the code leaked or when you stop recruiting through a channel.
- Disable removes the code entirely; riders entering the old one see "not valid" until you generate a new one.
- Every change is recorded in the store's audit log with who made it.
A code cannot poach a rider. A rider who is already in another fleet cannot switch by entering your code — their current operator has to remove them first. The same applies in reverse for your own riders. A rider who has left a fleet (Leave the store in the app, or removed by their operator) is free again: the app shows them Join an operator at their next sign-in, and your code takes them in as pending with their booking history intact.
Reviewing a Driver's Details
Click any row on Fleet → Drivers to open that driver's detail page. Everything about the driver is on one screen, split into what you can change and what you can only see.
What you can edit
- Fleet settings — service group, city, notes, the exclusivity lock, auto-assign, and early local orders.
- Pay — delivery share (percent, per transaction, per km) and, for pabili, the driver's share of your pabili fee. Your store's caps are shown beside the fields.
- App preferences — pickup radius, max trip length, minimum fare, cash on hand and the thermal-bag flag. These are normally set by the driver in their app; your edits apply immediately and are logged, and the driver sees the change.
- Status — Approve, Suspend and Remove, with the same rules as the list (a driver on a live booking cannot be suspended or removed; approval needs a free driver seat and an approved vehicle before they can go online).
- Contact details — only for drivers you registered yourself who do not have their own login. Drivers who signed up in the app manage their own name, phone and email.
What you can only view
- Vehicles — every vehicle registered to the driver with its type, plate, make, model, colour, year, approval status, and which one is active, plus the motorcycle photos and OR/CR for each.
- Verification documents — selfie and licence front/back, each with its review status and any rejection reason. Tap a thumbnail to view it full size.
Vehicle details and documents are reviewed and edited by KukuExpress support. If something is wrong — a plate typo, a rejected photo the driver has since fixed — open a support ticket and name the driver; the page gives you everything you need to describe the problem.
History
The page also lists the driver's status history (who approved, suspended, removed or reinstated them and when, including self-leave from the app) and their recent bookings. The Performance button opens the scoring page that a row click used to go to.
Your territory is also a shopping area in the customer app
From Kaminarigo app 3.2.0, the fences drawn for your territory are the service areas customers choose when they open the app. The customer sees the fence name exactly as it is written (fences that share a name are merged into one area) together with how many stores are inside it, and only stores pinned inside the fence are listed for that area. A tidy, recognisable name — the city or municipality — and a boundary that covers your real service area therefore matter for discovery, not just dispatch. Ask support if a fence name or shape needs changing.
Which feature booked it?
Each booking on the Fleet board and its detail page carries a badge for the customer feature that created it:
- Pabili — booked from the home-screen Pabili. The driver shops at the named store (shown above the pickup address, with the shopping list and budget on the detail page) and is reimbursed in cash on hand-off. Assign a driver who carries enough cash.
- KuKurier — a parcel run. A + pabili tag means the sender also asked the driver to buy items at pickup.
- KuKusina / KuKu Mart — an order from a partner store (food, or grocery / pharmacy / shopping).
- Store pabili — ordered through a pabili store's own storefront.
- POS walk-in — the merchant booked delivery for a walk-in sale from the POS.
- Web store — ordered on the store's web storefront.
GPS Tracking: Live Map and Route Replay
Fleet → Tracking has two layers. The live map shows every approved driver's last reported position, whatever they ride — the driver app sends it while they are online, no subscription needed. Route Replay draws where someone went over a chosen time range, and that needs the route to have been recorded, which is the paid part.
Recording routes
Open the Manage Tracking card on the right of the Tracking page. It has two lists:
- Vehicles — your store-fleet vehicles (Fleet → Vehicles). Switch one on and every fix from the driver assigned to it is recorded against that vehicle.
- Drivers — your approved drivers. Switch one on and every fix their app sends is recorded under them, whichever vehicle they are using. This is how you track drivers who ride their own motorcycle: you do not have to register their bike as a fleet vehicle.
A driver already riding a tracked fleet vehicle is covered by that vehicle's tracking; their row in the Drivers list says so instead of offering a second switch. Each tracked vehicle or driver is one unit on the GPS Tracking plan.
Replaying a route
Under Route Replay, pick a driver or a vehicle, set the time range, and press Load Route. The map draws the path with start and end markers; drag the slider or press play to follow it. Distance is summed from the recorded points. For a driver replay, the plates of the vehicles they used in that window are listed next to the distance.
Replay only shows fixes recorded after tracking was switched on. If you get "No GPS data", either tracking was off during that window or the driver's app was not reporting (see Stale GPS above).
Which vehicle a route is attributed to
Each recorded point carries the vehicle the driver had set active in the driver app at that moment. If a driver assigned to a tracked fleet vehicle switches their active vehicle to a personal one, points stop being written to the fleet vehicle — it is not moving with them. Turn on tracking for the driver if you want those trips recorded too.
Seeing the bookings behind a route
A recorded path on its own does not tell you whether the rider was working. Route Replay therefore lists every booking the driver was on during the chosen window — matched by driver and time, from assignment until completion or cancellation — and draws each one on the map: a green P pin at the pickup, a red D pin at the drop-off, and the recorded stretch between them in that booking's colour. The count sits beside the distance. Click a booking in the list to zoom to that leg and place the replay marker at its start; open takes you to the booking page. A booking marked no GPS in window was assigned to the driver but no fixes were recorded while it was active, which usually means tracking was off or the app was not reporting.
On the live map, a busy driver shows the pickup and drop-off pins of the booking they are on, a dashed line to the stop they are heading for (pickup until the parcel is picked up, then drop-off), and the booking number in the My Drivers panel. A busy driver with no open booking found is marked busy in the app without an assigned booking on the platform — worth a word with the rider.