QR Table Ordering: What It Changes in a Restaurant and What to Check Before You Buy One

QR code table ordering is a system where a guest scans a code at the table, the menu opens on their phone, the order goes to the kitchen on that table's ticket, and the guest pays and tips from the same screen when the meal ends. The code is trivial; what matters is the page behind it, the point of sale it feeds, and who keeps the guest afterwards.

Most writing on this topic is vendor copy, and its check-size and turn-time promises are the vendor's own unaudited figures. This post sticks to what the product documentation says the systems do, what the pricing pages charge, what the ADA guidance says about the page behind the code, and the questions left to ask.

How order and pay at the table actually works

Each table gets its own code, so the order routes to the right ticket. The guest scans, browses the menu with modifiers, and sends the order to the kitchen; staff deliver to the table on the ticket. At the end, the guest pays from the phone, tips from the suggestions, and can split the check.

Toast's and Square's documentation describe the same shape. Toast's Mobile Order and Pay overview says each table has a unique code, guests can combine orders into one tab or split them, servers can still add items from the point of sale or a handheld, and guests can save a card in advance to pay at the end of the meal. Square's page says each printed code maps to a table, walk-up window or parking spot, orders reach the point of sale and kitchen printers, and the ordering page is the restaurant's own Square Online site.

Two details from Toast's FAQ matter before launch day: guests cannot edit an order after submitting it, so menu copy and modifiers must be right, and the system does not work during an internet outage, so staff take orders until it returns.

What changes for servers, turn times and the check

The order-taking trip and the payment trip leave the server's route, and everything else follows from that. Toast's overview states that orders going directly to the kitchen reduce server trips, and that restaurants have reported reduced front-of-house labor, improved table turns and a larger average check, without publishing figures for those three; its one printed figure is a revenue claim of its own. Treat every number a vendor prints as a claim to test on your own floor.

The honest version is qualitative. Servers spend their time on the table rather than the terminal, which some guests read as better service and some as being left alone. Checks close when the guest decides, not when a server returns with the card machine, which is where a faster turn would come from. A guest who can reorder a drink without catching anyone's eye sometimes will. Pilot one section for four weeks and compare average check, covers per server and time from first scan to paid against last year.

Accessibility, and the guest who does not want it

Some guests will not scan, cannot scan, or should not have to, and the system has to serve them anyway. Toast documents that a server can still take the order on a handheld or the point of sale and that the guest can join the same check, so a paper menu and a human stay available at every table. The code is an option, not the gate.

The accessibility question is about the page behind the code. The Department of Justice's web accessibility guidance states that the ADA's requirements apply to all the goods, services, privileges or activities offered by public accommodations, including those offered on the web, lists food and drink establishments among businesses open to the public, and points to the Web Content Accessibility Guidelines as helpful guidance. A menu served as an image or PDF is unreadable to a screen reader; a text menu with real headings, contrast and keyboard-reachable buttons is not. Ask the vendor to show the page in a screen reader first.

The menu as text, and why search engines care

A QR ordering page is a public web page with every dish, price and description on it as text, which a search engine can read and a PDF menu is not. Google's Business Profile page for restaurants says a restaurant can edit its menu on the profile, work with online ordering providers for takeout and delivery, and indicate a preferred ordering partner. Point that preference at your own page.

The consequence: the page that takes the order at table twelve is the page a guest in Dilworth finds when searching for the dish, if it lives on your domain as text. Keep one menu source feeding the table page, the website and the profile, so a price change is live everywhere the same night.

Who owns the guest after they pay

The guest's phone number and order history land in whichever database the ordering page writes to, and that differs by vendor. Toast's FAQ says a guest can create a Toast account with a phone number and save payment details, and its overview says the tool helps a restaurant build a guest database for marketing. Square's 2020 launch release says the feature lets sellers collect customer information and award loyalty points.

Read the contract for three things: whether you can export the full guest list at any time, whether the vendor may market to your guests under its own brand, and what happens to the list when you cancel. Uber Eats' pricing page draws that line on the delivery side, listing customer data access for its Webshop and analytics only for marketplace plans; a QR vendor should be as plain.

What it costs, and the eight questions for the vendor

Costs come in three layers: software, card processing on every order, and hardware. Square launched its QR self-serve ordering in September 2020 at no additional charge, with processing at its published online rate of 3.3 percent plus 30 cents on the free plan and 2.9 percent plus 30 cents on paid plans, as of October 2026. Toast prints no price for Mobile Order and Pay; it quotes. Codes, stands and a kitchen printer are the hardware.

What this looks like when it runs

Running, the system is one loop: the code opens a menu the restaurant owns, the order lands on the right ticket, the payment closes the check, and the visit is recorded against a guest the restaurant can reach again, with a rewards balance that follows them home.

Mirastart built the ordering and rewards side of that loop for Sushi Hana's two Charlotte locations, in Ballantyne and South End, with payment staying on the restaurant's point of sale. A guest scans the code at the table, the menu opens on their phone, the order reaches the kitchen on the right table's ticket, and the reward balance sits beside it in the Sushi Hana Club app, which the guest keeps on their phone for the next visit. Whether you buy a platform's module or have it built around your own menu and rewards, the eight questions are the same.