Multi-Branch Management & Lifecycle Rules

Branch Creation & Setup Rules

The Owner can create and manage multiple branches subject to the active subscription plan tier and purchased branch add-ons.

Branch Creation Fields: To provision a new branch, the Owner provides the Branch Name, Physical Address, and Contact Phone Number.

Initial State & Operational Cloning: A newly created branch automatically inherits general operational settings copied from the Main Branch. However, its Menu catalog starts empty, its raw material Inventory starts empty, and its Employee roster starts empty.

Map & Geolocation Pin Activation: A newly created branch requires configuring its Branch Location Map and Geolocation Pin before it becomes visible and selectable to customers on the Customer Website for delivery and takeaway.

Main Branch Rules: The initial Main Branch cannot be deleted under any circumstances. The Owner can, however, edit and rename the Main Branch at any time.

Branch Capacity Changes & Freeze Mechanics

When a restaurant’s branch capacity decreases (due to plan downgrade or removing branch add-ons), the system applies deterministic freeze rules.

Newest Branch Freezes First: If the allowed branch count decreases below the active branch count, the newest added branch is frozen first.

Employee Scoping during Freeze: Employees assigned strictly to the frozen branch are frozen alongside it. Note that frozen employees continue counting toward the account’s overall Employee Limit.

Customer Visibility & Data Integrity: Historical operational data and financial records of the frozen branch are fully preserved. However, the frozen branch disappears immediately from customer-facing Delivery and Takeaway selection on the Customer Website.

Reactivation: Restoring subscription capacity or re-adding branch add-ons immediately reactivates the frozen branch and its assigned staff accounts.

Permanent Branch Deletion Rules

Branch deletion is restricted exclusively to the Owner and is a permanent, irreversible administrative action.

Branch deletion requires explicit confirmation through a destructive action prompt. Deleting a branch permanently removes its operational data, orders, tables, and branch configuration from the active system.

The system does not utilize an archive state for deleted branches; the action is permanently destructive.