Academy › Build › Bookings and orders
Sort the queue by delivery time, not by payment time
By the end, you'll know how to sort orders that come in at the same time by delivery time and by what's running low, and to send the "order in progress" alert when you actually start it, not when it was paid for.
By Yodai · Published September 6, 2026 · Updated October 12, 2026
When orders pile up, you have to decide what order to prepare them in and when to notify each customer. One Saturday at nine in the morning, six paid orders come in within twelve minutes. One has noon pickup, another has 6 PM pickup, and two call for the same bouquet, and you only have eight stems left to make it. Which one do you start with?
The answer almost everyone gives is the simplest one: first come, first served, whoever paid first gets prepped first. It sounds fair, and it's exactly what leaves you stuck at noon with a customer standing at the counter and their bouquet still untouched.
The payment time doesn't tell you anything about when it's needed
The noon order doesn't wait for you to finish the 6 PM one just because that one got paid first. If you build your queue by the order the notifications come in, the customer picking up at noon can show up and find their bouquet not even started, while you're still working on one that isn't needed for another eight hours.
The payment time only tells you when the customer made up their mind. It doesn't tell you when they need it, or which product might run out before the morning's over. Those are two different questions, and you mix them up the moment you use a single order to answer both at once.
- It's the order the orders come in, without lifting a finger
- It falls apart as soon as a single morning has orders with different time slots
- Forces you to check each order's time slot before touching anything
- Whoever picks up or receives earlier gets prepped earlier, no matter when they paid
- If two orders share a time slot, it still doesn't say which one goes first
- It matches the "in progress" notification: you notify in the order you actually work on them
Which one I'd pick: Sort by delivery time, unless your business doesn't work in time slots, where everything is "for today" with no set pickup time. In that case, payment time works fine, because there's nothing else to sort by. As soon as you promise a time, that time outranks everything else.
When two orders deliver at the same time
That's where the third criterion comes in: what might run out first. If two of the three noon orders call for the bouquet you've only got eight stems left for, those two go first in that time slot's queue, even if the third one paid ten minutes earlier.
That bouquet isn't worth more than the others. What changes is the information: if you're going to come up short on stems, you'd rather find out at nine in the morning, with time to buy more or give the customer a heads up and offer a swap, than at eleven thirty, with that person already on their way to the shop to pick up something that doesn't exist.
- 1Group orders by time slot
Before you touch the first order, split orders into blocks by pickup or delivery time: the noon ones in one group, the 6 PM ones in another. You don't have to calculate this: it's the time the customer gave you when they ordered, in the order notes or when you confirmed it with them. - 2Within each time slot, check what's running low
Check the stock on the products in that time slot. If two orders share a product with just a few units left, those two move to the front of the group, no matter what order they were paid in. - 3The rest of the slot, by payment time
Among orders that aren't competing for anything scarce, the order doesn't change the outcome. Use payment time because it's the criterion that takes the least thought, and overthinking something that doesn't matter is time taken away from what does. - 4Regroup whenever a new order comes in
A last-minute order for the noon slot slots in where it belongs within that block, it doesn't get tacked onto the end of the whole list just because it arrived after the others.
The "in progress" notification reflects the queue, not the payment
The "order in progress" alert has to go out when you actually start on it, not when it was paid for. If at nine in the morning you tell all six Saturday customers their order is in progress because all six paid at that time, the customer picking up at 6 PM spends nine hours thinking their bouquet is already being put together, when you haven't even opened the flower cooler for them yet.
It's a small crack in trust, but it's the first one of the day. If the notification arrives before it's actually true, the customer stops believing the next one, the "ready for pickup" one, and starts texting to ask instead of waiting for the message.
With the queue sorted by time slot, by what's running low within each slot, and the alert going out order by order, Saturday stops depending on your memory: anyone looking at the sorted list knows what to prepare first and who to notify. What's left is the last piece: keeping a record that the order actually went out.
- The prep queue is sorted by delivery slot, not by payment time
- Within the same slot, orders that share something in short supply go first
- Among orders not competing for stock, breaking ties by payment time doesn't change anything
- The "in progress" alert goes out order by order, when you actually start it
Three cases to decide
Answer before opening each one. If one gives you trouble, go back to the section that explains it.
1. Three orders come in at 9:00, 9:04, and 9:11 AM. The first one picks up at 6:00 PM, the other two at 1:00 PM. Which do you prep first?
One of the two picking up at 1:00 PM, not the one that paid at 9:00 AM. Payment time doesn't call the shots: the one picking up at 6:00 PM has plenty of room to spare even though it was paid first.
2. Two orders in the 1 PM time slot share a product with only 3 units left, and a third order in that same slot calls for a different product with plenty of stock. What order do you prepare them in?
The two that share the scarce product first, even if the third one paid earlier. If you come up short, you find out early and can give notice in time; the third order can wait because its product isn't at any risk.
3. You told six customers their order was "in progress" at nine in the morning because all six paid then, but by noon you'll have actually started only two of them. What do you change?
The alert goes out order by order, when you actually start it, not all at once when payment comes in. If you notify before it's true, the customer stops trusting the next alert, the "ready" one.
The notification already goes out order by order, when you actually start it. But an order marked ready isn't delivered yet, and that last step, who closes it and when, is what's missing so none of them stay open forever.
In Yodai the store comes with the Free plan, with a catalog, a cart and orders. See how to create your online store for free.
NextAn order isn't delivered until someone says so