Opening a second UK site on delivery apps
Restaurant operators expect the second site to be the first site again and it is a different kind of problem. With one restaurant, the person who runs the kitchen also notices the app, because they are standing next to the tablet. With two, nobody is standing next to both, and every check that used to be automatic becomes something somebody has to decide to do. That transition, rather than any single platform mechanic, is where most small groups start losing trading time without knowing it.
What changes when a restaurant opens its second UK site?
The number of things that can be wrong doubles, and the chance that anybody notices halves.
Two sites on three platforms is six listings, six schedules, six menus, six sets of opening hours and six devices. Each of those can drift independently. And the natural detector, a person seeing an empty order screen during a busy hour, only ever covers the site they are standing in.
The second site is also usually the one nobody has habits for yet, which makes it the one that fails.
Should the second site have its own accounts or sit under the first?
Ask the platform before you open, because changing it later is painful and the answer differs.
Some platforms model a group with multiple locations under a single partner account. Some create a separate account per site. The distinction decides who can see what, whether hours can be managed centrally, and whether reporting arrives combined or separately.
Whichever you get, write down who holds access to each. Access sprawl at two sites is annoying and at ten it is the reason nobody can fix anything at nine on a Friday.
What should be identical between sites, and what should not?
Identical: menu structure, item names, prices unless there is a deliberate local reason, and closing procedure.
Not identical: delivery zone, opening hours where licensing or footfall genuinely differ, and preparation times.
The failure is the second list being decided by accident instead of deliberately. A site that ended up with different prices because somebody uploaded a menu twice is not a local pricing decision, and neither is a site closing an hour earlier because its schedule was copied from a template.
How do I compare two sites without a report that does it?
By looking at both listings the same way on the same day, which nobody does after the first month.
Portals show one site at a time and are built for operating rather than comparing. So the comparison has to come from outside, and the useful columns are: was it orderable during published hours, are the prices the same, is the promotion showing, and how far does the zone reach.
Kitchain (kitchain.co) puts the two listings next to each other on the same day, and side by side is the one arrangement no portal offers and the first one a two-site operator actually needs.
What breaks first in practice?
Availability at the newer site, and menu drift between the two.
Availability, because the habits are not formed and nobody is watching. Menu drift, because a change made at the original site is applied there and forgotten elsewhere, and because the second site’s menu was created by copying instead of by the same process.
Both are cheap to catch early and expensive to discover in a customer complaint.
Does any platform metric change with a second site?
The thresholds are per listing, so each site is graded on its own.
Just Eat’s Local Legend criteria, including “Time offline at 10% or below” held “for two consecutive quarters”, are assessed against each restaurant separately, not against the brand above them. So your original site’s good record does not shelter the new one, and the new one’s early problems do not damage the original.
That is helpful and slightly counterintuitive. It means the newer site needs its own attention instead of being carried.