Case study · Service marketplace · UAE · 2024
Bookings were matched to providers after the fact, so availability shown at booking time was an estimate. Customers were being confirmed into slots that had already gone.
The marketplace showed provider availability derived from a stale view of the roster. A customer picked a slot, and only afterwards did the system work out whether anyone could take it — which is where cancellations and re-bookings came from.
Availability is now resolved against live provider state and location at the moment the customer is choosing. A slot shown is a slot that can actually be served, which removes the class of failure that was costing conversion.
Customer and provider clients share a Flutter codebase, so dispatch logic behaves identically on both sides and a change to scheduling rules ships once, not twice.
“The technical precision DataDaur brought to Faroo transformed our daily operations from reactive to proactive.”
Next
When those two diverge, cancellations are the symptom and scheduling is the cause. We start by measuring the gap.