Multi-Location Restaurant Ordering: Managing 3+ Sites in One App (UK 2026)

Going from one location to three is the hardest expansion phase a UK restaurant group will hit. The systems built for one site fall over the moment a customer needs to choose between locations, prices diverge between sites, or marketing wants a group-wide push notification. This guide covers what a multi-location ordering app should do, what to watch for, and how the maths shifts when you have 3+ sites.

What multi-location actually means for an ordering app

A multi-location ordering app needs to handle six things cleanly that single-site apps do not.

• Location picker on first open. Customers see a list of nearby sites (or a map) and pick where they want to order from. The picker should default to their nearest site by geolocation.
• Per-site menus. Site A might serve breakfast, Site B might not. Items can be common but availability per site needs to vary.
• Per-site pricing. London and Manchester sites sometimes price differently. The system has to support it without forcing two separate apps.
• Per-site opening hours. Site A is open until 11pm, Site B until 9pm. The order flow needs to respect each site's hours.
• Group-wide loyalty. A customer earning Bronze at Site A should not lose that progress at Site B. Loyalty is at the customer level, not the site level.
• Group analytics + per-site analytics. The manager of Site C sees their orders; the owner sees all three.

The decision: one app or multiple apps?

For a restaurant group with the same brand across all locations (think Honest Burgers, Pizza Pilgrims, Patisserie Valerie), one app with location-switching is the right answer. Customers download once and use it everywhere.

For a holding group with different brands per site (e.g., one Italian, one Thai, one cocktail bar), each brand gets its own app. Loyalty does not transfer between brands; customers do not want it to.

Aexir supports both patterns. A single branded app with multiple sites is the default and costs £1 per day per extra location on top of the base £31 per month subscription.

Group reporting that actually helps you run the business

Most multi-location POS systems give you a summary dashboard with totals per location. That is fine, but not enough. What you actually need is the comparison view: which site is over-performing on Friday nights, which is under-performing on Sunday lunches, which is sitting on dead stock, which is spending three times the average on driver costs.

Aexir's analytics dashboard surfaces those comparisons natively. Filter by site, time of day, day of week. Drill into the worst-performing slot and see what items are not selling. That is where group margin comes from.

Common multi-location issues

• Customer orders from the wrong site. Cause: location picker buried in settings, not first-open. Solution: make the location picker the first screen for new users; remember choice thereafter.
• Loyalty stamps "double credit" between sites. Cause: loyalty linked to site, not customer. Solution: pick a platform where loyalty is on the customer profile, not the site.
• Different opening hours cause confusion. Cause: site hours stored at app level, not site level. Solution: per-site opening hours, with the app refusing orders outside those windows.
• Manager at Site B cannot see Site B-only reports. Cause: admin dashboard shows group totals only. Solution: role-based access where site managers see their site, regional managers see their region, owner sees all.
• Marketing pushes the wrong promo to the wrong site. Cause: push targeting is app-wide. Solution: per-site push notification targeting (only customers who have ordered from Site A get the Site A promo).

The maths on a 3-site UK group

Take a real-world example. A small UK group, three sites, 40 orders per site per day on average, £17 average ticket. Annual gross revenue across the group: £744,600. Currently 65% on Uber Eats at 30% commission, 35% on phone and walk-in.

What to look for in a multi-location builder

• Single customer database across all sites. One customer profile, one loyalty balance, one order history.
• Per-site menu management with shared item library. Update the burger once, push to whichever sites you want.
• Group-level brand consistency, site-level flexibility for hours, pricing, stock.
• Role-based admin access. Site managers see their site, owner sees all.
• Push notifications targetable per-site. Promote a Friday-night deal at one site only without spamming the other two.
• Analytics filterable by site, with built-in comparison views.
• Transparent per-location pricing. Avoid platforms that double the subscription per site; you should pay incrementally, not multiplicatively.