Kirti Kumar Sahu · August 5, 2026 · 11:00 · 8 min read
Walk into any major airport today and notice how quiet the process has become. You check in on a kiosk, you find your gate on a screen, you board when your group is called. Nobody is shouting across a counter to confirm your seat number. And yet the lounges are full of conversation — people catching up, working, waiting together. The logistics went quiet; the people didn't. That's the distinction worth borrowing for cafes.
Now walk into your neighbourhood cafe. You sit down with someone you actually want to talk to, and the first thing that happens is your conversation gets interrupted — for someone to notice you, hand you a menu, take your order, remember your order, and eventually notice that you'd like the bill. Multiply that across every table in the room and you get the low hum of a restaurant floor: people waving for attention, waiters juggling requests, orders relayed by memory instead of by record. A cafe is supposed to be a place to talk and eat, not a place to manage logistics — and right now, far too much of the visit is logistics.
This piece is not a pitch for removing people from restaurants, and it's certainly not a pitch for a quieter room. It's an argument that cafes and QSR-style restaurants — the walk-in, order-at-your-own-pace, grab-your-food kind of place — are one missing piece away from letting the table stay yours, uninterrupted, the same way airports let travellers move through logistics without ever being pulled out of their own conversation. That missing piece is identity — and a storefront layer that connects it to the way a kitchen already runs.
Most cafes today have already taken the first half-step. There's a QR code taped to the table, you scan it, and you get a menu on your phone. That's where it stops. You still have to flag someone down to actually place the order, because the menu is a PDF, not a storefront. Nobody has built the layer that lets you go from scan to ordered to paid without a single conversation in between.
What's interesting is that the pieces to close this gap already exist — just not connected to each other. Swiggy and Zomato between them sit in almost every smartphone in urban India — Swiggy alone reported close to 18 million monthly transacting users last year, and Zomato a comparable number. Between food delivery and dining-out discovery, the two of them already know who you are, what you like to eat, and — increasingly — how you pay. On the other side, platforms like Petpooja, Odoo's restaurant tools, Restroworks, PosBytz, DineOpen, and a handful of similar players already run the back office for thousands of restaurants: their menus, their kitchen displays, their inventory, their billing.
A few attempts have already been made at closing part of this gap — Petpooja has its own Scan & Order flow, a couple of delivery platforms have piloted kiosk ordering at large chains, and some POS vendors have shipped multi-kiosk setups for big-format restaurants. None of them quite close the loop, though: they either skip identity entirely, so you're still typing in a phone number and waiting for an OTP every single visit, or they stop at the menu and leave billing exactly as manual as it always was. What's still missing is the storefront that sits between the two ends — something closer to what Shopify did for small merchants, except built specifically for a table, a QR code, and a walk-in guest.
Picture walking into a cafe you've never been to before. There's a small scanner on the table — the cafe's own storefront, not a shared listing on a delivery app. You scan it, and instead of filling out a phone number and waiting for an OTP, you simply continue with your Swiggy or Zomato account, the same way you'd continue with Google on a website you've never visited. One tap, and the cafe now knows who you are for this visit — nothing more, nothing less.
From there, the experience opens up. The menu isn't just a list of dishes and prices; it carries the texture that Swiggy and Zomato already do so well — what people ordered alongside this dish, how it was rated, what regulars tend to come back for. You order directly from your table. No one has to walk over to write it down. In the kitchen, the order simply appears. On your phone, you can watch it move — placed, being prepared, ready — the same quiet reassurance you get watching a delivery rider's dot move across a map, except now the "delivery" is thirty feet away. When it's ready, a waiter walks it over. That is, in fact, the only interruption your table has — and it's a welcome one, because it's the only moment that actually benefits from a human hand. Everything else about the conversation you were having stays exactly where you left it.
Paying is where most of the residual friction usually lives, and it's the part worth reimagining most. The moment you order, the estimated amount is simply held against the balance or credit already sitting in your Swiggy or Zomato account — the same trust mechanism that already lets you order food worth a few hundred rupees without typing your card details every time. When you're ready to leave, there's no flagging someone down for the bill, no card machine, no wondering if the tip got added twice. You simply share a one-time code with the waiter, they confirm it on the cafe's app, and the transaction settles. You stand up and walk out. That's the whole billing experience.
That's the guest side of it. Flip the perspective to a chain running fifty outlets across a city, and the same layer solves a different problem: instead of asking every guest to download a different branded app for every restaurant they walk into, one storefront handles all fifty, each one still looking and feeling like its own brand at the table.
It would be tempting to build this as yet another app that asks people to sign up, remember a password, and load in a new payment method. That's exactly the wrong instinct, and it's the reason most "smart restaurant" ideas quietly die after a pilot — they ask the guest to adopt something new for the sake of one meal. The entire value of this idea depends on not asking that. It depends on borrowing an identity people already carry everywhere.
That doesn't mean waiting around for Swiggy, Zomato, or Petpooja to decide to build it themselves, though. It's tempting to assume this can only ship as a feature inside one of those companies — but look at what each side actually owns today. The delivery and discovery platforms own the guest's identity, their reviews, and increasingly their wallet, but they stay focused on food coming to you. The restaurant-operations platforms own the kitchen, the menu, and the till, but they stop there. Neither side needs to become the other to make this work — they just need a layer that talks to both. That's a product in its own right: a storefront that plugs into guest identity on one side (Swiggy, Zomato) and restaurant operations on the other (Petpooja and the wider POS ecosystem around it), the same way Shopify never had to become a payments company or a courier to give small merchants a real storefront — it just had to connect cleanly to Stripe on one side and FedEx on the other, and get out of the way. A cafe owner should be able to spin up their own branded ordering storefront in an afternoon, get a scanner for every table, and let their guests do the rest using an identity they already trust — without any single one of these companies having to rebuild the whole picture themselves.
None of this has to stop at one cafe, either. A food court, a mall, or an airport terminal could run the exact same storefront across every counter, with one shared screen doing for orders what a departures board already does for gates — a single place to see every kitchen's status at once, instead of ten separate queues. And for a restaurant that wants to take the idea further upmarket, that same identity handshake doesn't have to live on a guest's own phone at all — it could sit on a small screen built into the table itself, with a guest simply tapping to confirm who they are and leaving the rest to the device in front of them.
None of this removes the waiter, and it shouldn't try to. It just changes what the job is for. Right now, a waiter's time gets split between taking orders, chasing the kitchen, and processing bills — the parts of the job that are really just relaying information back and forth. An uninterrupted table removes exactly that relay work, and leaves the part that actually needs a person: carrying a plate to a table, checking in on a guest, making a recommendation when someone genuinely wants one.
What guests get in return is a table that stays theirs for the whole visit — the same way an airport lounge lets a traveller sit with their coffee instead of standing in a queue. You walk in, you order at your own pace, you eat, and you walk out. No waving. No waiting to catch someone's eye. No end-of-meal scramble for the bill. Just the food, the company, and nothing pulling either of you away from the other.
This is the first of two pieces on the idea. The next one goes under the hood — how the storefront, the SSO, and the billing flow might actually be built.
Originally posted at https://medium.com/@kirtisahu05/the-uninterrupted-table-reimagining-how-cafes-take-your-order-42726cef9a58?sharedUserId=kirtisahu05