Multi-Branch Restaurant Management Software: What Changes at Branch 2

This guide is for restaurant owners in Gujarat and across India who run one successful outlet and are opening a second, or who already run three or four branches on separate systems and want one view. By the end you will know what must be separate at each branch, what should be central, which tax question to take to your accountant, and how to add a branch without disturbing the ones already running.

What changes when a restaurant opens a second branch

With one outlet, the owner is the control system. You are at the counter most evenings, you know the prices by heart and you see the cash. The second branch ends that. You cannot be in Rajkot and Jamnagar on the same Saturday night, so the software has to carry what your presence used to carry. Four things change at once.

Separate menus and prices

Branches diverge within weeks of opening. Rent differs, so prices differ: a dosa at ₹120 on a city ring road may be ₹140 at a highway branch. The kitchen differs, so the range differs: a small branch may skip the Chinese section. Availability differs every day, since one branch runs out of an item while the other has plenty.

So each branch needs its own menu and its own prices, with an easy way to start from a copy. An import from an Excel or CSV file works well: export the first branch's menu, edit prices and remove items, and load it into the new branch.

Separate printers and kitchen counters

Kitchen layout is never the same twice. One branch has a dosa counter, a main kitchen and a beverage counter, each with a printer. The next has a single kitchen with one printer. Item-to-printer mapping therefore belongs to the branch. So do the printers' network addresses, the bill printer at the counter and the ticket number sequences. The guide to KOT printing and kitchen order ticket setup covers the mapping.

Separate invoice series

Each branch issues its own tax invoices from its own counter, so each needs its own consecutive series for the financial year. Where branches share a GSTIN, the series must also be distinguishable from each other, usually with a short branch code. Agree the format with your accountant. The details are in the post on restaurant bill format and invoice numbering.

One GSTIN or several

GST registration is taken state by state. As a general rule, branches in the same state can operate under one GSTIN, with each outlet added to the registration as an additional place of business. A branch in another state needs a registration in that state.

This is your accountant's decision, and it should be made before the software is set up, because it decides which GSTIN prints on each branch's bill and how the returns are compiled. The food licence is a separate matter: an FSSAI licence or registration is normally tied to the premises, so each branch prints its own number. Check the current rules on the official portals.

What is central and what is per branch in a restaurant chain

A simple test sorts most items. If it describes the business, it is central. If it describes a building, a kitchen or the people in it, it belongs to the branch.

The table is lopsided on purpose: a restaurant branch is a physical operation and most of its settings are local. When you compare restaurant POS software for more than one outlet, ask the vendor to walk through this table line by line.

Central reports and who can change what

Central reports

The owner of a chain needs two views from one login: the business as a whole, and each branch on its own. The useful comparisons are simple ones.

• Sales and bills by branch, day by day, so a weak day at one outlet is visible the next morning.
• Average bill value by branch. If the same menu produces ₹310 at one branch and ₹260 at another, look at what the captains are offering.
• Discount as a percentage of sales by branch. One branch at 1% and another at 4% is a control question.
• Cancelled and void entries by branch, with user and reason.

The post on restaurant sales reports owners should check explains each report.

Who can change what

Distance turns permissions from a formality into the main control. A workable split for a restaurant chain looks like this.

• Owner or admin: everything, in every branch, including prices, tax settings, users and reports.
• Branch manager: day-to-day running of one branch: item availability, approvals for discounts above the cashier's limit, cancellations, closing.
• Cashier: billing and settlement at one branch, discounts up to a set limit with a reason.
• Captain: taking orders, sometimes limited to certain floors. No billing changes.

Every sensitive action should also leave a record: who gave the discount, who voided the item, who changed the price or the setting, and when.

How a branch keeps working offline and syncs to the cloud

A chain has to get this design decision right, because the two obvious designs both fail.

A purely cloud system gives live central reports, but every tap at a branch depends on its internet line. When the line drops at 8:30 PM on a Sunday, orders stop reaching the kitchen. A purely local system keeps each branch billing, but the owner has to telephone each outlet to learn the day's sale.

The design that works is local first with cloud sync. Each branch has a local server, which can be the counter PC or a small dedicated PC. The captain phones, the billing counter and the printers talk to it over the restaurant's own Wi-Fi. Orders, kitchen tickets and bills never leave the building while they are being processed, so service continues with no internet at all. In the background the server sends completed data to the cloud, and when the connection has been down it catches up after it returns.

The central reports are current when the branch is online and behind when it is not, and one branch's outage has no effect on any other branch. More detail is in the post on offline restaurant billing when the internet is down.

Rollout plan for adding a restaurant branch

Two weeks is a comfortable schedule if the premises and the wiring are ready. The steps are in the order that avoids rework.

1. Settle the tax and licence details (day 1 to 2). Confirm with your accountant which GSTIN the branch bills under, the invoice number format and the food licence number for the premises.
2. Prepare the menu file (day 2 to 4). Start from the existing branch's menu. Set this branch's prices, remove items it will not serve, and check the GST rate and the inclusive or exclusive setting on each item.
3. Install the network and hardware (day 4 to 6). Counter PC or mini PC as the local server, a dedicated Wi-Fi router for billing, thermal printers at each kitchen counter and at the billing counter. Give every printer a fixed IP address.
4. Create the branch in the software (day 6 to 7). Tables and floors, printer mapping for each item, bill header, invoice series and service charge setting.
5. Create users (day 7). One login per person, with a role. No shared logins.
6. Train the staff (day 8 to 10). Captains on taking and changing orders, cashiers on billing, discounts and settlement, the manager on approvals and closing.
7. Run a trial service (day 11 to 12). Staff meals or invited guests, with real orders through every printer. Unplug the internet for 20 minutes during the trial and confirm that nothing stops.
8. Go live and watch the first week (day 13 onward). Read the day end report and the cancelled and void report from the new branch every morning for the first seven days.

The trial in step 7 is the one most often skipped. A wrongly mapped item, such as coffee printing at the dosa counter, is a two-minute fix on Wednesday afternoon and a queue of angry tickets on Saturday night.

How Dhandhaan handles this

Dhandhaan is the restaurant POS and billing software built by JK Tech Hub in Rajkot. It holds several branches under one account. Each branch has its own menu, tables, printers, users and invoice series, and the owner sees combined and branch-wise reports from the cloud panel, which works in a phone browser.

Each branch runs on a local server, the counter PC or a mini PC. The Windows counter billing app, the Android captain app and the ESC/POS thermal printers talk over the restaurant's own Wi-Fi or LAN, so ordering, kitchen tickets and billing continue when the internet is down, and data syncs to the cloud when the connection returns. Menus can be imported from Excel or CSV, which shortens step 2 of the rollout.

Roles are owner or admin, manager, cashier and captain, and captains can be limited to certain floors. Discounts have a per-role permission and a maximum limit, with a manager PIN above it. Every discount, void, price change and settings change is written to an audit log. Invoice numbers are sequential per branch, restart each financial year and have a starting number setting for a branch that joins mid-year.

The multi-branch plan is ₹23,999 a year, against ₹12,999 a year for a single branch, with no charge per bill and no commission on sales. Hardware is bought separately. To be plain about scope: Dhandhaan does not include inventory, stock transfer or purchase management at present, so central purchasing and a central kitchen need their own process, and it has no live integration with food delivery apps yet.

What we learned building for a multi-branch restaurant in Gujarat

We built Dhandhaan for a multi-branch South Indian and fast food restaurant business in Gujarat that was moving off a hosted POS. Their main complaint was outages at peak hours, and with several outlets an outage was no longer one bad evening. It was a regular event somewhere in the business.

That shaped the first decision: a local server at every branch. The second lesson was about printers. The kitchens have separate counters with their own printers, and a printer that picks up a new address from the router after a power cut simply stops receiving tickets. Fixed IP addresses for every printer became a rule of installation, and they are the first thing we check on a support call.

The third lesson was about people. Staff wanted screens that felt familiar from the system they knew. Keeping the billing flow the same at every branch, while the menu and the printers differ, means a cashier who covers a shift at another outlet does not need retraining. The fourth was the mid-year start: the move could not wait for April, so each branch has to be able to continue its invoice numbers from where the old system stopped.

How to decide

If you are opening branch two, choose the system for branch five. Check five things before you sign: each branch has its own menu, printers and invoice series; each branch bills without internet; one login shows every branch; permissions and an audit log exist; and the price does not grow with every bill you print.

If you already run branches on separate systems, move one branch first, run it for two weeks, and then move the rest. The post on switching restaurant billing software without downtime sets out that sequence.

Related reading and next step

• Offline restaurant billing when the internet is down
• KOT printing and kitchen order ticket setup
• Restaurant POS hardware setup and cost in India
• Restaurant sales reports owners should check
• Restaurant POS software in Ahmedabad

To see two branches under one login with separate menus and reports, book a demo or ask for a quote through the contact page or on WhatsApp at +91 7265004040.