Features
Built around a real service, not a feature list
Every part of Diner exists because a restaurant floor needed it. Here is the whole of it.
Counter billing
A till screen built for the lunch rush — large tap targets, keyboard-first search, and no page it takes two hands to reach.
- Dine-in, takeaway and delivery on one screen
- Split, merge and transfer tables mid-service
- Item modifiers and variants without leaving the order
- Discounts capped by role, with over-cap approval
Kitchen orders (KOT)
Orders reach the kitchen the moment they are fired, on a display built to be read from across a hot line.
- Live KDS screens with oversized, glanceable cards
- Per-station routing so the grill only sees the grill
- Status flows back to the floor in real time
- Network printers supported alongside screens
GST that survives an audit
Tax is computed once, at settle time, and written onto the bill — an old invoice never changes because today's prices did.
- CGST/SGST and IGST resolved per bill
- Invoice numbers sequential and gapless, per GSTIN
- Configurable slabs per item tax group
- A branch cannot bill without its GSTIN mapped
Every branch, one menu
Branches share a single catalogue and staff directory, so a price change is one edit and reporting is already consolidated.
- Central menu with per-branch availability
- Consolidated reporting across locations
- Staff who work in more than one branch
- Branding cascades branch → restaurant → org
Roles that match the floor
Owner, manager, cashier, waiter, kitchen and finance — each sees what the job needs and nothing it does not.
- Permissions scoped to the whole org or one branch
- One person can hold several roles at once
- Roles resolved per request, so revocation is instant
- Voids, discounts and day-end close are all gated
Menu and modifiers
Categories, subcategories, variants and add-ons — priced and taxed properly, not bolted on as free text.
- Categories and subcategories for long menus
- Required and optional modifier groups
- Per-item tax group and HSN
- A QR menu diners can read on their own phone
The practical bits
The questions that decide it
The things that matter at 8pm on a Saturday, which rarely make it onto a feature grid.
A wobbly connection does not stop service
The order you are building is held locally and queued, so a few seconds of bad wifi costs you nothing. Settling needs the server on purpose — that is what keeps invoice numbers gapless.
Screens or paper, your call
Kitchen displays need nothing but a browser on a cheap monitor. If your line prefers paper, network thermal printers work alongside them.
Runs on what you have
A laptop, an Android tablet, an old iPad. There is no proprietary terminal to buy and nothing to install — it is a web app.
Day-end that actually closes
Cash counted against expected, voids and discounts listed with who authorised them, and a close that locks the day.
See it on your own menu
Send us your menu and we will load it in, then walk you through a full service — order, fire, settle, close — on a call. Takes about twenty minutes.