Restaurant billing software in Dehradun
Yes — LekhaPro runs a Dehradun restaurant's billing: table and KOT workflows, menu variants and modifiers, takeaway and delivery modes, 80mm thermal receipts, and a day-end that ties cash, UPI and aggregator settlements into real books — fully offline on the Desktop edition. Professional tax in Uttarakhand is not levied — worth knowing in a staff-heavy trade, though LekhaPro itself has no payroll module and does not compute it.
What Uttarakhand sets for a Dehradun restaurant
| Item | Uttarakhand | Source |
|---|---|---|
| GST state code | 05 — first two digits of every GSTIN here | Statutory |
| Professional tax | Not levied | CAG PA on 74th CAA, Uttarakhand (Rep. 2 of 2022) · cag.gov.in · checked 2026-08-05 |
| Intra-state e-way bill | ₹50,000 | Rule 138(1), CGST/SGST Rules · cbic-gst.gov.in · checked 2026-08-05 |
The full Uttarakhand compliance table — every state-level fact we track, with sources — is on the Uttarakhand state page.
The Dehradun trade, honestly
Dehradun eats like the student and gateway town it is. Rajpur Road has grown into the café-and-restaurant artery, Paltan Bazaar keeps the old bakery and chaat trade, and momos are practically civic food. Weekend traffic to Mussoorie brings transit diners who eat quickly and move on, while schools, academies and offices sustain steady weekday lunches. Summers swell with hill-bound tourists; winters quieten. Café tables hold students long on small bills, so covers matter as much as turns. Billing needs quick tourist checkouts beside unhurried tabs, and day-ends splitting cash, UPI and delivery-app volume.
What a Dehradun restaurant gets
- Table / KOT billing
- Menu with modifiers
- Takeaway & delivery
- 80mm thermal receipts
- Day-end & GST summary
- Real ledger
- Offline-first
Plans are ₹249, ₹449 and ₹2,499 a month — GST-inclusive totals on pricing. New to the terms? Place of supply decides the tax head on every invoice, and goods movements may need an e-way bill.
What it does not do — in Dehradun or anywhere
- · No aggregator API integration — delivery-platform orders are entered as delivery-mode bills and reconciled at day-end, not pulled automatically from the platforms.
- · No ingredient-level recipe costing — menu items bill as items; food-cost engineering stays in your kitchen workings.
- · No table-reservation or waitlist system — the product starts when the order does.
- · It does not file GST returns for you — bills post to the books; submission stays with you or your CA.
- · No office in Dehradun — sales and support are online (email and WhatsApp) from an India-based team, with no local branch, reseller or on-site visit.
- · No payroll, attendance or HR module — staff salaries and professional tax stay with your CA, in Uttarakhand as everywhere.
Questions Dehradun restaurateurs ask
Does it work for a Dehradun restaurant or café?
Yes — orders by table, KOTs fired to the kitchen, menu items with variants and add-ons, takeaway and delivery modes, and a GST bill settled fast at the end. It runs fully offline on the Desktop edition, so a dinner rush never depends on the connection.
How does the KOT flow work in a rush?
Take the order against the table, fire the KOT, keep adding rounds as the table orders more, and settle one bill at the end — with the 80mm ticket and receipt printing silently. During a Dehradun weekend rush, the point is that the queue of KOTs moves at kitchen speed, not software speed.
Can the menu handle variants and modifiers?
Yes — an item carries its variants (half/full, portion sizes) and add-ons (extra cheese, spice level), so the order the kitchen sees is the order the customer gave. Menu changes are yours to make seasonally without re-building the billing.
How do delivery-platform orders fit in?
Honestly: they are entered as delivery-mode bills — there is no automatic API pull from the aggregators — and the day-end then shows the cash, UPI and aggregator split so the platform settlement can be reconciled against your own numbers. The gap between platform reports and your books is where money quietly leaks; the day-end is the check.
Does professional tax apply to a Dehradun restaurant's staff?
Not levied — per CAG PA on 74th CAA, Uttarakhand (Rep. 2 of 2022) · cag.gov.in, checked 2026-08-05. In a staff-heavy trade that line matters, but the honest limit stands: LekhaPro has no payroll module and does not compute or file it; the levy stays with you or your CA.
How does GST work on restaurant bills?
The restaurant rate scheme and the composition option are national and set by notification, so we do not print figures here that move — your CA settles which regime you bill under, and LekhaPro raises compliant bills and posts them to real books either way. The GST summary at day-end comes from those postings, not a separate export.
What does day-end actually show?
The day's bills by mode — dine-in, takeaway, delivery — the tender split across cash, UPI and aggregator settlements, and the GST summary, all from the same posted ledger. Closing the till stops being arithmetic on chit paper.
Does it print kitchen tickets and receipts on thermal printers?
Yes — 80mm thermal printing, silent, for both the KOT and the customer receipt; A4 is there for the formal bill a corporate guest asks for. One printer choice, made once.
What happens when the internet drops mid-service?
Nothing — the Desktop edition runs the whole floor offline: orders, KOTs, bills, day-end. In Dehradun as anywhere, the connection failing at nine on a Saturday is precisely when billing must not.
How do we try it in our Dehradun kitchen?
14 days free, no card. Run one real service — tables, a takeaway, a delivery order — and read the day-end against your current closing sheet; restaurant software proves itself between the first KOT and the last settlement. We sell and support online only, with no Dehradun branch. Local context: Dehradun eats like the student and gateway town it is.