Multi-location
One menu publishing system. Every location correct.
For restaurant groups, franchises and multi-unit teams using Toast. Keep central visibility without flattening every location into one menu.
Location switcher
Change the location. Watch the menu change.
Same group, four locations, four menus. Notice the burger price.
Now showing
Mission St.
- Charred corn ribs9.50
- Burrata & stone fruit14.00
- Crispy brussels10.75
- Smash burger16.25
- Green curry noodles18.50
- Half roast chicken23.00
season.
- Smash burger16.25double patty, house pickles
- Green curry noodles18.50tofu or chicken, thai basil
- Half roast chicken23.00salsa verde, potatoes
Locations by surface
Can Garnsh publish different menus by location?
Yes. Each row is a location with its own mapped menu. Each column is a surface it may or may not use.
| Location | Smash burger | Hosted page | Website embed | QR view | Board |
|---|---|---|---|---|---|
| Mission St.Full menu + brunch board | 16.25 | Published | Published | Published | Published |
| DogpatchCounter service, compact board | 15.75 | Published | Published | Published | Published |
| Terminal 2Grab-and-go, promo heavy | 18.00 | Published | Not used | Published | Published |
| Oakland Pop-upWeekends only, QR first | 16.25 | Published | Not used | Published | Not used |
What groups get
Central view. Local truth.
- 01
Central oversight
One view of what is published at every location, on every surface, and when it went live.
- 02
Location-specific context
Each location is mapped to its own menu in Toast. Prices and items stay local.
- 03
Per-location surfaces
Hosted page, embed, QR view and board belong to one location each. Use only what a site needs.
- 04
Preview per location
Check the airport and the flagship separately before a shared change goes public.
- 05
Publish and roll back
Publishing is deliberate. Each location can return to its previous published version.
- 06
No cross-location leaks
A surface tied to one location never shows another location’s menu or pricing.
Garnsh does not manage staff permissions inside Toast, change menus in Toast, or run ordering. Your Toast setup determines which menu context is available to connect.
FAQ
Straight answers.
Can Garnsh publish different menus by location?
Yes. Each location is mapped to its own menu context and has its own hosted page, QR view and board configuration.
How does Garnsh keep prices from leaking across locations?
Each surface is tied to one mapped location, and each location is previewed and published on its own.
Does Garnsh manage staff permissions in Toast?
No. Garnsh does not change anything inside Toast. Your Toast setup determines what menu context is available.
Keep reading
The right menu at the right location.
Walk through your location map with the Garnsh team.