Scaling labelling from one kitchen to five: what breaks first
Most advice about multi-site labelling is written for estates of twenty or fifty. Very little covers the stage that actually causes trouble, which is somewhere between your second and your fifth site.
That's the point where the informal systems that worked beautifully for one kitchen stop working, usually without anyone noticing until something goes wrong.
Why one site works without a system
A single kitchen runs on shared knowledge. The head chef knows every shelf life. The team has been taught the same way, mostly by the same person. If someone is unsure, they ask, and the answer is a few feet away.
It's an efficient way to run one kitchen, and plenty of excellent restaurants operate exactly like that for years.
The trouble is that it doesn't scale well. You can't hand a new site a head chef's memory.
Site two: the copy problem
Your second kitchen gets set up by someone from your first. Standards travel with that person, and for a while it can seem like that works.
Six months later the two sites are somehow doing things differently. This isn’t usually an intentional choice, it tends to be as a result of different problems emerging in each site that lead the team to come up with different fixes.
What to do at this stage: write down what a label must contain and what shelf life applies to what. It doesn't need to be a manual, just a single sheet covering product name, prep date, use-by, allergens and initials, plus your shelf-life rules by storage method. Writing it down might help surface inconsistencies between sites.
Site three: the visibility problem
At three sites, it’s more difficult to keep track of everything going on within each kitchen, especially when it comes to something like labelling.
You stop knowing the day to day. You find out about problems when someone tells you, which means you only find out about the problems people think are worth mentioning. Quiet inconsistency stays quiet.
What to do at this stage: get some form of record that doesn't depend on anyone reporting. Automatic print logs, expiry tracking, anything that shows you what's actually happening across the sites rather than what you've been told. This is usually the point at which a digital system starts paying for itself on visibility alone, separate from any time and cost saving.
Site four and five: the training problem
By now the chain of people who learned from the person who learned from the person has stretched.
New sites tend to learn from their nearest neighbour rather than from you, unless there is a specific labelling process in place that is included in initial training.
What to do at this stage: make sure new sites get their setup from the centre. If you're running a system with a central product library, a new kitchen should inherit that rather than build its own. That single thing prevents most of what goes wrong between five and fifteen sites.
What's different about labelling specifically
Labelling is a useful early warning of inconsistent sites, because it fails visibly and quickly.
You can open a chiller at any of your sites and see immediately whether your standard is holding. Nothing else in a kitchen gives you that at a glance. If your labels differ between sites, so will other things you can't see as easily.
It's also the area where inconsistency has the sharpest consequences. Every site is inspected and rated separately, and every rating is published under your brand name. So one weak kitchen can tank the reputation of all of your other sites.
Where Labl.it fits
Labl.it is priced per device at £34 a month, or £28 on the annual plan excluding VAT, with no minimum site count.
Products, shelf lives and allergens live in one back office. Adding a fourth site means the new kitchen inherits your existing product library rather than starting from scratch, and a change made centrally reaches every device. Print logs and expiry reports give you visibility across sites without anyone having to compile anything, and permissions can be set so a chef adds products for their own kitchen without altering the central record.
Frequently asked questions
At what point does a growing restaurant group need a labelling system?
Usually around the third site, when you stop being able to hold every kitchen in your head and start finding out about problems only when someone reports them. That being said, there’s value in a labelling system for every kitchen, from single sites to massive enterprises.
What goes wrong first when you open a second kitchen?
Standards travel with the person who set the site up, then the two kitchens gradually diverge as the new one solves local problems in its own way.
How do we stop new sites developing their own way of working?
Set them up from the centre rather than letting them learn from the nearest existing kitchen. A central product library means a new site inherits your standard on day one.
Does each site get its own hygiene rating?
Yes. Every venue is inspected and rated separately, and each rating is published individually under your brand name.
Can different sites have different products?
Yes. Central product management can push to all sites or selected ones, and permissions allow a chef to add products for their own kitchen without changing the central record.
Check your chillers
Before deciding anything, walk into each of your kitchens and look at the labels. If they don't match, you've found a problem.
Labl.it comes with a 14-day free trial, and multi-site trials are available if you'd rather test across more than one kitchen. If it isn't right, return it in the prepaid box at no cost.
