Amazon Flex appeal process (UK 2026)

Summary

Amazon Flex UK uses a "standing" system from Fantastic to At Risk and can deactivate drivers whose standing falls after complaints, late returns, missing parcels or policy breaches. Appeals usually go first through the in-app or email support channel and, if that fails, some UK drivers report success by escalating a short, factual appeal with evidence to senior Amazon email addresses. Standing-score appeals are about getting back on the app, while worker-status arguments under Uber BV v Aslam [2021] UKSC 5 are about longer term rights and possible tribunal claims, so they are separate tracks that sometimes run in parallel.

Key facts (UK 2025 to 26)

Amazon Flex UK rates driver "standing" as Fantastic, Great, Fair or At Risk, based on recent delivery history, including on-time arrivals, successful deliveries, customer feedback and policy compliance; most drivers sit in Great or Fantastic, and falling to Fair or At Risk can restrict or remove access to blocks. Standing rules described in current guidance and videos in 2025.

Drops in standing come from "issues" such as late arrivals at the depot, late parcel returns, missed blocks, using unapproved third parties, and customer complaints about missing or damaged parcels; some UK drivers report deactivation after around 8 to 10 recorded "issues", although Amazon does not publish an official threshold.

Amazon Flex deactivation emails usually give a short reason, for example "repeated delivery issues", "using third parties" or "policy violations", and say the driver can respond within a set period, often 10 days, to appeal. This is reflected in guidance for Flex appeals in 2025.

The official appeal channel is via reply to the termination email or through the Flex app or support link, but UK drivers on r/AmazonFlexUK report that serious cases often need escalation to senior addresses such as jeff@amazon.com or jeff@amazon.co.uk to get a human review.

Evidence that helps appeals includes route and GPS data, photos of delivered parcels, depot scan logs, proof of safe place instructions and screenshots of app glitches; emotional "sob stories" without evidence might occasionally work, but more consistent success reports come from factual, apologetic appeals which explain what went wrong and how it has been fixed.

Response times for appeals vary. Some UK drivers report replies from escalated "Jeff" emails within one or two days, others hear nothing for weeks.

Uber BV v Aslam [2021] UKSC 5 established that Uber drivers were "workers" with rights, which Flex drivers and unions now use as a reference point in arguments that Amazon controls their work in similar ways. Any serious legal challenge on worker status or unfair dismissal would still have to go through ACAS early conciliation within three months minus one day of deactivation.

Legislation, case law, regulation

Uber BV v Aslam [2021] UKSC 5, Supreme Court decision confirming that Uber drivers were "workers" and entitled to rights such as minimum wage and holiday pay, cited by unions and lawyers when arguing that other app-based drivers like Amazon Flex couriers should also have worker status.

Employment Rights Act 1996 and later amendments, which give workers rights against unfair deductions, whistleblowing detriment and other protections, used as a model when lawyers assess whether a Flex driver can bring a claim by analogy with Uber drivers.

ACAS rules on early conciliation and tribunal time limits, which in 2025 to 26 still require starting ACAS within three months minus one day of dismissal or other act complained of, if an Amazon Flex driver wants to test worker status or unfair treatment in a tribunal.

General UK equality and health and safety law, including the Equality Act 2010, which can be relevant if a Flex driver argues that deactivation or standing downgrades are discriminatory rather than just performance based.

How it actually works

From a UK Flex driver's point of view, the process starts long before deactivation, with the standing score. After each block, Amazon logs data such as on-time arrival at the depot, how many parcels were delivered successfully, whether any parcels were returned late, and any customer complaints about missing or unsafe deliveries. That data feeds into the standing system and into a "history points" log inside the app that only some drivers ever see.

If a driver stays Fantastic or Great, they see more and better blocks. Once they fall to Fair or At Risk, they start losing access, especially to high paying routes. Drivers on UK Facebook groups complain that Amazon seems to hit them with more "dings" when they are Fantastic or Great and fewer when they are already At Risk, which suggests internal thresholds. Common triggers are late returns of undelivered parcels, missed blocks, arriving late at the station, repeated "no parcel" or "missing parcel" complaints, scans that do not match GPS traces, and any sign of using unapproved third parties to deliver.

When Amazon decides to deactivate, the driver usually gets an email and an in-app message saying their access to Amazon Flex has been revoked for policy reasons. The email usually has a line such as "You may respond within ten days if you believe this decision is in error" and may include a generic link to Flex support. This is the first chance to appeal. The official guidance and third party advice in 2025 say the appeal should be sent by replying to the termination email or through the app's help contact, kept concise, and focused on explaining the issues listed and providing any evidence.

In practice, UK drivers often report that the first-line support reply is a template confirming the decision, with no real explanation. That is when many drivers try escalation. Threads in r/AmazonFlexUK and Facebook groups mention emailing jeff@amazon.com or jeff@amazon.co.uk with a short, polite appeal. The pattern that seems to work is:

Subject that clearly states "Amazon Flex deactivation review request, UK driver"

A short introduction thanking Amazon for the opportunity to deliver and summarising length of service and standing history.

One paragraph explaining what Amazon says went wrong, for example "late returns" or "missing parcels".

A factual explanation of the circumstances, where the driver accepts responsibility for anything they genuinely did wrong, apologises, and explains changes such as better alarms, new route planning or childcare cover.

A bullet list of evidence attached, such as GPS tracks, depot CCTV references, photos of parcels at doors and screenshots of safe place instructions.

A final request for a second review and reinstatement or at least a clearer explanation.

Drivers who report successful appeals usually describe that format. They emphasise taking responsibility where they can, apologising, explaining genuine stress or family issues without making excuses, and showing exactly how they will avoid repeat problems. Appeals that are purely angry, deny everything without proof, or accuse Amazon of targeting them personally get either no reply or a short "decision stands" message.

The data that actually moves the needle is the same data Amazon uses to decide standing in the first place. This includes the timestamps from depot scans, GPS records of where the driver was at delivery time, whether customers claimed non delivery, whether the driver took delivery photos or scanned barcodes correctly, and whether parcels were returned and scanned back in within Amazon's rules. If the driver can show, for example, that they were physically at the right address at the right time, that their delivery photo shows the parcel in a safe place, and that the return system was down on a day when Amazon counted late returns against them, they have a more credible case.

Standing-score appeals and legal worker-status arguments are different tools. The standing-score appeal, through support and escalation emails, is about persuading Amazon to reactivate the account and restore blocks. Legal arguments that Amazon Flex drivers are really "workers", like Uber drivers in Uber BV v Aslam [2021] UKSC 5, are about pay, holiday, and unfair treatment. A driver might win reactivation without ever going near a tribunal. Or they might lose reactivation, then contact a union or law firm such as Leigh Day or Bates Wells to look at ACAS early conciliation and possibly a tribunal claim, arguing that Amazon's level of control looks like worker status. In that case, every email and piece of evidence used in the standing appeal becomes part of the legal file.

Worked example

Take a 34 year old Amazon Flex driver in Birmingham who has been doing Flex around childcare. In the 2025 to 26 tax year he is aiming for around £42,000 in turnover and expects about £8,000 in allowable expenses for petrol, insurance and car maintenance, similar to many full time gig drivers. One week in November 2025 he has a bad run. His child is ill, he returns several parcels late and misses one block entirely. Customers also lodge two "no parcel received" complaints for a Friday evening route.

The next week he opens the Flex app and sees his standing has fallen from Fantastic to At Risk. A few days later he receives an email saying his Amazon Flex agreement has been ended because of "repeated delivery issues and policy violations", including late parcel returns and customer complaints. The email says he can reply within ten days if he believes the decision is in error.

He does not panic. First, he pulls his own records. He exports GPS logs from his phone for the dates of the complaints. He checks photographs he took of parcels on doorsteps, which the app encourages. He reviews the Flex app's history to confirm the block times, the parcels returned to the depot and the times they were scanned back in.

He then replies to the termination email. He writes:

That he has been a Flex driver in Birmingham for two years, generally Fantastic or Great standing.

That he understands Amazon has concerns about late returns and two missing parcel complaints in the week of 10 to 16 November 2025.

That his child was seriously unwell that week and he accepts responsibility for a late block and some late returns, and apologises.

That he has now arranged regular childcare cover and will not book blocks unless he has back up.

That he has attached GPS logs and delivery photos for the two "missing parcel" stops, which show him at the right address and the parcels left in the safe places listed in the app.

That he respectfully asks for a second review of the deactivation given his long positive history, the unusual family emergency and the evidence showing that at least those parcels were delivered.

He keeps the email to about 300 words, attaches the evidence and sends it. If he receives a template refusal after a few days, he escalates by sending a similarly structured email to jeff@amazon.co.uk, mentioning the dates, his previous standing and the evidence already submitted, and asking for a member of the executive escalations team to review the case. In that escalated email he again accepts responsibility, apologises, and sets out how he will avoid repeat problems.

If Amazon reinstates him, his standing may come back as Fair or Great and he will have to rebuild trust by completing blocks without issues. If Amazon refuses and he believes the deactivation is unfair, especially if he thinks the data is wrong or he has been singled out because of something like race, immigration status or union activity, he can at that point speak to a union or firm like Leigh Day and look at ACAS early conciliation before the three-months-minus-one-day deadline from the date of the termination email.

What Reddit, TikTok and forums get wrong

Misinformation: "If your standing drops from Fantastic straight to At Risk, there is nothing you can do, it is all automated and appeals never work." This kind of fatalistic comment appears in r/AmazonFlexDrivers and UK Facebook groups after sudden standing drops. Correction: While Amazon's first decisions are heavily automated, UK drivers report some successful deactivation reversals after well structured escalated appeals with evidence sent to senior addresses. The internal data that caused the drop is still human readable, and pointing to specific errors or context can make a difference, especially when problems are temporary or caused by system glitches.

Misinformation: "You should send the same long story every day to Amazon support until they give in, that proves you are serious." Some third party "appeal" sites advise daily repeated emails with emotional narratives. Correction: Amazon's own processes and UK driver reports suggest that spammy repeated appeals are more likely to be filtered or ignored. The better pattern is one or two concise, factual appeals that accept responsibility where needed, show concrete changes and attach real evidence.

Misinformation: "Worker status cases like Uber BV v Aslam mean Amazon cannot deactivate you once you are on Fantastic, they have to treat you like a permanent employee." This misunderstanding shows up in comment threads about Uber and Amazon. Correction: Uber BV v Aslam [2021] UKSC 5 did not ban Uber from terminating or suspending drivers, it recognised them as workers with certain rights. Amazon Flex drivers may have similar arguments, but those would be tested in tribunals on a case by case basis. Even if a driver is legally a worker, they can still be fairly dismissed for genuine performance and misconduct issues, so standing-score appeals and legal worker status arguments are related but separate fights.

Action steps for the reader

Check your Amazon Flex standing regularly and treat any move from Fantastic or Great down to Fair as an early warning sign, not something to ignore.

As soon as you receive a deactivation or "At Risk" standing email, save it, screenshot it and note the date, since that date will matter if you ever need ACAS early conciliation.

Before sending an appeal, collect your own data: GPS logs, delivery photos, depot scan times, screenshots of safe place instructions and any app outage messages.

Send a first appeal by replying to the termination email or through the Flex support contact, keeping it short, factual, apologetic where you were at fault, and clear on what you have changed.

If you get a template refusal or no useful reply, send a concise escalation email with attachments to the senior address used by UK drivers, such as jeff@amazon.co.uk, clearly labelling it as an Amazon Flex UK deactivation review request.

Avoid copying "sob story" scripts you see on TikTok or forums without tailoring them, and never admit to using unapproved third parties or any behaviour that clearly breaches Amazon's policies.

If you think Amazon's control over your work is similar to Uber and you have a potential discrimination or unfair treatment claim, speak quickly to a union or law firm that knows gig work and start ACAS early conciliation within three months minus one day of the deactivation date.

Related tools GigKiln should build

Amazon Flex standing and deactivation appeal letter generator that asks about alleged issues, pulls in evidence and produces a short, UK-specific appeal email template.

Standing trend tracker where drivers can log "dings", see how close they may be to Fair or At Risk, and get advice on how many clean blocks they need to repair their standing.

Evidence pack checklist for Amazon Flex, showing drivers what to capture on every block so they are ready if they ever need to appeal missing parcel or late return allegations.

ACAS deadline calculator and reminder tool that turns a deactivation date into the last safe day to start early conciliation and sends alerts.

Worker-status argument primer that compares Uber BV v Aslam style factors with Amazon Flex practices, to help drivers and advisers decide when legal status arguments might be worth a test case.

Related guides

"Amazon Flex standing scores in 2025 to 26, how Fantastic, Great, Fair and At Risk really work", plain English breakdown of scores and triggers.

"Amazon Flex deactivation and how to write an appeal that gets read", step by step for UK drivers.

"What to record on every Amazon Flex block to protect yourself", evidence habits for missing parcel and late return disputes.

"Worker status, Uber BV v Aslam and what it could mean for Amazon Flex drivers", explaining how the Uber case might apply and what is still untested.

"Losing Amazon Flex income overnight, how to steady your finances and tax in 2025 to 26", linking deactivation to tax, NI and cash flow.

Sources

YouTube, Amazon Flex guidance video, "Fantastic or Flagged? What Amazon Really Means by Your Flex Standing", published 15 June 2025, accessed 19 April 2026.

Gridwise, "Demystified: Your Guide To Amazon Flex Standings", accessed 19 April 2026, used for an overview of standings and performance factors.

Reddit r/AmazonFlexUK, "Deactivated and appeal denied", 8 December 2025, accessed 19 April 2026, used for examples of UK appeal escalation language and Jeff email use.

Facebook Amazon Flex UK driver groups, multiple posts on rating drops, At Risk standings, late returns and use of third parties, accessed 19 April 2026.

Third party appeal guidance, "How to Appeal Amazon Flex Termination?", 28 October 2025, accessed 19 April 2026, used for general structure of appeals and 10 day response suggestion. Marked as secondary, not an official Amazon source.

Supreme Court of the United Kingdom, "Uber BV and others v Aslam and others, UKSC 2019/0029", accessed 19 April 2026, used to frame worker status arguments.

Arthur Cox, "UK Supreme Court rules Uber drivers entitled to workers' rights", 28 February 2021, accessed 19 April 2026, used for explanation of Uber BV v Aslam [2021] UKSC 5.

Academic commentary, "Uber BV v Aslam: work relations cannot safely be left to…" International Labour Law Journal, 30 December 2022, accessed 19 April 2026.