Tap-to-Order & UPI Payments — From Menu to Kitchen in 30 Seconds

Most QR menus are just menus — diners scan, read, and then verbally tell a waiter what they want. QRSeva's ordering feature closes the loop: the diner builds the order on their phone and sends it directly to the kitchen. The waiter becomes a checkpoint (confirming the order arrived correctly, bringing the food, attending the table) rather than a transcription service. The economics shift considerably.

How tap-to-order works

When a restaurant has ordering enabled, every menu item gets an "Add" button. The diner taps an item, picks customisations (spice level, milk type, size), adjusts quantity, and the item drops into a cart that sticks to the bottom of the screen. They keep adding, and when ready, tap "Place order".

At checkout, the diner enters their name and (optionally) phone number, picks a payment method, and confirms. The order is dispatched in two streams: a kitchen-printable ticket to your KOT printer (or order screen) and a customer-facing receipt that updates as the order moves through preparation. The waiter sees the new order in their dashboard within 5 seconds of the diner confirming.

The UPI and card payment integration

For restaurants in India, QRSeva supports UPI as the primary payment method. The diner taps "Pay with UPI", the platform generates a UPI link, and the diner's phone offers GPay, PhonePe, Paytm, BHIM, or any UPI app installed. They authorise. The payment confirms in 2-4 seconds. Settlement happens via the restaurant's configured UPI VPA or merchant account.

Card payments work through Razorpay or Stripe depending on your region — Razorpay for India (Visa, Mastercard, Rupay, plus saved cards), Stripe for international restaurants (Visa, Mastercard, Amex, Apple Pay, Google Pay). The diner enters their card details on a hosted payment page that never touches the restaurant's systems; the restaurant receives a settled payout the next business day.

Cash on delivery / pay-at-counter is also supported as a fallback. The diner picks "Pay at counter", the order goes to the kitchen, and the restaurant collects payment when the food is served. This option is most useful for casual dining where a digital menu replaces the printed one but the restaurant prefers to handle cash directly.

Three ordering modes

Table service mode

Diners sit, scan, order, and the food comes to their table. The order ticket includes the table number (printed on the table QR sticker), so the kitchen knows where each order goes. Diners can pay at the end of the meal — adding more items as they go — or pay upfront. Best for sit-down dining.

Takeaway mode

Diners scan from outside the restaurant or from the counter, order, pay upfront, and the order ticket includes pickup time. The kitchen prepares; the counter calls the diner when ready. Best for QSRs, takeaway counters, food trucks.

Quick-pay mode

Diners order verbally, the waiter rings it up in their dashboard, and a payment link is sent to the diner's phone via WhatsApp or SMS. The diner pays directly without the waiter handling cards or cash. Best for restaurants that want digital payment without the full ordering flow — closes the cash-handling gap.

What happens in the kitchen

When an order is placed, the kitchen receives the ticket via one of three channels: a thermal-printed KOT (kitchen order ticket) on your existing printer, a digital order list on a tablet, or directly into your existing POS system if one is integrated. The choice is yours — set it once during setup.

Each ticket includes: table number (or pickup time), items with customisations, dietary notes ("no onion", "extra spicy"), and the order timestamp. The waiter or kitchen manager marks the order as "preparing", then "ready", and the customer's on-screen order status updates in real-time.

Cutting the verbal-order bottleneck

In traditional dining, the waiter is the bottleneck. They take orders verbally, write them down, walk to the kitchen, hand off the ticket. A four-person table's order takes 3-5 minutes of waiter time. During peak hours, with 30 tables, this becomes the rate-limiting step. Either the waiter is rushing (and getting orders wrong) or diners are waiting.

Tap-to-order moves the bottleneck. Diners take their own order, simultaneously, in parallel. The waiter's time goes to attending the table, refilling water, bringing food — actual hospitality work. Across the QRSeva network, restaurants that enable ordering report 8-12% faster table turnover during peak hours, simply because the order-taking step disappears.

Handling order modifications and combinations

Real menus have variants: a Margherita pizza comes in 9-inch and 12-inch, a coffee comes with whole/oat/almond milk, a thali has a vegetarian and a non-vegetarian version. QRSeva's ordering supports these as inline customisation chips on the item card. The diner picks their variant before the item drops into the cart.

Combo deals — buy-2-get-1, lunch-special pricing — are configured at the menu level. When a diner adds items that qualify for a combo, the cart auto-applies the discount and shows the saving. No coupon code needed.

Reliability and offline fallback

The ordering feature degrades gracefully when payment infrastructure has a hiccup. If UPI is down, the diner can pick card. If card is down, they can pay at the counter. If their internet is flaky mid-order, the cart state persists locally on their device — they can keep scrolling and confirming without losing their selection.

Settlement is direct between the diner and the restaurant's payment processor. QRSeva does not hold the money — payments route through Razorpay/Stripe/UPI directly to your account, with QRSeva taking a small transaction fee on the payment processor side (1.5-2.5% typical, varies by method).

When NOT to enable ordering

Tap-to-order makes sense for casual dining, QSRs, cafés, takeaway counters and most mid-market restaurants. It doesn't fit every restaurant. Skip it if: you run a tasting menu where the chef chooses the order, you run a small fine-dining venue where the waiter's in-person interaction IS the product, or you have a kitchen that genuinely can't accept multiple orders simultaneously (a one-cook operation that can only cook one dish at a time).

For these venues, the QR menu still works perfectly — diners just read it and order verbally. Ordering is an opt-in feature, not the default.