The Indian Restaurant Operator’s POS Playbook.

Walk into any 30-cover restaurant in Coimbatore, Bangalore, or Chennai at 7:30 PM and you’ll see the same scene. The owner-cum-cashier is hunched over a 3-year-old desktop running some “restaurant POS suite”, taking a phone order while a waiter shouts an “extra spicy, no ghee” change toward the kitchen. The KOT prints. The waiter realizes they printed the wrong table. The kitchen runs the wrong dish anyway because they printed two minutes ago. The customer is waiting. The bill at the end has the wrong tax slab because someone forgot to update the GST rate when the rules changed three months ago.

This is what running a restaurant in India in 2026 looks like — and the irony is, every one of those problems exists despite the operator paying ₹3,000 a month for their POS software.

We've spent the last year talking to restaurant operators across South India about what they actually use, what they’ve abandoned, and what they wish someone would build. Here’s the honest playbook.

1. Most POS software is built for software professionals — your kitchen staff isn’t one

The single biggest reason restaurant POS deployments fail is this: the average steward, biller, or kitchen captain has never opened Excel. They speak English at the till but write Tamil, Telugu or Hindi at home. They learn the till by watching, not by reading documentation.

But your conventional restaurant POS — Petpooja, Posist, Limetray, even Square’s restaurant package in markets where it operates — is a feature-loaded system designed by software people for software people. Tabs nested inside tabs. Modal dialogs that open more modals. “Settings” pages with 40 toggles. To do something as basic as “split a bill between two cards”, you click into 4 different screens.

The result: 80% of features go unused. Your staff find one screen — usually the cart — and they live there. Anything that needs a deeper menu becomes a 3-minute support call.

What works instead: software designed around what the operator is actually doing right now. One screen for billing. One tap to add an item. KOTs print without anyone clicking “send”. A weekly summary that’s two paragraphs, not a 12-tab dashboard.

HeyMachi was built with this single rule: if a steward can’t learn it in 20 minutes by watching the previous shift, it doesn’t ship. Every screen has been reviewed by an actual restaurant owner who’d never written a line of code. If they got confused, we changed it.

2. You’re paying for 80% of features you’ll never use

Most Indian restaurant POS software is sold as a bundled monthly package — ₹2,500 to ₹5,000/month for the “Pro” tier — that includes inventory, online ordering integrations, customer database, payroll add-ons, marketing tools, “loyalty engine”, multi-outlet management, and a “BI dashboard”. Your restaurant uses billing, KOT, and maybe basic stock counting.

You’re paying full price for things you’ll never log into. Worse, the more features the system tries to do, the slower it gets, the more bugs it ships, and the more “Pro” pricing tiers it tries to upsell you into.

HeyMachi’s approach: turn on POS day one. Pay nothing else. The day you decide you actually need inventory, turn on the inventory plugin and start paying for that one. The day your restaurant gets to 5 staff and you need real attendance and payroll, turn that on too. Volume-based, modular, switch off any month with no penalty. We don’t have a “Premium” tier — we have eight modules, you pick yours.

This isn’t a marketing slogan. It’s the architecture: every module is a separate plugin that the platform loads on demand. Your bill scales with what flows through, not with how many checkboxes you’ve ticked.

3. Inventory in F&B is its own beast — and most software pretends it isn’t

Here's the dirty secret of restaurant inventory: what you buy and what you sell are not the same thing.

You buy 5kg of chicken, 100ml of cream, 2 packets of cardamom. Your menu sells “Chicken Korma” and “Mughlai Biryani”. The chicken from those 5kg gets divided across both dishes (and probably tomorrow’s tikka masala). Some of it gets wasted. Some of it goes home with a staff member nobody talks about.

Generic inventory software handles this terribly because it’s designed for retail — buy product, sell product, simple. F&B inventory needs recipes (BOM): 1 portion of Chicken Korma = 180g chicken + 30ml cream + 0.5g cardamom + ... When you sell 12 plates of korma tonight, the system has to decrement 12×180g chicken, 12×30ml cream, etc. — automatically.

Most “restaurant POS” tools don’t do this at all. The ones that do (Petpooja’s premium tier, Posist’s enterprise) require you to maintain elaborate BOM spreadsheets and reconcile manually every week. By the time you’re done, you’ve spent 4 hours that should have gone to the floor.

HeyMachi’s inventory module is built F&B-first:

• Define each menu item’s recipe once. Stock decrements automatically with every KOT.
• Bill scanner: snap a supplier invoice — Machi reads it, matches SKUs, updates stock. No manual data entry, no missed line items.
• Wastage tracking: when actual stock count diverges from theoretical, the system flags it. Now you can have a real conversation with the kitchen instead of guessing.
• Reorder alerts before you run out of butter at 8 PM on a Saturday.

4. The KOT-to-table dance — five minutes that compound

The single most expensive five minutes in any restaurant evening is the KOT round trip:

1. Customer orders
2. Waiter writes it on a slip
3. Waiter walks to the till to enter it
4. KOT prints in kitchen (if the printer is having a good day)
5. Customer realizes they wanted “no onions”
6. Waiter walks back to the till to correct it
7. Waiter walks to kitchen anyway because the printer is unreliable
8. Customer waits

Multiply that by 30 covers across an evening and you’ve burned an hour of waiter time and frustrated half your customers.

HeyMachi’s KOT loop is mobile-first by design:

• Waiters take orders on a phone or tablet at the table — no walk to the till
• KOT appears on the Kitchen Display Screen (KDS) instantly — no printer, no paper, no “did it print?”
• Edit an order from the table — kitchen sees the change in real-time, not on a re-printed slip
• Auto-route to the right kitchen station: tandoor, fryer, cold counter — each station sees only what they need to make

Most conventional POS software either doesn’t have a KDS at all (relies on receipt printers — fragile, paper-wasteful) or charges extra for it as a “premium add-on”. HeyMachi’s KDS is included with the restaurant industry pack. No extra license. No extra hardware beyond a basic Android tablet you hang in the kitchen.

5. QR ordering — let the customer order themselves

Restaurants in India lost an entire labour cost line during COVID and never got it back: the assumption that a waiter has to take every order. Today’s customer — especially the under-30 customer — would rather scan a QR code, browse the menu on their phone, customize their order, and tap “send to kitchen” themselves.

This isn’t just convenience. It’s:

• Faster table turnover — no waiting for a waiter to be free
• Fewer order errors — the customer typed it, not the waiter
• Higher average ticket — customers order more when nobody’s standing over them
• Lower labour cost — one waiter can handle more tables

HeyMachi includes QR ordering in the restaurant industry pack. Print one QR per table. Customer scans → branch-specific menu loads → orders go straight to KDS → waiter only handles delivery and payment. Most conventional POS systems either don’t support QR ordering or sell it as a bolt-on at ₹500–1500/month per outlet.

6. The food-aggregator tax — and how to opt out

Swiggy and Zomato take 22–30% of every order. For a typical mid-tier restaurant doing ₹3 lakh/month through aggregators, that’s ₹66,000–90,000/month leaving the building in commission alone. Multiply that across a year and you’ve paid for a small car.

The aggregators justify this with traffic — they bring you customers you wouldn’t have reached. Fair, for new restaurants. But after 18 months of operation, ~60% of your aggregator orders are repeat customers who already know you. You’re paying 25% commission on customers you’ve already won.

HeyMachi’s customer app changes the math:

• Every restaurant on HeyMachi gets a branded customer app — your logo, your colors, your menu, your loyalty
• Customers can order delivery or pickup directly from your app — your delivery (or hire your own runner), your delivery charge (which goes to you, not a platform), your loyalty rewards
• The cross-shop loyalty network brings new customers from neighbouring HeyMachi shops
• One-time setup. Zero commission per order. Forever.

This isn’t an “alternative to Swiggy” — keep Swiggy/Zomato for new customer acquisition if it works for you. But for repeat customers, give them a one-tap reorder app where 100% of the order value stays with you.

7. Reports that actually answer questions

Every restaurant POS ships with a “dashboard”. 12 charts. Sales by hour. Sales by day. Top items. Average ticket. You glance at it once a month and ignore it the rest of the time.

The actual question you have at 11 PM is: “Was tonight better or worse than Tuesday last week, and why?” That’s not a chart question. That’s a conversation.

Machi-AI answers it. Plain English query, plain English answer, rooted in your real data:

You: “Was tonight better than last Tuesday?”

Machi: Tonight: 47 covers, ₹38,420 in sales. Tuesday last week: 52 covers, ₹41,180. Two things stood out — filter coffee was out of stock from 8:10 to 9:40 PM, you lost ~6 orders worth roughly ₹720. Steward Ravi clocked out an hour early so tables 5–8 didn’t turn after 9:30 PM. Want me to draft a re-order and a shift adjustment?

That’s the difference. Not a chart you stare at. An assistant you ask.

8. Mobile parity — your restaurant runs from your phone, not your desktop

Most “restaurant management software” treats mobile as a sidekick: a stripped-down “owner app” for checking yesterday’s sales while you’re away. The actual operations — billing, KOT, inventory, payroll — happen on a desktop somewhere.

This is backward. Modern restaurant operators run their floor from a phone in their hand. Walking the kitchen, talking to a customer, settling a bill at the table, approving a leave request from a steward — all between the till and the door.

HeyMachi has full feature parity across iOS, Android and web. Every action you can take on a desktop, you can take on the phone. Bill, scan, hire, approve, run payroll, close the kitchen — from the till, the takeaway counter, or your auto-rickshaw home.

Side by side — HeyMachi vs the conventional stack

Where do we go from here?

If you’re running a restaurant and any of the above sounded too familiar — we’d like a 20-minute conversation. Not a sales demo, an actual conversation about your shop. Where it’s bleeding margin, what software you’ve already given up on, what you actually need.

Send a note to sales@heymachi.ai with one line: “I run a restaurant in [city]. The biggest pain is [whatever it is].” We’ll reply within a working day with a tailored walkthrough on your floor — your menu, your numbers, your problem.

The first month is on us. No card. No clock. If after thirty days HeyMachi isn’t earning its keep, walk away — we’ll hand you a clean export of every byte of your data on the way out.

HeyMachi is built in India for shops of every shape. POS, inventory, HRIS, payroll, loyalty, AI and a customer app — all from one login. Live today for restaurants, salons and pharmacies. The rest are shipping every couple of weeks.