Adding a venue to a group
Opening a second restaurant under the same brand shouldn’t mean retyping the menu and re-uploading every dish photo.
The rule
The new venue inherits everything but owns its copy of everything. The library is a starting point, not a leash.
What comes across
The group holds the master version of everything that’s the same everywhere: menu definitions, prices as suggestions, recipes and their ingredients, modifiers, supplier identities, category structure, role definitions, and every dish photo.
Adding a venue walks that library and creates a private copy of each row for the new location.
Why “its own copy” matters
The copies are independent in both directions. The new venue can change a price, hide a dish, swap a photo or rename a modifier without touching the library or any sibling. And when a sibling changes its price, the new venue’s price doesn’t drift.
Photos work the same way — each venue holds its own copies. A better shot uploaded six months later stays local.
How it’s done
From the group’s page in the super-admin area, two buttons sit near the member list:
- Create new member venue — for a brand-new location. Give it a name, a URL slug, a currency and a timezone. On confirm, the whole library materialises into it.
- Lift existing venue — for a restaurant that already exists outside the group.
Materialisation takes a few seconds for a typical menu. When it finishes the venue is genuinely ready: the menu is there, the photos are there, and every link between item, recipe and ingredient is already wired.
Good to know
- Prices come across as suggestions. Setting local ones is expected, not an exception.
- Nothing about the source venue changes when you lift or copy from it.
Related features
- Running more than one location — what lives at group versus venue
- Who can see your group — who can do this
- Keeping your venues’ data separate — the boundary afterwards