How to manage multiple restaurant locations from one dashboard
Running two or more sites with separate logins, separate booking systems, and separate guest databases is a common source of admin overhead for growing restaurant groups. Separate accounts mean manual reconciliation, inconsistent data, and no way to understand the whole business in one view.
Posto is built for multi-site operators from the start. Every venue is independent for day-to-day operations, but managed from a single account. This guide explains how to set it up.
Step 1Add all your venues to one account
From your dashboard, go to Locations and add each venue. Each site gets its own:
- Public booking page (e.g.
getposto.com/book/your-venue-name) - Independent availability calendar, opening hours, and closures
- Its own services, table layout, and branding
- Separate guest directory
You switch between venues using the venue switcher at the top of the dashboard. Switching is instant — the whole dashboard reloads with the selected venue's data.
Step 2Configure each venue independently
Each venue's settings are completely independent. A restaurant in Bristol and one in Manchester will typically have different:
- Opening hours (different trading patterns)
- Services (one site may offer a Tasting Menu that the other does not)
- Table configuration (different floor sizes)
- Deposit requirements per service
- Email templates and custom messaging
Changes you make in one venue's settings have no effect on others. This prevents accidental cross-venue changes while allowing each site to be configured precisely for its own operation.
Step 3Set up team access correctly
Posto has four team roles: Owner, Admin, Manager, and General. Each role has different permissions, enforced at the data layer — not just the UI.
| Role | Typical person | Access |
|---|---|---|
| Owner | Group owner / director | Full access — all venues, billing, settings |
| Admin | Operations manager | Full access except billing and ownership transfer |
| Manager | Site general manager | Manage bookings, tables, services, team at their venue |
| General | Host / front-of-house staff | View and update bookings only |
Staff members only see venues they have been explicitly invited to. A Manager at your Bristol site cannot see bookings or guest data for your Manchester site — this is enforced at the database level, not just hidden in the UI.
Step 4Understand how guest data works across venues
Each venue has its own guest directory. A guest who books at both your Bristol and Manchester sites appears in each venue's directory as a separate record, with their bookings at that venue only.
This approach keeps things simple and GDPR-clean — a guest at one venue has not consented to their data being visible to staff at another. It also means your Bristol team can see who their loyal regulars are without seeing unrelated bookings.
The Folio module (guest marketing intelligence) operates at organisation level — giving head office a unified view of contacts and cohorts across all venues, with appropriate consent enforcement. This is covered separately in the Folio documentation.
Step 5Track performance across all venues
Booking analytics (covers, completions, no-shows, revenue) are available per venue. To compare performance across all sites, use the Group plan which includes consolidated reporting.
The Posto back-office platform (for Posto operators managing their own customer accounts) is separate and not part of the operator dashboard.
Multi-site pricing
Posto is priced per location per month. Adding a second or third venue is billed separately at the same rate per site. Multi-venue management is included from the Core plan upwards — there is no additional fee for adding venues.
The Group plan (£249/month) is designed for operators running 5+ sites and includes unlimited locations, group-level analytics, a dedicated account manager, and SLA-backed support.
Multi-venue support included on all plans. 14-day free trial on Pro.