One Menu for Every Branch: Shared Dishes, Local Prices, Edit Rights
31 Oct 2026
A branch chain does not need a menu file on every manager phone. It needs one dish list, a price and an availability flag per branch, and a clear rule for who may add a dish and who may change a number. This guide orders those decisions, apart from simply publishing a menu for the guest.
A restaurant with several branches usually meets the menu problem on a busy night, not in a quiet meeting. A guest holds up a photo of a price from the mall branch. Another branch charges a different number for the same dish name. Each cashier is confident, because each one is reading a file that lives only on that branch. Unifying the menu means deciding which facts belong to the whole brand and which facts one branch may change without touching the rest.
The brief "one menu for the branches" is unfinished. It can be heard as one price for every room, or as freedom for every manager to rename the dish. Both readings break the chain. A single locked price is ignored in the first week a mall room and a street room need different numbers. Freedom to rename splits the list apart again within a month, because each room writes the description the way a new waiter explains the plate.
What is shared, and what stays with the branch?
Shared facts are what a guest recognizes as the brand: the dish name, the description, the photo, the sizes, and the extras. Local facts follow the room: the selling price, whether the dish is offered today, and sometimes an item one branch cooks because the oven or the space does not exist next door. A tool that freezes one price everywhere will be set aside. A tool that lets every supervisor rewrite the name becomes a stack of unrelated lists that share only a logo on the cover.
- Dish name, description, and photo are edited once on the brand list.
- The selling price is stored on the branch, not on the name alone.
- Hiding a sold-out dish in one branch does not delete it from the master list.
- An item cooked in one room only stays labeled with that branch.
- If service hours differ, they are stored with the branch, not with the dish.
Who is allowed to edit?
The permission table matters more than the page layout. Three roles cover most chains. The brand owner adds a dish, retires a dish, and edits the shared description and photo. The branch manager changes the price and the availability of that branch only, and cannot rename the dish or touch the next branch. The cashier sells what is on the screen and does not see an edit control. If one shared password can do all three jobs, there is no controlled menu. There is a file anyone on the shift can replace while rushing the next ticket.
Name the people, not only the job titles, when the chain is small. With two rooms the owner may be the only person who changes a price, and the manager only switches an item off when it runs out. That is simpler, as long as the screen does not show the price control to someone who should not have it. A rule explained in a chat and missing from the software returns to the phone at the first argument with a guest.
What the guest sees, and what the office sees
The guest sees one branch, not a blend of all of them. A code on the table opens the menu of that room. A delivery address selects the branch that will cook, or the guest picks the branch before any price appears. A comparison of branch prices is a screen for the owner, not a page a guest forwards to a friend and then pays against the wrong room. Changing a photo is a brand decision when the photo is shared. If plating differs in one room, the local photo is labeled so guests do not think the whole brand changed shape.
A sold-out hour is the real test. The manager switches the dish off for that branch. It disappears for guests in that room and remains next door. If the switch deletes the row from the master list, the next branch loses the item in the same minute, and staff go back to writing "available" on paper beside the till. That single behavior is enough to reject a design that does not separate hide from delete.
Where a ready product stops and a custom build starts
ENSMENU is a product ENS built and runs, and it is live at ensmenu.com. A guest opens a QR menu in Arabic or in English without installing an app. The restaurant can take a table order and a delivery order. AI extracts dishes from a photo or a PDF so the first list is not typed from an empty screen, and a person reviews the result before it is published. The dashboard is built for more than one branch, which is the part that matches this article. ENS also delivered a digital menu on ENSMENU for Afarem, for Nour Al Sham, and for Vida. Those three are menu deliveries. This article states no branch count and no sales result for any of them.
A custom build starts when the rules do not fit that shape. A franchise contract may freeze prices for some rooms and free them for others. A central kitchen may push a dish of the day to selected rooms only. A price at a branch may need an approval before guests see it. Write those rules in ordinary sentences before anyone estimates the work. A preview of a shared list plus a price per branch is a different project from a preview of one file on a manager phone.
What to send in the first message
- Branch names as you want guests to read them.
- One dish that shares a name and has two prices today.
- Who changes a price now, and who may add a new dish.
- Whether sold-out is a switch on the branch or a call to the manager.
- Whether delivery selects the branch or the guest selects it.
Questions that come up before a scope is agreed
Can two branches sell different dishes?
Yes. The master list holds what the brand can offer, and each branch marks what it actually sells. Deleting a dish from the master list because one room stopped cooking it removes it for every room. Hiding it in that room does not.
Should the guest see every branch price?
Usually no. Show the price of the branch that will serve the order. A comparison screen is an office tool. If you want a public transparency page, write that as its own decision, because it changes what must be correct before you publish.
When should you review the list after launch?
Review it on the first busy Friday. Check whether a sold-out item was hidden without vanishing next door, and whether the dish name stayed one name after more than one person touched the record. That observation is worth more than a slide about unification.
The product is ENSMENU. The Afarem, Nour Al Sham, and Vida menus are Afarem, Nour Al Sham, and Vida. Wider hospitality context is on restaurants and hospitality.
Send branch names and one dish with two prices through start your project. The WhatsApp button under this article opens a chat that keeps this topic with your note.
