Lunchbox Menus are pulled into the Admin Dashboard through two types of Manual Menu Syncing: Initial Menu Syncs, and Subsequent Menu Syncs, both of which do not require Lunchbox support to execute.

This is the first time that Lunchbox pulls your menu into the Lunchbox Admin Dashboard. It is important to make sure that your menu items are set up properly before pulling this sync.

NOTE: Importing Multiple Menus is supported through the Toast and Lunchbox integration.

NOTE: The Toast Online orders: Checkboxes have no affect on Menus that are imported to Lunchbox. All menus import with or without this checkbox.

Name, Price, Calories, Description, Image URL & Location Availability, Modifier Ordering Priority, Menu Modifier Groups and Modifiers within those groups. *Priority will appear as it does from the Toast Ordering Screen, Modifier Required Min Max & Inventory/Item Qty (Only when this is enabled on the Admin Dashboard on the item level).

This setting must be manually set up in the admin dashboard by locating the modifier group and checking off the This option can be selected once per item check box.

Subsequent menu syncs are any Syncs placed after the initial onboarding phase. These include new and previously imported menus, modifiers and items. Please read the following list of settings included in each of these syncs.

The following is a list of menu-related rules that must be adhered to on the Toast Admin Dashboard before doing the initial menu sync. There are a few Rules when configuring the menu in order to make sure it communicates properly with Lunchbox. Make sure to read through all of these carefully before proceeding to edit or build your menu.

Supported Toast Pricing Structures - Base Price, Location-Specific Price

Unsupported Toast Pricing Structures - Menu Based, Open Price, Time Specific Price, Sequence Price, Size Price, Inherited Modifier Price, Overridden Location Based Price

NOTE: Menu Items should never be based on these pricing structures on the item level, on the restaurant group level, or through some sort of inherited functionality. These types of menu pricing are not yet supported and Lunchbox will assume the highest pricing when the item imports. Lunchbox will always pull the highest price on GUIDs. See screenshots below.

WE DO NOT SUPPORT MENU GROUP PRICING INHERITANCE

WE DO NOT SUPPORT MODIFIER PRICING INHERITANCE

Size Pricing Alternative - We recommend using a modifier group called size with modifiers named the corresponding size with a base price set per size modifier. Benefit this allows you to maintain the same GUID per size and ingredient type. Size pricing generates multiple GUIDs that are not replicated when used on a like ingredient modifier.

Modifier Specific Pricing Limitations - Adjusting prices through price inheriting (or on the outside layer of modifiers or via modifier groups) to keep item GUID’s the same for depletion purposes is not yet supported and Lunchbox will show an incorrect price during the ordering process.

Modifier Sequence Pricing Alternative - We recommend using two separate groups, free options in the first group, and limiting the amount that can be ordered in the group. Then create a second group with additional charges. The GUIDs will have to be separate for all of those options to support the pricing change.

Don’t have a nested modifier reference an item that contains the parent modifier. (it creates a circular reference) For example do not nest a side of fries with the same GUID (Nested/Parent Modifier) nested inside of a side of fries with the same GUID (Parent Modifier).

Don't do 2 layers deep of subgroups, which means that you don’t put a subgroup inside of a subgroup. If you do by default Lunchbox drops the parent subgroup and just flattens both into one.

Example:

→ Drinks

→ → Cold Drinks

→ → Hot Drinks

Becomes just:

→ Cold Drinks

→ Hot Drinks

Subgroups can be turned on as an item should you need to have them visible on the Lunchbox Ordering Screen (you can see this in Sticky's and Wings Over). A special request would need to be made through your CSM or Delivery Manager.

It is important that menu images be uploaded in the proper format. If images aren’t uploaded properly, it can cause resolution problems, scaling issues, and delayed image loading times. Please follow these guidelines carefully:

Menu Item Images

Size: 1280x720px; landscape (16:9) ratio
File: JPG recommended or PNG
160kb or smaller

Menu Modifier Images

Size: 100x100px; square (1:1) ratio
File: PNG
160kb or smaller

Menu Items should be owned and targeted to the parent restaurant group in order to ensure that all locations have visibility. The three restaurant groups listed below are examples of how to limit menu visibility:

NOTE: When you want to limit visibility on an item, the Owner needs to be set to the parent restaurant group and the target needs to be set to the subgroup, which should be added to the Parent Restaurant Group in the restaurant group section of Toast to ensure visibility.

Toast has two ways to copy Menu Groups, Items and Modifiers: Copy & Deep Copy.

Deep Copies are made when the Make Deep Copy Checkbox has been checked. This is most typically used for copying modifiers without nested modifiers inside of them to ensure the external & internal layer of the modifier are copied.

WARNING: This is not recommended for Menu Groups with Items Inside, Menu Items with Modifiers and nested modifiers, Modifier Groups With Modifiers with nested modifiers. Don’t use Deep Copy unless you intend to make a copy of every item and modifier nested below the group or item! Selecting Deep Copy will create a copy of the selected Menu Groups and any items, subgroups, modifier groups, and modifiers it contains. Any changes made to these copies will not impact the originals.

Always double-check where your targets are when copying menu items, modifiers.

When building your menu for simplified depletion and 86ing purposes it is important to try and maintain a small number of GUIDs on like items. (Example a modifier group containing a side portion of fries that is also sold as an item should have the guid across both the side item and the side item built as a modifier.)

NOTE: Exceptions include price changes and portion changes unless you are using an external party to interpret the information into your inventory system. These instances are required to have separate GUIDs and will have to be manually toggled off across multiple GUIDs.

NOTE: When nesting items as modifiers inside of modifier groups within an item, it is important that, any layers nested below that item built as a modifier not have any additional items as modifiers nested below them. Second layers of modifiers should be modifiers only.

(Example: I want to sell popular additions on an item. So I add a brownie item as a modifier. Any modifiers nested below the brownie cannot have items as modifiers they must be modifiers only.) The only way that Lunchbox can process a request like this is if all modifiers in the second popular additions group are modifiers not items as modifiers.

Item

>Modifier Group

>>Item As Modifier

>>>Modifier Group

>>>>Modifiers Only

Make sure your menu is finalized in Toast before pulling the initial sync following all of the aforementioned rules and you should be all set to go and ready to sync!

For a full detail on how to build out the Menu on Toast check out the Toast article below:

Intro to Menu Management

Menu Hierarchy

Creating Menus

Arranging Order of Menus

Archive/Delete Menus

Rename Menus

Creating Menu Groups

Creating Subgroups

Renaming Groups & Subgroups

Arranging Order of Groups & Subgroups

Delete Groups and Subgroups

Creating Menus, Groups, and Items in the Menu Builder

Before pulling a menu sync, remember to publish the menu to all locations and then request that Lunchbox pull a menu sync through the Support icon located on your Admin Dashboard. If you do not do this, it will cause the menu sync to fail and settings to not reflect properly on the Admin Dashboard.