Updated July 4, 2026
The Locations screen sums the model up in a sentence: *each location is its own independent restaurant — its own menu, inventory, staff, orders, and payouts; customers and loyalty are shared across the brand.* The independence half is exactly right today; the customer/loyalty-sharing half is the direction, with one caveat below.
Per-location (independent)
- Menu and prices — cloned at creation if you chose to, divergent forever after. A price change at one store never leaks to another.
- Orders, kitchen, and inventory — each location runs its own queue, KDS, and stock.
- Staff — teams, permissions, and PINs are per location.
- Money — each location has its own Stripe account, balance, and payouts.
- Hours, delivery zones, and settings — local decisions, made locally.
Brand identity (copied at setup)
- Logo, colors, and visual identity — a new location starts from a copy of the brand's look, so it's unmistakably yours from day one. It's copied at setup, though, not a live shared source: change a logo or color afterward and you're editing that one location's branding — siblings keep theirs until you update each.
Heads up: One thing to set expectations on: the Locations screen describes customers and loyalty as brand-wide, and that's the direction — but today each location keeps its own customer list and loyalty balances. Don't assume a regular at your first store is automatically recognized (or has their points) at a second location yet; treat customer data as per-location for now.
Note: Delivery respects the split automatically: a delivery order routes to whichever location's ZIP zones cover the customer — see How address checking works.