Restaurant OS

Run the whole restaurant from one screen.

Restaurant OS is the complete restaurant system: counter POS, kitchen tickets and a full-screen Kitchen Display, tables and guest QR ordering, recipes and food cost, stock and purchasing, GST invoices with GSTR-1/3B filing, staff, payroll and owner reports. It runs on the shop's own computers and opens in any browser on the LAN or online — so billing never stops when the internet does.

Request a demo See pricing

Why Restaurant OS

Built for a full house, not a demo.

The counter screen is keyboard-first: type to search, one obvious primary action, exceptions surfaced instead of hidden. The busiest employee gets faster, not slower.

Fast when it matters

The counter screen is keyboard-first: type to search, one obvious primary action, exceptions surfaced instead of hidden. The busiest employee gets faster, not slower.

Keyboard-first Touch-friendly

The server is the boss

Prices, tax, station routing, numbering and permissions come from the server on every bill. Money is counted in integer paise — no rounding drift, ever.

Paise-exact Authoritative

Honest about connections

An integration that is not configured says exactly that and shows which field is missing. Nothing here pretends to be connected, and no paid feature fakes a result.

No fake sends Pending states

Everything in the box

The whole restaurant, module by module.

Billing & GST

Counter POS: order, bill and payment on one screen
Split payments — cash, UPI, card, khata — on one bill
Discounts with approval thresholds; refunds with proportional tax reversal and credit notes
Invoice numbering per outlet and financial year, race-safe
GSTR-1 (B2B, B2CL, B2CS, CDNR/CDNUR, HSN, DOCS) and GSTR-3B exports: section CSV and portal JSON
E-invoice fields (IRN) with status, when the scheme applies

POS GSTR-1 / 3B Credit notes

Kitchen — KOT & KDS

Tickets route themselves to the right station from the menu setup
Full-screen Kitchen Display with new → accepted → preparing → ready columns
Live ticket age from the server, so a wrong clock on a device changes nothing
Item-level progress for a table that eats in stages
Cancelling a fired item needs the permission and a reason
High-contrast KDS theme for a bright kitchen

Station routing Timers High contrast

Tables, floor & guest QR

Seven table states: free, seated, reserved, cleaning and more
Transfer and merge tables mid-meal; split a bill by items or amounts
Reservations with conflict-safe table assignment
QR menu at the table — guests order from their own phone, into the same bill
A sitting opens when the table is seated and closes when it is cleared, so a photographed sticker orders nothing at home

Floor plan QR ordering Reservations

Waitlist for walk-insNew

Queue in arrival order with a wait clock per party
Quote from your own sittings — median of similar parties, and it says how many it is based on
Call the guest on WhatsApp in one tap; with WhatsApp unconfigured the screen says so and nobody is marked "notified"
Seating from the queue takes the table and opens its sitting
Guests waiting past their quote raise one alert, not one per refresh

Queue WhatsApp call

Online orders & delivery

One inbox for website, QR and phone orders; accept or reject with a reason
Swiggy and Zomato channels are built with an honest pending state — they go live with your partner credentials
Rider dispatch with COD / prepaid, pickup and delivered trail
Ready-pickup tokens and a delivery run per day
Settlement reconciliation against what was actually billed

Aggregators Riders Settlements

Menu, variants & recipes

Categories, variants (half / full), modifier groups and combos
Availability toggles for the rush — 86 an item in one tap
Recipes with nested sub-recipes, portion costing and wastage %
Food-cost % per dish, updated as vendor prices move
Selling a dish deducts its ingredients from stock automatically

Food cost Modifiers Auto stock

Stock & purchasing

Ledger-based stock: every movement is signed and explainable
Wastage, damage and count corrections — each with a reason
Purchase orders → goods receipt → returns, with short and extra deliveries recorded, not rounded away
Vendor price-increase alerts, supplier ledger and payments
Inter-outlet transfers with variance handling
Reorder suggestions covering the supplier's lead time, turned into one draft PO per supplier for you to approve

Ledger GRN Reorder

Prep list & forecastingNew

How much of each dish a trading day needs, from your own same-weekday sales
Exploded through the recipes into raw materials, wastage included
Shortfall against stock on hand — what to buy, not just what to cook
Only days that actually traded feed the average; with no history it refuses to forecast instead of guessing
Dishes without a recipe are named on the list, never silently missing

Forecast Print for the kitchen

Customers, loyalty & khata

Guest profiles with birthday and anniversary for campaigns
Loyalty points with a full adjustment trail
Khata credit with balances, limits and settlement
Segments — new, returning, lapsed, high value, dues — ready for a message

Loyalty Khata Segments

Marketing & automationsNew

Coupons with limits and validity
WhatsApp campaigns to a segment, with sent and failed per recipient — real provider results
Birthday wishes and win-backs that run themselves, once per guest per window
Every send lands in the campaign list, with its own delivery status

Campaigns Automations

Reviews & the Google funnelNew

Guests rate the visit from the QR menu, the bill QR or the WhatsApp link — no login
Low scores open a private call-back trail, so a bad night is fixed, not published
Happy guests are offered your Google review link, and the click is counted before they land there
Trends and the dishes behind bad scores, plus NPS on the day-end report

Feedback Google link

Money, staff & payroll

Cash shifts with float, variance and closure; day-end Z-report
Expenses by category; tips captured at settlement and split by minutes or equally, to the last paisa
Attendance by PIN, manual entry with a reason, or fingerprint device
Leave, roster and payroll runs with payslips
Aggregator settlements reconciled against billed sales

Cash shift Tips Payroll

Reports, security & operations

Sales, GST, products, staff, inventory, customers, profit, variance and day-end — each with CSV
Nine roles and around seventy permissions, enforced on the server, with approval thresholds
Append-only audit trail: who changed what, with before and after
Backups with integrity verification; restore tested
Printers, routes and device health; Tally XML for the accountant's books
Multi-outlet, with per-outlet stock, numbering and isolation

RBAC Audit Backups Exports

Input-tax credit (ITC) registerNew

GST paid on purchases is recorded supplier-wise as goods are received — a partial GRN claims only the tax on what arrived
A purchase return writes its own reversal row; a correction is a new row with a reason, never an edit
CGST/SGST vs IGST split from the supplier's GSTIN; when it is missing the split is assumed and flagged for review
GSTR-3B table 4 and 6.1 are read straight from the register, head by head

Table 4 & 6.1 Reversals

Offline & sync

The till keeps billing with no internet; the queue replays when the line returns
Every replay is idempotent — a retried order never bills twice
Conflicts land in a queue a person resolves, instead of being silently overwritten
Sync health is visible on the Printers & Devices screen

Offline queue Idempotent

Hardware & printing

80mm thermal receipts and A4 tax invoices, with named print layouts
Station-wise ticket printing and a printer health view
Barcode scanner (keyboard-wedge) and a LAN weighing scale for weighed items
A second screen facing the guest at the counter
Role-based access with PIN approval at the till

80mm / A4 Routes Devices

Walkthrough

Twenty minutes with the real product.

This is the actual software running on a shop PC — install, first-run setup, then every screen: POS, KOT and Kitchen Display, tables and QR, orders, menu and recipes, stock, people, money, marketing, reviews, reports and backups. English captions are included; jump to any chapter below the player.

Installing

One file on the counter PC, then any browser.

One RestaurantOS-Setup.exe carries its own runtime and the whole application. No Node, no database server, no npm, no admin rights — and no internet needed to install.

Windows installer

One RestaurantOS-Setup.exe carries its own runtime and the whole application. No Node, no database server, no npm, no admin rights — and no internet needed to install.

One-click Offline install

Setup on the LAN

A setup script writes the configuration with fresh secrets and the till's own LAN address, opens the firewall for the till port and registers auto-start — so the counter is ready after a reboot without anyone signing in.

Auto-start LAN till Idempotent

Every screen on the network

The same system opens in a browser on the manager's office PC, a tablet on the floor or a phone — with role-based logins deciding what each person sees.

Any browser Roles Multi-outlet

Questions

Before you ask.

No. The counter PC runs everything locally and keeps billing when the line drops — the queue replays when it returns, and a retried order never bills twice. Internet is only needed for WhatsApp messages, online orders and remote access from outside the shop.

Restaurant OS questions

Answers before you buy.

The counter runs on a normal Windows PC: one installer, no admin rights, no database to maintain. Every other screen — manager's office, tablet, phone — is a browser on the same network, with role-based logins.

GSTR-1 and GSTR-3B come out as section CSVs and the portal JSON the GST offline utility accepts, plus an input-tax-credit register for tables 4 and 6.1. Everything ties out to the same invoices the reports read. Your accountant files it — we prepare it.

Yes. Each outlet has its own stock, numbering and settings, staff see only what their role allows, and stock can be transferred between outlets with the variance recorded.

80mm thermal printers for KOTs and receipts, A4 for tax invoices, with station-wise routing and a printer health view. A barcode scanner, a LAN weighing scale for weighed items and a guest-facing second screen are supported too. Printing hardware itself is bought separately.

The aggregator channels are built — inbox, accept/reject, dispatch and settlement reconciliation. They go live once your merchant credentials are issued by the partner; until then the screen says pending credentials instead of pretending to be connected.

Send an enquiry. We can set up a trial on your own menu, or start with the sample restaurant and walk your team through the screens — the same walkthrough you can watch above.

Next step

See it on your own menu

We can set up a demo restaurant with your actual dishes, taxes and stations, so you judge the software on your own rush rather than a sample menu.

Request a demo Talk to us