On Uber Eats the money moves before you hear about it. A customer reports a problem with an order, attaches a photo, and Uber issues a refund; if Uber attributes the problem to the restaurant, the amount appears on your payout statement as an order error adjustment. You find out when you read the statement, or when the notification lands in Uber Eats Manager — after the fact, with the customer's photo already accepted as the evidence.

This page is about the cases where that photo does not show what it claims to.

How Uber Eats decides who pays

Uber's partner terms split responsibility in the usual way: errors at the restaurant (missing items, wrong items, food quality) are charged to the restaurant; problems in delivery are Uber's. In practice the split is decided by the customer's report and the category they pick, checked against a few automatic signals — order value, how often this customer reports problems, whether the restaurant used Uber's order-accuracy tools on that order.

Uber publishes some protections for restaurants, and they matter. Orders where you confirmed items at the pass through the app, or attached a pass photo, are much harder to charge back to you as "missing" or "incorrect". Quality complaints ("food was cold / damaged / inedible") with a photo are the category where the photo does the most work and where your side is thinnest unless you have a photo of your own.

Where the dispute lives

In Uber Eats Manager, adjustments are listed against the order with the customer's reason and, where they supplied one, their photo. Each adjustment shows whether it can still be disputed and for how long; the window is short and strictly applied, so treat the notification as a deadline, not an FYI. The dispute form is a text box plus attachments. A human reads it, usually quickly, usually with a queue behind them.

What actually reverses an adjustment

From what our customers report back, disputes that succeed share a shape:

  • A pass photo of the specific order, timestamped, showing the items as sent. If you use Uber's photo confirmation at handover, reference it.
  • A concrete statement about the customer's photo: the packaging is not yours; the image shows signs of editing in the area of the alleged defect; the file carries no camera metadata; the capture time predates the order. The evidence guide has the exact wording and a template that fits the text box.
  • The order record placed next to the photo so the agent does not have to look it up.

Disputes that fail are the ones that argue about your standards instead of this order. "Our kitchen is spotless" is not evidence; a picture of the bag at 19:42 is.

The photo check, in practice

Before you write anything, download the customer's photo from the adjustment and check it. A darkened original, an inpainted hair, a reused image from another restaurant — the common tricks are described in how to tell if a complaint photo is edited. FraudBite gives you the same answer in seconds as a risk score, a heatmap of the suspect regions and a plain-language list of findings, exported as a PDF you can attach to the dispute.

Read the score for what it is: a signal. A high score means the image deserves a closer look and a technical, evidence-based reply — not an accusation. A low score, with a pass photo that shows a missing side, means the customer is right and the adjustment should stand.

Reducing Uber Eats adjustments before they happen

  • Use the app's order-accuracy features on every order; they are your cheapest pre-emptive evidence.
  • Photograph the sealed bag with the receipt visible.
  • Keep a simple log of disputed adjustments and outcomes; a pattern from one address is worth raising with your Uber account contact.

Uber Eats is a third-party platform; FraudBite is not affiliated with it. Interface details change — verify current dispute windows and locations in your own Uber Eats Manager.