POS for restaurants in India
Last reviewed 2026-05-27 · by the RetailPOS team
India's independent restaurant sector is roughly 5 million establishments across QSRs (quick-service restaurants), casual dining, cloud kitchens, dhabas (highway food stops), tiffin services, sweet shops, and the broader food-service economy. The pace of change over the past 5 years has been dramatic — UPI now carries 85% of digital food orders; Zomato + Swiggy combined handle roughly 60% of the online-food-delivery market; cloud kitchens (no dine-in, delivery-only) have scaled from niche to mainstream.
The POS systems serving this market are a mix: Petpooja (the dominant Indian restaurant POS), Posist, Restaurant 365, RistaApps. International systems (Square, Toast) have limited India presence. The buying decision is shaped by GST compliance complexity, the aggregator integration story, UPI as primary tender, and the cloud-kitchen workflow that doesn't exist in adjacent markets. This guide is for owner-operators of independent Indian restaurants navigating all four.
GST tiers + the AC vs non-AC distinction
India's GST on restaurant services has multiple tiers based on the establishment type:
5% GST — non-AC restaurants without alcohol licence; food service inside trains/aircraft/movie-theatre premises.
5% GST without ITC — most restaurants (including AC); composition scheme applies if turnover below INR 1.5 crore.
18% GST — restaurants in 5-star hotels (where room tariff is INR 7,500+); outside catering; food court within hotel.
0% GST — non-branded prepared food for sale by govt-recognised relief organisations.
The POS needs to apply the right rate based on the establishment type + (occasionally) the channel (dine-in vs takeaway might rate differently in some edge cases). For most independent restaurants, the standard 5% applies; the edge cases matter for boutique hotels + multi-format operators.
E-invoicing above INR 5 crore turnover
Businesses with annual turnover above INR 5 crore (relaxed to INR 10 crore in some recent updates; verify current threshold at GST portal) must generate e-invoices via the IRP (Invoice Registration Portal). Each B2B invoice (and now some B2C above thresholds) gets a unique IRN (Invoice Reference Number) + QR code; data submits to GSTN in near-real-time.
For restaurant operators above the threshold, the POS must integrate with the IRP — typically via a GSP (GST Suvidha Provider) like ClearTax, Avalara, or Masters India. RetailPOS' integration ships via our connector layer. Below-threshold restaurants don't need e-invoicing; standard GST receipts suffice.
UPI as primary tender + the QR-on-table flow
Indian restaurants increasingly use a static UPI QR code on each table for customer-initiated payment (vs the cashier-side UPI tender). Customer scans the table's QR; opens their UPI app; types the amount; confirms; the payment lands in the restaurant's merchant account.
The challenge: tying the customer's self-initiated UPI payment to the specific ticket. Most independents do this by including the table number in the UPI VPA (e.g., merchantname-table5@upi); the POS reconciles via the merchant statement T+1. For better accuracy, the POS can show a unique-per- ticket QR (with the ticket ID encoded) — customer scans, the payment auto- settles against the ticket.
RetailPOS supports both patterns: per-table static QR + per-ticket dynamic QR. Most operators pick per-table for QSR + dhabas, per-ticket for dine-in casual.
Zomato + Swiggy + Dunzo aggregator integration
Zomato and Swiggy combined handle the majority of India's online food orders. Dunzo (Bangalore-strong), EatSure, ONDC-network options are emerging alternatives. Each aggregator has a commission (20-30% typically) + an ordering API; orders should flow directly into the kitchen-ticket queue.
Without integration, the workflow is: aggregator rider arrives, hands the order printout to cashier, cashier re-types into POS, kitchen receives the re-typed order. Double-entry, error-prone, slow. With integration: aggregator order lands directly in the POS kitchen queue, marked with the aggregator channel; cashier doesn't re-type; kitchen prepares; rider picks up.
RetailPOS integrates with Zomato + Swiggy through our connector layer. Per- channel revenue + commission reporting separates the aggregator margin from dine-in.
Cloud kitchens — the multi-brand operator
India has a thriving cloud-kitchen sector — operators running 4-10 brands out of one shared kitchen, delivery-only via aggregators. Same kitchen produces biryani under brand A, pizza under brand B, dessert under brand C. The POS treats each brand as a separate sub-tenant under one parent group; one kitchen, multiple brand menus + reports.
Each brand has its own Zomato + Swiggy listings + commission rate + performance metrics. The POS' per-brand revenue + ingredient depletion (one biryani consumes the same rice + chicken across all brands that share the recipe) gives the cloud-kitchen operator visibility into which brand actually makes money.
Regional cuisine + the catalogue structure
India's restaurant catalogue is genuinely diverse. The POS' category + modifier structure should accommodate:
Veg vs non-veg flag on every item — table stakes; the customer expectation is unambiguous flagging. Some POS systems handle this as a tag; some as a category. Either works; the cashier UI surfaces clearly.
Spice level modifier— “less spicy / medium / spicy / extra spicy” — common across most Indian cuisine.
Regional menu sections— North Indian / South Indian / Chinese- Indian / Continental / Mughlai / Chettinad. Multi-cuisine restaurants need category-level organisation that doesn't collapse to a flat list.
Jain / Sattvic preparation — for some customer segments, preparation without onion/garlic/root vegetables is a binary requirement. Modifier or per-item flag.
Currency + the INR inflation reality
INR has been more stable than PKR but inflation matters for restaurant cost- management. Ingredient costs (especially LPG for kitchens, edible oil, dairy) move 8-15% annually. The POS' recipe-driven food-cost % dashboard becomes more valuable in this context — you see margin movement within days, not at year-end.
For QSR + cloud-kitchen operators, menu price adjustments happen 2-3 times per year; the POS' price-history tracking ensures past sales reflect the then-current price for refund + audit purposes.
Indian POS hardware landscape
iPads + tills: Apple authorised resellers (Imagine Stores, Reliance Digital, Croma) for new; Cashify + Quikr for refurbished. iPad 9-10 refurbished around INR 18,000-32,000 — most independents use refurbished given the price-sensitivity.
Receipt printers: Star + Epson via Indian POS suppliers (Cashbook, Velocity POS, Posist Hardware); Bixolon increasingly common. Star TSP143IIIBI around INR 12,000-18,000.
Barcode scanners: Honeywell + Zebra via local distributors; Symbol-rebrand cheaper options widely available. INR 3,000-9,000 range.
Card terminals: Pine Labs (dominant in India for POS card terminals); Mswipe; Innoviti; Razorpay POS. RetailPOS integrates with the major processor terminals via the alternative-tender pattern; UPI is typically the primary channel anyway.
Kitchen display systems: Standard tablets (Android or iPad) wall-mounted on the line; some operators use thermal printers for the kitchen- ticket print + a separate display for the bump status.
Frequently asked
- Does the POS handle the multi-tier GST structure?
- Yes — per-item tax classes mapped to GST tiers (5%, 5% without ITC, 18%, 0%). Configured at signup based on your restaurant type + AC/non-AC + alcohol licence. Receipt itemises tax-class-wise GST breakdown per Indian invoice requirements.
- E-invoicing via IRP — at what turnover?
- Current threshold is INR 5-10 crore depending on category + recent updates (check GST portal for current). Below threshold: standard GST receipts. Above: e-invoicing integration via GSP partner (ClearTax, Avalara, Masters India). RetailPOS connects via our integration layer.
- Zomato + Swiggy integration?
- Yes — orders flow directly into the kitchen-ticket queue; no manual re-typing. Per-aggregator commission + revenue reporting separates the channels. Configure at sign-up with your Zomato + Swiggy merchant credentials.
- UPI QR per-table vs per-ticket?
- Both supported. Per-table static QR (cheaper to deploy, easier for QSR/dhaba) with T+1 reconciliation via merchant statement; per-ticket dynamic QR (more accurate, better for dine-in casual) with real-time ticket reconciliation. Configurable per shop.
- Cloud-kitchen multi-brand support?
- Multi-brand sub-tenants under one parent group. One kitchen, multiple brand menus + reports + aggregator listings. Per-brand revenue + ingredient depletion reporting.
- Receipt language?
- Bilingual (English + Hindi or regional). Tamil, Telugu, Kannada, Malayalam, Marathi, Bengali, Gujarati, Punjabi character sets supported on Star + Epson printers. Item names typically in English for accuracy; payment-method + total + GST headers in regional language.
Open your shop in 30 seconds.
No card. Free until your first 100 sales. Bring your own Stripe; keep your hardware.