FluxDine runs the counter, the kitchen, the QR menu, the delivery board, the store room and the whole chain — from one login, on one database. It bills a legal GST invoice even with the internet down, then syncs itself when the line comes back.
Billing from one vendor, the kitchen screen from another, QR ordering from a third, delivery from a fourth. Raise a price and someone has to change it in four dashboards — and forgets one.
A cloud-only POS is only as good as your broadband. When the link goes, the queue at the counter does not — and neither does the law that says your GST invoice numbers must stay gapless.
Paneer walks out of the store room, voids pile up on one cashier's shift, an outlet runs out of gravy on a Saturday. You find out weeks later, in a spreadsheet, once the money is already gone.
FluxDine is not a POS with add-ons bolted on. Counter, kitchen, QR menu, delivery, store room and head office are screens of the same system, sharing one database and one price list.
Each branch runs its own node on your LAN. Orders, KOTs and GST invoices are numbered locally and keep flowing with zero internet, then replay to the cloud idempotently on reconnect.
GSTIN per branch, CGST/SGST intra-state or IGST inter-state, HSN/SAC on every line, configurable rate slabs, round-off — printed as a statutory PDF invoice and exportable as a GST CSV.
Dine-in, takeaway, delivery, kiosk and QR self-order are all first-class channels — and Zomato/Swiggy orders land as real orders too. One menu drives the counter, the QR and the menu board.
A node is Spring Boot + PostgreSQL + S3-compatible storage in Docker Compose. Run it in your own restaurant or let us host it — same build, full parity, no lock-in on your sales history.
From the first token at 7 a.m. to the drawer count at midnight — without reaching for paper or a second app
Server-authoritative pricing, split payments, UPI QR, and a statutory PDF GST invoice
Tickets stream to the KDS the instant they're fired, with real prep timers per station
Guests scan, browse and order from their own phone — no app, no login, straight to the KOT
Assign riders, track Picked-up to Delivered, and print a 58 mm packaging label
Stock depletes by recipe on every sale, with reorder thresholds and low-stock alerts
Suppliers, purchase orders, goods receipt and a wastage log with reasons
Item sales, tax summary, stock flow — plus a per-cashier void/comp/discount outlier scan
ESC/POS printing on 80 mm and 58 mm, station routing, reprints and a cash-drawer kick
Every module reads and writes the same tables — no exports, no nightly integration job, no vendor blaming another vendor
A till that a steward, a cashier or an owner can run
The kitchen sees the order the moment it is fired
Let the guest and the screens do some of the work
Know where the paneer went before month-end
Online orders stop being a second, parallel restaurant
From one kirana-scale counter to a chain, same software
The same three steps whether the order came from a steward's tablet, a table QR, a kiosk or Swiggy.
A steward, a guest's phone, a kiosk or an aggregator places the order. The server — never the till — computes every price, add-on, charge and GST component, so the bill can't be tampered with.
Each line routes to its kitchen station, appears on that station's display within the same second, and prints its KOT on the right thermal printer. Prep timers start from the real fire time.
Cash, card, UPI QR or a split of all three. The GST invoice takes the next gapless number, stock depletes by recipe, loyalty points post, and the sale lands in tonight's Z-report.
Any of these boxes can be ticked by buying another subscription. The question is what happens between them.
| What you actually care about | FluxDine | POS + KDS + QR + delivery, stitched |
|---|---|---|
| Change a dish price once, everywhere | One menu, all channels | Re-enter per dashboard |
| Kitchen sees the order instantly | Same system, live stream | Depends on the integration |
| Keep billing with the internet down | Edge node on your LAN | Each vendor's own answer |
| One GST invoice register across outlets | Single CSV export | Reconciled by hand |
| Stock depletes from online orders too | Same recipe engine | Usually not wired up |
| Run it on your own server, own the data | Docker, self-hosted | Rarely offered |
| Vendor contracts to manage | One | Four or five |
A FluxDine node is the whole application — reactive backend, PostgreSQL and object storage — and the same node runs at the edge in your restaurant or in the cloud. That single decision is what makes offline resilience real rather than a marketing line.
Prices below are indicative for launch in INR and exclude GST — final numbers are agreed with each early restaurant partner
One counter, one till
One restaurant, full floor
Up to 5 branches
Chains & central kitchens
The branch keeps trading with no internet at all. Orders, KOTs and gapless GST invoice numbers are generated locally, queued in a transactional outbox, and replayed to the cloud without duplicates when the line returns.
Counter, kitchen, QR menu, kiosk, menu board, delivery, store room and head office are one system on one database. There is no integration to fail at 9 p.m. on a Saturday, and no second vendor to call.
Built for India from the schema up: GSTIN per branch, CGST/SGST/IGST, HSN/SAC, UPI QR at the till, Zomato and Swiggy orders as first-class orders, and a Tally-ready GST export.
Yes. Each branch runs its own edge node on your local network, so the POS, kitchen display and thermal printers keep working with no internet at all. Invoice, token and KOT numbers are generated locally and stay gapless. Every order is written to a transactional outbox and replayed to the cloud idempotently when the connection returns, so nothing is lost and nothing is duplicated.
Yes. GSTIN and state code are held per branch, tax is split into CGST/SGST intra-state or IGST inter-state, HSN/SAC codes are snapshotted onto every line, rate slabs are configurable through tax groups, and the invoice total is rounded with a recorded round-off. Bills print as a statutory GST PDF invoice, and you can export an invoice-register CSV for Tally import or GSTR-1 prep.
No. POS, kitchen display, QR self-ordering, kiosks, customer-facing display, digital menu boards, delivery dispatch, inventory, purchasing, CRM and franchise are all screens of one system sharing one database. Change a price once and every channel — counter, QR, kiosk and menu board — shows it immediately.
Aggregator orders are first-class FluxDine orders, tagged with the platform and its external order id, and they fire a KOT to the kitchen display and flow into billing and reports like any other order. The ingest path is idempotent on that reference, so a retried webhook can never create a duplicate bill. Manual entry works today and a partner API integration plugs into the same path.
Yes. Print a table QR from the app, and the guest scans it to open the menu in their browser with no login and no app install. The order fires straight to the kitchen tagged as a self-order. The tenant and branch are validated server-side from the QR, so a guest can only ever order into that one outlet.
Yes. Each branch is tagged as an outlet, central kitchen or HQ. Outlets raise indents on the central kitchen and the Requested to Approved to Dispatched to Received lifecycle moves real stock between branches. HQ sees consolidated sales per outlet with a chain rollup, item velocity across branches, GST by rate, and royalty due per outlet.
Yes. A FluxDine node is a self-contained stack — Spring Boot, PostgreSQL and S3-compatible object storage — that ships with Docker Compose and runs on a machine in your own restaurant. You can also let us host it in the cloud. It is the same node either way, so your data stays yours and there is no lock-in.
Voids, comps and discounts are manager-gated, require a reason, and are recorded rather than deleted. Every order is stamped with who created it, so the anti-theft scan can rank each cashier's void rate, comp value and discount rate over a period and flag the outliers, alongside a full activity audit log.
Send us your menu and we'll set FluxDine up with it, then walk you through a full service — an order from the table QR, onto the kitchen display, out as a GST bill — in about thirty minutes.
Tell us how many outlets you run and what you use today. We'll set up a walkthrough on your own menu and show you exactly how a service runs on FluxDine — counter, kitchen and bill.