This article covers the recommended best practices regarding how to set up your menu in Toast to maximize the ability to PMIX your data and analyze your numbers. There are various Toast features mentioned that you can use to help organize your menu, tackle edge use cases and connect the dots in MarginEdge for the most accurate reporting.
General
-
Do not use the same POS button if the menu item has different recipes. Either use modifiers to denote the differences or create separate buttons in the POS.
-
When making a new item for your menu, do not “rename” an old button for a menu item - we recommend creating a brand new button. Otherwise, the mappings will be incorrect and it could ruin historical PMIX data.
-
If you have the same menu across your locations, then we recommend you take advantage of Toast’s “multi-location management” that allows you to have the same menu across your locations. This also helps [me] see which menu items are the same across locations.
-
More information on Toast' Multi-location Management here:
Multi-Location Management | Toast POS
-
Size Pricing (ex: Pizzeria, Cafes)
-
We recommend using “Size Pricing” in Toast to denote the different sizes (instead of having the sizes be modifiers). Within MarginEdge we will break out your menu items by the sizes that are set within Toast. This ensures that we are able to see how much of that modifier was used (adding modifiers to a small vs. large).
Example:
-
Small, Medium, Large Cheese Pizza will become “Cheese Pizza - Small”, “Cheese Pizza - Medium”, “Cheese Pizza - Large”. Then, if “Pepperoni” is added as a modifier, we will be able to see if the Pepperoni modifier is for a small, medium, or large pizza.
-
Small, Medium, Large Drip Coffee will become “Drip Coffee - Small”, “Drip Coffee - Medium”, “Drip Coffee - Large”. Then if “Almond Milk” is added as a modifier, we will be able to see if the almond milk modifier is for a small, medium, or large coffee.
-
Pre-Modifiers
-
We do not recommend using Pre-Modifiers in Toast. Our integration does not support pulling in Pre-Modifiers and you will not be able to tell the difference between “Add Bacon” and “No Bacon” - it will just show up as “Bacon” in MarginEdge.
Pick 2/Combo Setup
-
If you have a combination deal where the customer picks two or more menu items to form one “meal deal” (like a “Pick 2”) then we recommend creating a menu group called “Pick 2” and adding your menu item options to that menu group.
-
We do not recommend creating a menu item called “Pick 2” and having the customer select modifiers that are the menu items (example: “Chicken Taco” as a modifier). This will cause the menu item (“Chicken Taco”) to come into MarginEdge as a modifier and then the actual modifiers (example: “Add Cheese”) will come in as submodifiers which makes PMIX mapping in MarginEdge complex.
Note: We can support this if needed, but we do not recommend it.
Cocktails
-
We recommend that the cocktail (1) be selected first and then the liquor (2) when setting up cocktail items in Toast. Selecting the liquor first can cause issues when mapping PMIX.
-
We recommend having “Single” and “Double” be setup as submodifiers for the Liquor modifiers in this scenario.
Example:- Menu Item is “Old Fashioned”, Modifier is “Basil Hayden Rye Bourbon”, Submodifier is “Double”