# Digital tabs > A server opens the tab, guests add to it with staff or from the QR, and pay from their phone at the end. Order and pay, with the service kept in. Canonical: https://storekit.com/products/digital-tab-qr-add-to-bill-for-restaurants **One tab, staff or QR** A server opens the tab. Guests add to it with staff or from the QR, and settle from their phone at the end. - **Order with staff, or from the QR** - One guest orders from the server, the next from their phone. Both land on the same tab. - **The extra round gets ordered** - Another drink, a side, the dessert - added from the table without waiting to catch an eye. - **Paid from the phone at the end** - The bill arrives on their phone. Split, tip, pay, go - nobody chases it. - **+6.4%** Spend per head - **+5.2%** Total tips - **5x** 5-star Google reviews - **#1** Converting checkout ## How it works 1. **Staff open the tab** - A server opens the table's tab, the way they always have. The welcome doesn't change. 2. **Guests add to it, either way** - From the server or from the QR - the second round, the extra side - all onto one tab. 3. **They pay from their phone** - The bill is on their phone at the end. Split, tip, pay, and the table is free. ## What it does ### Order with staff, or from the QR Casual dining is not one kind of guest. At the same table, one person wants a recommendation and a conversation, and the next wants to add a drink without interrupting either. A digital tab takes both: the server opens it and takes orders as they always have, the QR sits on the table for anything a guest wants to add themselves, and every item lands on one running total whichever way it was ordered. ### The extra round gets ordered The most profitable orders of a meal are the small ones that happen after the main order: the second glass, the side that arrives late, the dessert nobody wanted to flag someone down for. In a busy section those go unasked. With the QR on the table, guests add them at the moment they want them, and the tab picks them up like anything the server keyed. ### Keep the service. Lose the waiting. Restaurants that care about hospitality are right to be wary of phone ordering - done badly, it turns a dining room into a food court. This is the other way round. The server still greets the table, still recommends, still takes the order; what the tab removes is the waiting in between - for a second drink, for a side, and above all for the bill. Guests get the human service they came for and the control they have everywhere else, and the section runs more covers with the same team. ### Paid from the table, at the end The end of a meal is where service goes to die: catching someone's eye for the bill, waiting for the machine, doing the maths out loud. When the tab settles from the guest's phone, none of that happens. The itemised bill is already there; they split it by item or evenly, tip the people who served them, and pay - and the table is free while they're still saying goodbye. ### Split at the end, without unpicking the night Every item on the tab is attributed as it is ordered, whether a server keyed it or a guest added it, so when the table settles they can split by item or evenly without anyone reconstructing who had what two hours ago. Nobody passes a card machine round and nobody does arithmetic at the table. ### Posts to your EPOS like any ticket A tab that lives outside the till is a reconciliation problem waiting for closing time. Storekit posts the tab into your EPOS as it builds - server orders and QR orders alike - so the till sees the table the way it always has, and the close-down does not change. ## Hospitality doesn't have to mean waiting. The problem in a good dining room is rarely the service. It's the gaps in it: the second drink nobody caught, the bill that took ten minutes. A tab keeps the server at the table and lets guests fill the gaps themselves. The room keeps its hospitality. The table turns when the meal is done. ## Questions ### Do guests still get served by staff? Yes - that is the point. A server opens the tab and takes orders as normal. The QR is there for anything a guest wants to add themselves, and both go onto the same tab. ### How is the tab paid? From the guest's phone at the end, with split and tip - the same pay-at-table flow. Anyone who would rather pay a card machine still can. ### Can a group share one tab? Yes. Everyone at the table adds to the same running total, and it can be split by item or evenly when they settle. ### Does it post to my EPOS? The tab builds in your till like any other ticket, whether an item was keyed by a server or added from the QR, so closing down doesn't change. ### What kind of restaurant is this for? Casual and fine-casual dining that want a server at the table and the efficiency of phone ordering - not one or the other. ### Do guests need an app? No. The QR opens the tab in their browser. ## Related - [Store designer](https://storekit.com/features/store-designer) - [Automatic upsells](https://storekit.com/features/automatic-upsells) - [Smart reviews](https://storekit.com/features/smart-reviews) - [Capacity control](https://storekit.com/features/capacity-control) - [Tipping & service charge](https://storekit.com/features/tipping-and-service-charge) - [Item videos & photos](https://storekit.com/features/item-videos-and-photos) - [Kitchen display system](https://storekit.com/features/kitchen-display-system) - [QR order and pay](https://storekit.com/products/order-pay-qr-ordering) - [Pay at table](https://storekit.com/products/pay-at-table-digital-bills) - [Takeaway & delivery](https://storekit.com/products/takeaway-system-for-restaurants) - [Pricing](https://storekit.com/pricing)