Pubs aren't 餐厅 and they're not bars. They're both, at the same time, on the same table. Your EPOS should know that.
Sunday lunch service. Table of eight. Three rounds of drinks at the bar, two Sunday roasts, three fish and chips, two burgers — and someone's forgotten what they ordered. Generic hospitality POS asks you to start a new order every round. Andromeda keeps the tab live, food firing to the pass, drinks firing to the bar, and settles at the end.
One live tab. Food amber, drinks blue, one bill at the end.
Every item on the tab knows whether it's going to the pass or the bar. Food fires to the 厨房 printer and the KDS, drinks fire to the bar printer, and both report back to the same open tab. Front-of-house doesn't have to remember.
At the end of service, split by diner, split by item, or settle in one. Gratuity suggestions, per-diner split, card, cash, Apple Pay — whatever they've got in their pocket.
客户 scan, order, pay — or order now, pay later. Drinks go to the bar, food goes to the pass, tab stays open.
One tab. Food amber on the screen, drinks blue. Split by diner, split by item, settle in full — all from one ticket.
Starters fire, pass marks away, mains fire on your timer. No more mains landing on top of bread and olives.
Natasha's Law compliant. Allergens shown on the 菜单, printed on the ticket, flagged to the pass when a customer has a note.
Six pubs, one estate. Sunday roast 菜单 across all, private hire add-ons per site. Head office pushes changes.
Table of 20 for a christening? Pre-order food, hold a capacity slot, print one running ticket for the 厨房.
| Capability | Zonal / Aztec | Generic hospitality POS | Andromeda |
|---|---|---|---|
| Food & drink on one tab, different printers | ✓ Heavy 设置 | Workarounds | ✓ Works out of the box |
| QR table ordering into the same tab | Add-on | ✗ | ✓ Native |
| Course-paced KDS (fire mains on timer) | ✓ | ✗ | ✓ With timings you set |
| Multi-site head-office 菜单 control | ✓ | Per site only | ✓ Push once, across estate |
| Cost | Enterprise pricing | Varies | ✓ Low flat 每月 fee |
"Sunday lunch used to be chaos on the till — drinks rounds, food 订单, split bills, nan's having the fish pie. One tab that knows which printer is which took the pressure off the whole service."
Yes. That's the default. Every item is tagged to its print route — food to the pass, drinks to the bar — but it's one live tab against the table. When the customer settles, they see one bill.
Yes. Split by diner, split by item, split evenly, or split whatever's easier in the moment. Front-of-house can drag items between splits on the till screen.
Course pacing. Starters fire together, the pass marks them away, mains fire on your timer — say 15 minutes. No wall of tickets, no mains landing on cold bread.
Yes. Take the pre-order through the website or a booking form, hold the table and the 厨房 slot, and it prints as a single running ticket on the day. Allergens flagged per diner if you've captured them.
Natasha's Law compliant. Allergens shown in the web and QR 菜单 before the customer adds an item, printed clearly on the 厨房 ticket, and flagged to the pass when there's a note like "no gluten please".
Yes. Run one master 菜单, allow local overrides (a site-only dish, a higher wine price in the flagship), and push changes to the estate in one click. Reporting rolls up by site or across the group.
预约演示. We'll open a tab, split food and drinks, pace the 厨房, and split the bill eight ways.
预约演示