Keeping menus consistent across multiple locations

With one location, the menu lives in one place and one person’s head. With two, it starts living in spreadsheets, group chats, and printouts taped near the pass. By the third, guests are noticing that the same dish has three prices, and nobody is quite sure which is right.

One source of truth, local exceptions

The pattern that works is a shared core menu managed centrally, with deliberate local differences layered on top: an item only one kitchen can make, a price adjusted for a different market, a location-specific special. The key word is deliberate. Differences should be decisions, not drift.

Change everything, everywhere, at once

When a price changes or an item retires, the update should reach every location and every guest-facing menu the moment it is saved. Every manual step in between is a place where one location falls out of date, and out-of-date menus surface at the worst moment: in front of a guest holding the wrong price.

Compare locations to learn, not to rank

Consistent menus make location data comparable. When the same item sells strongly at one site and barely moves at another, that gap is information: about presentation, about the neighborhood, about staff recommendations. Multi-location owners who read those gaps run experiments; the rest run on anecdotes.