Use the Menu Bulk Import Tool

Use this column to attach the entity created in this row to its parent.

• An identifier that specifies the parent entity for the entity being created in this row. For example, the identifier of a parent menu group to which the menu item created by this row will belong.
• The value of this field depends on whether the parent entity already exists or is being created in this same import spreadsheet.
• If the parent entity exists already, enter its Toast GUID in this field. For more information, see Specify Toast Identifiers.
• If the parent entity is being created in this same spreadsheet, enter the operation ID from the row where the entity is created. For example, the CREATE row for Menu Item X has an operation ID of 12. This row creates a modifier group that you want to attach to Menu Item X. Enter 12 in the Parent Version ID or operation ID field for this modifier group row.

The pricing strategy or method for the menu entity being created is case insensitive.

Acceptable values for the Pricing strategy or method column depend on the type of entity being created in the row.

• For menu items:
  • Menu items created with the basic template must use the BASE pricing strategy.
  • While not required, you should also consider supplying the base price in the Price field of the menu item's CREATE row.
• For modifier groups:
  • Modifier groups created with the basic template can use one of the following for the Pricing strategy or method:
  • BASE sets the pricing method for the modifier group to Additional charge - price set by the modifier group. The additional charge is a fixed price charge.
  • While not required, you should also consider supplying the fixed price charge in the Price field of the modifier group's CREATE row.
  • PRICED_BY_MODIFIERS sets the pricing method for the modifier group to Additional charge - price set on individual modifiers.
  • While not required, you should also consider supplying prices in the Price fields of the CREATE rows for the individual modifiers contained in the modifier group.

Note: You cannot create a modifier group with the bulk menu import tool that doesn't charge for its modifiers.

• For modifiers:
  • Modifiers created with the basic template must use the BASE pricing strategy.
  • While not required, you should also consider supplying the base price in the Price field of the modifier's CREATE row.
  • A modifier's pricing strategy and price are ignored if its parent modifier group uses the BASE pricing strategy, which corresponds to Additional charge - price set by modifier group.

A string representing the menu entity's price. This is the only optional column in the basic template.

• For menu items:
  • The Price column contains the base price for the menu item. (Menu items created using the basic template must use the BASE pricing strategy.)
• For modifier groups:
  • When the modifier group's Pricing strategy or method is set to BASE, the Price column contains the price that applies to all modifiers in the modifier group. (The BASE pricing method corresponds to the Additional charge - price set by modifier group setting in Toast Web.)
  • When the modifier group's Pricing strategy or method is set to PRICED_BY_MODIFIERS, you must leave the Price column empty. (The PRICED_BY_MODIFIERS pricing method corresponds to the Additional charge - price set on individual modifiers setting in Toast Web.)
• For modifiers:
  • When a modifier's parent modifier group uses the PRICED_BY_MODIFIERS pricing method, the Price column in the modifier's row specifies the individual base price of the modifier. (Modifiers created using the basic template must use base prices.)

Price strings must follow these rules:

• The string can use a minus sign, -1.00, or parentheses, (1.00), to indicate a reduction in price.
• Cents are optional. For example, both 10.00 and 10 are acceptable.
• Commas that separate thousands are optional. For example, both 1000 and 1,000 are acceptable.
• null is an acceptable value for the price.
• A price string cannot exceed 25 characters.
• A price string cannot include a currency symbol. For example, $100 is not acceptable.

Examples of valid price strings:

null
""
".12"
"1"
"10"
"100"
"100.00"
".1"
"100.0"
"100."
"-.1"
"(100.0)"

Examples of invalid price strings:

"$100"
"$a" 
"." 
"€1" 
"10.." 
"..100" 
"10.0." 
"abc" 
"100.0$0" 
"$10a.00"
"$"

A description of the menu item. Must follow these rules:

• Any characters are allowed.
• Maximum length is 1000 characters

Price strings must follow these rules:

• The string can use a minus sign, -1.00, or parentheses, (1.00), to indicate a reduction in price.
• Cents are optional. For example, both 10.00 and 10 are acceptable.
• Commas that separate thousands are optional. For example, both 1000 and 1,000 are acceptable.
• null is an acceptable value for the price.
• A price string cannot exceed 25 characters.
• A price string cannot include a currency symbol. For example, $100 is not acceptable.

Examples of valid price strings:

null
""
".12"
"1"
"10"
"100"
"100.00"
".1"
"100.0"
"100."
"-.1"
"(100.0)"

Examples of invalid price strings:

"$100"
"$a" 
"." 
"€1" 
"10.." 
"..100" 
"10.0." 
"abc" 
"100.0$0" 
"$10a.00"
"$"

The price look-up (PLU) code for the menu item. Must follow these rules:

• Any characters are allowed.
• Maximum length is 255 characters

The stock-keeping unit (SKU) code for the menu item. Must follow these rules:

• Any characters are allowed.
• Maximum length is 255 characters

The multilocation ID for the sales category that applies to this menu item.

If you update the sales category ID for a menu item that had previously been set to inherit its sales category from a parent menu group, the item is reconfigured so that it no longer inherits its sales category from that group. The menu item now has its own sales category.

Example of a sales category ID:

• 500000000032822323
• For more information, see Specify Toast identifiers.

The multilocation IDs for the prep stations to which this menu item should be sent when it is ordered. If you need to specify a single prep station, you can just provide the ID.

If you need to specify multiple prep stations, separate their multilocation IDs with commas and encapsulate the entire string in double quotes.

Example of a single prep station ID:

• 500000000032885671

Example of multiple prep stations IDs:

• "500000000032885671,500000000094945671"

For more information, see Specify Toast Identifiers.

Note: This feature is in limited release with select customers.

Specifies the guest count associated with the menu item. For example, a small pizza could have a guest count of 1, while a large pizza has a guest count of 2.

You can enter decimal values for Guest count, but the Toast platform rounds them to 2 decimal places.

    
The name of the menu entity. Must follow these rules:

• Any characters are allowed.
• Maximum length is 255 characters

Note: The import process does not prevent you from creating menu entities that use the same name as existing entities

Required for CREATE operations

Used for UPDATE operations

Empty for ATTACH operations

An identifier for the menu entity to be attached. The value of this field depends on whether the menu entity you want to attach already exists or is being created in this same import spreadsheet.

• If the menu entity exists already, enter its Toast GUID in this field.
• If the menu entity is being created in this same spreadsheet, enter the Operation ID from the row where the entity is created. For example, the CREATE row for Modifier Group A has an operation ID of 5. To attach Modifier Group A to another menu item, create an ATTACH row and enter 5 in the Version ID field.

For more information, see SpecifyToast Identifiers.

Required for ATTACH and UPDATE operations

Empty for CREATE operations

A unique ID for the import operation associated with this row in the import spreadsheet. Must follow these rules:

• Any characters are allowed.
• Maximum length is 255 characters
• No other rows in the import CSV file can have the same operation ID

Toast support recommends entering an operation ID of 1 for the first import operation in the spreadsheet and then incrementing by 1 for each additional operation, so that the operation ID of the second import operation is 2, the operation ID of the third import operation is 3, and so on.

For more information, see Understand the Operation ID.

The name of the menu entity as displayed on a Toast POS device. Must follow these rules:

• Any characters are allowed.
• Maximum length is 255 characters

Used for CREATE and UPDATE operations

Empty for ATTACH operations

The column can be omitted from the spreadsheet if empty for all rows

The name of the menu entity as displayed on kitchen tickets or on a kitchen display system device. Must follow these rules:

• Any characters are allowed.
• Maximum length is 255 characters

Used for CREATE and UPDATE operations

Empty for ATTACH operations

The column can be omitted from the spreadsheet if empty for all rows

Only used for menu items. Description of the menu item. Must follow these rules:

• Any characters are allowed.
• Maximum length is 1000 characters

Used for the CREATE operations where Entity type is MENU_ITEM and for UPDATE operations

Empty for all other operations

The column can be omitted from the spreadsheet if empty for all rows

A drop-down menu where you can choose the button color for the menu entity on a Toast POS device. For a diagram that shows the possible button colors, see Button colors.

If you generate your import spreadsheet programmatically, the Button color column can contain either a color's name or its hex value. Color names must be in all capitals and can be found in this article: Button Colors for the Menu Bulk Import Tool Advance Template.

Used for CREATE operations

Empty for UPDATE and ATTACH operations

The column can be omitted from the spreadsheet if empty for all rows

A drop-down menu where you can choose the pricing strategy or method for the menu entity being created. Values include:

• BASE
• LOCATION_SPECIFIC
• PRICED_BY_MODIFIERS

The value you choose for the Pricing strategy or method column depends on the type of entity you are creating.

• For menu items:
  • BASE sets the pricing strategy on the menu item to Base price. While not required, you should also consider supplying the base price in the Price field of the menu item's CREATE row.
• LOCATION_SPECIFIC sets the pricing strategy on the menu item to Location Specific Price.

If you pick this pricing strategy, you must also provide the location-specific price in the Price field of the menu item's CREATE row.

For modifier groups:

• BASE sets the pricing method for the modifier group to Additional charge - price set by the modifier group. The additional charge is a fixed price charge.
• While not required, you should also consider supplying the fixed price charge in the Price field of the modifier group's CREATE row.
• PRICED_BY_MODIFIERS sets the pricing method for the modifier group to Additional charge - price set on individual modifiers.

While not required, you should also consider supplying prices in the Price fields of the CREATE rows for the individual modifiers contained in the modifier group.

Required for CREATE operations

Empty for UPDATE and ATTACH operations

Optional: A string representing the menu entity's price. 

For menu items:

• The Price column contains the price for the menu item. The menu item may use either the BASE pricing strategy or the LOCATION_SPECIFIC pricing strategy, and the Price column will contain either a base price or a location-specific price, respectively.
• If the menu item uses a location-specific price, the Location-specific price target ID column identifies the location the price applies to.

For modifier groups:

• When the modifier group's Pricing strategy or method is set to BASE, the Price column contains the price that applies to all modifiers in the modifier group. (The BASE pricing method corresponds to the Additional charge - price set by the modifier group setting in Toast Web.)
• When the modifier group's Pricing strategy or method is set to PRICED_BY_MODIFIERS, you must leave the Price column empty. (The PRICED_BY_MODIFIERS pricing method corresponds to the Additional charge - price set on individual modifiers setting in Toast Web.)

For modifiers:

• When a modifier's parent modifier group uses the PRICED_BY_MODIFIERS pricing method, the Price column in the modifier's row specifies the individual price of the modifier. The modifier may use either the BASE pricing strategy or the LOCATION_SPECIFIC pricing strategy, and the Price column will contain either a base price or a location-specific price, respectively.
• If the modifier uses a location-specific price, the Location-specific price target ID column identifies the location the price applies to.

Price strings must follow these rules:

• The string can use a minus sign, -1.00, or parentheses, (1.00), to indicate a reduction in price.
• Cents are optional. For example, both 10.00 and 10 are acceptable.
• Commas that separate thousands are optional. For example, both 1000 and 1,000 are acceptable.
• null is an acceptable value for the price.
• A price string cannot exceed 25 characters.
• A price string cannot include a currency symbol. For example, $100 is not acceptable.

Examples of valid price strings:

null
""
".12"
"1"
"10"
"100"
"100.00"
".1"
"100.0"
"100."
"-.1"
"(100.0)"

Examples of invalid price strings:

"$100"
"$a" 
"." 
"€1" 
"10.." 
"..100" 
"10.0." 
"abc" 
"100.0$0" 
"$10a.00"
"$"

Used for:

CREATE operations where the entity type is MENU_ITEM.

CREATE operations where:

• The Entity type is MODIFIER_GROUP
• The modifier group's Pricing strategy or method is set to BASE, to indicate that it is using the Additional charge - price set by modifier group pricing method.

CREATE operations where:

• The Entity type is MODIFIER
• The Pricing strategy or method for the modifier's parent modifier group is set to PRICED_BY_MODIFIERS, to indicate that the modifier's parent group is using the Additional charge price set on the individual modifiers' pricing method.
• UPDATE operations where the menu item's Pricing strategy or method is set to BASE.

Empty for ATTACH operations

The Toast GUID of the target location group or location that the location-specific price applies to. Used when the row creates a new menu item or modifier and the Pricing strategy or method is set to LOCATION_SPECIFIC. Note that the target for the location-specific price must be the same as or an ancestor of the target assigned to the menu item or modifier itself. The target for the menu item or modifier is defined in the Target ID field.

Must be empty for all other operations.

For more information, see Specify Toast Identifiers.

Used for CREATE operations where the Entity type is MENU_ITEM or MODIFIER and Pricing strategy is LOCATION_SPECIFIC

Empty for all other operations

The column can be omitted from the spreadsheet if empty for all rows

    
The price look-up (PLU) code for the menu item or modifier option. Must follow these rules:

• Any characters are allowed.
• Maximum length is 255 characters

Used for CREATE operations where Entity type is MENU_ITEM or MODIFIER and the Pricing strategy is LOCATION_SPECIFIC

Empty for all other operations

Column can be omitted from spreadsheet if empty for all rows

The stock-keeping unit (SKU) code for the menu item or modifier option. Must follow these rules:

• Any characters are allowed.
• Maximum length is 255 characters

Used for CREATE operations where Entity type is MENU_ITEM or MODIFIER, and for UPDATE operations

Empty for all other operations

Column can be omitted from spreadsheet if empty for all rows

The multilocation IDs for the tax rates that apply to this menu item or modifier. If you specify a single tax rate, you can just provide the ID.

If you need to specify multiple tax rates, separate their multilocation IDs with commas and encapsulate the entire string in double quotes.

If you don't provide a tax rate ID when you create a menu item or modifier, the menu item or modifier inherits the tax rates assigned to its parent menu entity.

Example of a single tax rate ID:

500000000139746504

Example of multiple tax rates IDs:

"500000000139746504,500000000959646504"
For more information, see Specify Toast Identifiers.

Used for CREATE operations where Entity type is MENU_ITEM or MODIFIER, and for UPDATE operations

Empty for all other operations

Column can be omitted from spreadsheet if empty for all rows

The multilocation ID for the sales category that applies to this menu item or modifier.

If you don't provide a sales category ID when you create a menu item or modifier, the menu item or modifier inherits the sales category assigned to its parent menu entity.

Example of a sales category ID:

500000000032822323
For more information, see Specify Toast Identifiers.

Used for CREATE operations where Entity type is MENU_ITEM or MODIFIER

Empty for all other operations

Column can be omitted from spreadsheet if empty for all rows

    
The Toast GUID of the target location group or location for the menu entity.

Note that the target must be:

• In the same management group as the restaurant for which data is being imported.
• The same as the owner, or a child of the owner, in the restaurant group hierarchy.

For more information, see Specify Toast Identifiers.

Used for CREATE operations

Empty for UPDATE and ATTACH operations

Column can be omitted from spreadsheet if empty for all rows

The Toast GUID of the owner location group or location for the menu entity.

Note that the owner must be:

• In the same management group as the restaurant for which data is being imported.
• The same as the target, or a parent of the target, in the restaurant group hierarchy.

For more information, see Specify Toast Identifiers.

Used for CREATE operations

Empty for UPDATE and ATTACH operations

Column can be omitted from spreadsheet if empty for all rows

A drop-down menu where you can choose whether the menu entity is visible on Toast POS devices. Values include:

• TRUE
• FALSE
• Defaults to TRUE.

If you set either the Visible to Kiosk, Toast Order and Pay field or the Visible to Toast Online Ordering, Toast Takeout App field to TRUE, you must also set this field to TRUE.

Used for CREATE operations

Empty for UPDATE and ATTACH operations

Column can be omitted from spreadsheet if empty for all rows

A drop-down menu where you can choose whether the menu entity is visible on Toast Kiosk devices or in the Toast Order and Pay app. Values include:

• TRUE
• FALSE
• Defaults to TRUE.

Note:

• For all menu entity types, if you set this field to TRUE, you must also set the Visible to POS field to TRUE.
• For modifier groups only, the setting for the Visible to Kiosk, Toast Order and Pay field must match the setting in the Visible to Toast Online Ordering, Toast Takeout App field.

Used for CREATE operations

Empty for UPDATE and ATTACH operations

Column can be omitted from spreadsheet if empty for all rows

A drop-down menu where you can choose whether the menu entity is visible in the Toast Online Ordering website and the Toast Takeout (Local by Toast) app. Values include:

• TRUE
• FALSE
• Defaults to TRUE.

Note:

• For all menu entity types, if you set this field to TRUE, you must also set the Visible to POS field to TRUE.
• For modifier groups only, the setting for the Visible to Kiosk, Toast Order and Pay field must match the setting in the Visible to Toast Online Ordering, Toast Takeout App field.

Used for CREATE operations

Empty for UPDATE and ATTACH operations

Column can be omitted from spreadsheet if empty for all rows

A drop-down menu where you can choose whether the menu entity is visible on online ordering sites that integrate with the Toast platform using the orders API. Values include:

• TRUE
• FALSE
• Defaults to TRUE.

Used for CREATE operations

Empty for UPDATE and ATTACH operations

Column can be omitted from spreadsheet if empty for all rows

If the menu item the row is specifying will be used as a modifier option's item reference, you can override the item reference's name with a name that is used for the modifier option only. Must follow these rules:

• Any characters are allowed.
• Maximum length is 255 characters

For more information, see Create modifiers with the advanced template.

where Entity type is MODIFIER and you want to override the item reference name

Empty for all other operations

Column can be omitted from spreadsheet if empty for all rows

If the menu item the row is specifying will be used as a modifier option's item reference, you can override the item reference's target location group GUID with one that is used for the modifier option only. For more information, see Creating modifiers with the advanced template.

For more information, see Specify Toast Identifiers.

Used for CREATE operations where Entity type is MODIFIER and you want to override the item reference target

Empty for all other operations

Column can be omitted from spreadsheet if empty for all rows

If the menu item the row is specifying will be used as a modifier option's item reference, you can override the item reference's owner location group GUID with one that is used for the modifier option only. For more information, see the advanced template in this article.

For more information, see Specify Toast identifiers.

Used for CREATE operations where Entity type is MODIFIER and you want to override the item reference owner

Empty for all other operations

Column can be omitted from spreadsheet if empty for all rows

For rows that create a modifier, this field allows you to specify that the modifier is a default modifier. Set this field to TRUE if the modifier should be a default modifier. If the modifier should not be a default modifier, you can either leave the field blank or set it to FALSE.

Note: When using the bulk import spreadsheet, you are limited to specifying one modifier as the default modifier in any given modifier group. If you need to specify more than one modifier as a default modifier for a modifier group, you must do so on the modifier group's details page in Toast Web.

Used for CREATE operations where Entity type is MODIFIER and you want the modifier to be a default modifier

Empty for all other operations

Use this column to attach the entity created or modified in this row to its parent.

A drop-down menu where you can choose the type of menu entity that will be the parent for the entity created in this row of the import file. Values include:

• MENU_GROUP
• MENU_ITEM
• MODIFIER_GROUP

Required for all operations

• For specifying a menu group parent, use MENU_GROUP
• For specifying a menu item parent, use MENU_ITEM
• For specifying a modifier group parent, use MODIFIER_GROUP

Use this column to attach the entity created or modified in this row to its parent.

An identifier that specifies the parent menu entity for the entity being created or attached in this row. The value of this field depends on whether the parent menu entity you want to attach to already exists or is being created in this same import spreadsheet.

• If the parent menu entity exists already, enter its Toast GUID in this field.
• If the parent menu entity is being created in this same spreadsheet, enter the operation ID from the row where the entity is created. For example, the CREATE row for Menu Item X has an operation ID of 12. This row creates a modifier group that you want to attach to Menu Item X. Enter 12 in the Parent Version ID or operation ID field for this modifier group row.

For more information, see Specify Toast identifier.

Defines whether the menu item contains alcohol or not.

When creating a new menu item, this column can contain the values YES or NO, or it can be empty to indicate that the Contains alcohol configuration is not specified for the menu item.

When updating an existing menu item, this column must contain either YES or NO. It cannot be empty when updating an existing menu item.

For more information, see Menu item and modifier alcohol labeling in this article.

Used for CREATE operations where Entity type is MENU_ITEM and for UPDATE operations

• Empty for all other operations
• Column can be omitted from spreadsheet if empty for all rows

Note: This feature is in limited release with select customers. Specifies the guest count associated with the menu item. For example, a small pizza could have a guest count of 1 while a large pizza has a guest count of 2.

You can enter decimal values for Guest count but the Toast platform rounds any decimal values to two places.

Used for CREATE operations where Entity type is MENU_ITEM and for UPDATE operations

• Empty for all other operations
• Column can be omitted from spreadsheet if empty for all rows