Implement order cancellation and refund handling for Uber Eats Marketplace orders via the Partner API
domain: developer.uber.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
Verify Uber Direct webhook signatures — the full failure-mode walkthrough related to developer.uber.com, checked against official docs, with linked verified routes.
Steps
Receive an order cancellation trigger either from a customer request, an operator action, or an inventory-out event
Call the Uber Eats order cancellation endpoint with the order ID and a cancellation reason code
Confirm the response indicates the cancellation was accepted; Uber Eats may reject cancellations on orders already picked up by a courier
If a refund is applicable, Uber Eats processes the refund to the customer automatically for marketplace-facilitated transactions — confirm this in the API response
Log the cancellation reason, timestamp, and any Uber Eats-assigned cancellation code for reporting and dispute resolution
Known gotchas
Excessive cancellations by a merchant can trigger Uber Eats account penalties or reduced search ranking — track your cancellation rate metric
Cancellation eligibility depends on order state; once a Dasher has picked up the order, merchant-initiated cancellation is blocked or may incur a fee
Uber Eats distinguishes between merchant-fault and customer-fault cancellations for fee and refund purposes — supply accurate reason codes
Give your agent this knowledge — and 15,800+ more routes
One MCP install gives any agent live access to the full route map across 5,800+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?