Refunds as a quality instrument, not a finance leftover
Finance sees refunds as leakage. Ops should see them as labelled failures. A missing drink, a cold noodle, and a late arrival are not the same incident. If your reason codes are a junk drawer, you are flying without instruments.
We ask Partner Margin Ledgers students to put refund reason next to contribution, not in a separate tab. A SKU can look profitable until “cold on arrival” eats the delivery fee and the promo. The Yaowarat case on our reviews page is the cousin of this idea: when stalls packed down, refunds on cold dishes rose. The demand chart alone did not say why.
Clean the taxonomy first. Collapse twenty marketplace labels into a handful you can act on: kitchen miss, packing miss, travel time, wrong pin, customer change-of-mind. Then join to ticket anatomy. Cold-on-arrival that correlates with long bag-to-door is a corridor problem. The same label with short travel and long ticket-to-bag is a pass problem.
Do not weaponise refund rate against kitchens without the split. We have seen delisting threats that belonged to a handover pin. We have also seen kitchens whose item-level miss rate was real and needed a quieter SKU list, not another rider bonus.
Limitation: marketplace reason codes are often chosen by tired customers. Treat them as noisy labels. Look at volume and correlation, not at a single angry ticket. If your app allows free-text only, this essay will not save you — you need structured reasons before the chart.