Skip to main content

Amazon Flex UK weekly hours cap — how the 40-hour rolling window actually works in 2026

One of the most common questions on UK Flex driver threads is some version of "when does the cap reset?" The short answer is that it doesn't reset on a calendar day — it's a 40-hour rolling 7-day window, which behaves quite differently from how most drivers expect.

This post walks through what that mechanic actually means, why drivers misread it as "every Monday", what changes during peak periods, and what to do about it in your scheduling.

None of this is legal or contractual advice. It's drawn from public driver guides — sources are listed at the bottom. Where a detail isn't confidently verifiable from public sources, we say so rather than guess.

The plain version

You can work up to roughly 40 hours of Amazon Flex blocks in any rolling 7-day period. That's not "40 hours per calendar week" — there's no Monday morning reset that hands you a fresh allowance. It's a sliding window: at any given moment, Amazon looks at the last 168 hours and adds up the block time you've worked. If that total is below the cap, more blocks become available to you. If it's at or above, you'll stop seeing new block offers until enough of those hours fall off the back end of the window.

So if you worked a 4-hour block on Monday morning at 06:00, that 4 hours frees up again the following Monday morning at 06:00 — not on the calendar date the rest of the world thinks of as a "new week".

Why drivers misread it

A few reasons the "weekly reset" mental model sticks despite being wrong:

  • Pay arrives on a fixed weekly cadence. If your payment cycle is Wednesday-to-Wednesday it's natural to assume your working cycle follows the same boundary. It doesn't.
  • Visual cues in the app are time-bucketed. The earnings and schedule screens display in week-shaped chunks, which reinforces the calendar model even though the cap is computing something else underneath.
  • Other gig platforms work differently. Drivers used to other delivery apps where caps reset at midnight expect Amazon to behave the same way.

The practical consequence: drivers who think "I have a fresh 40 hours every Monday" often stack a heavy front-half of the week, hit the cap on Wednesday, then can't find any offers Thursday-Friday and assume something is wrong with their account. Nothing is — they're simply still inside their rolling window from the previous week.

What changes in peak periods

Public driver guides report that during peak demand windows — Prime Day, the run-up to Christmas, and (in some accounts) tax season — Amazon temporarily raises the rolling cap closer to 50 hours. We can't confirm the exact uplift number from official sources, and it appears to vary year to year and possibly by region. If you're getting more block availability than usual in November or December, that's likely why.

Outside of those peak windows, the 40-hour figure is the operating ceiling that most public guides converge on.

What counts toward the cap

The cap accumulator is calculated on the scheduled block duration of each accepted block you complete. A 3-hour block adds 3 hours to your rolling total whether you finished it in 2 hours or in 3:15.

What we can't confidently confirm from public sources, and what we'd encourage you to verify against your own account:

  • How blocks you forfeited before the start time are treated (probably not counted toward the cap, since they were never worked).
  • How blocks you cancelled during the block are treated (partial, full, or zero counted toward the cap — public driver reports differ).
  • Whether the depot wait time before a block officially starts counts.

If anyone has hard documentation on those edge cases, please share — we'd rather correct this post than leave a guess in it.

What it looks like in practice when you hit the cap

When you've used up your rolling allowance, the offers screen simply stops showing new blocks. You won't get an error message or a banner saying "you've hit the weekly cap" — the offers just dry up. As soon as enough of your earlier work rolls off the 7-day window, blocks reappear.

This is why the diagnosis is so confusing: there's no obvious in-app signal distinguishing "you've hit the cap" from "there genuinely aren't any blocks available right now". The way to tell them apart is to look at how many block hours you've worked in the last 7 days. If you're at or above 40, the cap is the likely explanation. If you're well below 40, it's a supply issue.

Planning around it

Three patterns drivers report as effective once the rolling mechanic is internalised:

  1. Spread the work. Roughly 5-6 hours a day across 6-7 days keeps you under the cap and keeps offer flow consistent. Stacking 10-hour days early in the week creates an unintended "no blocks Thursday-Friday" period.
  2. Track your own 7-day running total. A simple note on your phone with date + block hours, deleting entries older than 7 days, beats trying to guess from the app's calendar views.
  3. Treat peak periods as a different game. If the cap floats up to ~50 in December, the same "spread it evenly" rule applies, just with a higher ceiling. Don't stack 12-hour days expecting the cap to clear faster — the rolling-window mechanic doesn't change.

Common myths worth dropping

  • "The cap resets on Monday." No — there's no Monday boundary, only the rolling 168 hours from now.
  • "If I work overtime now, I get extra blocks later." The cap is fixed at any given moment, not pooled. Working extra now reduces what's available to you for the next 7 days exactly by the amount you worked.
  • "Forfeiting a block frees up cap hours." Forfeiting affects your standings, not your cap. The cap counter only changes when worked hours fall off the back of the rolling window.
  • "I can ask support to lift the cap." Public reports suggest the cap is a system-wide setting, not something support staff can adjust per driver.

How this relates to standings and deactivation

The weekly cap is a separate mechanism from your reliability standing. Hitting the cap doesn't damage your standing — it just means no new offers temporarily. Standings are affected by cancellations, missed deliveries, and other reliability metrics. We covered what actually moves your standings in a separate post: what actually gets you deactivated from Amazon Flex.

If you're working out whether a specific block is worth taking in the first place — once you've folded in drive in, depot wait, and unpaid drive home from the last drop — the headline £/hr can be misleading. We did the maths here: how to tell if an Amazon Flex block is actually worth accepting.

Sources

None of this is legal or contractual advice. Grabber is not affiliated with, endorsed by, or built by Amazon. Amazon Flex is a trademark of Amazon.com, Inc.

Related reading:

Comments

Popular posts from this blog

How to tell if an Amazon Flex block is actually worth accepting — the real maths every UK driver should run

Amazon Flex shows you a headline rate on every block offer. £45 for 3 hours. £18.50/hr. £22.00/hr. Those numbers look fine until you put them through the actual maths a driver does after the fact, and most of them turn out to be a different number than the one on the offer screen. This post is the maths you should be running before you accept, not after. It's the same conversation that happens in every UK driver thread on Reddit — most drivers eventually find their way to a version of this calculation, but it usually takes a few burnt Saturdays first. The headline number is misleading on purpose The £/hr Amazon shows you is the block window divided by the pay. That's the time the route itself takes, from your first drop scan to the last. Everything outside that window — and there's a lot of it — is unpaid. The real time you spend on a block looks more like this: Drive to the depot. Unpaid. Depends on which station you got the offer from. Depot wait time. ...

Amazon Flex bot detection in 2026 — why on-device block grabbers differ from cloud commission bots

Amazon's 2025 enforcement push made one thing clear: not all third-party block grabbers carry the same risk. The same Reddit threads that report "my account got flagged after I started using bot X" almost never describe the same architecture as the apps that don't show up in deactivation stories. The difference isn't whether automation is allowed — it isn't, per Amazon's terms. The difference is which detection signals each kind of tool leaves behind. This post is a technical breakdown of those signals: what cloud commission bots look like to Amazon's backend, what on-device accessibility-based grabbers look like, and what Grabber specifically does to keep its cadence pattern closer to a human driver's. None of this is a claim of undetectability — that doesn't exist. It's an explanation of why two block grabbers from the same Reddit thread can have very different deactivation profiles. What Amazon's 2025 enforcement actually targe...

What actually gets you deactivated from Amazon Flex in 2026 — and what doesn't

Every Amazon Flex driver thread eventually circles back to the same anxiety: am I about to lose this. Deactivation is the only thing about Flex that's genuinely punitive — every other problem (rate variance, station drama, route quality) is annoying but solvable. Deactivation is final. This post is what's actually known about Flex deactivation in 2026 — from Amazon's own enforcement posts, from driver reports across r/AmazonFlexUK and r/AmazonFlexDrivers, and from the patterns that appear consistently in deactivation stories. It isn't insider knowledge. It's the public picture, organised so you can stop worrying about myths and focus on the things that actually matter. What Amazon's terms actually say The Independent Contractor Agreement — the contract you ticked when you signed up — lists clear grounds for termination. Paraphrased, the main ones are: Failure to deliver in accordance with Amazon's operational standards. Theft, contraband, or v...