Skip to main content

About

Hi — I'm Seda Ayner, the person behind Grabber and this blog.

I started delivering for Amazon Flex in the UK in late 2025. The work itself was fine. The bit that wore me down was the offer screen: spending most of my downtime refreshing for blocks that disappeared the moment I tried to tap them, often because someone with a faster phone or a quicker thumb beat me to it. After enough of that I sat down to build a tool that would screen and accept blocks I actually wanted, on my own phone, without the cloud-bot baggage that triggers Amazon's enforcement.

That tool is Grabber. It's an Android app for Amazon Flex couriers in the UK. It runs as an Accessibility Service on your own device, reads the Flex app's offer screen, and one-tap accepts blocks matching filters you set (minimum £/hr, depot station, vehicle type, time window). No cloud server, no shared account, no subscription. First five blocks are free; after that it's a pay-as-you-go credit pack — £1 for ten jobs, £8 for a hundred, £35 for five hundred. Full product overview: what an Amazon Flex block grabber actually costs in 2026.

What this blog is

This blog is the long-form companion to Grabber. Each post is the answer to a question I either hit myself or kept seeing other drivers ask:

How I write these posts

Every factual claim about Amazon Flex (cap rules, escalation paths, forfeit timing, app behaviour) is cited from public sources at the bottom of each post. If I can't source a specific claim, I either flag it as uncertain or leave it out. I've also rewritten earlier posts where I overstated detail — when a UK driver pointed out that a specific in-app UI element I'd referenced didn't actually exist, I removed the claim and apologised in the comment thread on Reddit. I'd rather get fewer things right than more things wrong.

Disclaimer

Grabber is not affiliated with, endorsed by, or built by Amazon. Amazon Flex is a trademark of Amazon.com, Inc. Using any third-party tool to interact with the Flex app may breach Amazon's terms of service; the choice to use one is yours.

Getting in touch

All contact runs through GitHub. Open an issue and tag it appropriately:

  • Bug reports + feature requests: github.com/aynerseda-droid/gtrabber/issues
  • Blog post corrections, journalist queries, partnership ideas: open an issue at the same repo with a clear label (blog, press, partnership) — I'll route it.
  • Privacy / data requests: see the Privacy Policy for how to file one through GitHub.

If you're new and want to try the app, latest release is here: github.com/aynerseda-droid/gtrabber/releases/latest — APK SHA-256 and VirusTotal URL scan are published in the release notes.

Comments

Post a Comment

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. ...
Post a Comment
Read more

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...
Post a Comment
Read more

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...
Post a Comment
Read more