# QR code table ordering for restaurants in 2026: how it works, what it costs and when an AI waiter helps

> QR menus, tap-to-order carts and AI waiters that take orders by chat solve different problems. This owner's guide explains what each needs, works out flat fee against commission, and covers allergen rules, guest data and a rollout checklist.

- Canonical URL: https://www.broadnet.me/blog/qr-code-table-ordering-restaurants-guide-2026
- Language: en
- Last updated: 2026-10-22
- Publisher: BroadNet (https://www.broadnet.me)

- Published: 2026-10-22
- Author: BroadNet Editorial Team

QR code table ordering lets a seated guest scan a code on the table, open the menu in their phone's browser and send an order to your staff without waiting for a member of staff. Three different things are sold under that name: a QR menu that only displays the menu, QR ordering with a tap-to-order cart, and ordering by chat, where an AI waiter such as [WaiterPilot](https://waiterpilot.com/) answers questions from your menu and takes the order in the guest's language. Pick by the job you need done, then compare cost models.

> Facts checked at their sources on 22 October 2026. Product facts come only from WaiterPilot's own published pages; legal points come from EUR-Lex and the UK Food Standards Agency, linked where they appear. Cost figures marked "illustrative" are arithmetic examples, not any vendor's real price. This guide is general information, not legal advice.

|  | QR menu | QR ordering (tap to order) | AI waiter (ordering by chat) |
|---|---|---|---|
| What the guest does | Reads the menu on their phone | Taps dishes into a cart and sends it | Asks questions in their own words, then orders by chat |
| App needed | No, opens in the browser | Usually no | No, opens in the browser |
| Questions about dishes | Only what the page says | Only what the item page says | Answered from your menu, in conversation |
| Where orders go | Nowhere: a waiter still takes them | A staff board, kitchen screen or POS, depending on the tool | A staff board and kitchen screen, or a POS, depending on the tool |
| Payments | No | Sometimes, if the tool processes payments | Depends on the tool |
| Best for | Replacing paper menus | Guests who know what they want | Guests with questions, or who don't read your menu's language |

## QR menu, QR ordering or ordering by chat: what is the difference?

A **QR menu** is a web page. It saves reprinting, but a waiter still takes the order. **QR ordering** adds a cart: the guest picks items, chooses options and sends the order to a screen or a till. **Ordering by chat** puts a conversation in front of the cart. The guest can ask "which dishes are vegetarian?" or "is the soup spicy?" and get an answer drawn from your menu before they confirm.

None of these replaces the people who cook and serve. For a deeper look at what an AI waiter does at the table, see our [AI waiter page](https://www.broadnet.me/ai-waiter) and the [WaiterPilot product overview on the BroadNet blog](https://www.broadnet.me/blog/smart-waiter-ai-waiter-qr-ordering-restaurants).

## Before you compare prices: what each option needs

Before you compare prices, check what a tool assumes you already have. Four questions decide most of the fit.

- **An app or not.** Browser-based ordering removes the biggest drop-off: guests do not install anything or create an account.
- **A staff board and a kitchen screen.** Someone has to see each order, confirm it and pass it to the kitchen. Ask whether the board runs on phones or tablets you already own, or needs hardware you must buy or rent.
- **A POS connection or not.** Some tools push orders straight into a till and kitchen printer; others run alongside the till, and staff ring the sale in by hand. A connection saves re-keying; a standalone board means one manual step but keeps your till.
- **Payments or not.** If guests must pay from their phone at the table, you need a tool that processes payments. If they pay on your card terminal as today, a live bill they can see and split may be all you need.

Keep the printed menu whichever you choose. If you are weighing ordering by chat against broader automation across your business, our guide to [turnkey AI agents for hospitality, retail and healthcare](https://www.broadnet.me/blog/turnkey-ai-agents-hospitality-retail-healthcare-2026) covers the wider picture.

## What QR table ordering costs: flat fee vs commission

Vendors usually charge in one of two ways, sometimes combined: a **percentage of each order** (a commission), or a **flat monthly fee** per location. The break-even point is simple arithmetic: divide the flat fee by the commission rate. Above that monthly sales figure the flat fee is cheaper; below it, the commission is.

WaiterPilot publishes its price on its [pricing page](https://waiterpilot.com/pricing/): $200 per location per month, or $2,000 per location per year paid annually (the price of 10 months), with the first 30 days free, no setup fee, 0% commission, no contract and no per-table, per-order or per-user fees. The worked example below sets that against an **illustrative** 3% commission. The 3% is an assumption chosen for the arithmetic, not any vendor's real price.

| Monthly sales through table ordering (one location) | Illustrative 3% commission | WaiterPilot flat fee (monthly plan) | Cheaper option in this example |
|---|---|---|---|
| $3,000 | $90 | $200 | Commission ($110 less) |
| $6,667 | about $200 | $200 | Break-even ($200 ÷ 3%) |
| $10,000 | $300 | $200 | Flat fee ($100 less) |
| $20,000 | $600 | $200 | Flat fee ($400 less) |
| $40,000 | $1,200 | $200 | Flat fee ($1,000 less) |

Run the same sum with your own figures. At an illustrative 1% the break-even is $20,000 a month; at 5% it is $4,000. Ask every vendor about setup and menu-loading fees, hardware, per-table or per-user charges, contract length and exit fees, and whether a percentage includes card processing or comes on top of it. WaiterPilot takes no payments, so card fees stay with your existing payment processor, as they are today.

## Guests who don't read your menu's language

In tourist areas, hotel restaurants and cities with many visitors, a share of guests read your menu in their second or third language. A translated QR menu helps them read; ordering by chat also lets them ask.

When you test any multilingual tool, check each part separately, because "multilingual" rarely covers everything. Ask which parts follow the guest's language: the chat replies, the screen buttons, the dish names, and the notes that reach the kitchen. A note typed in a language nobody on shift reads is a service risk, so decide in advance who reads such notes and when.

## Allergens: what the rules say, and what software can and cannot do

In the European Union, [Regulation (EU) No 1169/2011 on food information to consumers](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32011R1169) covers restaurants: its definition of "mass caterer" names restaurants explicitly. Article 44(1) makes the allergen particulars of Article 9(1)(c) mandatory for food that is not prepacked, which includes meals served at the table. Annex II lists the 14 substances or products concerned: cereals containing gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, nuts, celery, mustard, sesame, sulphur dioxide and sulphites above 10 mg/kg or 10 mg/litre, lupin, and molluscs. Article 44(2) lets each Member State set national rules on *how* the information is made available, so check the rules where you trade.

In England, Wales and Northern Ireland, the Food Standards Agency's [allergen guidance for food businesses](https://www.gov.uk/government/publications/allergen-guidance-for-food-businesses/allergen-guidance-for-food-businesses) says you must supply allergen information for every non-prepacked item that contains any of the 14 allergens. It can be given in full in writing, for example on a menu, or verbally with a clearly visible written notice telling customers how to get it. The FSA's advice is that written information supported by a conversation works best.

For any digital ordering tool, that leads to three practical rules:

1. **The tool answers only from your menu.** It should repeat what your allergen information says and say plainly when the menu is silent, never guess or call a dish "safe".
2. **Staff confirm.** Any allergy mention, in the chat, in a note or in a waiter call, means a person goes to the table and checks with the kitchen before anything is cooked.
3. **Your written allergen information stays.** The chat is an extra way to ask, not a substitute for the information the law requires you to provide.

Write the allergens into every dish description, including sauces, dressings and frying oil. WaiterPilot's page on [allergy and dietary questions](https://waiterpilot.com/allergies-and-dietary-questions/) shows how one AI waiter handles this: menu facts only, then a request to confirm with staff, who have the final word.

## Guest data and privacy: what to ask before you sign

A table-ordering page sees what guests order and, with ordering by chat, what they type. If you serve guests in the EU, the GDPR's data-minimisation principle in [Article 5(1)(c) of Regulation (EU) 2016/679](https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32016R0679) says personal data must be "adequate, relevant and limited to what is necessary" for the purpose. For ordering food, very little personal data is necessary. Ask any vendor:

- Must guests give a name, email or phone number, or create an account, to order?
- Which cookies does the ordering page set, and are any used for advertising or analytics?
- Is guest data sold or used to build profiles?
- How long are chats, notes and orders kept, and can you export or delete them?
- Can staff read what a guest typed?

## Rollout checklist: from first call to first busy night

1. **Fix the menu first.** Clear dish names, required choices (size, side, cooking), prices, ingredients and allergens.
2. **One QR code per table.** Each code must identify its table. Place cards where a seated guest sees them.
3. **Decide who confirms.** Name one person per shift to watch the board and confirm first orders.
4. **Agree when the till is updated.** If there is no POS connection, staff ring the sale in either as they confirm or at the check. Pick one moment, not both.
5. **Run test orders.** Place orders from several tables and phones, in the languages your guests use, with a note and an allergy question. Time how long each takes to reach the board.
6. **Train staff in one short session.** Order states, rejecting an order, sold-out dishes, waiter calls and the allergy rule.
7. **Keep the printed menu and a fallback.** If the connection drops, go back to paper and a notepad until it returns.
8. **Review after a few weeks.** Look at what guests asked that your menu didn't answer, and fix the menu.

## How WaiterPilot fits

WaiterPilot is BroadNet.AI's AI waiter, part of the [BroadNet.AI platform](https://www.broadnet.me/platforms/broadnet-ai) and listed among [BroadNet's brands](https://www.broadnet.me/brands). On its own site it states the following:

- **How it works.** Guests scan the table's QR code, the chat opens in the phone's browser with no app and no sign-up, and they order by chat. The order lands on a staff board as Awaiting staff; the first order at each table waits for a person to confirm it, then moves to In kitchen and Served.
- **Speed.** In four test orders on 15 October 2026, confirmed orders reached the staff board in 0.8 to 2.7 seconds. WaiterPilot says to read that as "within a few seconds", not a guarantee for a busy night.
- **Languages.** The chat answers in the language the guest writes in (tested in English, Arabic and Spanish). Guest screen buttons are in English or Arabic only. Notes reach the ticket untranslated.
- **Allergies.** Answers come only from your menu, the guest is asked to confirm with staff, and staff decide. It does not alert staff automatically.
- **Bill.** Guests see a live bill with tax and any service charge you set, and can split it.
- **Price.** $200 per location per month or $2,000 per year, 30 days free, no setup fee, 0% commission, no contract.

Its stated limits matter as much: **no POS or kitchen-printer connection** (staff ring sales into their own till), **no payment processing** (guests pay on your terminal or till), and it runs alongside the printed menu. If guests must pay at the table, or every order must land in your POS or print in the kitchen without re-entry, WaiterPilot says a POS-native ordering tool may suit you better. You can watch one order go from guest chat to staff board in its [sample order in the browser](https://waiterpilot.com/demo/).

## Frequently asked questions

### Do guests need to download an app to order from a QR code?

Not with browser-based tools. The QR code opens a web page in the phone's browser, so there is nothing to install. Some systems still ask for an account first, so ask. WaiterPilot states that guests need no app, no sign-up and no name, email or phone number to order.

### Is QR table ordering the same as a QR menu?

No. A QR menu only displays the menu, and a waiter still takes the order. QR ordering lets the guest send the order from their phone to a staff board, kitchen screen or POS. Ordering by chat adds a conversation, so guests can ask about dishes in their own words before they confirm.

### Do I need a POS connection for QR ordering?

Not necessarily. A POS connection sends orders straight into your till and saves re-keying, but it only works with supported systems. A tool that runs alongside your till needs one manual step: staff ring the sale in, either as they confirm the order or at the check. Pick one moment, train everyone on it, and match the two each night at first.

### Is a flat monthly fee cheaper than a per-order commission?

It depends on your sales through the tool. Divide the flat fee by the commission rate to find the break-even. For a $200 monthly fee against an illustrative 3% commission, that is about $6,667 a month: above it the flat fee costs less, below it the commission does. Add setup, hardware and contract costs before you decide.

### Can an AI waiter tell a guest a dish is safe for their allergy?

It should not. A well-built AI waiter repeats what your menu says about allergens, says when the menu is silent, and asks the guest to confirm with staff, who check with the kitchen and decide. In the EU and UK, the allergen information the rules require for non-prepacked food must still be provided by the business.

### Can tourists order in their own language?

With ordering by chat, often yes: the guest asks and orders in their own language and the answers come from your menu. Check which parts are translated, because chat replies, screen buttons, dish names and kitchen notes are often handled differently. Test with the languages your guests actually use, and decide who reads notes in other languages.

### What guest data does QR table ordering collect?

At minimum, what each table orders. Some tools also ask for names, phone numbers or emails, set analytics or advertising cookies, or build guest profiles. Under the GDPR's data-minimisation principle, collect only what ordering needs. Ask each vendor about sign-up, cookies, retention, export and deletion, and whether guest data is ever sold.

### Should I keep printed menus after switching to QR ordering?

Yes. Some guests have no phone, a flat battery or prefer paper, and browser-based ordering needs a working connection on both the guest's phone and the staff screens. Keep printed menus on hand, make sure staff can still take orders the usual way, and treat QR ordering as an extra option rather than the only one.

**Ready to see ordering by chat on a real menu?** [Try a WaiterPilot sample order or book a demo](https://waiterpilot.com/demo/) and run a dish from your own menu through the flow, from the guest's question to your staff board, before you decide.