Take orders
Scan, order, split, leave when ready.
A QR code on the table opens your menu, runs a tab for that table, lets a group split the bill however they like, and calls a server when they need one — so nobody waits twice for the same thing.
- the guest scans and orders in the browser
- No appthe guest scans and orders in the browser
- per table, however many people order
- One tabper table, however many people order
- evenly, by item, or one person pays
- Split any wayevenly, by item, or one person pays
Waiter called
Table 12 · 8s ago
raised on your floor screen
Avg turn
54m
tracked per table
Drive-thru
Car #48 · pay at window
The problem
Guests wait twice: once to order, once to pay
The two longest waits in a full-service meal have nothing to do with the kitchen. A table is ready to order and cannot catch anyone's eye; then they are ready to leave and have to wave for the bill, wait for the card machine, and wait again to split it four ways. Each wait costs a table turn, and both happen at exactly the moment a guest decides how the evening went.
- A table sits ready to order while every server is at another table.
- Splitting a bill by hand at the terminal is slow and error-prone.
- One person paying for everyone quietly caps the check.
- You have no idea which tables actually turn and which sit.
How OwnTable solves it
The table orders and pays for itself
Each table gets its own QR. Scanning opens your menu with the table already known, so anything ordered joins one running tab — and when they are done, they settle it from the phone in their hand.
A real tab, not a series of orders
Four people ordering from four phones build one bill. Rounds added later join the same tab.
Splitting is the guest's problem, solved
Evenly, by item, or one person covers it — decided at the table, with no maths at the terminal.
Servers get called, not hunted
A call-waiter button raises it on your screen with the table number, so staff walk to a table that actually needs them.
What you get
The difference it makes, in practice
Turn tables faster
Both the ordering wait and the paying wait disappear. The guests leave when they are ready rather than when someone is free.
Bigger rounds
A second drink is one tap away rather than a wave across the room, and the upsell prompt runs on every order.
No app, no login
The guest scans and is on your menu. Nothing to install and nothing to sign up for.
Your servers do the human parts
Taking down a list of dishes is not hospitality. Being at the table when it matters is.
You learn per table
Which tables turn, which sit, what each one spends, and when your covers actually peak.
Drive-thru too
The same mechanism runs your window: a car number on the ticket, and pay at the window if that is how you work.
How it works
Live in days, not quarters
- 1
Generate your codes
Add your tables and print a QR for each. They are yours to design onto a card, a stand or a menu.
- 2
A guest scans
Your menu opens with the table already known. No code to type and no table number to remember.
- 3
The tab runs
Everything ordered from that table joins one bill, whoever ordered it and whenever they did.
- 4
They settle and go
Split it, pay it, and leave. The tab closes itself and the table shows clear on your screen.
In detail
Everything included
At the table
What the guest experiences between sitting down and leaving.
- One QR per table, generated and printable from the dashboard
- A running tab shared across every phone at the table
- Split evenly, split by item, or one payer covers the table
- Call a waiter, with the table number raised on your screen
- Tipping at the point of payment
- Pay by card, wallet, or ask for the terminal — nothing is forced
Drive-thru
The same order flow, adapted to a car. Built after a restaurant asked for it rather than designed in a vacuum.
- A QR at the speaker or the window
- An optional car number on the ticket so staff know whose order it is
- Pay at the window, if that is the way you already run it
- Orders join the same kitchen queue as everything else
What you learn
Dine-in has always been the least measured part of a restaurant. Not any more.
- Spend and turn time per table
- Which sections of the room actually earn
- Peak covers by hour and by day
- Dine-in revenue separated from pickup and delivery in every report
The business outcome
What changes on the floor
The two waits that decide how a meal ends both go away, and the check goes up because a second round is a tap rather than an interruption. Meanwhile every dine-in guest who pays leaves you a contactable customer record — something a table has never produced before.
- removed from every cover
- Two waitsremoved from every cover
- however many phones are on the table
- One tabhowever many phones are on the table
- become customers you can reach again
- Dine-in guestsbecome customers you can reach again
Questions
The things owners actually ask
Something not here? Ask us directly — you will get a straight answer, including when the answer is no.
No. Scanning the code opens your menu in the phone's browser. There is no app, no account and nothing to install — which is the only reason table QR ordering works at all.
Works with the rest of the platform
Own your orders, your guests and your margin.
Fourteen days, everything switched on, and we set it up with you. If it does not fit your restaurant, walk away.