Best QR Table Ordering Software: 5 Steps to Pick in 2027

The decision comes before the feature list

For a small restaurant, the first choice is not which QR menu looks best. It is whether you need a QR ordering layer that sits beside a point-of-sale system you already run, or a POS that handles table ordering, payments and the kitchen in one place. A layer costs less to start when your current POS already sends tickets to the kitchen reliably. A full POS makes more sense when you are replacing your system anyway, because two systems mean two menus, two sets of sales reports and a nightly reconciliation step.

QR table ordering is a setup where each table carries a code that guests scan to open the menu, place an order and, on some products, pay without flagging down a server.

TL;DR: If you already run a POS, shortlist the ordering layers that publish a price and confirm POS routing in writing. If you are replacing your POS, compare full systems on the monthly total after add-ons and processing, not the plan fee on the front page. Any feature a vendor page does not mention should count as unconfirmed until the vendor answers in writing.

The stakes are rising. The National Restaurant Association's 2026 release puts 2026 restaurant and foodservice sales: $1.55 trillion according to National Restaurant Association (2026). It also says "Operators will be focused on investments in innovative solutions like digital ordering and payments."

Key Takeaways

• Decide whether you need an ordering layer or a full POS before comparing features, because that choice sets your real monthly cost.

• Six products are profiled. Prices come only from each vendor's own pricing page. Toast is excluded because we could not verify its current plan prices or table-ordering details from pages we could open, so check Toast's pricing page and get a written quote.

• Sunday, UpMenu and Lightspeed describe guest QR ordering or pay-at-table on their own pages. SpotOn's table QR flow could not be confirmed from pages we could open. Square's pricing page shows QR payments on receipts but does not show guest QR ordering, so confirm which plan includes Square's self-serve ordering and what it costs.

• Processing rates, minimum terms and add-on fees are where headline prices mislead, so check them before you compare totals.

• A proposed reconciliation workflow can flag mismatches between guest orders and the POS, but it needs exports or API access, and a person must approve every adjustment.

How we evaluated these tools

This is an informed buyer's guide built from public vendor pages and independent sources, not hands-on trials. The ratings scale below tells you what to check, not a score we assigned. The weights reflect what usually causes regret after a QR ordering rollout: guests cannot order or pay, orders do not reach the kitchen, or the bill is larger than the headline.

Toast is absent from the price and feature tables because we could not verify its current plan prices or table-ordering details from pages we could open. We print no Toast price or feature claim, so check Toast's own pricing page, request a written quote, and compare it with the products below.

The category has also been volatile. A PYMNTS index recorded Eateries offering table QR ordering: 42% to 25% according to PYMNTS (2022). The share fell from 42% to 25% between September 2021 and April 2022. That is an older snapshot, so read it as a sign the category is volatile, not as a current adoption rate.

What the vendor pages confirm

The matrix records only what the vendor pages we could open say. "Not confirmed" means we could not verify the feature on an opened page. It does not mean the product lacks the feature.

What the published prices add up to

Pricing checked October 30, 2026. Every figure below comes from the vendor's own pricing page. Cells say "Quote-based" or "Not published" where the page gives no figure.

Read the table as a starting point, not a total. Lightspeed's page lists its three plan prices without a billing period, so confirm whether they are monthly before comparing them with anyone else's figure. Square's US page shows no base monthly price for Plus or Premium, only per-device add-ons, so a Square setup needs a written quote for the base cost. TouchBistro leaves hardware and payment processing outside its starting prices. SpotOn's All-In plan has the lowest published base fee in the table, but its page pairs that with processing minimums and a term, so the headline fee is the least useful number on that page.

Vendor profiles: best fit, limits and rollout

Each profile separates what the vendor publishes from our read. The evidence for each is the pricing page cited in the table above, which is the primary page we could open for that product.

Sunday: guests order, reorder and pay from one code

Published facts: Sunday's pricing page describes guests who "Scan, order, reorder and pay - one QR code." The Standard plan includes payments, ordering, online reputation, guest data collection and operations reports, and leaves out loyalty integration and the Enterprise Pack. Premium adds loyalty integrations and enterprise tools. The page contains no transaction or processing fee wording.

Our read: Sunday fits a single-location team that wants guests to pay at the table on a plan with a clear feature split. The limit is what the page leaves open. It does not say whether Sunday replaces your POS or how tickets reach your kitchen, and it shows no processing rate. Before you sign, get the kitchen routing and processing schedule in writing, then test one table end to end.

Choose it if guest payment at the table is the main goal. Disqualifier: no written answer on kitchen routing, or no written processing schedule.

UpMenu: an ordering layer for a POS you already run

Published facts: UpMenu's pricing page lists three web ordering tiers by order count. An overage fee applies only when accepting additional orders is switched on. If that setting is off, online orders and reservations stop at the limit. QR Code Menu is listed as included in the core platform. Tableside Ordering is described as self-order and pay at the table with no server needed, sold as a per-location module. POS integration is a no-charge module that sends online orders to your existing POS.

Our read: UpMenu fits a restaurant that keeps a working POS and wants guests to order at the table without replacing the register. The main limit is scope. UpMenu adds an ordering layer, so you still need a POS for service and in-person sales. Watch the order cap, because with the overage setting off, a busy night can cut off orders. Pick the tier from your real monthly order count, confirm the POS module with your current POS vendor, and test a table before you go live.

Choose it if your POS already works and only the table ordering is missing. Disqualifier: you need one system for every sale.

Lightspeed: a full POS with table ordering on one platform

Published facts: Lightspeed's restaurant pricing page lists Starter, Essential and Premium plans, with Enterprise on quote. It lists "Order and pay at table," described as "Includes QR code ordering," and says it is "Also available on all plans as an add-on." Kitchen display screens are priced per screen per month. The page does not publish processing rates and says prices "may vary depending on the nature of the business and the industry."

Our read: Lightspeed fits a restaurant that wants a full POS with table ordering on one platform and has someone to build the menus. The limits are clarity and missing numbers. The add-on wording does not make clear which tier includes what, and processing rates are absent. Get written confirmation of the tier that includes table ordering, the kitchen screen count and the processing rate before you compare totals.

Choose it if you want a full POS and can absorb a setup period. Disqualifier: a quote that leaves processing and kitchen screens out of the total.

TouchBistro: staff-run tableside ordering on a POS

Published facts: TouchBistro's pricing page lists a Point of Sale plan that requires hardware, and an Essentials Bundle that includes integrated payments and restaurant-grade hardware. Its FAQ says the POS plan includes Tableside Ordering, which staff use at the table. Online ordering is a separate add-on priced on quote. The FAQ says there are no commission fees on online orders. TouchBistro's public pages do not confirm guest-side QR ordering, so it is unconfirmed until the vendor confirms it in writing.

Our read: TouchBistro fits a full-service room where servers carry handhelds and the team wants a POS with tableside ordering. The limits are that guest self-ordering is unconfirmed on the pages we could open, and online ordering is quote-based. Budget the hardware, decide whether guests will order on their own phones, and ask for online ordering pricing in writing.

Choose it if staff take orders at the table. Disqualifier: guest self-ordering is the main goal and the vendor cannot confirm it in writing.

SpotOn: a POS-first setup with a term to check

Published facts: SpotOn's pricing page lists an All-In plan with POS hardware included, processing minimums and a minimum term. It lists a POS Essentials plan described as "Ideal for most restaurants, with month-to-month flexibility." Both list "Ordering" and "Table layouts," and neither mentions QR codes. SpotOn's help center appears to document a table QR order-and-pay flow, but SpotOn's public pages do not confirm that flow, so get written confirmation of it.

Our read: SpotOn fits a restaurant that wants a POS-first setup and can accept processing terms in exchange for a low upfront cost. The main limit is the QR claim itself, which needs written confirmation before you plan around it. Test a table QR end to end with your menu before you order hardware, and get the minimum term and processing minimums in writing.

Choose it if you want a POS-first setup and accept the processing terms. Disqualifier: a term or processing minimum you cannot accept, or no written confirmation of table QR ordering.

Square: a POS you may already own, with guest QR ordering to confirm

Published facts: Square's US restaurant pricing page lists a Free plan alongside Plus and Premium, but shows no base monthly price for Plus or Premium. It shows per-device add-ons for a kitchen display app and kiosks. Its QR feature is described as "QR code payments on receipts," which the page says speeds table turnover. A custom Square Pro tier is aimed at high-volume processors.

Our read: Square fits a restaurant already on Square hardware that needs payments and a POS. Guest QR ordering is not shown on the pricing page, so confirm which plan includes Square's self-serve ordering and what it costs. The page shows receipt QR payments, which are not guest table ordering. If you plan an integration, read the event details in the worked example below, because Square's developer documentation limits when some events fire.

Choose it if you already run Square. Disqualifier: a plan that depends on guest table ordering that Square's pages do not confirm.

Which to shortlist, by situation

A worked month on a per-order plan

Take an illustrative café that takes 90 guest orders in one month on a web ordering tier like UpMenu's. UpMenu's published figures used here are a $49 tier with 75 orders, a $1.90 charge per extra order and a $19 Tableside Ordering module per location, according to UpMenu. The 15 orders over the cap cost 15 × $1.90, or $28.50, which brings the tier to $77.50. Adding Tableside Ordering at $19 gives an illustrative $96.50 a month, before processing and before a POS, which UpMenu does not replace. If the café's POS were Square instead, a workflow listening for Square's order.created event would miss orders keyed into the Point of Sale app, because Square's developer reference says that event fires only when the CreateOrder endpoint is called.

The reconciliation work the price table leaves out

The price table does not show who checks that a guest-placed order reached the POS and was paid. A configurable workflow we would propose for that gap is a nightly reconciliation. The trigger is a run scheduled after close. It reads the day's closed checks from the POS export and the guest-order export from the ordering product, compares counts and totals, and sorts every mismatch into a void, a comp, an unsent item or a missing ticket. The output is an exceptions list in a Google Sheet and a short summary sent from Gmail to the manager on shift. Prerequisites are a CSV or API export from both systems, a Google account with Sheets and Gmail connected, and one named owner for the sheet. The human review point is that a manager approves every comp or void before anything reaches the books, and the workflow posts no accounting entries on its own. US Tech Automations describes its service as designing, building and running workflows for clients, so ask what the export looks like before you assume the design fits.

A second proposed workflow handles guest feedback. The trigger is a new submission from a feedback form or review request. The action tags each message as wait time, order accuracy, or allergy or food safety, and drafts a reply for the manager. The output is a Gmail draft that a person edits and sends. Any message that mentions an allergy goes to a phone-call escalation to the manager on shift, not into a draft queue. Prerequisites are access to the feedback export, a Gmail connection, and a keyword list the team has written and approved. The site describes support drafts that are reviewed before sending, and this design keeps that rule, so no reply reaches a guest without a person approving it.

The trigger decides whether the reconciliation can be trusted, as the Square example above shows. Test any trigger against a sample of real checks before go-live, and treat a gap between the two lists as a failure to investigate, not a rounding difference.

Build it yourself, stitch it together, or buy the workflow

Many buyers will try to stitch this together in Zapier, Make or n8n, or build it in-house. Those tools can keep run histories, retry failed steps, branch on errors and keep audit trails when you configure them. What they do not supply is the design you own: idempotency so a retried event does not count a check twice, escalation when a run fails, access controls on the keys that read guest and payment data, and maintenance when a POS changes its export format. A proposed US Tech Automations design could configure the same retries, error branches and escalation paths, but the restaurant still supplies the exports or API credentials and approves each review point, so the work moves rather than disappears.

When NOT to use US Tech Automations: skip a custom build if your ordering product's own sales report already matches your POS totals every night, because the check is already done for you. Skip it if you run one location on one system and nobody will read an exceptions list each week, since an unread list gives no control. And skip it if one Zapier or Make step covers the only handoff you need, because a custom design adds review points you would then have to maintain.

Who this is for

This guide is for an owner or operations lead at a small restaurant who is close to choosing. If you run one kitchen and want guests to order and pay from the table, start with the feature matrix. If you have to replace the POS, start with the pricing table and ask each vendor for a written quote on the total. Operators prioritizing customer-experience tech: 60% according to MarketScale (2026). That figure is survey data about priorities, not a verdict on any one product.

Red flags: nobody on the team can approve voids and comps, the kitchen has no reliable ticket printer, or the menu changes daily with no one assigned to update the QR system.

Common mistakes

• Comparing headline plan fees without add-ons, kitchen screens, processing and hardware.

• Treating a QR menu as QR ordering. A menu that guests read is not the same as an order that reaches the kitchen.

• Switching on additional orders without a monthly cost ceiling, which turns a cap into an open bill.

• Skipping the test table. Scan, order and pay with your real menu before you order hardware.

• Leaving the guest-order export unreconciled. Mismatches between guest orders and the POS are where missing revenue hides.

Five steps before you sign

1. Decide whether you need an ordering layer on your current POS or a full POS replacement.

2. Get written answers on guest ordering, pay-at-table, kitchen routing and processing rates for each shortlisted product.

3. Turn the published prices into one monthly estimate that includes add-ons, kitchen screens and processing.

4. Test one table end to end with your real menu, including a split check and a card payment.

5. Name the person who approves exceptions, and set the reconciliation check before you go live.

Frequently asked questions

Do I need a new POS to get QR table ordering?

No. An ordering layer such as UpMenu's can send orders to a POS you already have, but you then still need that POS for table service and in-person sales.

Is QR table ordering cheaper than servers?

The vendor pages we opened do not compare QR ordering with server labor, so the answer depends on your own labor costs and order volume.

Can a guest pay at the table without an app?

Sunday, Lightspeed and UpMenu each describe paying from the table code on their pages, but none of those pages says whether the guest needs an app.

Is the published price the whole cost?

No. The pages we opened also list per-order fees, device add-ons, processing rates, hardware or minimum terms, so the headline price is only the starting point.

Why is Toast not in the table?

We could not verify Toast's current plan prices from pages we could open, so we print no Toast figure. Check Toast's own pricing page, request a written quote, and compare it with the products above.

Choosing this week

Start by writing a one-line decision: an ordering layer on the POS you run, or a POS replacement. Then shortlist two products from the table, get their written answers on guest ordering, processing and terms, and run one table end to end. If you are still deciding between online ordering and the counter, our earlier comparison of online ordering and manual service covers that choice. For the reconciliation side, see how US Tech Automations configures this, including the exports you would need to supply and the review points a person would keep.