Recipe
Show the waiter what each person ordered
Reading a menu you do not know is one problem. Being understood when you order is the other one — and it is the one that decides whose plate ends up in front of whom.
Last reviewed: September 2026
Most of the difficulty of ordering abroad gets described as reading the menu. The harder half happens a minute later, when eight people have decided and one of you has to convey all of it to someone who does not share your language. The usual result is a merged list: six dishes, quantities, no owners. That gets the food to the table but not to the right seats, so the last two minutes of every course are plates hovering while people point at themselves. Split The Bill's waiter page answers the other question — not what the table wants, but who wants what. It lists every diner with their own dishes, written in the restaurant's language, and by default shows only the dishes that have not yet gone to the kitchen. You can show it on your phone, or let the waiter scan a QR code and open it on theirs. Nothing is transmitted to the restaurant: there is no till or kitchen integration anywhere in this feature. It is a screen a person reads, which is precisely why it works in a place that has never heard of us.
Step-by-step
- 1
Everyone picks on their own phone
The table opens one shared link and each person chooses their own dishes. Because people pick for themselves rather than calling choices across a table, the order already knows who wanted what — nobody has to reconstruct it afterwards.
- 2
Open the waiter page
The order is regrouped by person: each diner with their own dishes and a seat number. The number exists because names are not unique — two people called Ana is an ordinary Tuesday, and a waiter cannot tell them apart. Someone who ordered nothing still appears, marked as such, so four plates at a table of five never reads as a missing dish.
- 3
Show it, or let them scan it
Hold up your phone, or let the waiter scan a QR code and open the page themselves. Dish names are shown exactly as the menu prints them, in the restaurant's language, so nothing depends on your pronunciation.
- 4
Mark the round sent, and carry on
Once that lot has gone to the kitchen, mark the round as sent. The sitting stays open, later dishes form the next round, and the page goes back to showing only what is new — so the walk back from the kitchen means reading two drinks, not the whole meal again.
Why by person and not one merged list
A combined list is the right answer to 'what does this table want' and the wrong answer to 'who gets what'. Kitchens work from the first question; the person carrying the plates needs the second. Grouping by diner means the risotto arrives at the seat that asked for it without a round of pointing, which matters most in exactly the situation this feature exists for: nobody at the table can explain the mix-up in the waiter's language, and the waiter cannot explain it back. The seat numbers do the disambiguating that names cannot, and the diners can count the same way around the table.
Only what is new since the last round
Meals are not single events. Drinks arrive, then starters, then someone adds a coffee an hour later. If the page showed the whole sitting every time, a waiter returning for the third time would have to find the two new lines inside a list of twenty already-served dishes. So the default is the delta: only the dishes nobody has sent to the kitchen yet. Marking a round as sent moves that lot into the history and starts the next one. The full sitting stays available for the end of the evening, when 'what did this table order in total' becomes a real question again.
Nothing is sent to the restaurant
There is no POS, till or kitchen integration in this feature, and that is a deliberate boundary rather than a missing release. The page is a screen you show a human being, and a human being takes the order exactly as they always have. That is why it works in a family restaurant with a paper pad as well as anywhere else — it asks nothing of the venue, needs no agreement with them, and cannot put your table into a state their system disagrees with. It also does not filter for allergens or dietary requirements: a wrong automated allergen claim can put someone in hospital, so ask the restaurant directly, every time, and treat nothing here as allergen information.
The order becomes the bill
Because the app already knows who chose what, the end of the meal is not a reconstruction. Turn the order into a draft bill and each person's dishes are already attached to them, with a tip added if the table wants one — a suggested percentage you can change or decline. The bill stays fully editable for whatever actually happened: a service charge, a round that went on the house, a dish sent back. What it removes is the part where six people try to remember who had the second bottle.
Frequently asked questions
Does the restaurant get our order automatically?▾
No. There is no integration with any restaurant, till or kitchen system. The waiter page is a screen you show a person — or that they open by scanning a QR code — and a human takes the order exactly as they normally would.
What language is the waiter page in?▾
The restaurant's. Dish names are shown as the menu prints them rather than as your translation of them, because the page exists to be read by someone who works there. Your own translated view of the menu is unaffected and stays in your language.
Why does each person have a number?▾
Because display names are not unique and a waiter cannot guess which Ana is which. The seat number is stable for the whole sitting, it is what someone can read out, and it is something the table can count around themselves.
What happens to someone who did not order anything?▾
They still appear, marked as having nothing yet. Hiding them would turn 'this person wanted nothing' into 'where is this person's food' — which is the exact ambiguity the page exists to remove.
Can we order in more than one round?▾
Yes. Mark a round as sent to the kitchen and the sitting continues; anything added afterwards forms the next round. The waiter page defaults to showing only that newest round, with the whole sitting available on demand.
Does this work if we did not scan the menu?▾
The waiter page is part of a shared menu order, so it comes from a scanned or saved menu that the table ordered from. If you are splitting a bill after the meal instead, that is the ordinary bill flow and does not need this page.
Can I ask for a dish without onions?▾
Not through the app in this version. You can pick dishes and quantities; item modifiers are not supported yet, so special requests still go to the waiter the usual way.
How accurate is the translation?▾
Good, not perfect — the feature is in beta. The waiter page sidesteps the question for the venue's side, because dish names are shown exactly as the menu prints them rather than translated back. Your own reading view always keeps the original name next to the translation for the same reason.
Free tier covers most recipes. Pro is 100 receipts every 30 days + private invite links.
