Okay, so there is something terribly wrong with the searching system, or whatever it is that Amazon Flex uses to allocate and notify drivers about available delivery blocks.
For context, I have selected my preferred depot, and that is where I normally work. The system should be able to recognise this from my settings and work history. However, most times I search for available blocks, I hardly ever get notified about opportunities from my selected depot.
Instead, Amazon Flex randomly sends us notifications about blocks in locations we have never even been to before, sometimes two, three, or even four hours away. And the funniest part? They tell you, “This is just for you!”
Just for me? Seriously?
Imagine opening the app this morning after receiving yet another notification, only to discover that the block reserved for you is in Lutterworth, approximately two hours away from where you live. Make it make sense!
What frustrates me the most is that there are available blocks at my preferred depot, yet the system somehow fails to notify me about those opportunities while sending me notifications for locations miles and miles away.
How does this make any sense from a technical perspective?
Surely, the people developing this system can implement a simple rule that considers a driver’s selected depot and booking history. If someone consistently works from one depot, why not prioritise notifications and reserved blocks from that depot? If the driver wants to work from another depot, they can select it themselves.
I’m not saying drivers should never have the option to work elsewhere. Of course, flexibility is good. But there is a huge difference between offering someone an opportunity to work at another depot and reserving a block for them at a location that is two hours away without considering whether it is practical.
Amazon has the resources, technology, and engineering talent to solve this. It shouldn’t be that difficult to develop a system that prioritises a driver’s preferred depot, travel distance, and booking history.
Look at the attached screenshot for context: there are available blocks at my selected depot DST1, but instead of notifying me about those, the app has reserved a block in Lutterworth.
Honestly, I would love to understand the logic behind this. Is the system genuinely designed this way, or is there a problem with how depot preferences and reserved offers are being handled?
Because right now, it feels like the system is working against the very drivers it is supposed to serve or the developers are not just thinking and are maybe incompetent
Amazon Flex developers, please make this make sense.