How to manage menu prices across multiple restaurant locations

Most diner owners don’t decide to have different prices at different locations. It happens. The second diner opens with the first diner’s menu, someone tweaks a price on the new tablet, the old printed menu stays up, and a year later nobody is sure what a short stack costs where.

This guide is for owners and operations managers running two to fifteen locations who want menu prices to be a decision again, not an accident.

What does “one master menu” mean?

One master menu means every dish, side and drink exists exactly once in your system, with one name, one category, one recipe and one default price. Locations don’t get their own copies of the menu; they get permission to sell items from it, and optionally their own prices.

That sounds like a technicality. It isn’t. When each location has its own copy of the menu:

• names drift (“3 Stack”, “Short Stack”, “Pancakes x3”), so group sales reports count one dish as three;
• a new dish has to be typed into every location, so it launches on different days;
• food cost can’t be compared, because the “same” dish has different recipes in each copy.

When there is one master menu, the only things that should change per location are:

1. Price — through a price list for that location.
2. Availability — whether the location sells the item at all.
3. Tax — because tax rates differ by city, county or emirate.

Everything else — the name, the photo, the modifiers, the recipe — stays shared.

When should locations charge different prices?

Charge differently where your costs differ, not because a manager prefers it. The usual reasons are:

Reason	Typical example	Usual approach
Rent	Airport, mall or downtown location	A price list for that location, 8–20% higher on most items
Wages	A location in a higher-minimum-wage city	Higher prices on labour-heavy dishes
Local tax	City or county restaurant taxes (US)	Same menu price, different tax group — or adjust price if you show tax-inclusive
Competition	A location next to a cheaper competitor	Hold prices on a few traffic-driving items
Menu fit	A drive-in branch with no flat-top	Turn items off rather than re-price them

In the UAE, a mall branch commonly charges more than a street branch for the same plate, and prices are shown VAT-inclusive. In Pakistan, mall and DHA branches often price above food-street branches. The logic is the same everywhere: price lists follow costs.

How do price lists work in practice?

A price list (in GetDinerPOS, a selling price group) is a named list of prices that overrides the master price for the items you fill in. You only enter the prices that differ:

1. Create the list — “Airport”.
2. Enter airport prices for the items that should cost more. Leave the rest blank.
3. Assign the list to the airport location.

At the airport till, an item with an airport price rings that price; every other item rings the master price. When you raise the master price of coffee next month, every location without its own coffee price follows automatically.

The same mechanism works for customer groups: a staff price list or a VIP discount, applied at any location.

How should a chain change prices safely?

Change prices on a fixed day, from one screen, and check one register per location afterwards. A simple routine:

1. Monday morning, before the rush, pull food cost per plate for your top 30 dishes (see our guide to recipe costing).
2. Decide per location: which dishes need a change, and at which locations.
3. Edit once — the master price for group-wide changes, the price list for location-specific ones.
4. Check one register per location by ringing (and voiding) one changed item.
5. Update printed menus and menu boards the same day. The online store updates itself if it reads your POS catalogue.

Because each sale stores the price it was rung at, reports for last month don’t change.

Who should be allowed to change prices?

Fewer people than you think. In most chains:

• The owner and one operations manager can change master prices and price lists.
• Branch managers can 86 items (mark them unavailable) at their own location, and possibly edit prices for their own location only.
• Cashiers and servers can’t edit prices; discounts need manager approval.

Role permissions combined with location access make this practical — see staff roles per location.

What about combos, modifiers and the online store?

Combos and priced modifiers should follow the same price lists, so a breakfast combo at the airport costs more, and so does “add bacon”. Your online store should read the same catalogue and the location’s price list, so customers ordering from the airport branch see airport prices — otherwise you will honour the cheaper price at pickup and lose the margin you priced in.

A short checklist

• One catalogue for all locations; no per-location copies of items
• A price list per location that needs different prices
• Tax groups per location
• Price changes on a fixed day, by one or two people
• One test sale per location after every change
• Online store reading the same catalogue

If you want to see this with your own menu, book a demo and we will set up two of your locations with their own price lists before the call. Or read how multi-store menus work in GetDinerPOS.