The stack backtrack and the point of the stack
Welcome. This article is about the stack. The stack attack, the multiple run, or just a double delivery. The stack by any other name is still the same.
Not only is the stack an additional delivery, but it is also an effective way to clear a queue. Once the courier accepts the offers, it’s time to get busy.
Having multiple deliveries while working as a courier is cool. The idea of carrying multiple deliveries, for the courier, is one that resembles the pursuit of prosperity. Achieving a goal.
This applies to couriers that are delivering with crews as well. In fact, for the purposes of this article, the crew driver will be a good example for the dropoff scenarios that follow.
The Stack
In every delivery crew there is always a point in the rush that requires the crew to deliver multiple orders at a time.
There is a structured way that this occurs. Furthermore, deliveries are expedited in a manner that makes the best overall sense. For the courier, as well as, the dropoffs.
A stack is multiple deliveries in one trip. A courier, that is carrying cargo to more than one location, is attempting to combine multiple deliveries into one trip. This is an efficient use of time and equipment.
However if the courier passes by one dropoff location, to go the longer distance to the next dropoff location first, there is no point in the courier having that stack, because the courier now has to backtrack.
In the screenshot example, the courier is right next to a dropoff location. However it is not possible to toggle between the deliveries in this example.
The courier has to pass by a dropoff location carrying the cargo to the next dropoff, and then backtrack, delivering cargo that should have been delivered first.
Why would the courier have the second delivery onboard, if it is to be carried past its dropoff location to another location, and then back again?
It should be noted that in the Doordash app, it is possible to toggle between tasks, in the app. Stay safe out there.
Comment here