Branches

A branch is a physical location with its own daily life: it opens, sells, closes its drawers and closes its day. Everything that is true of this location but not the company lives on the branch.

Shop start time#

The single most consequential branch setting: it defines the business day. A branch that trades past midnight needs a start time that puts the late hours in the right day — 5:00 a.m. is a common choice. Change it only with an understanding of the day boundary, ideally never after go-live.

Kitchen routing#

The branch maps its kitchen departments to printers or displays: the grill's tickets print at the grill. An item's department comes from the menu; the branch decides where that department physically prints.

Per-branch behaviour switches#

• Stock consumption on day close — whether this branch's day close runs recipe-based consumption. The recommended setting for food businesses; branches that don't track stock leave it off.
• Shift rules — which shift may close while pending delivery orders exist.
• Register policies — manual closing and strict denomination counting, where the branch wants them.

Authorizer lists#

The branch names who may sign for each guarded action — discount authorization, register view, credit orders, charge edits and the rest. Lists are per-branch because trust is per-location: the person who can sign at the flagship isn't necessarily present at the kiosk. See Authorizations for how the signature flow works and the one rule worth memorizing: an empty list means unrestricted.

Opening a new branch#

Create the branch, set its shop start time, map its printers, set its switches, fill its authorizer lists, and define which users work there. The menu and roles come from the business automatically — a new branch is mostly a matter of location facts, not re-setup.