Standardising across sites
Total consistency is expensive and total autonomy is unmanageable. A practical split of what a group should centralise and what each site should decide.
Every growing group runs into the same argument. Head office wants consistency because it is easier to manage and protects the brand. Site managers want latitude because they can see things head office cannot. Both are right about their own half, and the argument only resolves if you separate the things that must match from the things that should not.
Standardise what breaks reporting or the brand
- ✓Item identity. The same dish must be the same record everywhere, or you can never compare its performance across sites. This is the one that quietly ruins multi-site reporting.
- ✓Recipes and specs. A dish that differs between sites is a different product wearing the same name, and guests notice before your reports do.
- ✓Category and naming conventions. Divergent names make every group-level report an exercise in translation.
- ✓Anything guest-facing that carries the brand promise: portion, presentation, service standards.
Leave local what is genuinely local
- ✓Price. Rent, wages and willingness to pay differ, and forcing one price across all sites gives up margin at one end and covers at the other.
- ✓Availability. Not every kitchen has the same equipment, storage or supplier coverage.
- ✓A small number of local items. One site's neighbourhood favourite is worth more than uniformity.
- ✓Staffing shape and schedule. Demand curves differ by site, and a rota imposed centrally will fit none of them.
Standardise IDENTITY, localise PRICE AND AVAILABILITY. A dish should be one thing everywhere; what it costs and whether this kitchen makes it today are local calls.
Write it down before you enforce it
Most inconsistency across a group is not defiance. It is the absence of a written standard, filled in by whoever was on shift. Managers invent a way to do something because nobody told them the way, and by the time head office notices, three sites have three habits.
The cheapest intervention in most groups is transcription: writing down what is currently in the founder's head, so the standard exists to be followed.
How this works in Opero
Opero's data model matches the split above. Products are an account-wide catalog, so a dish is one record with one identity across the group and stays comparable in reporting. Menus are per location, and per-location overrides carry both price and availability — so a site can charge its own price or 86 an item locally without creating a duplicate product.
Opening a site can start from an existing location's menu, copied and then edited, which is what stops naming drift at the moment it usually begins. Reporting rolls up by brand and by region for groups that need sets rather than one flat list.
See one catalog with local price and availability.
Explore multi-locationFrequently asked questions
- Should every location charge the same price?
- Rarely, if rent and wages differ materially. Per-location price overrides let a site price to its own market while the dish stays one product for reporting, which is the combination you want.
- How do I stop menus drifting apart between sites?
- Standardise item identity and naming centrally, and start new sites by copying an existing menu rather than building one. Most drift begins at opening, when someone rebuilds a category from memory.
- What is the most commonly over-standardised thing?
- Price, followed by staffing patterns. Both are visible and easy to mandate centrally, and both are genuinely local decisions that cost money when they are imposed.
Run your whole restaurant on one platform
POS, kiosk, QR ordering, kitchen display, and payments on one spine — you bring the tablets, and the card reader is the one piece you buy from us. Unlimited devices, no per-device fees.
Explore the platform
Keep reading
Multi-Location Menu Management Without Six Spreadsheets
The second location is where menu management stops being a task and becomes a system problem.
Comparing Restaurant Locations Without Fooling Yourself
Ranking locations by sales is the most common multi-site reporting mistake, and it usually punishes your best operator.
What Breaks When a Restaurant Group Adds Locations
Every group hits the same wall at roughly the same size, and it is almost never the food.