ReserOne

Multi-branch management

See reservation operations across multiple locations

Company is the SaaS tenant boundary, and one company can contain multiple branches. Authorised users can work in one branch or across several.

Quick answer

How does multi-branch support work?

In ReserOne, Company is the SaaS tenant boundary and one company can contain multiple Branches. A branch is an operational restaurant, cafe, bar or lounge location. The standard model uses one tenant database per company; branches are not separate tenant databases by default. Which branches a user can work in is determined by roles, permissions and branch access.

  • Company and branch model

    Multiple operational locations are defined under one company.

  • Company-level guest profile

    Reservation history stays coherent across branches.

  • Branch-based access

    User permissions are defined together with branch context.

  • Multi-branch view

    Branches can be followed comparatively.

Separating head-office and branch visibility

In a multi-branch business not everyone needs to see everything. What a head-office role needs differs from what a branch manager needs. The role and permission model lets you draw that line.

  • Branch-based user access
  • Role and permission definitions
  • Switching branch context
  • Comparative multi-branch operational view

Branch overview

  • Central Branchİstanbul86% occupancy
  • Seaside Branchİzmir72% occupancy
  • Marina BranchBodrum91% occupancy

Frequently asked questions

Do we need a separate system per branch?

No. Branches are defined under the same company and, in the standard model, are not separate tenant databases.

Is guest information shared across branches?

The customer record is at company level by default; access is determined by the role, permission and branch-access model.

Related pages

Let us plan your multi-branch setup

We will review your head-office and branch permissions against an example structure.