Multi-site
Running multiple venues: what to standardise and what to leave local
A second site does not double the work: it changes it. Here is what to centralise.
KlyraOS Editorial · Published on 22 July 2026 · 8 min read
With one site control is visual: you walk in, look, correct. With two or more, control becomes informational, and it only works when data arrives in the same format from every site.
Always standardise
- Product and recipe master data: same name, same unit, same yield
- HACCP check structure: same categories, frequencies adapted per site
- Job tags and permissions: the same role must mean the same thing everywhere
- Report formats and comparison periods
Leave to the site
- Opening hours and rota shape
- Local suppliers and purchase prices
- Equipment and its check frequencies
Permissions: the most common mistake
A site manager should not see other sites' financials; an area manager should, read-only. A cascading model (organisation → site → person) avoids rebuilding permissions at every opening.
People working across sites
Normal in chains and the main source of errors: double assignment at the same time, hours counted twice, rest periods broken. Conflict detection must look at the person, not the single site.
What to compare across sites
- Labour cost as a percentage of revenue, not absolute
- Actual food cost per product family
- Share of HACCP checks completed on time
- Open non-conformities and average time to close
FAQ
One organisation or one per site?
One organisation with multiple sites keeps master data shared and comparisons immediate. Separate organisations only make sense with truly independent legal entities.
Keep reading
Keep reading
Gestire piu locali
Practical guides on HACCP, food cost, rotas and multi-site management.
Request access