Ingredients
Grow the estate. Not the menu admin.
Keep ingredients, recipes and food information connected across the group, while each location carries the menu, price and guest experience it actually needs.
One menu change. Too many versions to chase.
As menus rotate, copied files and local fixes multiply. One change becomes a trail of version checks across sites, prices and guest menus.
A supplier changes
One supplier update shouldn’t mean correcting the same ingredient or recipe across every site.
A site needs a different price or menu
Local differences shouldn’t mean creating another disconnected copy.
Every menu cycle creates more work
A new menu cycle can set off another round of checks, local edits and guest-menu updates across the group.
Central where it should be. Local where it needs to be.
Keep the shared operational detail connected, then apply the local menu, availability and pricing where it belongs.
One connected menu foundation
The shared structure behind every location.
Share the things that should stay the same, then give each site the differences it genuinely needs.
Analytics across the group
See menu views, location activity, dish performance and the allergen filters guests use most, so you can understand customer behaviour across every location.
All locations
Last 30 daysViews by location
300200100
BrightonManchesterLeeds
Allergen filters
Gluten
Milk
MustardNutrition calculated automatically
For groups covered by calorie-labelling rules, show calories or full nutrition with figures that update when recipes, portions or ingredients change.
Chicken Caesar salad
ShowCalories onlyFull nutrition
31.5gProtein48.2gCarbs14.2gFat8.9gFibre
Keep one menu. Price locally.
Set the price each site needs without copying the dish or rebuilding its shared recipe, allergen and nutrition detail. Local commercial decisions stay local; the underlying menu remains one connected source.
Shared menu item
Chicken Caesar salad
Brighton£15.50
Manchester£16.00
London£17.50 entered for London
Allergen detail, ready at every site
Keep written allergen records current across every menu, supporting FSA guidance and Natasha’s Law workflows while staying ready for Owen’s Law.
Allergen profile
Chicken Caesar salad
Contains
GlutenMilkMustardMay contain
Soya
SulphitesRemovable ingredients
Milk ParmesanMustard DressingPlan the change before it goes live.
Build the next menu while the current one stays live. Keep it hidden while the team works, then schedule when each location should switch to the new version.
Next menu
Autumn menu
Guest visibility
Hidden while reviewed
Scheduled
15 Oct · 18:00
Ready to publish
01
Build next menu
Update dishes, prices or availability
02
Keep hidden
Guests still see the current menu
03
Schedule
Choose date and time
04
Live at location
New menu is now guest-facing
Switch by destinationLeedsShoreditchManchester
Bring the whole group across without the migration headache.
Bring the recipes, supplier data and menus you already run into one shared structure, then roll out each site with the right local detail.
- Fast guided onboarding shaped around the group.
- Bring in the recipes, supplier data and menus you already run.
- Roll out site by site while the shared structure stays intact.
Running a franchise model?
When the brand standard and the local operator are separate, Harlo can support a different way of structuring the menu.
Questions growing teams ask before they switch.
Can we manage shared ingredients and recipes centrally?
Yes. Shared ingredients, recipes and batch recipes can sit in one connected structure and be used by the relevant menus and locations.
Can locations have different menus, availability and prices?
Yes. Harlo keeps the shared menu structure connected while supporting the local menu, availability and pricing differences each site needs.
What happens when a supplier, recipe or allergen changes?
Update the source information, review the affected recipes and menu items, then publish the guest-facing change where required.
Can allergens and nutrition stay consistent across locations?
Yes. Allergen and nutrition information can travel from the same ingredient and recipe structure into the dishes and menus that use it. Allergen Management and Nutrition & Calories.
Can each site publish its own guest-facing menu?
Yes. Harlo Menu Publishing supports branded live menus that can be shared by normal web link or QR code for the relevant destination. Menu Publishing.
Can we add new locations without rebuilding everything?
Yes. Bring the new site onto the existing menu foundation, then add the menu, price and availability differences that apply locally.
Can Harlo help us understand dish costs and margins?
Harlo keeps ingredient costs, selling prices and margin-related information close to the recipe so the commercial effect of a change is easier to assess.
What if our locations aren’t all the same?
That is the point of the shared/local structure. Keep common ingredients, recipes and menu information connected, while genuine site differences stay local.
Give the next location the same foundation as the last one.
Keep the group’s menu structure connected before more locations mean more versions to manage.