Table ordering (QR)

Table ordering lets seated guests open your menu on their phone, build a cart, and send food to the kitchen — paying either per round or at the end, depending on your payment mode. Staff still see the same orders on the floor map and order panel.

Before you begin

You need a plan that includes table ordering / table payment, an Active Stripe connection on Payments if guests will pay by card, and a published menu with dishes. Turning the feature on lives under Settings → General. Putting a durable QR on the table is often done with Dynamic Links.

Turn table ordering on

1. Open Settings → General.
2. Find Table ordering (wording may read as ordering from a QR at the table).
3. Switch it on and Save changes (or use the unsaved-changes bar).
4. Confirm Payments shows Payouts active if guests should pay by card.

Without table ordering enabled, table QR destinations may not offer the full order experience even if payments are set up.

Give each table a QR

Guests need a link that is tied to this restaurant and this table. Common patterns:

• Dynamic Links — print a stable goto… QR once, re-point the destination when you reprint menus or change URLs. See Dynamic links.
• Table / map tools — generate or print a table-specific order code from the floor map or table tools when your plan exposes them.
• Operator app — paired tablets can take orders on the floor for guests who do not want to use a phone (see Connected devices).

Tip

Print the QR on the table tent, not only in a PDF: staff should be able to point at it during service. Re-test one table after every menu or payments mode change.

What the guest does

Exact screens follow your menu template and branding, but the flow is the same:

1. Scan the table QR → open the public order page for that table.
2. Browse categories and dishes (same menu you maintain in the CRM).
3. Add items and options to the cart.
4. Depending on mode:
   • Pay per round — pay with card, then the order goes to the kitchen. Further items start a new round.
   • Pay at end — Order / send to kitchen first; Pay the bill later (full bill, split, tip).
5. After payment, the guest sees a paid / settled state so they do not double-pay.

Staff can still add lines from the CRM; in pay-at-end mode those lines join the same table bill.

What staff sees

• Live floor map — table activity during service; open the table to work orders.
• Order panel — lines, status (open / submitted / …), paid badge when applicable, Cancel & refund when a card payment exists.
• Table bill (pay at end only) — outstanding amount, shares paid, settle offline, refund bill.
• Kitchen / KDS (if enabled) — tickets when the order is submitted according to your mode.

Cart sections after the kitchen has the ticket

Once a round is in the kitchen, the guest cart typically separates:

• items still being composed,
• ordered items already sent,
• served items when staff mark them done,

so guests do not re-order the same dish by accident while they add dessert.

Related

When customers payPay per round vs pay at end.

Bills, splits & offline settleEnd-of-meal payment options.

Menus overviewBuild the menu guests order from.

Dynamic linksStable QR codes for the table.