Multi-Branch Controls
This is the add-on that lets one organisation hold more than one branch: every branch you create is checked against the ceiling before it is written. Each branch then carries its own menu availability — a dish switched off at one location keeps selling at the others, and an order for it there is refused at the counter. Routines go the other way: write the checklist once, preview per branch what publishing would do, publish to the ones you tick, and read back which version each branch is running.
- Settings · Add-on
What it does.
- More than one branch under one organisation, checked as each is added
- A dish switched off at one branch while the others keep selling it
- A routine written once and published to the branches you tick
- A publish preview that names what each branch gets, and writes nothing
- A branch that edited its own copy skipped rather than overwritten
- An adoption list naming the version each branch is running
It does not work alone.
These sit on the same order record, so what one of them writes the next one can already read.
Book a RestoMama demo
Tell us about your restaurant and the workflows you want to launch first.
- One replyA person from the team, not an autoresponder sequence.
- One serviceWe walk your own dinner rush end to end — bill, KOT, payment, dispatch, day close.
- No hardwareIt runs in the browser on the machines and printers you already have.
See a real service, end to end.
We will take one dinner rush the whole way — ring a bill, print the KOT, call the token, mark the payment, dispatch the order, pay the agent and read the day close. On your menu, with your zones, in about thirty minutes.
- Billing and the counterOrder, modifiers, receipt, token
- The kitchen screenKOT routing, stations, prep state
- Payments and closingUPI, card, cash, wallet, day-end
- Dispatch and payoutsZones, assignment, tracking, settlement