Introduction to Menu Item Definitions
Menu item definitions are a required part of a menu item. Without them, the menu item does not appear on workstation screens. Definitions are the behavioral hub of a menu item.
Definitions use menu level links to determine when a menu item is accessible to workstation operators. By activating specific menu levels, the menu item is available to workstation operators when the level is active.
Menu item definitions also tie price records and menu item classes to the menu item.
The following table shows an example of three different iterations of mac and cheese, all behaving differently, all costing different prices, but all are reporting as mac and cheese. This is possible because each menu item master record can have up to 64 individual menu item definitions. These definitions are all available and configured in the Menu Item Maintenance module, on the Definition tab.
Table 13-7 Defining Definitions
| Definition and Availability(Using Menu Levels) | Menu Item Class | Price |
|---|---|---|
|
Mac and Cheese – Lunch |
R – M&C Topping |
$8.00 |
|
Mac and Cheese – Dinner |
R – M&C Topping |
$10.99 |
|
Basic Mac and Cheese – Lunch and Dinner Side |
R – No Prep |
$3.99 |
If a menu item definition is not enabled on both the main or the sub level when those levels are active, the item does not appear on the workstation screens. As each menu item can have up to 64 definitions, making sure the correct levels are enabled in each definition is critical.
-
Single menu item master with multiple definitions
-
Multiple menu item masters, each with their own definition
-
Single menu item master with definitions only available on sizing levels
Single menu item master with multiple definitions
The menu item definition name appears on the workstation screen,
not its master record. For example, a restaurant serves the menu item
Tomato Soup. When a guest orders soup, they choose either a cup or
a bowl size. Both the menu item definitions Tomato Soup-Cup and Tomato Soup-Bowl appear on the workstation
screen as two separate items, each with a different price record.
The menu item Tomato Soup appears on reports as the
master record name.
Multiple menu item masters, each with their own definition
If the restaurant wants the cup and bowl to report separately,
they may configure a separate menu item master record for each—Tomato Soup-Cup and Tomato Soup-Bowl—with
a single definition and price for each master record.
Single menu item master with definitions only available on sizing levels
A single master record can also have multiple definitions. For example, a restaurant uses menu levels for sizing. Instead of Breakfast, Lunch, and Dinner menu levels, they have menu levels for Small, Medium, and Large. One definition is only available on the Small level, another is only available on Medium, and so on.
The menu item class specifies whether the item is a regular menu item (such as a burger or salad), or a condiment item (such as meat temperature or ketchup). This is how you can get a master record, like bowl of soup, to behave both as an entrée on its own and as a side dish. Each has its own menu item class associated with its own definition.
As for price records, each item definition can have up to eight price records, each controlled by either the main or sub menu level. For example, a beer bottle can have two prices: one regular price and one happy hour price. When the menu level changes from regular to happy hour, the price record that is active on that level also changes.
However, a location may not want two definitions (regular and happy hour), but instead may create a single definition with two prices. A price record is either active on the main or sub level, but not on both levels. By default, price records operate on the main level. If needed, you can open the Menu Item Classes module, click the Options tab, and change the price record to operate on the sub level for the item’s definition by selecting 10 - ON = Use Sub Level Pricing; OFF = Use Main Level Pricing.