A bubble tea shop, a bakery counter and a fast food window have the same problem and none of the table map’s answers. Nobody is seated, so there is nothing to attach the order to and nobody to bring it to.
How it runs
The order is placed and paid at the counter or on the guest’s own phone. It receives a pickup number. That number appears on a display — a screen on the wall, or the same screen the bar is working from — and moves to the ready column when the drink or the bag is done. The guest collects and the number clears.
For a drinks bar the label printer usually joins in: the cup gets a sticker with the number and the exact configuration — size, sugar, ice, toppings — so a barista making six drinks at once is not reconstructing them from memory. That label printer is a different machine from the counter receipt printer, with different paper; see routing tickets to the right device.
The format switch does the rest
When the shop is set up you pick the business format. Choose bubble tea or fast food and the interface reorganises around this flow: pickup numbers appear, the table map does not. There is no dining-room machinery to ignore or configure around, and staff do not learn features they will never use.
Change format later — a takeaway counter that adds six seats, or a restaurant that opens a takeaway window — and it is a setting, not a new system and not a data migration. See one system across formats.
Three channels, one queue
The moment you add delivery, a decision arrives that people usually get wrong: how to order the queue when dine-in, takeaway and riders all want food from the same pass.
Do not give a channel priority. Put all three into one production queue ordered by when the order was placed. The channel marker decides how it is packed and which number range it is called on — it is not a licence to jump ahead. A rider order that queue-jumps ten walk-in guests is you paying a commission for the privilege of annoying the customers who came to you directly.
Peak-hour reality
The bottleneck in a counter shop at 08:00 is usually not the software. It is whether the popular items are on the first screen of the ordering interface, whether prices are on the shelf so guests decide before they reach the counter, and whether the customer display lets them confirm the amount without a conversation. Those save ten or fifteen seconds per order, and ten seconds per order is the entire difference between a queue that moves and one that does not.
