How to run reservation operations across multiple locations

Separating the business from the branch

The basic decision in a multi-branch business is what belongs to the whole business and what belongs to one branch. All branches sit under one account; each runs independently with its own hours, services, areas and table layout.

Guest records, by contrast, are shared. A guest hosted at one branch is recognised at the next.

Giving each role its own view

A branch manager and the head-office team need different things. The branch manager is focused on tonight’s service; head office wants to compare branches.

Permissions draw that line: who is authorised in which branch, and what they can do there.

• Branch-based user access
• Roles and permissions
• Switching between branches
• Reports that compare branches

One guest, different branches

The same guest visiting several of your branches is common. Keeping guest records for the whole business means history and preferences are not split by branch, and communication consent stays consistent too.

A common standard with branch flexibility

The common mistake in central management is forcing every branch into the same setup. Branches genuinely differ in capacity and in how they serve.

The right balance is a shared frame for reservation policy and the guest experience, with each branch free to set its own hours, areas and table layout.