For businesses

Run two or three restaurant sites without three of everything

Mosey · 15 November 2026 · 11 min read

To run two or three restaurant or café sites without three of everything, keep one owner login and give every person their own role at each site. Share only what should be shared: a copied menu, one loyalty card, one job advert. Keep prices, rota and plan per site, and read the group in one Chain view.

Five numbered steps for running several sites: add each site to your login, give every person a role at each site, copy the menu and check it, switch on what should be shared, then read the Chain view each week.

Why does a second site double the admin and not the income?

The first site runs on your head. You know the prices, the regulars, who can open and who cannot. A second site takes the same head and splits it.

So the admin does not add, it multiplies. Two menus to keep in step. Two sets of passwords, or worse, one shared password that three managers know. Two screens where a price can be wrong. A Friday figure that sits in one tab while the Saturday figure sits in another, and a bookkeeper who asks for both.

Most owners handle this with shortcuts that feel kind and cost later:

  • One shared owner login. Quick, and then you cannot tell who changed a price, and you cannot take access back from one person without changing it for everyone.
  • A copy of the menu in a spreadsheet. It is out of date by the second week.
  • Everyone is a manager. It saves a conversation, and it gives the Saturday kitchen porter the power to change your bank details.

The fix is not more software. It is deciding, once, what is shared across the group and what belongs to one site, then giving each person only the keys their job needs.

What should you share across sites, and what should stay separate?

Start with a rule: share what makes the group feel like one business to a customer, and keep what makes each site run to its own room, its own team and its own numbers.

Share across the group Keep separate per site
Your owner login, so one sign-in covers every site Prices and the live menu, because each site has its own kitchen and costs
A starting menu, copied across once Opening hours, bookings and tables
A loyalty card honoured at every site (your choice) The rota, staff records and clock PINs
A job advert posted at several sites at once The reservation plan and monthly billing
Role names and the permissions you give each job Who holds the keys at each site
The weekly group figures Allergen declarations, checked on each menu

On Mosey, each site is its own business page with its own menu, bookings, plan and billing. Your login links to all of them, and a switcher at the top of the dashboard chooses which one you are working in. Everything you do applies to the site you have selected, so read the name before you save a price.

How do roles work when one person covers two sites?

A role belongs to the link between one person and one site, not to the person. The same person can own two sites, manage a third and work the floor at a fourth, and the access follows the site.

There are three roles. Owners run everything: billing, payouts, the team and every setting. Managers run the business day to day: orders, bookings, the menu, offers and reports. They cannot change billing, payouts or who is on the team. Staff handle service: orders, taking payments, bookings and the inbox, and they do not see reports, settings or billing.

On top of the role, you can switch single permissions on or off for one person, such as replying to ratings, issuing refunds or managing the rota. That is how a shift lead at one site can issue refunds without becoming a manager.

Some guard rails hold whatever you do:

  • Only an owner can hand out billing, team and chain control. A manager cannot give them to anyone, in any invite.
  • Only an owner can remove another owner, and nobody can change their own role.
  • The last owner of a site cannot be removed or leave.
  • Team changes are recorded, so you can see who changed what.

Who should hold which keys? A permissions plan for three sites

Write the plan on one sheet before you invite anyone. Here is an example for a group of three: a café, a restaurant and a takeaway. The names are invented, the pattern is the point.

  1. You, owner at all three. You hold billing, the team and the Chain view.
  2. Your operations manager, manager at all three. Menu, offers, bookings, orders and reports, no billing and no team control. Add the rota permission, because running the rota is a different job from owning the business.
  3. A head chef, manager at the restaurant only. Menu and orders there, no access to the other two.
  4. A shift lead who covers the café and the takeaway. Staff at the takeaway, manager at the café. Same person, two roles.
  5. Counter staff, staff at one site each. Take payments and handle orders. Switch off anything the job does not use.
  6. A bookkeeper. Not a team member at all. Give them the Chain report export instead.

Review the plan monthly. The usual failure is a manager who left one site and still has a link to another. On Mosey, the Chain team view shows a grid of every person against every site with their role at each, and team changes are logged, so the review takes five minutes. Remove leavers the same day.

New people are invited by email. Someone with no Mosey account gets a single-use link that lasts seven days. Someone who already has one is added straight away. Read the team and access roles guide for the set-up steps.

How do you see the whole group on one screen?

Once you have more than one site on your login, a Chain page appears under Account. It has five tabs, and the page and each tab show only to people who hold the permission behind them. By default that means owners. Treat it as a tidy screen, not a lock: anyone you link to several sites is someone you trust with those sites.

  • Overview. Revenue, orders, Mosey fees, Mosey Pay takings, reservations, loyalty members and average rating, by site, for the last 7, 30 or 90 days, with a daily trend. You see which site is slow before the month ends.
  • Financials. A month at a time: what each site owes Mosey in fees and its reservation plan, with group totals.
  • Reports. Orders or payments by day and by site as a spreadsheet file. An export is capped at 5,000 rows and says so when it has been cut short, so narrow the dates and run it again.
  • Team and access. The grid of people against sites and roles.
  • Mosey Pay. In-store payments by site and by member of staff. Payments are attributed to whoever was logged in, and earlier payments carry no name.

If your sites ever bill in different currencies, the Chain view does not blend them into one false total. Most Irish groups will never see this.

One limit to know: the Chain view reads what Mosey handles. Takings that never touched Mosey are not in it, so keep your own record for those. The chain guide walks through each tab.

How do you run one menu across sites without copying mistakes?

Build the menu once at the site that has it right, then copy it. You need menu access at both sites, and the copy brings the menu, its sections, every dish that is not archived, and each dish's extras, sizes and options.

What it deliberately leaves behind is as useful to know:

  • Ratings, likes and stock. They belong to the dish at the site where it was eaten.
  • Members-only links. A membership plan belongs to one site.
  • Anything across currencies. The copy is refused if the two sites price in different currencies, because 12.50 in one currency is not 12.50 in another.

After the copy, do three things at the new site. Change the prices that should differ. Switch off dishes that site does not make. Check the allergens. Mosey copies each dish's allergen declaration and records the copy in that dish's history, but the kitchen at the new site may use a different supplier, and you are responsible for what each menu declares. A dish with nothing declared shows as not listed, never as safe.

Keep dish names, categories and allergens consistent across sites, so reports compare like with like and a regular who moves between sites meets the same words. The menu scanning guide helps if a site's menu exists only on paper.

Can one loyalty card, one membership and one job advert work across sites?

Yes, and each is a choice rather than a default.

Loyalty. A loyalty card is free on every plan. In its advanced settings there is a tick to honour the card at all your sites under one business profile. Leave it off and each site keeps its own card. Switch it on and a customer can earn at one site and redeem at another: one card across the business. Switch it on only if the sites share a brand and a reward you can afford at any of them. A card that is generous at the café and costly at the restaurant will be spent at the restaurant. Nothing is settled between sites, because loyalty carries no commission. See how to run a loyalty programme.

Memberships. A membership plan belongs to one site, and its price and perks should be checked against that site's margin. If you want one membership across several sites, a pass is sold by one lead site, with each other site taking an agreed share, and the lead pays the others their shares. The membership commission is 8% plus VAT of each payment, shown on the pricing page. Do the margin sum site by site first, as in how to price a membership and check the margin. A neighbourhood version with other businesses is in the neighbourhood pass guide.

Hiring. Post one job advert at up to 25 sites in one action. Each site gets its own job through its own pay rules, and a site that is refused is listed with the reason, without stopping the others. You need the hiring permission at each. The hiring guide covers the rest.

Staff records stay with the site. Staff records, the rota, leave and clock PINs are kept per site. Someone who works at two sites has a record at each, and a clock PIN from one site is not recognised at the other. That is more typing on day one, and it keeps hours and pay clean when the two sites run different rotas.

What does each site cost on Mosey?

Sites do not pool. Each has its own plan, its own monthly billing and its own fees, at the same published rates whichever site takes the order or the payment.

The reservation plan is per site. Bookings have a free plan, and the Starter plan is €79.99 a month, so two sites on Starter pay it twice. The Chain financials tab shows each site's plan line and fees side by side, so the cost of the group is one screen, not three invoices. Roles, invites and the Chain page have no charge of their own.

Money from a site goes to the Stripe account of that site's main approved owner: the primary owner, or else the earliest. If you are that owner at all three sites, all three pay into your one Stripe account. If a partner who holds a share is the main owner at one site, that site's takings go to their account, so decide who the owners are before you invite anyone. A manager's or staff member's account is never paid, and bank details are entered in Stripe's own screens.

Rather than compare against a total, compare each site's fees with its own takings. For the wider picture of what a group spends on software, read how much restaurant software costs.

What should you check every week across the group?

Pick five numbers and read them in the same order on the same day. A suggested set for a group:

  1. Orders and revenue by site, against the last period.
  2. Bookings by site, and which nights were empty.
  3. Mosey Pay takings by site and by person, if you take payments at the table or counter.
  4. Loyalty members by site, to see whether the card is working where you expected.
  5. Average rating by site, and the ratings you have not replied to.

Do not chase the difference between sites as a league table. A site with a smaller room is not failing. Compare each site with its own last month. Then change one thing at one site, wait a fortnight and look again. What to read and what to ignore is in what to measure each week. If bookings differ most, choosing a booking system shows what to compare.

What can you do this week?

Do these in order:

  1. List every site and every person with access. Remove anyone who has left.
  2. Write the permissions plan on one sheet and compare it with the Team and access grid.
  3. Make sure only owners hold billing, team and chain access.
  4. Copy your best menu to the next site, then fix prices and allergens there.
  5. Decide whether the loyalty card should work at every site, and why.
  6. Open the Chain overview and write down this month's starting figures.
  7. Ask your bookkeeper whether the orders and payments export gives them what they need.

When you are ready to run the group from one login, Host on Mosey, host each site, then invite your first manager. More in the guides for food businesses, and the several sites and staff roles page lists the features.

This guide is general information, not legal, tax or financial advice. Rules change and depend on your business and where it is, so check the current rule with the official body named in the guide and take advice from a solicitor or accountant in your area before you act.

Questions

Common questions

  • Can I run two restaurants from one Mosey login?

    Yes. Each site is its own business page, linked to your login, and a switcher at the top of the dashboard picks which one you work in. Once you have more than one, a Chain page appears under Account for owners to read the group.

  • Can a manager see the figures for all my sites?

    Not by default. The Chain page and its tabs show only to people who hold the chain, billing or team permissions, which owners hold and managers do not unless you grant them. A manager works in the site or sites they are linked to, at the role you set there.

  • Can one person be a manager at one site and staff at another?

    Yes. A role belongs to the link between one person and one site, so the same person can be owner at one, manager at another and staff at a third. You can also switch single permissions on or off for each person.

  • Can I copy a menu from one site to another?

    Yes, if you have menu access at both and the sites price in the same currency. The sections, dishes, extras and options are copied, with each dish allergen declaration. Ratings, likes, stock and members-only links are not. Check prices and allergens at the new site.

  • Can customers use one loyalty card at all my sites?

    If you switch it on. A tick in the loyalty set-up honours the card at all your sites, so a customer can earn at one and redeem at another. It is off by default, and loyalty is free on every plan. Check the reward is affordable at each site.

  • Does each site pay for its own plan on Mosey?

    Yes. Each site has its own plan, monthly billing and fees, at the same published rates. The reservation plan is per site, so two sites on Starter pay it twice. The Chain financials tab shows each site beside the others. See the pricing page.

  • How do I stop a leaver keeping access to one of my sites?

    Remove them from each site they are linked to the same day. The Team and access grid shows every person against every site, so you can see where they still appear. The last owner of a site cannot be removed, which protects you from locking yourself out.

  • Can my bookkeeper get takings for all my sites?

    Yes, as a spreadsheet. Owners can export orders or payments by day and by site from the Chain page. Exports are capped at 5,000 rows and flagged when cut short, so narrow the dates and run it again. Mosey does not file your VAT or give accounting advice.

More like this

Read next

Get started

Host your business on Mosey. It is free to claim.

Free to list, no set-up fee, and Order Ahead is 1.5% commission when you start taking orders.