Where fleet control actually lives today
Eight warehouses. Over a thousand riders. Every jacket, bag, helmet and no-show tracked across spreadsheets, WhatsApp groups and paper forms that never agree with each other. Flip the switch to see the same fleet on one system.
| Rider | Hub | Bag | Jacket | Helmet | Returned? | Deduct |
|---|---|---|---|---|---|---|
| Ahmed Mohamed | Maadi | Yes | Yes | ask Karim | — | — |
| Ahmed Mohamed | Nasr City | Yes | No?? | Yes | — | 150?? |
| Mahmoud S. | Heliopolis | Yes | Yes | Yes | left 3 Sept, bag? | — |
| Omar Farag | New Cairo | 2 bags | Yes | — | — | — |
| Youssef A. | Zayed | Yes | size L→XL | Yes | — | no-show 12/9? |
| Karim Mansour | Maadi | Yes | Yes | Yes | — | paid twice |
| TOTAL BAGS ISSUED: 412 (sheet) vs 388 (warehouse count) vs 431 (finance) | ||||||
Needs a human right now
Ahmed Mohamed · R-1042 · Nasr City (moved from Maadi 4 Sept)
Deductions: none open. The EGP 150 no-show flagged 12 Sept was auto-waived — gate log shows he was on site at 08:04.
Training: 4 of 4 assigned courses passed. Last quiz 94%.
Every number on the right is derived from one event log. There is no version 7 and no "which Ahmed". That single source of truth is the product. Everything that follows is a stage in the rider's life that writes to it.
Proven at scale, isolated by design
This is not a prototype. The same platform runs rider gear operations for Talabat across eight markets. Because our clients compete in the same cities, isolation is a hard architectural commitment, not a policy.
Live for Talabat across MENA
Onboarding, gear issuance, exchanges, clearance, deductions and reporting for rider fleets in eight countries, with market-level teams operating independently on one platform.
- In production since [INSERT: go-live year]
- [INSERT: riders under management] riders and [INSERT: items tracked] gear items tracked
- Embedded help centre, taxonomy and reporting maintained by Boolanga as a managed service
Your data never shares a room with anyone else's
Separate tenant, separate database. Breadfast runs on its own instance. No shared tables, no shared indexes, no shared storage buckets.
Access is scoped to your organisation and your warehouses. Roles are configured by you. Boolanga staff access is logged and visible to your admins.
Zero cross-client reporting. No benchmark, aggregate or anonymised dataset is built across clients. Your metrics are yours.
Hosting where you need it. Dedicated cloud deployment and data-residency options; DPA provided on request.
Appointments and onboarding
A new rider books a kit-issuance slot at their warehouse from a one-tap link. The warehouse sees capacity per slot, the POC gets a digest every evening, and cancelling a service for a day is one action, not fourteen.
Select a service slot on the calendar
Capacity, bookings and no-show history for the slot appear here.
No-shows are the most expensive minutes in a warehouse: a counter is staffed, a kit is prepared, a rider is not earning. Reminders the evening before and a POC who knows exactly who is coming are the two cheapest levers on that number, and both run without anyone remembering to do them.
Gear assignment at the counter
The kit is defined per role, vehicle and warehouse. Each item is scanned to the rider, the rider signs on the tablet, and stock moves the instant the receipt is confirmed. Walk through an issuance and watch the warehouse inventory change.
Live stock · Maadi
Reorder point per item is set per warehouse. Falling below it raises an exception in the control tower and drafts a replenishment request automatically.
The signature is the point. Every future deduction, exchange or clearance dispute resolves against a timestamped receipt the rider acknowledged, in their language, with the item barcodes on it. No receipt, no argument.
Exchanges and replacements
Not every replacement is the same. The system routes each request to one of four exchange types, and the type decides who pays, who approves and where the old item goes. Answer the questions the counter staff would answer.
Answer the first question
The exchange type, charge, approval requirement and destination of the returned item will resolve here.
When every replacement is just "gave him a new bag", the loss rate is invisible. Typed exchanges make the difference between wear-and-tear and negligence measurable per warehouse, which is the number procurement and HR both want and neither has.
Compliance and AI evaluation
A rider submits a photo from their phone at shift start or on request. The evaluation scores gear condition and uniform compliance, flags what it sees, and recommends an action. A supervisor confirms with one tap or overrides.
Condition and compliance score
Waiting for a photo.
Recommended action
Compliance rules for Heliopolis
every 14 days and on any customer complaint70 assigns the refresher course automatically50 blocks shift start until a supervisor clears itSupervisors cannot inspect a thousand riders a fortnight. Scoring makes inspection continuous and consistent across warehouses, and every score is a dated record that later justifies a deduction, an exchange or a course, without a supervisor's memory being the evidence.
Deductions and penalties, governed
Your riders are employees, so a deduction is a payroll event with legal weight, not an invoice line. Nothing here is automatic except the evidence. Every deduction runs through the same eight steps, and the rider can contest it from their phone before payroll ever sees it.
By reason · EGP
Outcome of every deduction raised
A waiver rate that climbs in one warehouse is a signal about that warehouse's supervisors, not its riders. Regional managers see this by default.
Unfair or unexplained deductions are how you lose riders and how you end up in a labour dispute. A deduction that arrives with its evidence and a fair way to contest it is one riders accept, and the approval and waiver rates tell management where the policy is being applied badly.
Training that reaches riders where they already are
No app to install. A course arrives on WhatsApp, opens in one tap, scrolls like a feed and ends in a quiz that produces per-rider proof of completion. A compliance flag assigns the corrective course before anyone is suspended. Flip the rider language at the top of the page.
any warehouse → Welcome, Road safety, Great customer handoversMotorbike → Riding safely in extreme heat (Apr–Oct)< 70 → Uniform and gear standards refresher, due in 3 days+1d, +3d, supervisor notified at +5d11 riders stopped before the quiz. The card before it is flagged for shortening. Courses are built inside the platform from a PDF or SOP, narrated by AI in Arabic and five more languages, with a 24/7 assistant that answers policy questions from the same content.
Training you cannot prove did not happen. Completion, score and timestamp per rider close the loop on compliance: a flagged rider is corrected, the correction is recorded, and the next audit or customer complaint has an answer.
Offboarding and clearance
An exit in the HR system books a return appointment automatically. At the counter each item is checked in and graded, the outstanding balance is computed on the spot, and HR and payroll receive a clearance certificate. Grade the items and watch the balance move.
The last day is when gear disappears. A return appointment that books itself and a balance HR sees before the final salary run is the difference between recovering a bag and writing it off. The five outcomes also give procurement the reuse and disposal numbers it currently guesses.
The control tower
Every stage above writes to one event log; this is what it looks like read back. Change any filter and every figure, chart and row on the page recomputes from the underlying records. Nothing here is a screenshot.
| # | Warehouse | Riders | Compliance | Training | No-show | Open deductions | Overdue returns |
|---|
Exceptions needing a human
Any view exports to CSV or Excel with the current filters applied. Scheduled reports send the same views on a cadence you set.
Visibility is not a dashboard; it is the confidence that the dashboard and the warehouse floor agree. Because the same records drive issuance, deductions and reports, finance, HR and operations stop reconciling three versions of the truth every month.
Requests, approvals and communication
Anything that today starts as a WhatsApp message to whoever might know, starts here instead: a typed request, the right fields, the right approvers, a thread that stays attached to the record.
Down to 4 insulated bags, 9 onboardings booked this week. Requesting 30.
Approved 30. Can we take 10 from Zamalek instead of ordering? They are at 41.
Transfer request TRF-118 drafted: 10 × insulated bag, Zamalek → Nasr City. Awaiting Zamalek confirmation.
Approved. Order the remaining 20 from the Q4 PO.
Kit template v4 goes live on the 15th. Book rider exchange slots from the 8th. Reply in this thread with your first-week capacity.
Requests that live in chat are invisible to management and unaccountable to anyone. Typed requests with configurable approval chains give every warehouse the same process, and give the regional manager a queue instead of a phone that never stops.
Admin, security and control
Three roles by default, configurable per warehouse. Every action anyone takes is logged and exportable. Your identity provider and HR system stay the source of who exists.
| Capability | Warehouse user | Regional manager | Admin |
|---|---|---|---|
| Issue and receive gear | Own warehouse | — | Any |
| Raise a deduction | Own warehouse | — | Any |
| Approve or waive a deduction | — | Region | Any |
| See reports and dashboards | Own warehouse | Read-only, all warehouses | All |
| Export rider-level data | — | Region | All |
| Change kit templates and rules | — | — | Yes |
| Manage users and roles | — | — | Yes |
| View audit log | — | Read-only | Yes |
What control is worth per year
Move the sliders to your fleet. The assumptions are deliberately conservative and shown in full; change any of them.
Rollout in eight weeks, one warehouse first
The platform exists; the work is your kit templates, your rules and your data feed. We pilot where the pain is loudest, prove the numbers, then roll out.
Configure
- Warehouses, roles, kit templates per vehicle
- Deduction rules agreed with HR and legal
- Rider feed from HRIS, notification sender set up
- Training team onboarding
Pilot warehouse
- Live issuance, exchanges and appointments
- Existing gear baseline captured by scan
- Daily check-in with the pilot POC
- First deduction cycle run in shadow mode
Prove
- Pilot numbers vs. the spreadsheet baseline
- Rules and templates adjusted
- Payroll export validated end to end
- Go / no-go for rollout
Roll out
- Remaining warehouses in two waves
- Regional dashboards live
- Scheduled reports to finance, HR, ops
- Handover to steady-state support
What we need from Breadfast
- A rider feed: ID, name, warehouse, vehicle, start and exit dates, from your HR or rider system
- Access to your WhatsApp Business sender or SMS provider, or we provision one
- A named POC per warehouse and one product owner on your side
- Your current gear list, prices and any deduction policy already in use
What you have by when
- Week 1: every rider and every item in the pilot warehouse on the system, spreadsheet retired
- Month 1: appointments, reminders and digest running; first governed deduction cycle
- Month 3: all warehouses live, regional league table, payroll and finance exports scheduled, training compliance visible per rider
Next step: book a discovery call
A short call with your ops lead to confirm scope. From there we run a two-hour scoping session with one warehouse manager, map your kit, deduction policy and rider feed onto the platform live, and leave you with a configured pilot plan and a fixed-scope proposal.
Presented by Hamdan Albakr · Boolanga · hamdan@boolanga.com · +36 30 553 8222 · calendly.com/hamdan-boolanga/discovery