On this page
- Why do menus drift across branches?
- What is a central catalog and how does it work?
- How do you handle genuine local pricing differences?
- What happens when an item is not available at a specific branch?
- How do you manage menu updates across branches?
- How should you think about modifiers and variants in a multi-branch context?
- In the product
- Frequently asked questions
Quick answer: Standardizing menus and pricing across locations keeps the brand consistent, while allowing controlled local exceptions where a branch faces different costs or customer expectations.
The mechanism is a central catalog that every branch reads from, with a limited set of branch-level overrides - such as local surcharges or availability toggles - that do not change the group's base pricing structure.
The moment a customer visits two branches of the same restaurant and finds different prices for the same item, the brand loses credibility. It might be a AED 2 difference on a main course, but the customer's instinct is to feel they were overcharged somewhere. Menu and pricing standardization is not about rigidity - it is about protecting the consistent experience that makes a group worth more than the sum of its outlets.
Why do menus drift across branches?
Menu drift happens for predictable reasons:
- A branch manager adds a local special and it never gets removed
- A cashier manually changes an item price to match "what the customer remembers"
- A new seasonal item launches at one branch and never gets added to others
- A supplier price increase leads one branch to quietly increase a price without group approval
None of these are dramatic decisions, but their cumulative effect is a group where each branch has developed its own version of the menu. Reporting becomes unreliable because the same item name means different things at different branches.
What is a central catalog and how does it work?
A central catalog is a single definition of every menu item - name, description, price, variants, modifiers, tax profile, and images - that all branches read from. When the group owner updates an item in the central catalog, that change propagates to every branch POS immediately, without any branch needing to do anything.
The central catalog works in three layers:
| Layer | Who manages it | What it contains |
|---|---|---|
| Group catalog | Owner or HQ Admin | All items, base prices, variants, modifiers, tax profiles |
| Branch availability | Branch manager | Which items are available at this branch (toggle, not edit) |
| Local override (permitted) | Branch manager | Specific local surcharges where the group has granted permission |
The key control is the distinction between toggling availability and editing prices. A branch manager can mark an item unavailable (it ran out, it is seasonal, it is not relevant to this branch's customer mix) but cannot change the base price. Price changes go through the central catalog and apply everywhere.
How do you handle genuine local pricing differences?
Some branches do face legitimately different cost structures. A mall branch pays higher rent and may need to apply a service charge. A branch in a tourist area may face different supplier pricing. Two mechanisms handle this without breaking central pricing integrity:
Service charges. A branch-level service charge is a transparent addition to the bill, not a change to item pricing. The customer sees "Service charge: AED X" as a separate line. The base item price remains consistent across branches.
Permitted local surcharges. Where the group decides that a specific branch genuinely needs different pricing for documented reasons - say, a premium location with higher operating costs - that override is set at the group level, documented, and applied to the branch configuration. It is not a branch manager deciding unilaterally.
In both cases, the override is visible in the Admin portal and tracked in audit logs. Nothing changes invisibly.
What happens when an item is not available at a specific branch?
The right approach is to mark the item unavailable at that branch, not to delete it from the catalog. Deletion causes problems when the item returns, when you want to compare across branches, or when a report references historical sales of that item. An availability toggle keeps the item in the catalog for reporting and analytics while hiding it from that branch's POS selling screen.
How do you manage menu updates across branches?
Without a central catalog, a menu update means contacting every branch, confirming the change was made, and hoping it was entered correctly. With a central catalog, the group owner or Admin makes one change and every branch is updated the moment they save.
The sequence for a menu update:
- Update the item in the central catalog (new price, new description, new image, new variant)
- The change propagates immediately to all branches
- Branch managers are notified (via the in-app Action Required widget or the morning briefing) if the update affects their branch operationally
- Any branch that has a local override related to the changed item is flagged for review
For a new item launch across all branches simultaneously, the item is created in the central catalog, marked available at all branches from a specific date and time, and any promotional configuration is applied in the Promotions module. Every till in the group goes live with the new item at the same moment.
How should you think about modifiers and variants in a multi-branch context?
Modifiers (add-ons, customizations) and variants (sizes, formats) are defined at the item level in the central catalog and apply consistently across branches. If a branch wants to offer an additional modifier that other branches do not carry - say, a local garnish option - that needs to be added to the catalog as a modifier with availability restricted to that branch, rather than configured locally outside the catalog.
This keeps the catalog as the single source of truth for what can be sold and how it is priced, even when branches have some local variation in what they offer.
Read next: How to manage a multi-branch restaurant in the UAE (pillar) · Centralized control vs branch-level flexibility · Rolling out a new branch: an operations checklist
Frequently asked questions
How do I make sure all branches are selling from the same menu?
Use a central catalog that all branches read from. Any item added or changed in the central catalog propagates to every branch POS immediately. Branches can toggle item availability but cannot create items or change prices outside the central catalog.
Can one branch charge more than another for the same item?
Only through a transparent mechanism: a branch-level service charge (visible as a separate line on the bill) or a permitted local surcharge approved and set at the group level. Branch managers should not be able to change item base prices independently.
How do I launch a new item at all branches at the same time?
Create the item in the central catalog, set it as available at all branches, and specify the launch date and time if using a scheduled promotion. Every POS in the group goes live with the new item at the same moment.
What should I do if an item is not available at one branch?
Mark it unavailable at that branch using the availability toggle, rather than deleting it from the catalog. This keeps the item in historical reporting and makes it easy to reactivate when it returns.
About this guide. Maintained by the TajerGo Editorial Team. Last updated 22 Aug 2026. Worked examples use illustrative numbers, not customer results.