Skip to main content

Manage several restaurants

Workspace = account, Restaurant = venue​

Your workspace is the account that groups all your restaurants under the same subscription and team.

Workspace
+-- Restaurant A (Bar Centro)
+-- Restaurant B (Cafetería Plaza)
+-- Restaurant C (Asador Norte)

If you have a chain, a brand with several venues, or a hospitality group - everything sits under a single workspace.

Workspace-level shared data​

What every restaurant in the workspace shares:

  • Customers (CRM): if Juan reserved at Bar Centro and later at Asador Norte, he's still the same customer. Unified history.
  • Marketing and coupons: campaign config, Meta Pixel, coupons that apply to all.
  • Plan and subscription: one invoice, one plan, one trial.
  • Users and roles: invite someone to the workspace and they access every restaurant (or those you choose).

Per-restaurant data​

What's independent per venue:

  • Menu, categories, dishes, prices, photos.
  • Tables, floor plans, capacity, capacity mode.
  • Reservations, service pauses, table blocks.
  • Opening hours.
  • Operational config (slot interval, duration, window).
  • Logo, cover, visual theme.
  • Public slug.

Restaurant Switcher​

Block at the top of the sidebar shows the active restaurant. Click to open the dropdown:

  • Lists every restaurant in the workspace.
  • Status indicator: "Backoffice ready" or "Setup pending: step X".
  • Your role on each one.
  • "+ New restaurant" button at the end.

When you switch, the entire backoffice (reservations, menu, analytics) reflects the new restaurant's context.

Add a new restaurant​

From the switcher → + New restaurant → onboarding wizard.

Pre-checks:

  • Essential plan: 1 restaurant.
  • Advanced plan: up to 3.
  • Elite plan: unlimited.

If you hit the limit, RestaPro shows the required upgrade before continuing.

Workspace-level plan​

A single subscription covers every restaurant. Changing plan updates them all at once. More in Subscription and billing.

Comparative analytics​

/app/analytics shows the entire workspace:

  • Aggregate KPIs (total reservations, covers, cancellation rate).
  • Per-restaurant table with individual metrics.
  • Stacked bar charts (confirmed, canceled, no-shows) per venue.
  • Period over period to see growth.
  • Channel breakdown (web, embed, manual, walk_in).
  • Combined time heatmap.
  • Top-performing restaurant ranking.
  • Custom date filter (any range).

Useful to spot:

  • Which venue converts best from the web.
  • Which seasonal patterns repeat across all.
  • Which restaurants need more marketing attention.

Collaborative flow​

  • Owner: creates the workspace, the first restaurant, invites the team, manages billing.
  • Admin: manages every restaurant (except critical billing).
  • Staff: daily operations.

More in Roles and permissions.

Best practices​

  • Clear names: "Bar Centro" > "Venue 1". Avoid ambiguity when switching between venues.
  • Separate hours if they differ: each restaurant has its own opening_intervals.
  • Centralized marketing: campaigns usually apply to the whole portfolio; segment by restaurant if you need.
  • Customer CRM: take advantage that the customer is one person even if they visit several venues.
  • Weekly analytics: spend 15 min on Monday looking at the comparison.
Last updated on
ESENCA