Gopal Bandameeda has been delivering for Amazon for nearly two years now, and has completed a total of nearly 22,000 deliveries without committing mistakes. In other words, his delivery record is spotless.
However, he just got sacked by Amazon Flex.
Now, how could he work to support his newborn and his ill wife?
The big conflict started during his routine delivery last April 4th when he arrived at a residence with the front door wide open, he told the country’s Fair Work Commission.
It is eerie and weird, especially when the man who “lives” in the house just told him to drop the package inside.
But then, he followed the instruction.
He stepped some few paces in and placed the envelope on a table, realizing that his customer was watching him, like watching a baby crawl. He did as per usual, snapped a photo for proof and left.
This is when things are getting exciting.
Shortly after, Bandameeda told Ridesharing Forum that he received a complaint from Amazon, saying that he burst in and infiltrated a home without permission, causing his Amazon Flex account to get deactivated. Now, he can no longer access jobs on the platform.
What’s worse is that Amazon wasn’t satisfied of the warning. The driver received a new message via email three days later, stating he committed a “serious violation” of the terms of service of Amazon Flex because of “what he did.”
He was permanently deactivated the following day.
Did he let the incident pass? Of course not. Amazon Flex has been his bread and butter, so he sent at least 25 emails to the company to appeal and get him back on the app.
Then, an argument between Amazon and Bandameeda ensued, but not because of the incident per se, but because of the driver accusing Amazon of breaching their terms, such as deactivating him from the app without warning.
Amazon is denying his claims.
But the case is moving.
“We accept the unchallenged evidence from Mr Bandameeda that in the period from about mid-April 2025, he was suffering from significant physical and mental health difficulties, including suicidal ideation, and the need to care for his ill wife and newborn child,” stated Amazon’s deputy president, Tony Saunders. “There is no doubt that these matters would have impacted Mr Bandameeda’s ability and capacity to prepare and lodge his unfair deactivation application.”
A hearing is now underway.
Here’s Ridesharing Forum’s take. The matter has been detoured to Amazon deactivating him from the app, without focusing on the probable issue and cause from the customer who gave him instructions. Was it really the driver that should be at fault, or the customer? Was their a “foul play” or “connivance” involved?
Tell the team your thoughts by signing up for your account and joining the discussions.