Delivery App Compensations: The Complete Recovery Guide for Restaurants

Short answer: Compensations are amounts deducted from the restaurant and returned to customers over order complaints — and they're the most neglected line on delivery-app invoices because they scatter across different labels and never appear in full on the invoice. In one month Ballurh analyzed for a restaurant on Jahez, 64% of orders carried compensations — much of it disputable, and restaurants using Ballurh recover around 80% of their eligible claims.

How much was deducted from your restaurant last month under compensations?

If your answer is a number off the invoice, it's almost certainly an undercount. On Saudi delivery platforms — HungerStation, Keeta, Jahez, The Chefz, Ninja — compensations never sit in one clean line: some are folded into aggregate items, some hide between payment movements and never reach the invoice at all, and some exceed the value of the order itself. Across Ballurh's client network, we've seen restaurants lose the equivalent of a full marketing budget to this line every month — then book it as "normal operating cost." It isn't, and most of it has a formal recovery path. This guide gives you the full method.

First: refund vs. compensation

Many accountants and operators conflate the two, and the confusion kills follow-up:

• Refund: the order value (full or partial) returned to the customer, usually on cancellation. On some platforms it's deducted straight from payments and never appears on the invoice — you find it only as a negative movement next to the original order in the payments report.
• Compensation: an amount returned to the customer over a complaint on a completed order (missing item, error, quality), added to the restaurant's deductions — on some platforms a near-flat goodwill amount set by complaint category.
• Merchant compensation: the reverse flow — the platform pays you back when the fault was its own (courier delay, say) or when your dispute is accepted. In contracts we've reviewed, one platform automatically returns roughly 75–80% of an order's value when the cancellation was on its side.

The accounting rule: refunds reduce sales, compensations increase deductions — and each needs its own tracking.

Where compensations hide (four hiding spots from our reviews)

1. Aggregate lines: HungerStation's orders report, for example, merges compensations and refunds into a single line called "seller fees" — one number swallowing two different deduction types.
2. Between payment movements: on some platforms refunds skip the invoice entirely — a positive and a negative movement sit side by side in the payments report, which is why the sales summary never matches net payments; the gap between them is the refund.
3. Unexpected labels: on other invoices they surface as "platform deductions from the merchant" or inside subsidy lines — and a single order can appear two or three times (original positive, refunds negative).
4. Compensations larger than the order: yes, it happens. Analyzing one restaurant's Jahez compensations, we found 58 orders in a single month where the customer was refunded more than 100% of order value — a SAR 50 order refunded at 70 or 80. We also found orders compensated two, three, even four times: 91% of compensations were single movements, but 7% carried two or more — and those alone deserve immediate disputes.

The monthly plan: four steps that turn compensations from a leak into a managed number

1. Collect. Download the compensation report and the orders report from each platform for the same period and set them side by side: what share of sales do compensations take? What share of orders? (The affected-order ratio is a sharper signal than the amount alone.)

2. Classify. Bucket compensations by their share of order value: above 100% (top priority), 50–99%, below 50%. Then by movements per order: anything compensated twice or more goes straight to the dispute list. Compare the month to your trailing average to tell a one-off operational incident from a pattern.

3. Dispute. Each platform has a path (the map below). The shared rules: dispute within the window — what expires is gone; attach proof (a photo or video of the completed order at handover); and for bulk disputes, prepare one clean unified file: order number, order value, compensation amount, the platform's stated reason, your dispute reason, and an open-permission attachments link so the support agent opens everything friction-free.

4. Track and learn. Every platform shows dispute status (under review / accepted / rejected), and rejections usually come with reasons — read them closely: they teach you how to win the next one, and they flag the operational gaps (photography, packaging, portioning) behind repeat complaints. Close the loop operationally too — see cancellations and timeouts.

What gets accepted — and what gets rejected (from thousands of disputes)

Across Ballurh's client dispute data, the split of compensation causes is remarkably stable: ~90% missing, wrong or damaged items, ~10% quality complaints (taste, smell, doneness). The distinction decides your dispute strategy:

• Missing / wrong / damaged: the photo decides it. Clear proof at handover means full or partial acceptance in most cases — which is why value recovery in this category runs near-complete.
• Quality: the hardest category — on average one or two in ten get accepted, because "taste" and "smell" don't show in a photo. Discipline changes the math, though: one client who documents every order photographically reached a 50% acceptance rate on quality disputes.
• Usually rejected: "restaurant closed" and "item unavailable" claims (the platform has the logs), and "slow preparation" on platforms that timestamp prep and pickup to the second.

Three field notes: some platforms ask for a clearer photo within a set window (around 7 days) — so keep order photos for at least a month; some name the exact wrong item in the complaint while others only say "wrong items" — build your documentation accordingly; and new disputes surface on some dashboards within one to 24 hours of the complaint, so a daily morning review catches everything in time.

The dispute map, platform by platform

Paths below reflect the interfaces and contracts we had reviewed as of the update date — platforms change their UIs, so treat this as a working guide:

• Jahez: compensations live in the compensation-hub report, where reasons are often generic ("missing item"). Dispute by email to the support team with your account manager in CC, attaching one unified case file plus links to evidence. A key advantage: many contracts allow disputing periods up to a month back — check your contract's compensation clause, with the full playbook in the Jahez compensation guide.
• HungerStation: compensation is often a near-flat amount by complaint category (around SAR 15 in contracts we've reviewed), and refunds pass between payment movements while the report merges them under "seller fees." Dispute via Help Center → new inquiry → invoices & payments → compensation request with details and attachments; after a case closes you get about 3 processing days with no replies afterward — though you can open a fresh request. Details in the HungerStation compensation guide.
• Keeta: two categories — refunds (full or partial) and compensations — with deductions sitting under "platform deductions from merchant." Dispute from Orders → refund orders → the dispute icon beside the order, picking a category, writing details and attaching photo or video, then track status on the same page with the dispute filter. Keeta automatically returns about 75–80% of an order's value when the cancellation is its fault, contract-dependent.
• Ninja: four weekly tax invoices plus a monthly compensation document (five attachments a month), transparently showing commissions and bank fees on cancelled orders before reversing them. Dispute from order compensations → the view icon beside the order → the dispute form (up to 3 photos) → submit, and track under "compensation disputes" with status filters — rejections arrive with reasons.
• The Chefz: the compensation line sits inside the two monthly invoices, and disputes run from invoice management → order deductions → the view icon → details and attachments → submit. Its unique feature: an archive documenting every closed case with an official text explaining acceptance or rejection.

Why it's worth the effort

Because the numbers say so. When 64% of a month's orders carry compensations, and when orders exist that were refunded above their own value — or refunded four separate times — you're not looking at an operating cost. You're looking at lost revenue with a formal recovery channel. The difference between restaurants that recover and restaurants that bleed isn't luck: it's running the four steps every month, inside the windows, with the right evidence.

Disputes recover your money — fixing root causes stops losing it

The most powerful outcome of compensation analysis is discovering that the cause often isn't customer complaints at all, but a silent error in registration or operations data. Two real cases from Ballurh's clients:

• A wrongly registered location: a multi-branch restaurant had one branch's location registered incorrectly on the apps. Every time: the courier can't find the branch, the order is never picked up, the customer gets nothing — and the restaurant loses the ingredient cost and absorbs compensation for the full order value plus delivery. Across dozens of locations, nobody spotted the pattern. Correcting that single location registration saved the restaurant about SAR 80,000 per month it had been losing without knowing.
• Mismatched working hours: branches were receiving orders in hours the kitchen wasn't actually operating, because the hours registered on the apps didn't match reality — and with many branches, no one noticed. Ballurh's system caught the pattern, our team verified it, and the working hours were corrected.

The lesson: a recurring compensation is a symptom; its root is usually elsewhere — branch data, working hours, inventory, or prep. Disputing alone gets this month's money back; fixing the root stops the loss every month.

How Ballurh helps

The real problem isn't any single step — it's repeating all of them monthly across five platforms, five report formats and five dispute paths. Ballurh consolidates your compensations from HungerStation, Keeta, Jahez, The Chefz and Ninja, unpacks the merged lines, flags repeat and above-order-value compensations, and runs the dispute cycle and its follow-up for you — then fixes compensation causes at the root, as in the two cases above. The result across our client network: around 80% of eligible compensations recovered by order count — and by value, recovery approaching 100% of deductions on some platforms — with one client recovering over SAR 100,000 in under 90 days. For calibration: the normal dispute rate we see is about 3% of total orders. All built on 17M+ analyzed transactions.

How much eligible compensation did you leave on the table this month? Calculate your recovery opportunity or book a demo.

Frequently asked questions

What's the difference between a compensation and a refund on delivery apps?

A refund returns order value (full or partial) to the customer, usually on cancellation, and is deducted from your payouts. A compensation reimburses the customer over a complaint on a completed order and is added to your deductions. Some platforms never show refunds on the invoice, so they must be tracked from the payments report.

Can I dispute old compensations?

It depends on platform and contract: some contracts allow disputes reaching a month back, while some platforms close replies days after a case closes but allow a fresh request. The working rule: make compensation review a fixed monthly habit so you never depend on exceptions.

How do I raise my dispute acceptance rate?

Three factors: visual proof (photo or video of the completed order at handover), precise details (order number, value, and your specific dispute reason), and clean bulk organization in one file with open-permission attachment links. Disputing inside the window is a requirement, not a bonus.

Am I charged commission on cancelled orders?

On some platforms, yes — we've seen invoices showing basic and bank commissions on cancelled orders, and others reversing them as positive movements. So don't just sum the lines: reconcile the orders report against the invoice to confirm cancelled-order commissions actually came back to you.

When is a compensation an operations signal rather than an accounting one?

When it repeats on the same items, branches or hours: recurring missing-item claims point to inventory or prep issues; recurring peak-hour compensations point to kitchen overload. Analyze compensations monthly by item, branch and hour, and you'll know where to fix operations instead of paying for them every month.