Client Stories
Client stories from grocery delivery reviews
Operators describe what changed after clarifying baskets, courier clocks, and reorder definitions.
Aina R. — operations lead, Selangor dark store
We finally agreed what counts as a completed basket when a shopper accepts two substitutions. The audit forced that definition onto one page before anyone touched the warehouse board. I still wish we had booked it before festive season — we lost two weeks arguing in December.
Marcus T. — courier supervisor, Penang
Courier late rates looked worse than they felt on the road. Filenestbase showed our clock started at assignment, not at pick-complete — once we fixed that, the weekly review stopped arguing about ghosts.
Siti N. — product owner, Johor grocery app
The funnel review caught that our minimum-order banner fired an event even when the shopper never reached payment. Quiet fix, louder Monday meetings.
Daniel K. — regional manager, dual-brand fleet
The reorder session was shorter than I expected. We walked out with definitions for “skipped week” that match how households buy rice and oil, not how a fashion app counts returns. Useful, though we still need our CRM vendor to rename three fields.
Extended story: reconciling late drops in George Town
A Penang operator brought three weeks of courier extracts after condominium access delays inflated “late” labels. We sat with supervisors and mapped when the app started the clock versus when riders left the dark store. The brief recommended starting the SLA at pick-complete for island routes and logging access waits as a separate code. Within one release cycle, the late rate dropped into a range supervisors recognised from the road — without changing rider bonuses.
Constraint worth noting: rainy-week samples remained thin, so we marked weather adjustments as provisional until a fuller monsoon month of data arrived.