POS counter
Billing built for a queue behind the customer — every action a single tap, every price in tabular monospace so nothing is misread, and the whole thing still works when the line drops.
Digital billing, inventory & ordering platform
One tenant-aware platform behind the counter, the kitchen, the waiter's phone, the delivery rider and the customer's own screen — POS, KDS, inventory, CRM and online ordering, built specifically for how Indian food businesses actually run a shift.
Table 12 · Order #4471
Table 12 · Order 4471
Your order has been placed
40+
capability modules across one platform
40+
capability modules across one platform
30
operational reports, exportable
5
notification channels from one engine
SMS, WhatsApp, email, push, in-app
8
outlet types the app reshapes around
7
working surfaces, each designed separately
One platform, seven real working conditions
Most restaurant software is designed on a laptop and forced onto a kitchen tablet afterwards. DesiMenus starts from the opposite direction — every screen is built for the light, noise, hands and pressure it will actually be used under.
Billing built for a queue behind the customer — every action a single tap, every price in tabular monospace so nothing is misread, and the whole thing still works when the line drops.
Table map, order taking, courses and bill requests designed to be read one-handed while carrying a plate.
Large tickets, per-station urgency rails, an allergen band and a running clock the whole line can read without walking up to the screen.
High-contrast, glove-friendly dispatch and proof-of-delivery that still reads clearly in harsh midday sun — and still records the drop when the signal doesn't.
The web console for menus, staff, stock, reports and settings across every outlet you run — plus a manager-on-the-go view for the days you are not at a desk.
The one screen allowed to be charming — larger radii, photography-led, dish-first ordering, and an install-free progressive web app that will not serve a stale bill.
The platform side: onboarding, plans, billing, dunning, support, health and the audit chain. You never see it, but it is why your invoices arrive and your outage has a status page.
One order, four screens
Scroll through this section — the dot below traces the same order as it moves from the counter to the kitchen, out for delivery, and back to a served table.
Everything the platform actually does, in one place
You don't need every module on day one. DesiMenus is built in four stages — Core, Growth, Pro and Platform — so you can start billing this week and grow into inventory, loyalty, delivery and multi-outlet control when you're ready.
Categories, item variants and modifier groups with min/max rules, tax rates, HSN codes, allergens and veg/non-veg flags — with per-outlet and per-dining-area price overrides resolved for you.
Menu
Live floor plans with table positions, merges, transfers and per-area pricing, built for a captain moving fast between sections.
Floor
Billing built for a queue behind the customer: held orders, a token pad, a customer-facing display, weighed items and a keyboard-first flow that works with no internet.
Ordering
One order becomes one ticket per kitchen — tandoor, Chinese, bar — plus a separate "to serve, no cooking" slip at the counter for water and cold drinks. Routed by category, overridable per item.
Kitchen
Split bills, coupons, discount policies, and invoices carrying your GSTIN, FSSAI number, HSN summary and a per-invoice CGST/SGST/IGST split frozen at the moment you issue it.
Billing
Cash, card, UPI, wallet and online tenders on the same bill, with change, part payments and a refund and void console that makes you write down why.
Billing
Guests scan the table sticker and read the menu on their own phone — no app, no install, and it works before anyone has typed a phone number.
Guest
Opening float by denomination, counted cash at close, a variance the server computes rather than trusts, and a reason plus an approver when it doesn't match.
Billing
Four-digit PINs with lockout, single-use manager override tokens for the things a cashier shouldn't do alone, and a device approval queue so an unknown tablet can't just start billing.
Security
Recipe-linked deduction on every sale, adjustments, wastage with review thresholds, low-stock alerts and unit conversion — with an offline write-off recorded first and flagged after, never silently dropped.
Inventory
Bills of material per dish, live ingredient costing and a margin report that tells you which of your best sellers is the one losing money.
Inventory
A ticket queue built for two-metre legibility: per-station prep targets driving the urgency colour, an allergen band pinned to the ticket, an all-day view, arrival chime, and no auto-scroll under a chef's hand.
Kitchen
Visit history, spend and preferences shared across your outlets, plus a counter desk for looking someone up, topping up their wallet and selling a membership while they wait.
CRM
Points earned and redeemed at the till, membership plans with automatic expiry, and manual adjustments behind their own permission.
CRM
Guests top up and spend across your outlets. Deposit and bonus are tracked apart — bonus expires on dated tranches, deposit stays refundable — and redemption is a tender, not a discount, so GST is never under-reported.
CRM
A booking calendar with clash detection, automatic reminders, a week grid for the host, and one action that seats a booking and opens its order in a single step.
Floor
SMS, WhatsApp, email, mobile push and a real in-app inbox — from one engine, with quiet hours, consent gating, per-channel entitlements and delivery receipts written back onto the attempt.
Communications
A prepaid message wallet with GST-invoiced recharges, negotiated per-restaurant rates, immutable rate history and low-balance warnings that still go out when the balance is zero.
Communications
A token pad and display for walk-ins, so a busy counter has a number to call instead of a crowd to shout into.
Ordering
A diner scans, verifies a phone number by OTP and orders from their seat into your kitchen queue — behind a staff-opened table window, so a sticker photographed last week orders nothing.
Guest
The table asks for the bill, pays by UPI intent, wallet or points on their own phone, and your counter confirms it through the same code path a cashier uses.
Guest
A short rating prompt after the bill, tied to what was actually eaten, rolled up per dish so the feedback points at a recipe rather than at a mood.
Guest
Dispatch board, live status, proof-of-delivery photos that queue offline, a masked customer number with an audited reveal, and rider cash-in-hand reconciled at handover.
Delivery
Zomato and Swiggy orders land in the same kitchen queue as your counter and dine-in orders, badged at the POS and KDS, with a reconciliation report at the end of the month.
Delivery
Route through your own merchant account or the platform's, order by order, with signature-verified webhooks settling the payment rather than a human refreshing a screen.
Billing
Table-side ordering built for one hand, a dim room and a plate in the other — with courses, fire control, and a sent/unsent axis so the second round actually reaches the kitchen.
Ordering
Inter-branch transfer requests with manager approval, in-transit tracking and receipt confirmation, so stock leaving one kitchen is stock arriving at another rather than stock vanishing.
Inventory
Vendor master, purchase and spend reporting, and production batches for a central kitchen turning ingredients into things other outlets sell.
Inventory
Thirty operational reports — sales, items, staff, wastage, valuation, margins, loyalty, delivery, aggregator reconciliation — exported to CSV, XLSX, JSON or ZIP through a queue, with PDF rendered on the spot.
Reporting
A GST return built from the frozen per-invoice split rather than recomputed months later, GSTR-1 JSON for filing, and threshold-gated e-invoicing with IRN and signed QR when you cross the limit.
Compliance
One console across several tenants or franchise outlets, with per-user outlet access, an outlet switcher on every screen, tenant health monitoring and view-as assist sessions that are individually audited.
Platform
Counter and kitchen devices keep working with no internet — an encrypted local cache, an outbox that survives a restart, per-entity sync cursors, and a hard rule that money is never discarded on the device.
Platform
Plans, per-plan limits and feature entitlements with grace windows and grandfathered baselines, proration on mid-cycle upgrades, auto-debit mandates, and a read-only mode that lets a lapsed account still read and export.
Platform
Reminder, warning and final notice over the real notification channel, delivery outcome stamped on each attempt, retry with backoff, and suspension that a human confirms unless you have said otherwise.
Platform
Per-tenant usage and health monitoring, monthly SLA computation, incident records, restore-verification drills and a public status page your customers can read during an outage.
Platform
An append-only audit log sealed into a verifiable chain with periodic checkpoints, cross-tenant search for support, and export — with encrypted columns redacted rather than reproduced.
Compliance
DPDP-shaped retention policies, consent records, data-subject requests, and a tenant exit that goes read-only, exports, holds, then purges — leaving a certificate and an audit trail rather than a gap.
Compliance
Roles and permissions scoped to the client app they are used from, so a kitchen tablet and the web console can hold the same role and still not offer the same buttons. Cloned from platform templates, edited per tenant.
Security
Visible focus, keyboard reachability, touch targets read from density tokens, screen-reader labels on every icon-only control, reduced-motion support, and a palette checked against three colour-vision simulations in a conformance test. The guest menu ships in English and Hindi.
Quality
Same platform, tuned per outlet
Menu structure, order flow and floor logic change completely between a bakery counter and a bar. DesiMenus configures around your outlet type instead of forcing one workflow on everyone.
Flexible menu, quick invoices and a counter flow built for fast repeat orders.
How the platform is built
Each stage is sequenced by real technical dependency — you can't split a bill before you can build a menu — so what you see below is the actual order the platform comes together in.
Foundation Shipped
Multi-outlet tenancy, sign-in with refresh-token rotation and two-factor, and role-based permissions scoped per client app so every screen shows only what that staff member may touch.
Core Shipped
Menu management, table orders, multi-kitchen KOT routing, GST-ready invoicing, shift cash-up and the QR guest menu.
Growth Shipped
Recipe-linked stock deduction, customer profiles, memberships, the prepaid wallet, reservations, the kitchen display system and a five-channel communications engine.
Pro Shipped
Rider management, Zomato and Swiggy order sync, own-or-platform gateway routing, multi-outlet stock transfers, and thirty operational reports with queued exports.
Platform Shipped
A central console for operators running several tenants, subscription billing with entitlements and dunning, tenant health and SLA, the tamper-evident audit chain and DPDP retention.
Offline & insight Shipped
Counter, captain and kitchen devices keep working with no internet — encrypted local cache, a durable outbox, per-entity cursors and reconciliation when the connection returns.
In flight In progress
Tickets already route to the right kitchen screen; sending them to that kitchen's own printer, and opening the signup flow the API already supports to a public page, are next.
Planned Planned
Ingredient batches with expiry and FIFO valuation, purchase orders as a first-class document, and pushing your menu out to aggregator catalogues rather than only receiving their orders.
Pricing
Every plan runs on the same platform — you're never migrated to a different product as you grow. Tell us your outlet type and outlet count and we'll put together a quote.
Core
Talk to us
Menu, POS billing, kitchen tickets, GST invoicing and the QR guest menu.
Most outlets choose this
Growth
Talk to us
Everything in Core, plus inventory, recipe costing, CRM, loyalty, the wallet, reservations and the kitchen display.
Pro
Talk to us
Everything in Growth, plus delivery, aggregators, gateway routing and the full reporting suite.
Platform
Talk to us
For operators running several brands or franchisees: a central multi-tenant console on top of everything in Pro.
Questions
Yes. The counter, captain and kitchen apps are offline-first — orders and bills are written to an encrypted local cache and a durable outbox, and sync automatically the moment connectivity returns. Money is never discarded on the device: a payment recorded offline is retried, or surfaced for a human, but never quietly dropped.
Yes — that is exactly how the platform is staged. Most outlets start on Core (menu, POS, kitchen tickets, GST billing, QR guest menu) and add inventory, CRM, delivery or aggregator sync when they are ready, without switching products or re-entering their menu.
Bills carry your GSTIN and FSSAI number, an HSN summary, and a CGST/SGST/IGST split frozen onto the invoice at the moment you issue it rather than recomputed later. GST return and GSTR-1 JSON export are built in, and e-invoicing with IRN and signed QR is available once you cross the threshold.
Yes. Aggregator orders land in the same kitchen queue as your dine-in and counter orders, badged so the line knows where they came from, with a reconciliation report at month end. Menu push in the other direction — your catalogue into theirs — is on the roadmap rather than shipped.
The counter app runs on ordinary Windows PCs and Android tablets; the kitchen display runs on an Android tablet or a desktop screen. Thermal printers and cash drawers connect the usual way. We will confirm exact specs for your outlet during the demo rather than guess here.
Yes. One account spans every outlet you run, with per-user outlet access and an outlet switcher on every screen. If you are operating several brands or franchisees, the Platform tier adds a central multi-tenant console on top.
No. The guest menu is a web page behind the QR sticker on the table. Reading the menu needs nothing at all; placing an order needs a one-time phone verification and a table your staff have opened, which is what stops a sticker photographed last week from ordering anything.
You export it, and then it goes. Offboarding runs a defined sequence — read-only, export, a hold period, then purge — and produces a certificate at the end. The audit trail of what was done survives; the personal data in it does not.
The staff apps and console are in English. The guest QR menu ships in English and Hindi, with the language chosen from the URL, a cookie, or the phone's own preference. More languages are added by translation rather than by code.
Get started
Tell us about your outlet and we'll walk you through the modules that matter for it — no generic sales deck.