How to queue a counter order versus a table wait at the same cafe
A counter order and a table wait run out for different reasons - one needs a barista's attention for thirty seconds, the other needs a table to clear, which can take twenty minutes. Taking one number for both means a quick coffee order waits behind someone who's really waiting on seating. Running them as two separate queues, from the same counter, fixes it without adding staff.
A cafe with one "take a number" system for everyone looks fair on paper - first come, first served, same rule for all. In practice, customer #14 ordered a drip coffee to go and customer #15 wants a table for two. If the cafe calls strictly in order, #14 stands there while #15 is told to wait for a table that isn't free yet, holding up everyone behind them for no reason related to their own order.
Why one line doesn't work for two different waits
A queue works best when everyone in it is waiting on the same thing. A counter order queue is really waiting on staff capacity - how fast the person behind the counter can make and hand over drinks. A table wait is waiting on a completely different resource - how fast existing tables turn over, which has nothing to do with how fast the barista works. Mixing both into one number sequence ties the speed of one to the speed of the other, when neither actually depends on the other.
Example: a Saturday morning rush
It's 9am and the espresso machine is keeping up fine - orders are moving every 30 to 60 seconds. But every table is full of people lingering over breakfast, and nobody's cleared one in fifteen minutes. A single queue fed by one number dispenser means the next person waiting for a table is stuck behind a growing run of counter orders, even though the barista has plenty of capacity. Meanwhile, someone who just wants a flat white to go is stuck behind that same table-wait customer, for a seat they never asked for.
Run them as two lines, not one counter with one number
The fix isn't more staff - it's recognizing these are two separate queues that happen to share a building:
- Give counter orders their own queue, called purely by how fast drinks come out. Someone ordering a coffee to go shouldn't wait on table turnover they have nothing to do with.
- Give the table wait its own separate queue, called as tables actually clear, independent of how busy the counter is at that moment.
- Let the customer pick which line they're actually in at the point they join, rather than making everyone draw from one shared number that doesn't reflect what they're really waiting for.
Where Qrua fits
Qrua lets a cafe run more than one queue from the same account - a counter-order queue and a table-wait queue, each with its own name, settings and daily limits, managed side by side from one dashboard. A single QR code can list both as separate options, so a customer picks "Order" or "Table" when they scan, and joins the queue that actually matches what they're waiting for. Each queue moves at its own pace and shows its own live position on the customer's phone, so a quick coffee order is never stuck behind someone waiting on a table, or the other way around.