--- title: "QR Menu Ordering and Online Ordering Without Commission | GoSufra" description: "How table QR ordering actually works, why the token expires, what an owned ordering channel is worth against aggregator commission, and the mistakes that make guests give up." url: "https://gosufra.com/en/blog/qr-menu-and-online-ordering/" language: "en" source: "https://gosufra.com" --- # QR menus and your own ordering channel: getting off the commission treadmill How table QR ordering actually works, why the token expires, what an owned ordering channel is worth against aggregator commission, and the mistakes that make guests give up. 2026-08-23 · 7 min read ![Illustration of a QR block beside a phone placing an order](https://gosufra.com/blog/qr-menu-and-online-ordering.svg) ## Key points - A QR menu is a menu. QR ordering is a till the guest holds — they are different projects. - Table QR tokens expire and cannot be replayed, which is what stops a photographed code being reused. - Every order on your own channel keeps the commission and the customer's details. - The usual failure is a PDF menu. It is unreadable on a phone and tells you nothing. Two things get called “QR ordering” and they are not the same. One shows the guest your menu. The other lets them order from it. The first is a document; the second is a point of sale in someone else’s hand, and it needs to behave like one. ## The two levels, honestly **A QR menu** replaces a laminated card. The guest scans, reads, and calls the waiter. It is worth doing — it removes reprints and lets you change a price at lunchtime — but it changes nothing about how orders reach the kitchen. **QR ordering** goes further: the guest picks items, adds notes, and sends. The ticket appears on the kitchen screen against their table number, the same way a waiter’s order would. That is where the labour saving and the accuracy come from, and also where the design has to be careful. ## Why the code on the table has a lifetime A printed QR code that permanently identifies table six is a small security problem waiting to happen: someone photographs it and orders from home, on your table, all week. So the token behind a table code is signed and time-limited, and each use is recorded so the same one cannot be replayed. In practice a guest sees nothing — they scan, and it works. The value is that you can leave codes on tables without leaving the ordering channel open to anyone who once sat there. Ordering endpoints are also rate-limited, which is what stops a bored teenager sending forty orders to your kitchen in a minute. ## What an owned channel is actually worth The reason to do this is not modernity. It is arithmetic. An aggregator typically takes a meaningful slice of every ticket, and keeps the customer’s phone number, order history and address. Your own channel — a web ordering page, a QR menu, or your branded app — keeps all four. | What you keep | Aggregator | Your own channel | | --- | --- | --- | | The commission | No | Yes | | Customer’s contact details | No | Yes | | Order history for that guest | No | Yes | | Ability to run your own offer | Limited | Yes | This is not an argument for leaving the aggregators. They bring discovery, and discovery is worth paying for. It is an argument for making sure your **regulars** — the people who already know your name — are not being rented back to you every week. ## What makes guests abandon it Four mistakes cause most of the drop-off, and all four are avoidable: 1. **A PDF menu.** It is a document, not a page. Pinching and zooming on a phone is how you lose a guest at the first course. 2. **Photos of some items and not others.** The items with pictures sell; the rest look unfinished. Either photograph the whole section or none of it. 3. **Hidden fees at the last step.** A delivery fee or service charge that appears only at payment does more damage than the fee itself. 4. **Asking for an account before the order.** Let them order, then offer to save the details. Registration is a reward you ask for after value, not a toll before it. ## A sensible order of adoption - **Week one:** QR menu on tables and a web ordering page. No app install, no store review. - **Week two:** turn on ordering from the QR for dine-in, at a few tables first, with a waiter watching. - **Later:** loyalty points on the same account, so a returning guest sees their balance without asking. - **When the regulars are there:** your own branded app, because now there is a reason to install one. Do it in that order and each step pays for the next. Do it backwards — app first, no menu discipline — and you will have an app nobody opens. - QR menu - online ordering system - contactless ordering - restaurant website ordering ## In the product ### [Tables, QR & Reservations](https://gosufra.com/en/features/table-management-and-qr-ordering/) Explore ### [Customers & Marketing](https://gosufra.com/en/features/loyalty-and-marketing/) Explore ## Run all of this from one system POS, kitchen, inventory, recipe costing, staff and accounting — connected, and free to start. [Create your free account](https://app.gosufra.com/register?lang=en) ## Related articles ![Illustration of a storefront on a browser tab](https://gosufra.com/blog/your-restaurant-website.svg) Marketing 2026-08-09 · 7 min read ### [Your restaurant website: an ordering channel you actually own](https://gosufra.com/en/blog/your-restaurant-website/) What a restaurant site generated from the menu is for, how it differs from a QR code and from a branded app, when a custom domain is worth it, and why it beats renting your regulars from an aggregator. Read article ![Illustration of a prize wheel beside a points card](https://gosufra.com/blog/loyalty-promotions-and-spin-wheel.svg) Marketing 2026-08-20 · 7 min read ### [Loyalty, promo codes and the spin wheel: what actually brings people back](https://gosufra.com/en/blog/loyalty-promotions-and-spin-wheel/) How points, referrals, promo codes and feedback rewards fit together, why a personal offer beats a broadcast discount, and the rules that stop a loyalty scheme costing more than it earns. Read article ![Illustration of a floor plan with one table flagged](https://gosufra.com/blog/table-management-and-waiter-app.svg) Operations 2026-08-22 · 7 min read ### [The floor plan, the waiter app and the four states a table can be in](https://gosufra.com/en/blog/table-management-and-waiter-app/) How table status, waiter assignment, merges and split bills work together, why 'waiting for bill' deserves its own state, and what reservations should do about no-shows. Read article [← All articles](https://gosufra.com/en/blog/) [Contact us](https://t.me/GoSufraSupport)