Many groups reach this point as they add branches, when each outlet has drifted into its own item names, recipes and spreadsheets, and head office can no longer tell which branch is actually profitable. This guide covers the menu, local pricing with a worked example, central kitchen transfers, the reports to compare, and the tax set-up in the UAE and Saudi Arabia.
How do you keep one menu across several branches?
Build the menu once, at head office, and let branches choose from it rather than edit it. Every item has one code, one name in English and Arabic, and one recipe, whichever branch sells it. That single rule is what makes branch reports comparable later.
| Set centrally by head office | Set by each branch |
|---|---|
| Item codes and names | Which items are available today |
| Recipes, portion sizes and yields | Staff rota and shift times |
| Modifiers and combos | Kitchen printer and screen routing |
| Menu categories and photos | Opening hours and service periods |
| Calories and allergens | Table layout |
| Tax codes, price lists and which list each branch uses | Local stock levels and par levels |
A branch that needs a local item, such as a breakfast menu only one location serves, asks head office to add it to the master menu and switch it on for that branch only. It still gets a proper code and recipe, so it shows up in group reports.
The same applies to delivery apps. The items on talabat, Deliveroo, HungerStation or Jahez should be the master menu items, mapped to each app, so an app order lands in the POS as the same item a dine-in guest would order.
How should you set local prices for each branch?
Use a small number of price lists, grouped by location type and channel, rather than a separate price for every branch. Three or four tiers cover most groups: standard street branches, malls, airports or hotels, and delivery apps. A price change is then made once per tier, not once per branch.
Here is one dish, a chicken shawarma plate with a recipe cost of AED 9.00, across four price lists. Prices include 5% VAT, so the food cost percentage is worked out on the price before VAT.
| Price list | Menu price incl. VAT (AED) | Price before VAT (AED) | Food cost % |
|---|---|---|---|
| Street branches | 32 | 30.48 | 29.5% |
| Malls | 36 | 34.29 | 26.2% |
| Airport | 42 | 40.00 | 22.5% |
| Delivery apps | 38 | 36.19 | 24.9% |
The mall and airport prices are higher because rent, service hours and staffing cost more there, not because the dish costs more to make. The delivery price looks generous at 24.9%, but after a 25% commission on the pre-VAT price the restaurant keeps AED 27.14, and food cost on what it actually receives rises to 33.2%. Our guide to delivery app commissions works through the full calculation.
Two rules keep tiered pricing manageable. Prices change only at head office, on a set date, for a whole tier. And every price list uses the same item codes, so a report can compare the same dish across branches without anyone matching names by hand.
The prices and commission here are illustrative; use your own recipe costs and contract terms.
How should a central kitchen supply the branches?
Treat every delivery from the central kitchen as a stock transfer, at standard cost, that the branch confirms on receipt. The central kitchen's stock goes down, the branch's goes up, and the branch's food cost includes what it received at the same cost every other branch pays.
| Step | Who | Record |
|---|---|---|
| 1. Branch orders | Branch manager | Transfer request, based on par levels |
| 2. Kitchen prepares and dispatches | Central kitchen | Transfer note with items, quantities and batch dates |
| 3. Branch receives | Branch staff | Confirms quantities; records any shortage or damage |
| 4. Difference resolved | Central kitchen and branch | Shortage written off or re-sent, with a reason |
Use a standard cost for each prepared item, such as a kilo of marinated chicken or a litre of sauce, updated monthly from the central kitchen's actual production costs. Branches then compete on how well they run, not on whose transfers were priced higher that week.
If the central kitchen belongs to a different company in your group, transfers between the companies are sales, with invoices and VAT, unless the companies are in the same VAT group. Check the set-up with your tax adviser before the first transfer.
Which reports should you compare across branches?
Compare ratios, not totals. A mall branch will always sell more than a quiet street branch, so the useful questions are how much of each dirham goes on food and labour, and how far each branch is from what its recipes say it should spend.
| Measure | What it tells you | How often |
|---|---|---|
| Sales, covers and average bill | Demand and upselling | Daily |
| Theoretical food cost % | What food should cost, given what was sold | Weekly |
| Actual food cost % | What food did cost, from stock counts | Weekly or monthly |
| Gap between the two | Waste, over-portioning, theft, unrecorded staff meals | Weekly or monthly |
| Labour cost % | Rota against sales | Weekly |
| Voids, comps and discounts as % of sales | Control at the till | Weekly |
| Delivery share of sales | Channel mix and commission exposure | Monthly |
Here is a month for three Dubai branches of the same group:
| Branch | Sales (AED) | Theoretical food cost | Actual food cost | Gap | Labour cost |
|---|---|---|---|---|---|
| Jumeirah | 310,000 | 29.5% | 31.0% | 1.5 points | 24.0% |
| Mall | 420,000 | 29.8% | 30.6% | 0.8 points | 22.5% |
| Business Bay | 265,000 | 29.2% | 34.1% | 4.9 points | 27.0% |
The theoretical food cost is almost identical across the three, because they share one menu and one set of recipes. Business Bay's actual cost is not. A 4.9-point gap on AED 265,000 of sales is about AED 13,000 a month that went somewhere other than the guests' plates. The waste log, the void report and the receiving records are where to look first.
This comparison only works because every branch uses the same item codes and recipes. Without them, the theoretical column can't be calculated, and you are left comparing totals.
How do tax and licensing work across several branches?
In both countries, tax registration belongs to the company, not the branch: one VAT number covers every outlet. Licences are the opposite, because they are tied to premises. Each outlet needs its own municipal approval.
| Topic | UAE | Saudi Arabia |
|---|---|---|
| VAT registration | One TRN for the company, covering all branches, with one VAT return | One VAT number for the company, whatever the number of branches |
| What the return needs from each branch | Standard-rated sales in Box 1 are split by emirate, using the branch the sale belongs to | One return for all branches |
| Commercial registration | A branch licence in each emirate where you open; check with the licensing authority whether each outlet in the same emirate needs its own | Since 3 April 2025, one commercial register covers the whole Kingdom; old branch registers are being phased out |
| Outlet licence | Food establishment approval from the municipality for each outlet | Municipal (Balady) licence for each outlet |
| E-invoicing | Sales to consumers are outside the system for now; invoices to businesses, such as corporate catering, go through your service provider from 1 July 2027 for most SMEs | Each POS device that signs invoices needs its own ZATCA cryptographic identifier, and invoices show the branch address |
| Menu prices | Must be displayed including VAT | Must include VAT and match the final invoice |
Two of these shape how you set up the POS. In the UAE, every sale needs to carry its branch, so the VAT return can be split by emirate without a spreadsheet. In Saudi Arabia, a new branch's tills must be onboarded with ZATCA before the first sale, so build that into the opening plan.
These are the general rules. Confirm your own set-up with your tax adviser and licensing authority.
What goes wrong when restaurant groups grow?
In the multi-branch groups HYP works with, the problems rarely start in the kitchen. They start in the master data, when each new branch is set up by copying the last one and then changed locally.
| What we see | What it causes | The fix |
|---|---|---|
| The same dish under three names and codes | Group reports can't add it up | One master menu; branches can't create items |
| Prices edited at the branch till | Different prices for the same tier; guest complaints | Price changes only at head office, by tier |
| Recipes updated in one branch only | Theoretical food cost wrong elsewhere | Recipes owned centrally, with a change date |
| Central kitchen deliveries with no transfer note | Branch food cost too low, central kitchen too high | Transfer, receive and confirm in the system |
| Each branch closing its books differently | Head office waits weeks for comparable numbers | One chart of accounts and one month-end routine |
The common thread is that every branch can be set up quickly, but drifts unless head office owns the shared data. Once the menu, recipes and price lists are central, adding a new branch means choosing its price list and switching on its items.
HYP runs the master menu, branch price lists, central kitchen transfers and group reporting in one system, with HYP's POS at each branch. See how on our Restaurants & Cafés and F&B Cloud ERP pages.
Sources
- FTA: VAT registration (one TRN for all branches)
- FTA: VAT Returns User Guide (Box 1 by emirate)
- FTA: tax group registration
- Dubai Municipality: food establishment licensing information
- SAMA Rulebook: circular on the new Commercial Register Law
- Balady: issuing a commercial (municipal) licence
- ZATCA: E-Invoicing Detailed Technical Guideline (CSID per device)
- ZATCA: Guideline for Tax Invoicing and Records, May 2026
- Saudi Ministry of Commerce: shelf prices must include VAT
- KPMG: UAE e-invoicing framework and scope