Power your restaurant with AI.
Zero leaks. Zero blind spots. Superfast on the floor.
Billing, kitchen, cash, menu, staff and guests on one system — with an intelligence layer that watches every void, comp, discount and drawer open and tells you the moment money starts walking out. It keeps working when the internet doesn't, and nothing on it can be quietly deleted.
₹6,240
The offline model
Most systems overwrite.
This one keeps a ledger.
Ordinary POS software saves the current state of a bill. When two devices touch the same table offline, the last one to reach the server wins and the other's items disappear. RestroSync never saves state — it appends what happened and computes the bill from that.
Friday night, Wi-Fi drops at 8:00 PM
Captain A · queued offlineQueued
Captain B · other tablet, also offlineQueued
Folded by client time — neither overwritesApplied
Nothing lost₹300
What staff actually see
Honest about what offline cannot do
- Billing needs no server
Totals, tax and charges compute on the device from the published tax profile. No round trip in front of a guest. - Cash settles offline
At the till the receipt prints over USB and the drawer opens. The payment reaches the ledger when the line is back. - A refresh doesn't lose the queue
Operations waiting to sync are stored on the device, and the terminal stays paired to its outlet.
One app, every role
The PIN decides
what the screen becomes.
Not six apps to install and update. One build; the terminal is paired to an outlet once, and each PIN opens the screen that person needs — with the actions they aren't allowed to take simply absent, not greyed out.
- Search that matches how staff think
Item name, category chip, or the short code called across the pass — type 214, get Butter Chicken. - Fire once, the kitchen splits it
One tap; each line routes to grill, bar or pantry from the published routing rules. - The menu changes itself at 11:30
Day-part windows ship inside the menu snapshot, so the pad switches on the device clock — no network needed. - Prices freeze when the item is added
A price published mid-meal never rewrites a seated table's bill. - 86'd items are blocked at the pad
Marked unavailable in the kitchen, badged and unaddable for every captain.
- Discount ceilings are set centrally
A cashier's limit comes from the published role config. Above it, a manager approves on the same screen with a reason — both signatures land on the event. - Voids after firing leave a trail
The line is never deleted. It stays in the ledger with who, when, why and who approved. - Split, merge, reprint
By item or by cover; a reprint counts as a copy rather than quietly replacing the first bill. - Cash in and out, reason-coded
Float top-ups and payouts recorded against the shift and shown on the X report.
- 2 × Butter Chicken
- 1 × Dal Makhani
- 1 × Mutton Biryani
- 3 × Paneer Tikka
- Bar never sees grill traffic
Each screen subscribes to its own station, assigned on the device itself. - Bump one ticket, not the whole order
Drinks go out while the steak cooks — the runner sees "1 of 2 tickets ready". - 86 from the kitchen, instantly
Every pad greys the item out. Manual 86s clear at the start of the next business day. - Late tickets are labelled late
A ticket fired while offline arrives flagged with the time it was actually rung in.
- A queue built from bumps, not guesses
Food appears the moment the kitchen bumps it, with the table it belongs to. - Partial orders are visible as partial
"1 of 2 tickets ready", so nobody carries out half a table thinking it's complete. - An expo hold lane for plating
Bumped but not yet carried out sits in its own lane, so the pass and the floor agree. - Host seats, then hands off
Covers and table go on the order, the captain picks it up. Waitlist with a quoted time for the door. - Transfers keep the same order
Move T04 to T12 or merge two tables; fired tickets follow. A printed bill needs approval to reopen.
- One board for the room
Open tables, ticket age, covers, 86 count, printer trouble and the shift's sales so far. - Approvals happen where the problem is
The same approval box everywhere: manager PIN, reason, both names on the event. - Day close that refuses to lie
The day cannot close while a terminal is still holding unsent operations.
Floor & service
From the door to the table
to the bill.
The host seats a party, the captain picks it up, tables move when the room changes — and every step stays on the same order, so nothing is retyped and nothing is lost in the hand-off.
The door
Seat party · T07
The room
- Transfers keep the order intact
Move a table or merge two; fired tickets follow and only the label changes. - Dine-in, takeaway and delivery on one pad
One queue, one running total, one day-end. - Captains see their own work first
Filter to mine or the whole room; draft, fired and printed kept separate.
Kitchen & pass
The kitchen gets tickets,
not arguments.
One fire splits into station tickets by rules head office set. Each screen shows only its own station, bumps its own tickets, and reports its own times.
- Live menu, as the terminal sees it
Read-only browse of exactly what's sellable right now, with the day-part and version stamped on it. - 86 board
Toggle an item unavailable; it disappears from every pad and reappears at the next business day. - This screen = this station
Assign the TV to grill, bar or expo on the device — not in a menu publish. - Ticket queue by age
A list view with age bands for the chef running the pass, separate from the bump wall. - Expo hold
Bumped but not carried out, in its own lane.
Cash control & day close
The day can't close
on a guess.
Two controls do most of the work. The cashier counts the drawer without being shown what the system expects. And the business day refuses to close while any terminal still holds operations it hasn't sent.
Blind count
Sync barrier before Z
- Nothing is deleted, ever
Voids, comps, discounts, reprints, drawer opens and transfers append with an actor. There is no button that removes the trace. - Two payments on one table both survive
If a table gets settled twice offline, neither payment is dropped — the bill is flagged overpaid for a manager to refund. - Z resets the room, not just the report
Closing the day locks the numbers, snapshots them for reprinting years later, resets ticket numbers and rolls the business date on every terminal.
Leakage & staff risk
From "something feels off"
to proof, in five taps.
Because nothing on the till can be deleted, the awkward questions become answerable. Start at the brand, end at a single void with a timestamp, an actor and an approver.
- L0 Which outlet is red this week?Brand pulse across every outlet Analyse
- L1 How bad is this outlet right now?Risk score · exposure ₹ · open incidents Elevated
- L2 Who is the pattern?Staff matrix — sales against risk 3 flagged
- L3 What is this person's story this period?Dossier — KPIs, trend, linked incidents Rahul
- L4 Which incidents are still open?Queue, filtered to that person or outlet 7 open
- L5 Can I prove this one to HR?Evidence locker — event timeline, resolve, export Evidence
Staff matrix — sales against risk
Evidence locker — one incident
Table 12 · ₹4,180 · copy 1 · Anil
No settlement recorded within 4 minutes
2 × Mutton Biryani · ₹1,240 · actor Rahul · approved Anil · reason "guest left"
- Owner-facing, never on the till
Staff cannot see their own risk view, and the terminal never hosts it. It lives in the manager console. - Patterns, not accusations
Void rates, drawer opens without a sale, comps after printing, cash variance — ranked, with the exposure in rupees. - A breadcrumb back out
Every deep page shows the path it came from, so a conversation can move from the incident back to the pattern.
The manager console
The till is a till.
Setup happens somewhere else.
Menus, day-parts, kitchen stations, routing, staff, PINs, terminals, tax and the floor plan are authored on a desktop by whoever is allowed to — then published to the terminals as a version.
Changes in this version
- Day-parts with a timeline
Lunch and dinner windows drawn against the outlet's timezone, with overlaps refused at entry. - Items with the detail you actually keep
Price, day-parts, short code, station override, variants, channel prices, diet and allergen tags — with drag ordering for the pad. - Modifiers and combos
Required or optional, min and max choices, and combo pricing distributed across the children. - Stations and routing rules
Item override, then category rule, then the bar split, then a default — one order of precedence, applied identically in the preview and on the terminal. - People, roles and PINs
Roster, a role and permission matrix, PIN set and reset, published to the terminals as a version. - Terminals
Approve a pairing code, name the device, revoke a lost one from the console. - Tax, charges and the floor
Tax profiles, service and packaging charges, discount ceilings, reason codes, and the table layout the floor plan draws from. - Version history you can point at
Every publish kept: version, time, author, what changed.
Customers & growth
The bill is the start
of the relationship.
Every settled bill builds a guest record. From there: who's lapsing, which campaign brought them back, and what it earned — measured against bills at the counter, not opens and clicks.
- Guest profiles that build themselves
Phone, visits, spend, favourites and channel mix attach at the counter — no data entry. - Loyalty and memberships
Points and tiers off the same record; redemption matched to a bill at the POS.
- Campaigns with guardrails
Segment, channel, offer, and a rule that skips anyone messaged in the last fortnight. - Results in footfall
Every send ties back to visits and net revenue, so ROI is a number rather than a feeling.
- Feedback and referrals
Catch a bad night before it becomes a review; let regulars bring the next table. - Smart insights
Needs attention or going well, each one linking to the screen that acts on it.
Hardware & setup
Browser-based, but it drives
real hardware.
A web app can't reach a printer on your network by itself. So there are three paths, chosen per surface rather than pretending one covers everything.
- Receipt printer & cash drawer
Connected by USB to the billing terminal and driven straight from the browser. This is the path that keeps printing with the internet down.
- Kitchen ticket printers
Cloud-capable printers fetch their own jobs, so there's nothing to install in the kitchen.
- Older network printers
A small on-site bridge handles legacy LAN printers and instant printing.
A7X-92M
Setting up a tablet takes a code, not a technician
Open the outlet's URL, add it to the home screen, read out the six-character code. A manager approves it and names the terminal. No API keys typed on the floor and no device-management software.
The device is identified separately from the person. Signing out or rebooting doesn't unpair it — and if a tablet leaves the building, revoking it wipes the cached menu, the queued operations and the token, leaving a blank browser. Whoever has it still needs a staff PIN.
Switching a terminal to another outlet means re-pairing. A daily PIN can never move it — that's the most common source of misposted sales.
Reports & exceptions
What sold, and what
came off the bill.
Two reports do the daily work: what actually sold this shift, and every discount, comp, void and refund with the name of whoever did it and whoever approved it.
Item sales · this shift
Exceptions · this shift
Logged
- Printers you can test from the floor
Map bill, ticket and label printers per terminal, switch one off when it jams, fire a test print before service. - Drawer and scanner checks
Pulse the drawer and test the scanner from settings, so problems surface at 11 am rather than 9 pm. - X and Z reports
A non-destructive mid-shift tally, and a day close that locks and snapshots the numbers.
India first
Built for how the counter
actually works here.
Patchy connectivity is a design assumption, not an edge case. So are UPI, GST, a kitchen that runs on tickets, and a group running six outlets off one console.
- Cash, UPI and card in one count
Tender recorded per bill and reconciled per shift, with variance computed from the ledger. - GST computed on the device
Rates and charges configured per outlet and published to the terminals, so a bill totals identically offline and online — to the paisa. - Service charge is a setting
On, off, or removable on the bill. Your policy, not our default.
- Dine-in, takeaway and delivery together
One order book and one day-end across channels. - Weekend volume and the kitchen
Tickets routed per station by rules you set, with an expo lane for the pass. - Offline billing as standard
Not an add-on module. It's how the till is built.
- Groups, not just outlets
Menus, stations, staff and routing authored per outlet from one console. - Your business day, not midnight
The day closes when your kitchen closes; ticket numbers reset and the date rolls on every terminal at once. - Roles that match a real floor
Captain, runner, bill desk, kitchen, host, floor manager — each with its own screen and its own limits.
Why this one
The differences that show up
on a bad night.
| Installed legacy POS | Cloud POS with an offline mode | RestroSync | |
|---|---|---|---|
| Two devices, one table, no internet | Local server decides | Last to sync wins — items vanish | Both sets survive; nothing overwritten |
| Getting a new tablet running | Technician visit | App store install and login | Open a URL, read out a six-character code |
| Updates | Scheduled downtime | Per-device app updates | Refresh — every terminal is on the current build |
| Price change mid-service | Risky; usually after close | Can rewrite open bills | Versioned publish; open bills keep quoted prices |
| Who can change a price | Anyone with the manager key | Anyone logged into the till | Nobody on the till — authoring is in the console |
| Which station a dish prints to | Trial and error in service | Buried in item settings | Previewed per item before you publish |
| Day close with a terminal offline | Manual tally | Closes anyway, numbers drift | Blocked until it syncs, or a recorded force close |
| Voids and comps | Editable rows | Soft-deleted | Appended with actor, reason and approver |
| Suspecting a staff pattern | Gut feel | Export and squint at a spreadsheet | Risk matrix → dossier → evidence pack |
| Stolen tablet | Physical risk | Remote wipe if MDM exists | Revoke; the device wipes itself to a blank browser |
The whole system
Every screen
the business needs.
Grouped the way the software is. On the terminal, each PIN sees only the groups its role can open.
Orders
- Order pad with code search
- Open orders
- New order · dine-in, takeaway, delivery
- Fire with per-station tickets
Billing
- Open bills
- Bill preview
- Settle
- Discounts & no-charge
- Void & refund
- Split & merge
- Print & reprint
- Till open / blind close
Floor
- Floor plan
- Seat party
- Waitlist
- Transfer & merge tables
Kitchen & runner
- Station display with bump
- Ticket queue by age
- Ready-to-run queue
- Expo hold
- Live menu · 86 board
Shift, cash & reports
- Shift open with float
- Cash in / out with reasons
- X report · Z report with sync barrier
- Item sales
- Voids, comps & discounts
Terminal settings
- Device pairing & re-pair
- Printers with test print
- Drawer & scanner tests
- Kitchen screen assignment
- Sync diagnostics
Console · menu & kitchen
- Day-parts
- Categories & items
- Modifiers & combos
- Stations & routing rules
- Publish with routing preview
- Version history
Console · people & setup
- Staff roster
- Roles & permissions
- PIN set / reset
- Terminals approve / revoke
- Tax, charges & ceilings
- Floor plan editor
Grow & insight
- Dashboard
- Smart insights
- Customers & profiles
- Loyalty & memberships
- Campaigns & results
- Feedback · referrals · QR
- Leakage & staff risk
- Analyse & attribution
Questions operators ask
Before you change
your till.
What exactly still works with the internet down?
If it's a website, what happens when the tab closes?
Can a cashier give an unauthorised discount?
Will staff know they're being monitored?
Do you support my printers?
How do GST and service charge get calculated?
Can I move off my current POS without losing history?
What happens on the first Saturday?
See it fail gracefully.
Ask us to pull the internet during the demo. That's the part worth watching, and the part most POS demos avoid.
- 30 minutes, on your menu and your tax setup
- We'll price the hardware you actually need
- Migration from your current POS, handled by us
- Onboarding per outlet, in the language your floor works in
Prefer to talk? +91 00000 00000