This section provides information specific to using menu manager when your restaurant also uses the multi-location management module.
Full menu view has the following limitations when used by multi-location restaurants:
-
For single-location restaurants, when you select a menu entity in Full menu view, a side panel opens where you can configure the details of that menu entity. This side panel is not yet available for multi-location restaurants. Instead, selecting a menu entity in Full menu view opens the entity's classic details page.
This chapter provides instructions for editing menu entities using the side panel. It does not provide instructions for editing a menu entity using the classic details pages.
-
For menu items, Full menu view is currently limited to viewing, removing, and archiving items. You cannot add new or existing menu items or edit menu items in Full menu view.
-
The reordering feature in Full menu view that allows you to reorganize the order of your menus, menu groups, and menu items is not yet supported for multi-location restaurants.
-
The location filter setting is not retained when you move to Full menu view from any of the other views.
When a restaurant uses the multi-location management module, its menu entities can be versioned and those versions can be assigned to specific restaurant locations, or groups of locations. For example, a restaurant could have two versions of an Egg Sandwich menu item, one for a Boston location and another for a New York City location. Versioned entities share the majority of, but not all, of their data. For example, the Boston version of the Egg Sandwich has sausage, bacon, and cheese modifiers while the New York City version only has bacon and cheese modifiers.
This section describes some key points when working with versioned menu entities in the menu manager.
The menu manager can display both versioned and unversioned menu entities but they behave slightly differently:
-
If a menu entity is not versioned, you see a single row in the menu manager view for it.
-
If a menu entity is versioned, you see a row in the menu manager view for each version that is associated with a location you are currently viewing. For example, Menu Item A has three versions, one each for the Boston, Miami, and New York City locations. If you are viewing the Boston and Miami locations in the menu manager, you see two rows in the view for the Boston and Miami versions. The New York City version is not visible.
The illustration below shows a versioned menu item in Items view.
The illustration below shows the same versioned menu item in Full menu view
For more information, see Versions.
When you create a new menu entity for a multi-location restaurant, you define the locations or location groups that use that entity. This is the menu entity's target. You also define who can edit the menu entity. This is the menu entity's owner.
Newly created menus are automatically targeted at the highest location group or location you have the Edit Full Menu permission to. The owner defaults to this same location group or location.
For example, consider the following location group hierarchy:
-
Corporate
-
Northeast Franchises
-
Boston
-
New York City
-
-
If you have Edit Full Menu permissions to the Northeast Franchises location group, any new menu you create is targeted at the Northeast Franchises location group by default.
Newly created menu groups and menu items inherit the target and owner of their parent menu or menu group by default. For example, if you add a new menu item to a menu group that is targeted at the Northeast Franchises location group, that menu item is also targeted at the Northeast Franchises location group.
Toast Web prevents you from setting a target and owner that you don't have permissions to.
For more information, see Targets and Owners and permissions.