Use cases

QR ordering for full-service restaurants

Use QR ordering alongside your waiter team. Waiter approval gates fakes, the floor still walks.

QR ordering that works with a waiter team, not against it

Full-service restaurants do not want guests to feel like they are ordering at a vending machine. The job of QR ordering here is to remove the wait between sitting down and the first drink arriving, while the waiter keeps the social moments that matter. MobiTaste Growth runs 60 tables across three locations for $25 a month, and waiter approval keeps the floor in control of every first ticket.

The outcomes you should expect

  • Sixty tables per location on Growth at $25 a month. A 40-cover restaurant fits with headroom; a three-location group runs on the same plan without per-seat fees.
  • Waiter approval keeps the kitchen clean. The first order from each table waits in a Pending column until staff taps it through. The kitchen never sees an unapproved ticket, which means no wasted prep on a stranger’s prank scan.
  • The live order board appears in seconds on a normal Wi-Fi link. Cooks see the new ticket before the waiter has walked back to the floor, which collapses the standard pad-to-pass gap.

Why a full-service room benefits

A waiter takes drink orders, recommends a dish, and handles the cheque. A QR menu does not replace any of that. What it replaces is the awkward middle: the table that ordered drinks at 7:42, then waited until 8:01 to order food because the waiter was at another section. With the QR, the guest opens the menu while the waiter is delivering drinks elsewhere, and the order lands on the kanban before the waiter walks back.

The live order board is a kanban for new, in progress, and ready tickets. It is not a stripped-down menu viewer; cooks tap to advance, and the floor sees the same column move on their own device. No separate KDS device is required. A $150 Android tablet or an old iPad runs the same view as the manager’s laptop.

For mixed service, you can leave waiter approval on for the dining room and off for the bar. The setting is per restaurant in the current build; per-table policy is on the roadmap. The best-practices guide walks through shift patterns that work in real rooms.

How approval shapes the rhythm

The objection most full-service owners raise is that QR ordering removes the waiter’s authority. Waiter approval is the answer. Every first order from a table sits in a Pending column with the items, the modifier choices, and the guest’s selected language. The waiter taps Approve or Reject; the kitchen sees only approved tickets. Follow-up orders from the same table session can either flow through automatically or require approval each time, depending on the policy you set.

Approval also gates the Kunming-prank scenario: a stranger who photographs a printed QR cannot submit a useful order from outside the building, because the floor controls every first ticket. The mechanism is the same one a cautious owner wants on a Saturday night and can switch off for a quiet Tuesday lunch.

Hard caps run alongside approval. Maximum items per order, maximum items per session, and maximum orders per session per hour all default to safe values and tighten further on request. A 9,990-portion order returns a 429 long before the waiter sees it, which means the queue stays clean even on a viral-prank day.

Two questions full-service owners ask

Does this replace the POS? No. Your POS still rings the bill, processes the card, and prints the receipt. MobiTaste sits in front of the kitchen and the floor, handling the menu and the order intake. The POS comparison guide walks the trade-offs in detail.

Can my floor stay paper-only if a section prefers it? Yes. A waiter can still write an order on a pad and enter it from the dashboard. The QR is the fast path for the guest, not a requirement.

Start where the operations need it most

Print QRs for the bar section first, run a week with auto-approve on bar tables and waiter approval on dining tables, then expand. Pricing math sits on the pricing page; the audience pages live on the use-cases hub.

Operations

  • What happens when a guest scans the QR but never orders?

    The table session sits idle. After 30 minutes of no activity it auto-clears so the next guest starts fresh. You can set the window between 10 and 90 minutes per restaurant. The waiter can also clear it manually.

  • How do I stop strangers from spamming fake QR orders at my restaurant?

    Turn on waiter approval. The first order from every table waits for a staff tap in the order board. The kitchen never sees an unapproved order. Once a table is approved, follow-up orders go straight through unless you require approval each time.

Ready to start without stopping service?

14-day free trial, no card. First table order in under an hour.