Branches And Outlet Controls

Manage branch profiles, branch status, feature assignments, organization-level controls, and multi-outlet operating context.

Branches is how Zesty runs more than one outlet under one restaurant group—or how a single outlet keeps a clear location record.

In the app, look for Branches in navigation. This docs URL (/docs/franchise) stays for old links; the product term is Branches, not "franchise module."

Single outlet vs multi-outlet

Setup	What to do
One café, one kitchen	One main branch is enough
Chain or franchise group	One branch record per physical location

Even single outlets benefit from branch context on reports, QR codes, and staff scope.

Organization-level controls

At the organization level owners set:

sales workflow mode — Orders only, POS only, or Combined
feature catalog — which modules the group can use
plan and billing — what entitlements apply
default menu — shared catalog across branches

Changes here affect every branch unless a branch has an override.

Detail: Feature catalog

Branch-level controls

Each branch can have:

own address, hours, and contact
feature assignments — enable or restrict modules per location
own tables, QR codes, and inventory
branch-scoped staff (managers see only their outlet)
separate reports and Shift Desk closes

Use overrides when one location is a cloud kitchen and another is full dine-in, or when a new branch is still in soft launch.

Branch workspace

Managers working in branch context see sections such as:

orders and Shift Desk
inventory and menu (if permitted)
staff for that branch
branch reports and settings

Rule: branch managers should stay inside their branch. Mixing context causes orders, stock, and expenses to land in the wrong outlet.

Branch profiles

Keep current:

legal and customer-facing name
address (for receipts and support)
operating status
contact for local emergencies

Stale branch data breaks customer QR screens and support investigations.

Branch status (active / inactive)

Deactivate a branch when it should stop operating in live workflows.

Before changing status, confirm impact on:

open orders and table sessions
staff logins scoped to that branch
QR codes still scanned by customers
inventory in transit
reports and tax period boundaries

Prefer planned deactivation with communication—not Friday-night toggle without checklist.

Governance habits

Review when:

Event	Review
New branch opens	Features, menu inheritance, staff invites
Branch manager changes	Permissions and branch scope
Plan upgrade/downgrade	Feature catalog vs each branch override
Acquisition / closure	Status, data export, QR takedown

Align each branch's sales workflow mode with how that site actually sells—do not copy HQ mode blindly to a POS-only kiosk.

Groups choose:

central menu with branch price/availability overrides
fully local menus per branch

Document your choice so menu imports do not overwrite local specials by accident.

Reporting across branches

Owners may compare branches in org-level analytics. Each branch still closes its own shift in Shift Desk. Do not close Branch A's money while logged into Branch B.

Common questions

Staff cannot switch branch
Check assignment, role, and whether branch is active.

QR shows wrong outlet
Reprint QR tied to correct branch table record.

Feature on at org but missing at branch
Branch override may have disabled it.