The 3 Amazon Flex pay top-ups most UK drivers never claim — and the one Amazon won't pay unless you ask

If you drive Amazon Flex in the UK and you've ever gone home from a block thinking "I should have been paid more for that," you're probably right — and there's a decent chance Amazon would have paid you more if you'd known to ask. There are three separate pay top-up mechanisms in the Flex system. Two are automatic. The third one is the biggest, and Amazon will quietly never mention it to you because the entire point of it is that you have to claim it yourself.

Most Flex drivers we've seen discussing this on r/AmazonFlexUK fall into one of two camps: drivers who've stumbled into one or two of these top-ups by accident and don't realise the others exist, and drivers who do know about all three but have hit a refusal wall with support and given up. This post is the structural overview neither group can find anywhere driver-facing — what each mechanism is, what triggers it, real amounts other UK drivers have received, and exactly how to push back when support's first reply is the boilerplate denial.

The three mechanisms — at a glance

Top-up	How it triggers	Typical amount	Do you need to claim?
Mileage adjustment	Route mileage significantly above expected	£5 default; £12.50–£39.99 for longer overruns	No — auto-only, cannot be requested
Block-time-overrun ("earnings guarantee")	Block runs over scheduled time on Amazon's systems	Variable — depends on overrun length and block rate	No — auto when triggered
Overtime Payment	You returned late because of factors outside your control	Tiered by 30-min bands at your block's £/hr	Yes — manual claim via Earnings tab

The third one is where the real money is left on the table. We've covered the mileage-adjustment mechanism in the payment-adjustment post already; this piece focuses on the Overtime Payment claim, because (a) it's the one that requires action from you and (b) it's the one most consistently denied on the first attempt.

1. Mileage adjustment — automatic, no claim possible

This is the "payment adjustment for more driving" email. Amazon's logistics system flags routes that went significantly over the expected mileage and sends a one-off top-up, usually within 48 hours. £5 is the default, but for genuinely long overruns the numbers driver community members in r/AmazonFlexUK have reported include £12.50, £25, £31 and one driver describing £39.99 as a personal highest. The clearest amount-to-mileage pairing we've seen is a £25 adjustment for a roughly 200-mile single route a driver shared as their own record.

The thing to know: this cannot be requested. As one driver who's been around long enough to know put it: "you cannot email requesting a mileage adjustment. It is automatic, and automatic only." Support has no manual ability to trigger one. If you didn't get one for a route that felt long, the system simply didn't flag your block-time-to-mileage ratio as anomalous enough. Don't waste a support ticket on it.

What appears to drive the trigger (no Amazon documentation, only driver pattern observation): the ratio of mileage to expected block length. A 2-hour block with 90 miles is more likely to flag than a 4-hour block with the same 90. Block-rate doesn't appear to factor in directly.

2. Block-time-overrun top-up — automatic, different email subject

Different email subject from the mileage one, often described loosely as the "earnings guarantee" payment by drivers (Amazon doesn't use that name in the email — it's just what some drivers call it). This is triggered when Amazon's system itself logs your block ending later than scheduled.

It's similar to the mileage one in being automatic — you don't claim it, it lands or it doesn't. The difference: the trigger is wall-clock block time, not route distance. A driver who finishes a 4-hour block in 4 hours 35 minutes might get this; a driver who finishes a 4-hour block in 4 hours 5 minutes but drove 30 unexpected extra miles is more likely to get the mileage one.

Practical note: if either of these auto-payments shows up, it'll appear in your Earnings within 48 hours of the email arriving. If 72 hours pass and it's still not there, that's the only legitimate reason to message support about a mileage or block-time auto-payment.

3. The Overtime Payment claim — the one Amazon won't pay unless you ask

This is the big one. Distinct from both auto-payments above. Here's the difference: the auto-payments fire when Amazon's system independently detects an overrun. The Overtime Payment claim is for the gap between "your block officially ended" and "you finished returning parcels and could leave the depot" — time that you actually worked but Amazon's automated detection didn't catch.

The rule, per Amazon's own support correspondence summarised by experienced UK drivers: if you went over your block time because of factors outside your control — traffic, road closures, abnormally high stop count, delays at the depot, returning parcels after the marked block end — you are entitled to claim the extra time at your block's hourly rate.

What drivers have reported actually receiving:

A documented claim of 45 minutes at £25/hr being paid in full after a single email to support.
The tariff pattern most often described: on a £20/hr block you get £10 for up to 30 minutes over, £20 for 31–60 minutes over, and so on in 30-minute bands. So the system effectively rounds your overrun up to the next half-hour, then pays the equivalent fraction of your block rate.
One driver who pushed past the 45-minute threshold to drag the overrun out to a full hour received the full hour's pay rather than the half-hour band.

That last point is worth pausing on. If you're going to be 35 minutes over because of a return-to-depot trip, you're in the same payment band (31–60 min) as if you'd been 55 minutes over. The marginal extra effort to push the overrun into the next band can sometimes cost you nothing but does change which band you're in. We're not advising you to deliberately drag out work — but if your overrun was genuinely out of your control and you're at 35 minutes, there's no reason to short-change yourself by not claiming for it.

How to make the Overtime Payment claim

The route everyone uses: open the Flex app, Earnings tab, find the specific block, tap "Contact Support" against that block, choose the topic relating to pay/earnings, and send a short email. Keep it short, factual, and specific to one block — don't bundle multiple weeks of overruns into one email, that's the fastest path to a denial.

What works in the email body:

Block date and start time
The block end time (scheduled) and the time you actually returned the last parcel / left the depot
The specific cause that was outside your control (e.g. "two road closures on the route to the last cluster of drops" or "had to return 6 parcels which took an extra 25 minutes at the depot")
The request: ask to be paid for the [X minutes] overrun at the block's hourly rate

Don't editorialise. Don't tell Amazon their route was badly built. Don't compare to other drivers. The email is doing one job — establishing that the overrun cause was outside your control and the time worked is documented.

What to do when support's first reply is a denial

Be prepared for this. A very common pattern reported by UK drivers is a quick (often within minutes) reply that says some variant of: "We have determined that you were paid in full for the block you delivered, so you will not receive extra payment." This is a tier-1 keyword-matched response. It doesn't mean a human reviewed your case and decided against you.

What works on the second attempt:

Reply on the same thread, don't open a new one. Cite the specific block date and the original ticket reference.
Restate the out-of-your-control cause specifically. If you mentioned traffic in the first email, name the road and the specific delay (e.g. "M62 westbound was closed between J27 and J26 from approximately 18:20–19:05 due to a road traffic collision").
Be specific about timing. Block end was 19:30. Last parcel scanned at 20:15. Returned to depot at 20:42. Therefore claiming for 1 hour 12 minutes overrun.
Reference that you understand the Overtime Payment policy. Don't quote made-up policy text but make it clear you know the entitlement exists for out-of-control overruns.

Drivers who follow this format have reported getting paid on the second reply most of the time. The ones who get denied a third time are usually in one of two situations: the overrun wasn't actually outside the driver's control on the timing log (e.g. the driver was 90 minutes into a 2-hour block with only 10 stops done), or there's no documented cause and the email is reading as speculative. In both cases support has a legitimate reason to deny; you have to be honest with yourself first.

The other quiet money: cancellation pay

Worth a brief mention because it's the fourth payment mechanism most drivers don't fully understand. If Amazon cancels a block (not you forfeiting it), you are normally paid for the full block, with the payment landing in Earnings the same evening. When the auto-payment doesn't fire — and it doesn't always — message support with the cancellation email and a screenshot of the empty Earnings entry, and the manual fix usually lands within 24–72 hours.

The thing to know: this only applies to Amazon-side cancellations. If you forfeited the block yourself, even for a legitimate reason (illness, vehicle problem), there's no automatic payment. The cancellation reason code in the email tells you which type it was.

Standing impact — does claiming hurt your Standing?

Short answer: no, and it's worth being explicit about this because some drivers don't claim out of a vague fear that flagging an overrun "draws attention." The Standing Score system looks at completion patterns, route quality flags, customer feedback, and forfeit/no-show events. It doesn't surface overtime claims as a negative signal. The patterns that actually move Standing in a negative direction are covered in the deactivation post — Overtime Payment requests aren't on that list.

What can affect Standing is if the late drops themselves get flagged. If the last four of your drops were marked late because of a road closure, the late-drop flags are the Standing concern, not your overtime email. The overtime email is a separate workstream that goes through a different team.

The maths — what these top-ups are actually worth

Putting realistic numbers on this for a regular driver doing 4–6 blocks a week:

If 1 in 5 blocks triggers an automatic mileage adjustment at £5 average, that's £40–60 / year of pay you'd otherwise miss.
If 1 in 10 blocks runs late enough to qualify for an Overtime Payment claim and you actually claim it (let's say a £15 average payout), that's £130–195 / year for a 5-block-per-week driver, before the times you push for the next 30-min band.
Cancellation pay isn't a regular event but the auto-pay failure mode happens often enough that knowing to chase it after 24h saves real money.

So the realistic total for a driver who consistently claims is £200–300 / year of extra earnings on top of headline block rate, depending on how often your blocks actually overrun. For a driver who doesn't know to claim, all of it just stays at Amazon.

Sources

Mileage adjustment data drawn from the r/AmazonFlexUK 2026-06-02 "Payment adjustment for more driving" thread (15 substantive driver replies confirming the £5 default and observed amounts up to £39.99). Overtime Payment mechanism and tariff pattern confirmed across r/AmazonFlexUK "If you go over your block, please remember to email and ask for payment" (PatientIceCube), "Don't leave money on the table" (SweatyWookieNuts — claimed 45 min at £25/hr), and the recent 2026-06-01 "Payment adjustment" thread (Icy-Concern7713's tariff description). Refusal patterns and the boilerplate denial text from older r/AmazonFlexUK overtime-payment threads where drivers documented the support reply they kept hitting. Where specific numbers came from a single driver, we've described the range to reflect that no two driver outcomes are identical — claim wording, block length, depot, and cause all move the result.

Disclaimer

This post describes the pay top-up mechanisms Amazon Flex UK drivers have observed and reported — it is not a quotation of Amazon's internal policy. Amazon's actual triggers and amounts can change without notice and we can't guarantee any specific outcome from a claim. Always document your own block timings, route causes, and support correspondence. Grabber is not affiliated with, endorsed by, or built by Amazon. Amazon Flex is a trademark of Amazon.com, Inc.