Master menu, branch reality: design lessons for 1,000-location scale
Head office wants 95% brand consistency while every franchisee swears their market is different. That tension isn't only a software problem — but software can make it tractable or hopeless.
The sentence we hear most in large chain rollouts: "make the system flexible, but don't let anyone break it." Those two requests contradict each other directly, and software's job is not to resolve the contradiction but to draw its boundaries explicitly.
Why banning overrides doesn't work
Systems that permit no branch-level change produce the same outcome in the field every time: managers go around the system. Price differences get applied by hand at the till, promotions run over WhatsApp, and your reports stop reflecting reality.
Every flexibility you ban comes back outside the system and invisibly. The choice isn't whether flexibility exists — it's whether it's measurable.
What works: bounded, logged overrides
- Item availability: branch's call (local supply reality).
- Price: free within the band defined by its tier, approval required outside it.
- Product name and imagery: locked by head office — this is the core of brand consistency.
- Local promotions: a branch can start one, head office can see and stop it.
- Every override is logged with who, when and on what grounds.
The rule that holds at 1,000-location scale
Once branch count reaches three digits, head office cannot review each override individually. At that point the approval flow has to become exception reporting: instead of approving everything, a screen that lists only what fell outside the band.
The human side
Even the best override policy meets resistance when nobody explains to the franchisee why it exists. Adding a half-day "what we lock and why" session to the rollout noticeably reduces the support load over the following six months.
