Running Several Venues: One Account, Separate Rooms

Two venues is not one venue twice. It is a different job, and the thing that changes is not the work — it is that you can no longer see both rooms.

Who it is for

Anybody running more than one site: a second café, a group of restaurants, a venue plus a food truck, or a business that has grown into three towns.

One account, separate venues

Everything sits under one account and you switch between venues.

Each one keeps its own menu, opening hours, photographs, ratings and team, because they are genuinely different places. A second location with different specials and a different kitchen should not be forced to share a menu with the first, and a rating left about one is about that one.

What is shared is you: one login, one place to look, and no juggling of separate accounts with separate passwords.

Staff see their own site

This is the part that matters most as soon as there are more than about ten people.

Somebody who works in one location has no reason to see another's takings, rota or customer list. Roles are per venue, so a member of staff sees where they work and a manager manages the site they manage.

Two consequences worth spelling out. A manager can run a venue without seeing money — billing and payouts are owner-only, so you can delegate the day-to-day without delegating the commercial side. And nobody shares a login, so a staff change is a role change rather than a password change across three sites.

Loyalty: pooled, or deliberately not

A loyalty programme can work across all your locations, and it is off by default.

That default is deliberate rather than lazy. Pooling is obviously right for some groups — a coffee chain where the whole proposition is that your card works at every branch. It is obviously wrong for others: a location that has spent two years building its own regulars may not want to fund rewards earned across town, and some groups differentiate between sites on purpose.

It is a commercial decision, so it is yours to make rather than one made for you by a default.

One detail worth knowing if you do pool: a visit records both where it happened and which programme it belonged to. That is what lets you see "visits to my group's programme, by location" rather than a single undifferentiated number.

Comparing venues is the whole point

A single-venue view tells you how a venue did. It cannot tell you whether a quiet week was the week or the venue.

Chain reporting puts your sites beside each other: takings, visits, members, trends. Most of what you actually want to know is comparative — is Tuesday soft everywhere or only here, is the new site tracking the way the first one did at the same age, is one location's loyalty programme doing more work than another's.

It also shows every site including the ones with nothing happening, which sounds trivial and is not: a location missing from a report because it had no activity is the one you most needed to see.

A group of independents is a different thing

If the venues have different owners, this is not the right model.

What you want there is a coalition: separate businesses sharing one membership, with money settled according to where it was actually spent. The distinction matters because the hard problem in a group of independents is trust about money, and a chain does not have that problem.

Opening the second one

The mistake worth avoiding is treating the second venue as a copy of the first.

Practically, that shows up as reusing the menu, the hours and the photographs because it is quicker. It is quicker, and it produces a listing that describes somewhere else — different room, different specials, sometimes a different kitchen and almost always a different neighbourhood. A customer choosing between two places nearby is choosing on exactly those details.

The parts genuinely worth carrying over are the ones that are about the business rather than the room: how you reply to ratings, what your loyalty programme offers, how you run the rota. Set those up the same way on day one and the new site inherits the standard without inheriting the description.

What it costs

Nothing extra for having more than one venue. There is no per-location fee and no account charge — each venue pays the same commission on what it sells as it would if it were the only one.

A worked example

A café group with three sites.

Each has its own menu and photographs, and its own team who see only their own rota. Two managers run their sites day to day without access to billing. Loyalty is pooled, because the proposition is that your coffee card works at all three.

The owner's actual use of the reporting is narrower than it sounds: once a week, which site is behind and why. That question is unanswerable from three separate dashboards and takes about a minute from one.

What it connects to

• Rota, timesheets and leave — roles, and who sees what
• Run a loyalty programme — and the decision about pooling
• Coalitions — the version for independent venues
• Analytics and your customer data — what the reporting shows
• What Mosey costs — every rate on one page