Keep branch menus controlled without hiding local differences
Quick answer
Define which menu details are shared and which remain branch-specific, then assign a local verifier before publishing. Wobistro supports separate restaurant tenants, staff permissions, menu management, domains, and location storefronts.
Step-by-step workflow
- Document the brand-wide naming, image, allergen, and modifier rules.
- Record branch-specific prices, hours, availability, taxes, and fulfillment constraints.
- Assign a local verifier and a central approver.
- Test each location URL and QR code after a menu or domain change.
Pre-launch checks
- Guests land on the intended branch, not a generic menu.
- Local prices and availability match the physical location.
- Ownership for urgent sold-out changes is explicit.
Frequently asked questions
Should every branch have identical menus?
Only shared brand elements should be identical; price, stock, hours, taxes, and fulfillment may require local control.
Who approves changes?
Use a named local verifier and central owner where brand governance requires both.
What should be tested per location?
The domain, menu URL, QR destination, ordering modes, hours, charges, and staff handoff.
Product scope and operator responsibility
Wobistro provides the digital controls referenced in this guide, subject to the active plan and configuration. The restaurant remains responsible for food safety, allergen disclosure, pricing, taxes, payments, staffing, availability, fulfillment, accessibility, and local compliance.