Big tables and families: how QR ordering works with several phones

At a big table, each phone that scans the table’s QR code gets its own chat and its own cart, and every phone shares one live bill for the table. With WaiterPilot, staff confirm the table’s first order before the kitchen cooks; after that, later rounds from the table go straight to the kitchen screen. Guests split the bill evenly or by phone and pay your staff as usual. Allergy decisions stay with your staff, and for some parties a server taking the order is still the better way.

Below: how several phones behave at one table, how rounds, kids’ questions and allergies work, a worked Sunday lunch for ten with the bill shown, where a server should still take the order, and a setup checklist. For the feature summary, see the family restaurants page.

What happens when several phones order at one table?

Short answer: each phone orders on its own, the table shares one bill, and only the table’s first order waits for staff.

Anyone at the table can scan the QR code. The menu opens in the phone’s browser, with no app and no sign-up. Each phone has its own conversation and its own cart: one parent can ask about the kids’ options while an uncle asks what comes with the lamb. Nothing reaches staff until that guest reviews the cart and taps Confirm, and before that they can change quantities as often as they like.

Then the table rule applies:

1. The table’s first order waits. It appears on the staff board as “Awaiting staff” until someone taps Confirm. Staff can also reject a first order that looks wrong.
2. Later orders go straight through. After staff confirm, new orders from that table, from any phone, go straight to the kitchen screen until staff close the table.
3. Guests can still back out early. A guest can cancel an order while it is still awaiting staff. Once confirmed, changes go through a server.

Required choices, such as a side or a size, must be picked before an order can be confirmed, so the kitchen doesn’t get “one kids’ meal” with no side.

One practical point: we suggest one phone per family or couple, not one phone per person and not one phone for twelve. It keeps each share of the bill meaningful, keeps carts short enough to check, and gives staff a first order they can actually read before confirming.

How do rounds of orders work at a long table?

Short answer: guests order when they are ready, and after the first confirm each round goes to the kitchen screen without waiting for staff.

Family meals come in waves: drinks and something for the children first, mains when everyone has decided, dessert an hour later. The kitchen screen shows dishes, choices and notes, without prices, so the cooks see each round as it arrives. A request such as “no onions” goes on the ticket as a short note, written by the AI from the guest’s words and not translated.

Two staff tools help at big tables:

• Add a dish for a table. When a grandparent tells the server what they’d like, the server adds it from the staff screen; nobody has to hand over a phone.
• Move the party. If a bigger table frees up, staff move the party there.

If a dish runs out mid-meal, the owner or manager marks it sold out from their phone and the chat stops offering it right away. If it was already in the kitchen, staff mark it out of stock; it comes off the bill and the guest sees a note.

How does the chat handle kids’ questions?

Short answer: it answers from your menu, shows dish photos, and stays on the subject of food.

Children and their parents ask the same things at every table: is it spicy, what comes with it, is there a smaller one, what does it look like? The chat answers from what your menu says. A dish name in the chat opens its photo, which settles a lot of “what is it?” before anyone orders. If your menu has a kids’ section, the chat answers from that; if it doesn’t say whether a portion can be smaller, the chat tells the guest to ask a staff member.

The AI stays on the menu: it steers questions on politics, religion, medical or legal matters back to food, and guests can’t change its rules.

Who decides on allergies at a big table?

Short answer: your staff, every time. The chat gives what your menu says and asks the guest to confirm with staff; it never confirms a dish is safe.

Food allergies are common at family tables. In the US, 5.8% of children and 6.2% of adults have a diagnosed food allergy (CDC NCHS, 2021 data, published 2023). In a registry of 2,827 people with food allergies, dining out was the second most common place for a reaction after home (21% against 44%), and in 53.9% of the restaurant reactions the guest had told staff about the allergy (Oriel et al., 2020).

Big tables add a specific risk. The person ordering a child’s food on one phone may not be the person who knows about the allergy, and shared plates ordered on another phone reach everyone. WaiterPilot doesn’t alert staff when an allergy comes up in a chat. And only the table’s first order waits for a staff Confirm, so later rounds don’t stop for a person to read them.

So the allergy check belongs at the greeting, out loud, to the whole table: “Does anyone have an allergy or anything they can’t eat?” The server then tells the kitchen. Our allergy protocol for QR ordering has the full routine, including what the chat does and doesn’t do.

A worked example: Sunday lunch for ten at Casa Olivo

Casa Olivo is a fictional restaurant we use for examples (an example, not a customer). The people, prices, charges and timings are our assumptions, not WaiterPilot defaults and not tax advice.

The table: ten people at a long table. Lina’s family (two adults, two children) orders on Lina’s phone. Omar’s family (two adults, one child) orders on Omar’s phone. The grandparents order on their own phone. Omar’s daughter is allergic to sesame. Casa Olivo sets Service 10% and Tax 8%, both on the food subtotal.

How the meal runs:

• 12:30 The server greets the table and asks about allergies. Omar mentions sesame; the server tells the kitchen.
• 12:34 Lina’s phone sends the first order: a mezze board to share, drinks and juice for the children. It shows as “Awaiting staff”. The server reads it, sees the mezze includes hummus (tahini is sesame), mentions it to Omar, and taps Confirm.
• 12:45 Omar asks his chat whether the falafel has sesame. The chat gives what the menu says and asks him to confirm with staff; he checks with the server, who already knows. Omar’s and the grandparents’ mains go straight to the kitchen screen, because the table’s first order is confirmed.
• 13:10 A juice goes over. Lina taps Call waiter; the call shows on the floor screen as “Wants a waiter”, with the minutes it has waited, and turns color at 1, 5 and 10 minutes if nobody answers.
• 13:25 The grandparents order a dessert platter for the table. It goes straight to the kitchen.
• 13:50 Lina taps Check please; the request asks cash or card, and the server brings the card machine.

What each phone ordered:

Just my share gives each phone its own food plus 18% of charges on that food:

The shares add up to the total. Notice the shared plates: the $18 mezze sits on Lina’s share and the $16 dessert on the grandparents’, because a phone only knows what was ordered on it. Families who want to share those differently can use Split evenly, settle up between themselves, or ask the server to adjust at the terminal. Payment happens with your staff either way. Our bill-splitting guide works through the other methods.

Where is a server taking the order still better?

Short answer: wherever the order is simple, the party is very large, or the guests want a person.

Many guests prefer people. In the National Restaurant Association’s 2024 survey of US full-service diners, 64% would choose traditional service from employees over a restaurant that incorporates technology, including 88% of Boomers (NRA, 2024). At a family table, that is often the grandparents.

Mixing the two is normal: a server takes the grandparents’ order, the parents order a second round on their phones, and everything lands on one bill.

A checklist for big tables

1. Ask about allergies out loud when greeting every big table, before anyone orders.
2. Read every big first order before tapping Confirm; reject it if it looks wrong.
3. Suggest one phone per family or couple, and say how the bill can be split.
4. Write what families ask about into the menu: spice, what comes with each dish, smaller portions, a kids’ section if you have one, allergens.
5. Add dish photos. They answer children’s questions faster than words.
6. Put the floor screen where someone sees it, and agree who answers calls in each section. See waiter call and bill.
7. Train servers to add dishes for a table for guests without a phone.
8. Keep the printed menu and a server for every table.
9. Decide how big-table orders reach your till, since WaiterPilot has no POS or printer connection.
10. Close the table when the party leaves, so the next party’s first order waits for a staff Confirm again.

What to do next

Look at last month’s big tables: how many were families choosing from the menu, and how many were set menus or parties of 15 and up. If the first group is large, try a sample order to see an order reach the staff board, and compare the monthly price on the pricing page: $200 per location per month after 30 days free, with 0% commission and no contract. If many of your guests are visitors, our guide to QR ordering for tourist restaurants covers the season, and who it’s for lists the other venue types.