For restaurants with multiple locations, it's common for individual locations to offer menu items that other locations may not carry. Such items might be carried for a limited time only or maybe they get rotated in and out of a menu on a seasonal basis.
When this is the case, the corporate level of a franchise concept creates the entire "items database" for all locations, then gives store level managers the ability to add/remove those existing items to their location's menu. To utilize local menu editing, assign the employee (or job role) the Local Menu Edit permission.
- A user with the Local Menu Edit permission will be able to do the following to corporate level menu items or item modifiers:
- Change item price only if the item has Location Specific Pricing turned on
- Note: Location Specific Pricing can be turned on by a user with Full Edit Permissions
- A user with the Local Menu Edit permission will be able to do the following to local objects, including items in local menu groups and local modifier groups:
- Add or remove existing menu items and existing modifier options
- Change the name
- Change the price or pricing strategy
A user with Local Menu Edit permissions will view this Non-Alcoholic Beverages menu as shown below. The user will only have the option to add items that exist in the corporate level items' database:
A user with Full Menu Edit permissions will be able to add new items to the same Non-Alcoholic Beverages menu:
In some cases, the corporate level of a franchise concept controls pricing structure and which menu items can be added or removed from individual locations. In order to maintain synchronicity in one single above store reporting structure, it's important that menu items aren't created on an individual store level and are instead pulled from an existing database of items. This prevents local managers from creating menu items that could potentially inflate above store reporting data.