The refund you find out about on Monday
A customer says the garlic bread was missing. Another says the wrong drink came. A third says the whole order was cold and asks for a full refund. The app decides, usually in the customer's favour, and the deduction turns up on your statement a week later. By then nobody remembers the order, and you have no way of knowing whether the garlic bread really was left out.
Some claims are genuine. Bags do go out short on a busy night, especially drinks and dips that live in a different fridge. But some are not, and a handful of accounts seem to claim far more often than others. Without evidence, you pay for both.
Why you have nothing to push back with
The packing step is the least recorded part of a takeaway. The kitchen ticket shows what was ordered. Nothing shows what actually went in the bag. The person bagging is also answering the phone and talking to riders, so checking every item against the ticket gets skipped exactly when volume is highest.
When a claim comes in, the app gives you a short window to respond, if it asks at all. By the time you see it, the evidence is gone. And because claims arrive scattered across statements from different apps, you cannot see patterns: the same item missing again and again, or the same account claiming every week.
The quiet drain from refunds
| Type of claim | What usually lies behind it |
|---|---|
| Missing side or drink | Items packed from a different area, skipped at peak |
| Wrong item | Similar dishes, unclear ticket or bag mix-up at handover |
| Cold or late | Waiting for a rider, or a rider carrying several orders |
| Whole order missing | Handed to the wrong rider, or a delivery issue |
| Repeat claimant | A small number of accounts claiming unusually often |
Each claim is small. Together they are a real deduction, and they also affect your standing on the apps. The worst part is not knowing which of those rows is the one you can actually fix.
A packing check that leaves a record
What we build adds a light step at the pass, designed for a busy counter rather than a warehouse.
- When an order is ready to bag, its items appear on a screen at the pass as a checklist, taken from the same order feed the kitchen uses.
- The packer taps items as they go in, or scans a bag label. Drinks, dips and sides are highlighted because they are the usual misses.
- An optional photo of the open bag is taken on a fixed camera or tablet above the packing area and stored against the order with a timestamp.
- The rider handover is recorded, with the time and the app, so you can show when the order left.
- When refunds show up in the app statements, they are matched to the order and its packing record, so you can see at a glance whether you have evidence worth submitting through the app's process.
- A report shows claims by item, by time of night and by customer account where the app provides it, so repeat problems stand out.
We keep the step quick enough that staff will actually use it, and we set it up around your existing counter layout. Whether and how you dispute a claim is your decision within each app's rules.
After a few weeks of records
You find, for example, that most missing-item claims are drinks on Friday between eight and nine, when drinks come from a fridge at the other end of the counter. Moving the drinks or adding a prompt fixes that. For the rest, when a claim comes in, you have a photo and a tick list to show. And you can see whether a particular account claims far more than normal, which the app may want to know.
- A record of what went in each bag
- Refunds matched to orders instead of lost in statements
- Patterns by item and time that point to real fixes
- Evidence ready when a claim is worth disputing
Recognise these refund problems?
- Refunds appear on your statements that nobody can explain.
- You suspect some customers claim more often than they should.
- Drinks or sides go missing on the busiest nights.
- You have no photo or record of what left the kitchen.
- You have given up disputing claims because there is nothing to show.