{ "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://raw.githubusercontent.com/api-evangelist/toast-tab/refs/heads/main/json-schema/menus-modifier-option-schema.json", "title": "ModifierOption", "description": "Information about a modifier option configured for this restaurant.\n", "type": "object", "properties": { "referenceId": { "description": "An integer identifier that is used to refer to this modifier option by modifier option groups that contain it.\n", "type": "integer", "example": 1 }, "name": { "description": "A descriptive name for this modifier option, for example, \"Cheese\" or \"Pepperoni\".\n \nTo avoid menu ingestion failures, if the `name` value for a modifier option is an empty string or `null`, the menus API updates it to the string `Missing name` in the returned menus data. A modifier option has a blank name if both its item reference name and its modifier override name are missing.\n\nNote that, while this solution allows menu ingestion to proceed without failure, it does allow a modifier option with the name `Missing name` to appear in a restaurant\u2019s menu, creating potential confusion for guests and employees. Also, the menus API only updates the returned data. It does not update the modifier option in the Toast database, meaning the name will still be blank when looking at the modifier option in Toast Web.\n\nTo fix the issue in Toast Web, the restaurant must identify the parent menu entity for the modifier option, view its details page in Toast Web, and then locate and fix the modifier option with the blank name.\n\nFor a detailed description of a modifier option's item reference, see Understanding a modifier option\u2019s item reference in the Toast Platform Guide.\n", "type": "string", "example": "Example Name" }, "kitchenName": { "description": "The name of the modifier option as it appears on kitchen tickets. The `kitchenName` can include both numbers and letters. This value contains an empty string if a kitchen name has not been configured for the modifier option.\n", "type": "string", "example": "Example Name" }, "guid": { "description": "A unique identifier for this modifier option's item reference, assigned by the Toast POS system. For a detailed description of a modifier option's item reference, see Understanding a modifier option\u2019s item reference in the Toast Platform Guide.\n", "type": "string", "example": "5a401af8-d2e2-4090-8c45-9f87b8b6c4d1" }, "multiLocationId": { "$ref": "#/$defs/MultiLocationId" }, "masterId": { "$ref": "#/$defs/MasterId" }, "description": { "description": "An optional short description of this modifier option.\n", "type": "string", "example": "string" }, "posName": { "$ref": "#/$defs/PosName" }, "posButtonColorLight": { "$ref": "#/$defs/PosButtonColorLight" }, "posButtonColorDark": { "$ref": "#/$defs/PosButtonColorDark" }, "prepStations": { "type": "array", "description": "An array of GUIDs for the prep stations that have been assigned to this modifier option.\n\nIf a modifier option's item reference has prep stations assigned to it, then the modifier option uses those prep stations. If the modifier option's item reference *does not* have prep stations assigned to it, then the modifier option inherits the prep stations of the menu group, menu item, or modifier (in the case of nested modifiers) it is modifying.\n\nThe array is empty if no prep stations have been assigned to the modifier option.
\n
\n*Related topics:*
\nRouting to prep stations\nUnderstanding a modifier option\u2019s item reference\n", "items": { "type": "string" } }, "image": { "$ref": "#/$defs/Image" }, "visibility": { "$ref": "#/$defs/Visibility" }, "price": { "type": "number", "format": "double", "description": "The price of this modifier option.\n\nIn Toast Web, a modifier option may:\n * Inherit its price from a parent modifier group.\n * Use the price specified for its modifier option item reference.\n * Specify a price that overrides the price defined for its item reference.\n\nThe `price` value is populated differently depending on which of these pricing scenarios is used for the modifier option. The sections below describe how the `price` value is populated in these different scenarios.\n\n_Note:_ To determine how a modifier option has been priced, you can inspect the modifier option's `pricingStrategy` value. If it is GROUP_PRICE, then the modifier option is inheriting its price from a parent modifier group. If it is any value other than GROUP_PRICE (for example, MENU_SPECIFIC_PRICE or TIME_SPECIFIC PRICE), then the modifier option is using either the price specified for its item reference or an override price (override prices always use the BASE_PRICE strategy).\n\n_Modifier Option Inherits Its Price from a Parent Modifier Group_\n\nIf the modifier option inherits its price from a parent modifier group and that group uses the:\n * Fixed Price pricing strategy, then the modifier option's `price` value is populated with the fixed price specified for the parent modifier group. No additional calculations are required.\n * Size Price, Sequence Price, or Size/Sequence pricing strategy, then the modifier option's `price` value is null. You must use the _parent modifier group's_ `pricingStrategy` and `pricingRules` values to calculate the modifier option's price.\n\n_Modifier Option Specifies an Override Price_\n\nIf the modifier option specifies an override price, the `price` value is set to that override price. No additional calculations are required.\n\n_Modifier Option Uses the Price from Its Item Reference_\n\nIf a modifier option uses the price from its underlying item reference, then the `price` value is populated using the same logic as the `price` value for a `MenuItem` object:\n * For base prices, the `price` value is populated with the specified base price.\n * For menu-specific prices, the `price` value is resolved based on the current menu. For example, consider a modifier option that is included in both Lunch and Dinner menus and is priced at $1 for the Lunch menu and $2 for the Dinner menu. In the fully resolved JSON returned by the menus API, this modifier option would appear twice, once as a child of the Lunch menu with a `price` value of $1, and again as a child of the Dinner menu with a `price` value of $2.\n\n If this same modifier option is added to a Breakfast menu but a menu-specific price is not defined for the Breakfast menu, then the `price` value for the instance of the modifier option that appears in the Breakfast menu JSON is populated with the base price from the menu-specific price configuration. Menu-specific price configurations include a base price that functions as a default price when a menu-specific price cannot be resolved.\n \n * For location-specific prices, the `price` value is resolved based on the current location. For example, consider a modifier option that costs $2 in the Boston location and $3 in the New York location. When you retrieve menu data for the Boston location, this modifier option's `price` value is $2. When you retrieve menu data for the New York location, the modifier option's `price` value is $3.\n * For time-specific prices, the `price` value is populated with the base price that is specified as part of the time-specific price configuration. This base price functions as a default price for the modifier option during times of the day when a time-specific price has not been defined. For example, consider a modifier option that costs $1 from noon to 2pm and $2 during the rest of the day. The `price` value for this item would be $2. You must use _this modifier option's_ `pricingStrategy` and `pricingRules` values to calculate the price of the modifier option during time periods for which a time-specific price has been defined.\n * For size prices, the `price` value is null. You must use _this modifier option's_ `pricingStrategy` and `pricingRules` values to calculate the price of the modifier option for different sizes.\n * For open prices, the `price` value is null.\n\nIf the modifier option is priced using a price level, the `price` value reflects the pricing strategy used for the price level, using the same logic described above. For example, consider a price level that applies a size price to the modifier option it is assigned to. In this case, the `price` value for the modifier option is null and you must use this modifier option's `pricingStrategy` and `pricingRules` values to calculate the price of the modifier option for different sizes.\n_Note:_ For detailed information on modifier option pricing and pricing strategies, see the Menu pricing section in the Toast Platform Guide.\n", "x-nullable": true, "example": 1.0 }, "pricingStrategy": { "type": "string", "description": "A string that indicates how this modifier option has been priced. If `pricingStrategy` is:\n * GROUP_PRICE, then the modifier option inherits its price from a parent modifier group.\n * Any value other than GROUP_PRICE (for example, MENU_SPECIFIC_PRICE or TIME_SPECIFIC PRICE), then the modifier option is using either the price specified for its item reference or an override price (override prices always use the BASE_PRICE strategy).\n\nIf the modifier option is using the price of its underlying item reference, and that item reference is priced using the Location Specific Price pricing strategy, then the `pricingStrategy` value indicates which pricing strategy is used at the current location. For example, consider a modifier option that uses a menu-specific price at the Boston location and a base price at the New York location. When you retrieve the menu data for the Boston location, the `pricingStrategy` for the modifier option is MENU_SPECIFIC_PRICE. When you retrieve menu data for the New York location, the `pricingStrategy` for the modifier option is BASE_PRICE.\n\nIf the modifier option is using the price of its underlying item reference, and that item reference is priced using a price level, then the `pricingStrategy` value indicates which pricing strategy is used for that price level. For example, if the \"Special Toppings\" price level uses a time-specific price, then the `pricingStrategy` value for a modifier option that is assigned the \"Special Toppings\" price level is TIME_SPECIFIC_PRICE.\n\nIt is important to understand which `pricingRules` object to use when modifier option prices must be calculated. If the `pricingStrategy` value is:\n * BASE_PRICE or MENU_SPECIFIC_PRICE, then you can retrieve the modifier option's price from its `price` value. No additional calculations are required.\n * GROUP_PRICE, then you must use the `pricingStrategy` and `pricingRules` values from _the modifier option's parent modifier group_ to calculate the modifier option's price.\n * TIME_SPECIFIC_PRICE or SIZE_PRICE, then you must use the rules provided in _this modifier option's_ `pricingRules` value to calculate the price for the modifier option.\n", "example": "string" }, "pricingRules": { "type": "object", "description": "A `PricingRules` object with information about how to calculate the price for this modifier option. You use a modifier option's `pricingRules` object, in conjunction with its `pricingStrategy` value, to calculate a price for the modifier option when the modifier option is _individually priced_ and its `price` value is null.\n\n_Note:_ If the modifier option is priced at the group level, you must use the `pricingRules` object of its parent modifier group to calculate its price. A modifier option is priced at the group level if its `pricingStrategy` value is GROUP_PRICE.\n\nThe `pricingRules` object takes different forms depending on the pricing strategy configured for the modifier option. Use the `pricingStrategy` value to determine which pricing strategy has been used so that you can properly interpret the data in the `pricingRules` object. For the BASE_PRICE, and MENU_SPECIFIC_PRICE pricing strategies, the `pricingRules` object is null because you can retrieve the price from the `price` value without additional calculation. For the OPEN_PRICE pricing strategy, the `pricingRules` object is also null (the price of a modifier option whose item reference uses the Open Price pricing strategy is specified at the time that the modifier option is ordered). For the TIME_SPECIFIC_PRICE and SIZE_PRICE pricing strategies, the `pricingRules` object contains additional values that you use to calculate the modifier option's price.\n", "items": { "$ref": "#/$defs/PricingRules" }, "x-nullable": true }, "salesCategory": { "$ref": "#/$defs/SalesCategory" }, "taxInfo": { "type": "array", "description": "The `taxInfo` value on the `ModifierOption` object has been deprecated. An upcoming release will introduce new configuration settings for the taxes on a modifier option. The `taxInfo` value will not accurately represent these additional configurations. Your integration should switch to using the `modifierOptionTaxInfo` value instead. See Using taxInfo and modifierOptionTaxInfo to calculate taxes for menu items and modifier options in the Toast Developer Guide for more information. \n", "items": { "type": "string" } }, "modifierOptionTaxInfo": { "$ref": "#/$defs/ModifierOptionTaxInfo" }, "itemTags": { "type": "array", "description": "An array of `ItemTag` objects that are assigned to this modifier option. Item tags are used to assign identifying characteristics to a modifier option, for example, vegetarian, gluten-free, alcohol.\n", "items": { "$ref": "#/$defs/ItemTag" } }, "plu": { "type": "string", "description": "The price lookup (PLU) code for this modifier option. The PLU code can contain both numbers and letters. This value contains an empty string if a PLU code has not been defined.\n", "example": "string" }, "sku": { "type": "string", "description": "The stock keeping unit (SKU) identifier for this modifier option. The SKU identifier can contain both numbers and letters. This value contains an empty string if a SKU has not been defined.\n", "example": "string" }, "calories": { "type": "integer", "description": "The number of calories in this modifier option. The calories value can be any positive or negative integer, or zero. This value is null if a calories amount has not been configured for the modifier option.\n", "x-nullable": true, "example": 1 }, "contentAdvisories": { "$ref": "#/$defs/ContentAdvisories" }, "unitOfMeasure": { "type": "string", "enum": [ "NONE", "LB", "OZ", "KG", "G", "GAL", "L", "ML", "FL_OZ", "M", "CM", "FT", "IN", "YD" ], "description": "The unit of measure used to determine the price of the modifier option. For example, $10.00 per gram.\n\nThe default is `NONE`, which means that the item is not meant to be measured during a sale.\n\nValues are:\n* `NONE` - The item is not meant to be measured.\n* `LB` - Weighed in pounds.\n* `OZ` - Weighed in ounces.\n* `KG` - Weighed in kilograms.\n* `G` - Weighed in grams.\n* `GAL` - Measured in gallons.\n* `L` - Measured in liters.\n* `ML` - Measured in milliliters.\n* `FL_OZ` - Measured in fluid ounces.\n* `M` - Measured in meters.\n* `CM` - Measured in centimeters.\n* `FT` - Measured in feet.\n* `IN` - Measured in inches.\n* `YD` - Measured in yards.\n", "example": "NONE" }, "isDefault": { "type": "boolean", "description": "Indicates whether this modifier option is included on the menu item by default.\n\n_Important:_ If a menu item is configured to use default modifiers and you submit an order to the orders API for that menu item but you omit those default modifiers, then the Toast POS system assumes you want to omit the default modifiers and they will not be included in the order. For example, consider a Burger menu item that has Lettuce and Tomato as default modifiers. If you submit an order to the orders API for the Burger menu item but omit the Lettuce and Tomato default modifiers in the request, the order ticket will include the Burger but not the Lettuce and Tomato modifier options.\n", "example": true }, "allowsDuplicates": { "type": "boolean", "description": "Indicates whether the modifier option may be added to a menu item multiple times.\n\nIf a modifier option belongs to a modifier group whose `isMultiSelect` value is FALSE, then the Toast POS system sets the modifier option\u2019s `allowsDuplicates` value to FALSE to prevent more than one modifier option being selected for the group.\n", "example": true }, "portions": { "type": "array", "description": "An array of `Portion` objects that define the portions that this modifier option can be added to. For example, for a pizza menu item, you could define 1st Half and 2nd Half portions and this modifier option could be added to either portion. See Portions overview in the Toast Platform Guide for more information.\n", "minItems": 0, "items": { "$ref": "#/$defs/Portion" } }, "prepTime": { "type": "integer", "description": "The amount of time, in seconds, that it takes to prepare this modifier option. This value is null if a prep time has not been specified for the modifier option.
\n
\n*Related topics*
\nUsing prep times to automate item firing
\n", "format": "int32", "x-nullable": true, "example": 1 }, "modifierGroupReferences": { "type": "array", "description": "An array of `referenceId`s for `ModifierGroup` objects. These objects define nested modifier groups contained in this modifier option. For example, you can have an entree that has a Sides modifier group that contains a Salad modifier option. The Salad modifier option has its own modifier group, Salad Dressing, that includes Ranch, Vinaigrette, and Blue Cheese modifier options. Salad Dressing is a nested modifier group and the individual salad dressings are nested modifier options.\n", "minItems": 0, "items": { "type": "integer" } }, "length": { "$ref": "#/$defs/Length" }, "height": { "$ref": "#/$defs/Height" }, "width": { "$ref": "#/$defs/Width" }, "dimensionUnitOfMeasure": { "$ref": "#/$defs/DimensionUnitOfMeasure" }, "weight": { "$ref": "#/$defs/Weight" }, "weightUnitOfMeasure": { "$ref": "#/$defs/WeightUnitOfMeasure" }, "images": { "$ref": "#/$defs/Images" }, "guestCount": { "$ref": "#/$defs/GuestCount" }, "sortOrder": { "type": "integer", "description": "A number determining the order in which this modifier option should appear on kitchen tickets. The sort order value can be any positive or negative integer, or zero. This value is null if a sort order has not been configured for the modifier option.\n", "x-nullable": true, "example": 1 }, "allergens": { "type": "array", "description": "Reserved for future functionality. Not currently supported for external integrations.\n", "minItems": 0, "items": { "$ref": "#/$defs/AllergenItem" }, "x-nullable": true } }, "$defs": { "MultiLocationId": { "type": "string", "description": "An identifier that is used to identify and consolidate menu entities that are versions of each other.\n\n`multiLocationId` replaces `masterId`. `multiLocationId` and `masterId` always have the same value.\n\nMenu entities can be versioned. Those versions can be assigned to specific restaurant locations, or groups of locations, in a management group. For example, you could have two versions of a burger, one for a Boston location and another for a New York City location. Versioned menu entities share the majority of, but not all of, their data. For example, the Boston version is called the Minuteman Burger and has pickles, while the New York City version is called the Empire Burger and does not.\n\nYou use the `multiLocationId` to identify menu entities that are versions of each other. To continue the example above, the Minuteman Burger in the JSON returned for the Boston location has the same `multilocationId` as the Empire Burger in the JSON returned for the New York City location. These matching `multlocationId` values indicate that the two items are related versions of the same item. In Toast reports, this allows a restaurant to track sales of the burger across both locations.\n\nThe Toast POS system ensures that once a `multilocationId` value is assigned to a set of versions within a management group, that `multiLocationId` is not used for any other version sets in the same management group. It does not guarantee, however, that the `multiLocationId` is not used by another management group to identify a set of versions within it.\n\nSee Toast identifiers in the Toast Developer Guide for more information on the `multiLocationId` and its relationship to other Toast identifiers.\n\nSee Enterprise module overview in the Toast Platform Guide for more information on the enterprise module and versioning.\n" }, "MasterId": { "type": "integer", "format": "int64", "description": "This value is deprecated. Instead of `masterId`, use `multiLocationId`.\n\nAn identifier that is used to identify and consolidate menu entities that are versions of each other.\n" }, "PosName": { "type": "string", "description": "The button label name that appears for this menu entity in the Toast POS app. `posName` contains an empty string if a `posName` has not been defined for the menu entity and the `name` value is used for the button label instead.\n" }, "PosButtonColorLight": { "type": "string", "description": "The color of the menu entity's button on the Toast POS app, when the app is running in light mode.\n \nWhen an employee configures a POS button's color, they select a color pairing that consists of two colors, one for light mode and one for dark mode. `posButtonColorLight` contains the HEX code for the light mode color.\n\n`posButtonColorLight` defaults to `#f7f7f7`, the HEX code when the `WHITE` color pairing is chosen.\n\nThe following list shows the possible HEX codes for `posButtonColorLight`, with the associated color pairing in parentheses.\n\n* #f7f7f7 (WHITE)\n* #ffe6e9 (TERRACOTTA_1)\n* #efa49f (TERRACOTTA_2)\n* #f07166 (TERRACOTTA_3)\n* #e45a4e (TERRACOTTA_4)\n* #fbd9b6 (ORANGE_1)\n* #f7be6e (ORANGE_2)\n* #f98c1f (ORANGE_3)\n* #e56f1a (ORANGE_4) \n* #fbf5b6 (YELLOW_1)\n* #fed850 (YELLOW_2)\n* #e9b10c (YELLOW_3)\n* #c78605 (YELLOW_4) \n* #e8f7d4 (GRASS_1)\n* #afe26c (GRASS_2)\n* #71b314 (GRASS_3)\n* #32a206 (GRASS_4) \n* #e3f0fb (SKY_1)\n* #9fc5f0 (SKY_2)\n* #77a5e4 (SKY_3)\n* #558edd (SKY_4) \n* #f1e3fd (LAVENDER_1)\n* #dab2f7 (LAVENDER_2)\n* #b26ee2 (LAVENDER_3)\n* #a270db (LAVENDER_4) \n* #d0d0d0 (GRAY_1)\n* #c3c3c3 (GRAY_2)\n* #b1b1b1 (GRAY_3)\n* #989898 (GRAY_4)\n" }, "PosButtonColorDark": { "type": "string", "description": "The color of the menu entity's button on the Toast POS app, when the app is running in dark mode.\n \nWhen an employee configures a POS button's color, they select a color pairing that consists of two colors, one for light mode and one for dark mode. `posButtonColorDark` contains the HEX code for the dark mode color.\n\n`posButtonColorDark` defaults to `#1a1c23`, the HEX code when the `WHITE` color pairing is chosen.\n\nThe following list shows the possible HEX codes for `posButtonColorDark`, with the associated color pairing in parentheses.\n\n* #1a1c23 (WHITE)\n* #7e635d (TERRACOTTA_1)\n* #74504D (TERRACOTTA_2)\n* #722e25 (TERRACOTTA_3)\n* #561408 (TERRACOTTA_4)\n* #8f5f3d (ORANGE_1)\n* #7e4116 (ORANGE_2)\n* #803500 (ORANGE_3)\n* #682d03 (ORANGE_4) \n* #7e6b44 (YELLOW_1)\n* #7b5f27 (YELLOW_2)\n* #7c5000 (YELLOW_3)\n* #633d09 (YELLOW_4) \n* #657552 (GRASS_1)\n* #556e34 (GRASS_2)\n* #37570a (GRASS_3)\n* #113a00 (GRASS_4) \n* #637486 (SKY_1)\n* #4d6074 (SKY_2)\n* #2a456b (SKY_3)\n* #213554 (SKY_4) \n* #78668a (LAVENDER_1)\n* #5e4776 (LAVENDER_2)\n* #402960 (LAVENDER_3)\n* #25174f (LAVENDER_4) \n* #6c6c6c (GRAY_1)\n* #5f5f5f (GRAY_2)\n* #474747 (GRAY_3)\n* #404040 (GRAY_4)\n" }, "Image": { "type": "string", "description": "The URL to an image that has been uploaded for this menu entity. This value is null if no image has been specified.\n", "x-nullable": true }, "Visibility": { "type": "array", "description": "An array of strings that indicate where this menu entity is visible:\n\n* POS: The menu entity is visible in the Toast POS app. \n\n* KIOSK: The menu entity is visible on a Toast kiosk. \n\n* TOAST_ONLINE_ORDERING: The menu entity is visible in the Toast online\n ordering site for this restaurant. \n\n* ORDERING_PARTNERS: The restaurants wants this menu entity to be visible\n on online ordering sites that integrate with the Toast POS system using the orders API. \n\n* GRUBHUB: Deprecated. The menu entity is included during a menu sync to\n Grubhub and will be visible on the Grubhub online ordering service after a\n menu sync has completed. _Note:_ Conceptually, the _Grubhub_ configuration\n option that was associated with the `GRUBHUB` string in this array has\n been replaced by the more general _Online orders: Ordering partners_\n configuration option and restaurants that used the _Grubhub_ option have\n been automatically migrated to the new _Online orders: Ordering partners_\n option. This means that any menu entity that had the _Grubhub_ option set\n to _Yes_ will now have the _Online orders: Ordering partners_ option\n enabled and the `ORDERING_PARTNERS` enum will be present in the\n `visibility` array for it. To support backwards compatibility, the\n `visibility` array for these entities will also continue to contain the\n `GRUBHUB` enum for a short period of time. See Menu\n Visibility Enhancements (Rolled Out) for more information.\n\nThe `visibility` array is empty if the menu entity is not configured to be visible for any of the use cases listed above.\n", "items": { "type": "string", "enum": [ "POS", "KIOSK", "GRUBHUB", "TOAST_ONLINE_ORDERING", "ORDERING_PARTNERS" ] } }, "PricingRules": { "type": "object", "description": "The PricingRules object is a multi-use object that provides pricing rules for:\n * A menu item or modifier option item reference that uses the Time Specific Price or Size Price pricing strategy.\n * A modifier group that uses the Size Price, Sequence Price, or Size/Sequence Price pricing strategy.\n", "properties": { "timeSpecificPricingRules": { "description": "An array of `TimeSpecificPrice` objects that define the time-specific prices for a menu item or modifier option item reference that uses the Time Specific Price pricing strategy. If the menu item or modifier option item reference does not use time-specific prices, this array is empty.\n", "type": "array", "items": { "$ref": "#/$defs/TimeSpecificPrice" } }, "sizeSpecificPricingGuid": { "description": "The GUID of a Size modifier group that defines sizes and prices for a menu item or a modifier option item reference that uses the Size Price pricing strategy.\n\nIf the menu item or modifier option item reference does not use the Size Price pricing strategy, then `sizeSpecificPricingGuid` is null.\n\nThe Toast POS system automatically creates a Size modifier group when you choose the Size Price pricing strategy for a menu item or modifier option item reference and stores the sizes and prices you specify in it. You use the `sizeSpecificPricingGuid` value to locate the correct Size modifier group to use when pricing a menu item or modifier option item reference that uses size pricing. In the JSON fragment below, you can see that the Cheese Pizza menu item uses the SIZE_PRICE pricing strategy and the Size modifier group where the sizes and prices for Cheese Pizza are defined has a GUID that ends in `31b0`.\n\n```\n{\n \"restaurantGuid\": \"2071fb81-988b-4d75-b8dc-c5c17cff9706\",\n ...\n \"menus\": [\n {\n \"name\": \"Dinner\",\n \"guid\": \"ddd681de-3c12-4d45-b8b1-a5b2ea898210\",\n ...\n \"menuGroups\": [\n {\n \"name\": \"Pizza\",\n \"guid\": \"dc868006-919a-4950-a4cc-3a03f9770fd7\",\n ...\n \"menuItems\": [\n {\n \"name\": \"Cheese Pizza\",\n \"guid\": \"95c5d500-8d92-46f2-bec4-fb2a42a46621\",\n ...\n \"price\": null,\n \"pricingStrategy\": \"SIZE_PRICE\",\n \"pricingRules\": {\n \"timeSpecificPricingRules\": [],\n \"sizeSpecificPricingGuid\": \"23c02762-9d6a-4d3f-a298-71c989bf31b0\",\n \"sizeSequencePricingRules\": []\n },\n ...\n \"modifierGroupReferences\": [\n 2,\n 6,\n ...\n ],\n ...\n }\n ]\n }\n ]\n }\n ],\n \"modifierGroupReferences\": {\n ...\n \"2\": {\n \"referenceId\": 2,\n \"name\": \"Size\",\n \"guid\": \"23c02762-9d6a-4d3f-a298-71c989bf31b0\",\n ...\n \"pricingStrategy\": \"NONE\",\n \"pricingRules\": null,\n ...\n \"modifierOptionReferences\": [\n 12,\n 13\n ],\n ...\n },\n ...\n },\n \"modifierOptionReferences\": {\n ...\n \"12\": {\n \"referenceId\": 12,\n \"name\": \"Small\",\n \"guid\": \"352244f2-a952-4a3a-a3ae-7775fa221ce7\",\n ...\n \"price\": 8.0,\n \"pricingStrategy\": \"BASE_PRICE\",\n \"pricingRules\": null,\n ...\n \"modifierGroupReferences\": []\n },\n \"13\": {\n \"referenceId\": 13,\n \"name\": \"Large\",\n \"guid\": \"4ff89bca-b448-4892-bc4c-62c37a28ac44\",\n ...\n \"price\": 10.0,\n \"pricingStrategy\": \"BASE_PRICE\",\n \"pricingRules\": null,\n ...\n \"modifierGroupReferences\": []\n }\n ...\n }\n}\n```\n\n\nWhen the `PricingRules` object appears in the context of a modifier\ngroup, the `sizeSpecificPricingGuid` value it contains is also used to\nfind matching sizes between menu items and any modifier options that\nuse the Size Price or Size/Sequence Pricing pricing strategies (for\nexample, toppings on a small pizza cost $1 while toppings on a large\npizza cost $2). In this scenario, the Toast POS system locates the\nmodifier option size that matches the menu item size and uses the\nprice defined for that size of the modifier option. The sizes for the\nmenu item are defined in the Size modifier group specified by the\n`sizeSpecificPricingGuid` value. The sizes for the modifier options\nare defined in objects contained in the `sizeSequencePricingRules`\narray that is contained in the modifier group's `PricingRules` object.\nSizes are considered matching when their names are identical. For\ndetailed information on the **Size Price** and **Size/Sequence Price**\npricing strategies, see [Pricing\nStrategies](https://doc.toasttab.com/doc/platformguide/adminPricingStrategies.html)\nin the _Toast Platform Guide_.\n\nIn the example below, the Cheese Pizza menu item and the Toppings\nmodifier group use the `SIZE_PRICE` pricing strategy. The menu item\nsizes and prices are defined in the Size modifier group with a GUID\nending in `31b0`. The sizes and prices for the modifier options are\ndefined in the `sizeSequencePricingRules` value that is a child of the\nToppings modifier group.\n\n```\n{\n \"restaurantGuid\": \"2071fb81-988b-4d75-b8dc-c5c17cff9706\",\n ...\n \"menus\": [\n {\n \"name\": \"Dinner\",\n \"guid\": \"ddd681de-3c12-4d45-b8b1-a5b2ea898210\",\n ...\n \"menuGroups\": [\n {\n \"name\": \"Pizza\",\n \"guid\": \"dc868006-919a-4950-a4cc-3a03f9770fd7\",\n ...\n \"menuItems\": [\n {\n \"name\": \"Cheese Pizza\",\n \"guid\": \"95c5d500-8d92-46f2-bec4-fb2a42a46621\",\n ...\n \"price\": null,\n \"pricingStrategy\": \"SIZE_PRICE\",\n \"pricingRules\": {\n \"timeSpecificPricingRules\": [],\n \"sizeSpecificPricingGuid\": \"23c02762-9d6a-4d3f-a298-71c989bf31b0\",\n \"sizeSequencePricingRules\": []\n },\n ...\n \"modifierGroupReferences\": [\n 2,\n 3,\n ...\n ],\n ...\n }\n ]\n }\n ]\n }\n ],\n \"modifierGroupReferences\": {\n ...\n \"2\": {\n \"referenceId\": 2,\n \"name\": \"Size\",\n \"guid\": \"23c02762-9d6a-4d3f-a298-71c989bf31b0\",\n ...\n \"pricingStrategy\": \"NONE\",\n \"pricingRules\": null,\n ...\n \"modifierOptionReferences\": [\n 12,\n 13\n ],\n ...\n },\n \"3\": {\n \"referenceId\": 3,\n \"name\": \"Toppings\",\n \"guid\": \"58b79986-f88f-411d-ba18-14b1e2441e9d\",\n ...\n \"pricingStrategy\": \"SIZE_PRICE\",\n \"pricingRules\": {\n \"timeSpecificPricingRules\": [],\n \"sizeSpecificPricingGuid\": \"23c02762-9d6a-4d3f-a298-71c989bf31b0\",\n \"sizeSequencePricingRules\": [\n {\n \"sizeName\": \"Small\",\n \"sizeGuid\": \"352244f2-a952-4a3a-a3ae-7775fa221ce7\",\n \"sequencePrices\": [\n {\n \"sequence\": 1,\n \"price\": 2.0\n }\n ]\n },\n {\n \"sizeName\": \"Large\",\n \"sizeGuid\": \"4ff89bca-b448-4892-bc4c-62c37a28ac44\",\n \"sequencePrices\": [\n {\n \"sequence\": 1,\n \"price\": 4.0\n }\n ]\n }\n ]\n },\n ...\n \"modifierOptionReferences\": [\n 10,\n 11\n ],\n ...\n },\n ...\n },\n \"modifierOptionReferences\": {\n ...\n \"10\": {\n \"referenceId\": 10,\n \"name\": \"Mushrooms\",\n \"guid\": \"fa24fee9-76c4-40ba-ae3c-7dfccafdd8d3\",\n ...\n \"price\": null,\n \"pricingStrategy\": \"GROUP_PRICE\",\n \"pricingRules\": null,\n ...\n \"modifierGroupReferences\": []\n },\n \"11\": {\n \"referenceId\": 11,\n \"name\": \"Onions\",\n \"guid\": \"afee6be7-8280-4c69-a170-9fdf4c76bf7b\",\n ...\n \"price\": null,\n \"pricingStrategy\": \"GROUP_PRICE\",\n \"pricingRules\": null,\n ...\n \"modifierGroupReferences\": []\n },\n \"12\": {\n \"referenceId\": 12,\n \"name\": \"Small\",\n \"guid\": \"352244f2-a952-4a3a-a3ae-7775fa221ce7\",\n ...\n \"price\": 8.0,\n \"pricingStrategy\": \"BASE_PRICE\",\n \"pricingRules\": null,\n ...\n \"modifierGroupReferences\": []\n },\n \"13\": {\n \"referenceId\": 13,\n \"name\": \"Large\",\n \"guid\": \"4ff89bca-b448-4892-bc4c-62c37a28ac44\",\n ...\n \"price\": 10.0,\n \"pricingStrategy\": \"BASE_PRICE\",\n \"pricingRules\": null,\n ...\n \"modifierGroupReferences\": []\n },\n ...\n }\n} \n``` \n", "type": "string", "x-nullable": true, "example": "5a401af8-d2e2-4090-8c45-9f87b8b6c4d1" }, "sizeSequencePricingRules": { "type": "array", "description": "An array of `SizeSequencePricingRule` objects that define the prices for the modifier options in a modifier group that uses the Size Price, Sequence Price, or Size/Sequence Pricing pricing strategy. If the modifier group does not use one of these pricing strategies, this array is empty.\n", "items": { "$ref": "#/$defs/SizeSequencePricingRule" } } } }, "TimeSpecificPrice": { "type": "object", "description": "Represents the pricing rules for a menu item that uses a time-specific price.\n", "properties": { "timeSpecificPrice": { "type": "number", "format": "double", "description": "The price of the menu item during the periods of time defined by the associated `schedule` array.\n", "example": 1.0 }, "basePrice": { "type": "number", "format": "double", "description": "The base price of the menu item, used for time periods when a time-specific price has not been defined.\n", "example": 1.0 }, "schedule": { "type": "array", "description": "An array of `Schedule` objects that indicate the specific days and times that a time-specific price is available.\n", "items": { "$ref": "#/$defs/Schedule" } } } }, "Schedule": { "type": "object", "description": "A multi-use object that is used to:\n\n* Define when a menu is available.\n* Define when a time-specific price is available for a menu item or modifier option.\n\nA `Schedule` object defines a set of days of the week and a set of time ranges for those days. Days that have identical time ranges are grouped into a single `Schedule` object, for example, MONDAY, TUESDAY, WEDNESDAY, THURSDAY, and FRIDAY in the example below have identical time ranges and are in the same `Schedule` object while SATURDAY and SUNDAY are in a separate `Schedule` object because their time ranges differ from the weekday time ranges.\n\n```\n\"availability\": {\n \"alwaysAvailable\": false,\n \"schedule\": [\n {\n \"days\": [\n \"MONDAY\", \n \"TUESDAY\", \n \"WEDNESDAY\", \n \"THURSDAY\"\n ],\n \"timeRanges\": [\n {\n \"start\": \"09:00\",\n \"end\": \"18:00\"\n }\n ]\n },\n {\n \"days\": [\n \"FRIDAY\", \n \"SATURDAY\"\n ],\n \"timeRanges\": [\n {\n \"start\": \"09:00\",\n \"end\": \"18:00\"\n },\n {\n \"start\": \"20:00\",\n \"end\": \"23:00\"\n }\n ]\n }\n ]\n}\n```\n\nTime ranges are in 24-hour HH:MM format.\n\nIf a day is not represented in the `Schedule` objects, the menu or time-specific price is not available on that day. \n", "properties": { "days": { "type": "array", "description": "An array of days of the week that are associated with identical time ranges. The time ranges are defined in a corresponding `timeRanges` value. Names of the days are in upper case, for example, MONDAY.\n", "items": { "type": "string", "description": "A day of the week, for example, SUNDAY or THURSDAY.", "enum": [ "SUNDAY", "MONDAY", "TUESDAY", "WEDNESDAY", "THURSDAY", "FRIDAY", "SATURDAY" ] } }, "timeRanges": { "type": "array", "description": "An array of `TimeRange` objects that define the time ranges that a menu or a time-specific price is available on the days defined by the corresponding `days` value. A `TimeRange` object contains a `start` time and an `end` time, expressed in the restaurant\u2019s local time. If both the `start` and `end` times for a given day are 00:00, it indicates that the menu or the time-specific price is available 24 hours on the associated days. Time ranges may also run overnight, for example, a time range that starts at \"07:00\" and ends at \"03:00\" runs from 7am until 3am the next day. \n", "items": { "$ref": "#/$defs/TimeRange" } } } }, "TimeRange": { "type": "object", "description": "Represents a time range for when a menu or a time-specific price is available.\n", "properties": { "start": { "type": "string", "description": "The start time of the time range. Expressed in the restaurant\u2019s local time.\n", "example": "string" }, "end": { "type": "string", "description": "The end time of the time range. Expressed in the restaurant\u2019s local time.\n", "example": "string" } } }, "SizeSequencePricingRule": { "type": "object", "description": "A multi-use object that defines the pricing rules for modifier options that belong to a modifier group that uses the Size Price, Sequence Price, or Size/Sequence Price pricing strategy. The contents of this object depend on the pricing strategy that is in effect.\n", "properties": { "sizeName": { "type": "string", "description": "A string that represents the size of a modifier option in this modifier group, for example, Small, Medium, or Large.\n\nWith Size Price and the Size/Sequence Price pricing strategies, the price of a modifier option changes based on the size of the menu item it is applied to, for example, a topping costs $1 on a small pizza and $2 on a large pizza. To determine which size and size-based price to use for a modifier option, the Toast POS system matches the size name of the modifier option to the size name of the menu item. For example, the Small size of a modifier option would match the Small size of a menu item. The `sizeName` value of the `SizeSequencePricingRule` object represents the modifier option size while the `sizeGuid` value represents the matching menu item size.\n\nThe Toast POS system does allow a configuration where the size of the modifier option is specified independently from the size of the menu item it applies to. In this scenario, you could order a Large menu item and apply a Small size of the modifier option to it. This configuration is unusual but the menus API supports it. When this configuration is in use, the `sizeName` value is populated with the modifier option size but the `sizeGuid` value that represents the menu item size will be null because there is no matching menu item size.\n\nThe `sizeName` value is null if the modifier group uses the Sequence Price pricing strategy because this strategy does not use sizes.\n\nSee the Pricing strategies section in the Toast Platform Guide for information on the Size Price, Sequence Price, and Size/Sequence Price pricing strategies.\n", "x-nullable": true, "example": "Example Name" }, "sizeGuid": { "type": "string", "description": "The GUID of the modifier option where a menu item size has been defined that matches the `sizeName` value. For example, if a menu item has Small and Large sizes, those sizes are represented in a Size modifier group with a Small modifier option and a Large modifier option. It is the GUID of one of those size modifier options that appears in this value. If the `sizeName` value is Small, then the `sizeGuid` value would contain the Small modifier option\u2019s GUID.\n\nWith Size Price and the Size/Sequence Price pricing strategies, the price of a modifier option changes based on the size of the menu item it is applied to, for example, a topping costs $1 on a small pizza and $2 on a large pizza. To determine which size and size-based price to use for a modifier option, the Toast POS system matches the size name of the modifier option to the size name of the menu item. For example, the Small size of a modifier option would match the Small size of a menu item. The `sizeName` value represents the modifier option size while the `sizeGuid` value represents the matching menu item size.\n\nThe Toast POS system does allow a configuration where the size of the modifier option is specified independently from the size of the menu item it applies to. In this scenario, you could order a Large menu item and apply a Small size of the modifier option to it. This configuration is unusual but the menus API supports it. When this configuration is in use, the `sizeName` value is populated with the modifier option size but there is no corresponding `sizeGuid` for the menu item size.\n\nThe `sizeGuid` value is null if the modifier group uses the Sequence Price pricing strategy because this strategy does not use sizes.\n\nSee the Pricing strategies section in the Toast Platform Guide for information on the Size Price, Sequence Price, and Size/Sequence Price pricing strategies.\n", "x-nullable": true, "example": "5a401af8-d2e2-4090-8c45-9f87b8b6c4d1" }, "sequencePrices": { "type": "array", "description": "An array of `SequencePrices` objects that define the size, sequence, or size/sequence prices for the modifier options in this modifier group.\n\nBecause they are multi use objects, the `SequencePrices` objects always contain `sequence` and `price` values for all three pricing strategies. However, the `sequence` is always 1 for the Size Price pricing strategy because only one price is defined per size for that strategy. For example, the `sequencePrices` value for a modifier group priced using the Size Price pricing strategy looks similar to the following:\n```\n\"sizeSequencePricingRules\": [\n {\n \"sizeName\": \"Small\",\n \"sizeGuid\": \"e02d1a57-5f9f-4800-a8c3-a5fe1a0b029b\",\n \"sequencePrices\": [\n {\n \"sequence\": 1,\n \"price\": 2\n }\n ]\n },\n {\n \"sizeName\": \"Large\",\n \"sizeGuid\": \"0e206b2d-72ab-46d1-b273-a5425cbef9a5\",\n \"sequencePrices\": [\n {\n \"sequence\": 1,\n \"price\": 4\n }\n ]\n }\n ]\n``` \n\nThe modifier options in this group cost $2.00 for the Small size and $4.00 for the Large size.\n\nThe `sequencePrices` value for a modifier group priced using the Sequence Price pricing strategy looks like this:\n```\n\"sizeSequencePricingRules\": [\n {\n \"sizeName\": null,\n \"sizeGuid\": null,\n \"sequencePrices\": [\n {\n \"sequence\": 1,\n \"price\": 1\n },\n {\n \"sequence\": 2,\n \"price\": 2\n },\n {\n \"sequence\": 3,\n \"price\": 2.5\n }\n ]\n }\n ]\n```\n\nThe first modifier option in this group costs $1.00, the second modifier option costs $2.00, and any additional modifier options from this group costs $2.50.\n\nThe `sequencePrices` value for a modifier group using the Size/Sequence Price pricing strategy looks like this:\n```\n\"sizeSequencePricingRules\": [\n {\n \"sizeName\": \"Small\",\n \"sizeGuid\": \"e02d1a57-5f9f-4800-a8c3-a5fe1a0b029b\",\n \"sequencePrices\": [\n {\n \"sequence\": 1,\n \"price\": 1\n },\n {\n \"sequence\": 2,\n \"price\": 2\n }\n ]\n },\n {\n \"sizeName\": \"Large\",\n \"sizeGuid\": \"0e206b2d-72ab-46d1-b273-a5425cbef9a5\",\n \"sequencePrices\": [\n {\n \"sequence\": 1,\n \"price\": 3\n },\n {\n \"sequence\": 2,\n \"price\": 4\n }\n ]\n }\n ]\n```\n\nThe first modifier option on a Small menu item costs $1.00 and additional modifier options on a Small cost $2.00, while the first modifier option on a Large menu item costs $3.00 and additional modifier options on a Large cost $4.00.\n", "items": { "$ref": "#/$defs/SequencePrice" } } } }, "SequencePrice": { "type": "object", "description": "Defines the size, sequence, or size/sequence prices for modifier options contained in a modifier group that uses the Size Price, Sequence Price, or Size/Sequence Price pricing strategy.\n", "properties": { "sequence": { "type": "integer", "format": "int32", "description": "Specifies the order of the prices.\n\nFor modifier groups that use the Size Price pricing strategy, the `sequence` is always 1 because only one price is defined per size for that strategy.\n\nFor modifier groups that use the Sequence Price or Size/Sequence Price pricing strategy, this value starts at 1 and increases with each successive price in the sequence. For example, in the JSON snippet below, `\"sequence\":1` defines the first price in the sequence and `\"sequence\":2` defines the second price in the sequence.\n```\n\"sequencePrices\": [\n {\n \"sequence\": 1,\n \"price\": 3\n },\n {\n \"sequence\": 2,\n \"price\": 4\n }\n ]\n```\n", "example": 1 }, "price": { "type": "number", "format": "double", "description": "The price for a modifier option when it is ordered at the specified point in the sequence.\n", "example": 1.0 } } }, "SalesCategory": { "type": "object", "description": "A descriptive category, for example, \"Food\" or \"Liquor\" that, when applied to the menu items and modifier options in your menu, allow you to view sales data by category. Null if no sales category has been defined.\n", "properties": { "name": { "description": "A descriptive name for this sales category, for example, \"Food\" or \"Liquor\".\n", "type": "string", "example": "Example Name" }, "guid": { "description": "A unique identifier for this sales category, assigned by the Toast POS system.\n", "type": "string", "example": "5a401af8-d2e2-4090-8c45-9f87b8b6c4d1" } } }, "ModifierOptionTaxInfo": { "type": "object", "description": "Information about the tax rates and tax behavior of this modifier option.\n\n_Note:_ The `modifierOptionTaxInfo` value always reflects the parent menu item tax rate, unless Toast grants the restaurant the ability to override modifier tax rates. If this permission is not granted, then even if the restaurant configured the modifier with a different tax rate, `modifierOptionTaxInfo` reflects the parent menu item tax rate.\n\nNote that there are other tax-related features that can impact the tax of a modifier option, such as tax inclusion and smart tax, that are not returned in this `ModifierOptionTaxInfo` object. For more information, see Tax on modifiers and Tax functionality interaction.\n\n_Important:_ The `ModifierOptionTaxInfo` object is intended to help you display prices but the `/prices` endpoint of the orders API is the only supported way to determine the prices of orders that you submit to the orders API. See Order prices in the Toast Developer Guide for more information.\n", "properties": { "taxRateGuids": { "type": "array", "description": "An array of GUIDs for the tax rates that apply to this modifier option.\n\nThe `taxRateGuids` value includes different tax rate GUIDs, depending on whether the modifier option is configured in Toast Web to use its own tax rates or to inherit tax rates from a menu item it has been applied to. See Using taxInfo and modifierOptionTaxInfo to calculate taxes for menu items and modifier options in the Toast Developer Guide for more information.\n \nTo retrieve full configuration data for a tax rate, use the `/taxRates/{guid}` endpoint in the configuration API.\n", "items": { "type": "string" } }, "overrideItemTaxRates": { "description": "Indicates whether the tax rates configured for this modifier option override the tax rates configured for a menu item that this modifier option has been applied to. For example, if the menu item is configured for a 6.25% tax rate and the modifier option is configured for a 2.75% tax rate, when that modifier option is applied to the menu item, both are taxed at the 2.75% tax rate.\n\nNote that the menu item's tax rate is overridden only if the modifier option is added to the menu item on a Toast POS device. The modifier option may be available to apply to the menu item, but if it is not actually added to the menu item on a Toast POS device, then the menu item's tax rate is not overridden. See Using taxInfo and modifierOptionTaxInfo to calculate taxes for menu items and modifier options in the Toast Developer Guide for more information.\n", "type": "boolean", "example": true } } }, "ItemTag": { "type": "object", "description": "A descriptive term that identifies a characteristic of a menu item or menu group, for example, vegetarian, gluten-free, or alcohol.\n", "properties": { "name": { "description": "A descriptive name for this item tag, for example, \"Vegetarian\" or \"Alcohol\".\n", "type": "string", "example": "Example Name" }, "guid": { "description": "A unique identifier for this item tag category, assigned by the Toast POS system.\n", "type": "string", "example": "5a401af8-d2e2-4090-8c45-9f87b8b6c4d1" } } }, "ContentAdvisories": { "type": "object", "description": "Information about the contents of this menu item or modifier, for example, whether it contains alcohol.\n", "properties": { "alcohol": { "$ref": "#/$defs/Alcohol" } } }, "Alcohol": { "type": "object", "description": "Information about whether this menu item or modifier contains alcohol and may require, \nor benefit from, additional handling. For example, a delivery partner may need \nto identify a menu item or modifier as containing alcohol to ensure that delivery drivers\nrequest identification before giving it to a customer.\n", "properties": { "containsAlcohol": { "type": "string", "description": "A string that indicates whether the menu item or modifier contains alcohol. Possible values \ninclude:\n\n* `YES`: The menu item or modifier contains alcohol.\n* `NO`: The menu item or modifier does not contain alcohol.\n \nThe `containsAlcohol` value may also be `null`. A `null` value indicates that the corresponding UI option in Toast Web has not been configured for this menu item or modifier.\n", "enum": [ "YES", "NO" ], "example": "YES" } } }, "Portion": { "type": "object", "description": "A container for the modifier groups that can be applied to a portion of a menu item.\n", "properties": { "name": { "description": "A descriptive name for this portion, for example, \"1st Half\" or \"2nd Half\".\n", "type": "string", "example": "Example Name" }, "guid": { "description": "A unique identifier for this portion, assigned by the Toast POS system.\n", "type": "string", "example": "5a401af8-d2e2-4090-8c45-9f87b8b6c4d1" }, "modifierGroupReferences": { "type": "array", "description": "An array of `referenceId`s for `ModifierGroup` objects. These objects define the modifier groups that can be applied to this portion.\n", "minItems": 0, "items": { "type": "integer" } }, "priceScaleFactor": { "type": "number", "format": "double", "description": "A multiplier that adjusts the cost of modifiers in this portion.\n", "x-nullable": true, "example": 1.0 } } }, "Length": { "type": "number", "description": "The length of the item or modifier. Use the `dimensionUnitOfMeasure` value to determine the unit of measurement.\n\nThe `length` value is `null` if no length is specified for the item or modifier.\n\nYou can use the `length`, `height`, and `width` values to determine the overall size of the item or modifier. This information is useful, for example, when determining shipping costs or choosing the size of delivery vehicle to use.\n", "format": "float", "x-nullable": true }, "Height": { "type": "number", "description": "The height of the item or modifier. Use the `dimensionUnitOfMeasure` value to determine the unit of measurement.\n\nThe `height` value is `null` if no height is specified for the item or modifier.\n\nYou can use the `length`, `height`, and `width` values to determine the overall size of the item or modifier. This information is useful, for example, when determining shipping costs or choosing the size of delivery vehicle to use.\n", "format": "float", "x-nullable": true }, "Width": { "type": "number", "description": "The width of the item or modifier. Use the `dimensionUnitOfMeasure` value to determine the unit of measurement.\n\nThe `width` value is `null` if no width is specified for the item or modifier.\n\nYou can use the `length`, `height`, and `width` values to determine the overall size of the item or modifier. This information is useful, for example, when determining shipping costs or choosing the size of delivery vehicle to use.\n", "format": "float", "x-nullable": true }, "DimensionUnitOfMeasure": { "type": "string", "enum": [ "IN", "CM", "FT", "M", "MM", "YD" ], "description": "The unit of measure assigned to the `length`, `height`, and `width` values.\n \nPossible values include:\n \n* IN: Inches\n* CM: Centimeters\n* FT: Feet\n* M: Meters\n* MM: Millimeters\n* YD: Yards\n \n`dimensionUnitOfMeasure` is `null` if no unit of measurement has been specified.\n", "x-nullable": true }, "Weight": { "type": "number", "description": "The weight of the item or modifier. Use the `weightUnitOfMeasure` value to determine the unit of measurement.\n\nTh `weight` value is `null` if no weight is specified for the item or modifier.\n \nYou can use the `weight` value when determining shipping costs or choosing a delivery vehicle to use.\n", "format": "float", "x-nullable": true }, "WeightUnitOfMeasure": { "type": "string", "enum": [ "NONE", "LB", "OZ", "KG", "G" ], "description": "The unit of measure assigned to the `weight` value.\n \nPossible values include:\n \n* NONE: No unit of measurement is assigned. `weightUnitOfMeasure` can also be `null`. `NONE` and `null` are equivalent. \n* LB: Pounds\n* OZ: Ounces\n* KG: Kilograms\n* G: Grams\n", "x-nullable": true }, "Images": { "type": "array", "description": "An array of strings that contain URLs for images that have been uploaded for this item or modifier. The array is empty if no images have been uploaded.\n \n_Note:_ The `images` array contains multiple URLs for multiple images for the same item or modifier. The older `image` value contains a single URL for a single image.\n", "items": { "type": "string" } }, "GuestCount": { "type": "number", "description": "The number of guests the item or modifier is expected to serve. This value is `null` if no guest count is specified.\n", "format": "float", "x-nullable": true }, "AllergenItem": { "type": "object", "description": "Reserved for future functionality. Not currently supported for external integrations.\n", "properties": { "guid": { "description": "Reserved for future functionality. Not currently supported for external integrations.\n", "type": "string", "format": "uuid", "example": "5a401af8-d2e2-4090-8c45-9f87b8b6c4d1" }, "code": { "description": "Reserved for future functionality. Not currently supported for external integrations.\n", "type": "string", "example": "string" }, "groupGuid": { "description": "Reserved for future functionality. Not currently supported for external integrations.\n", "type": "string", "format": "uuid", "x-nullable": true, "example": "5a401af8-d2e2-4090-8c45-9f87b8b6c4d1" }, "groupCode": { "description": "Reserved for future functionality. Not currently supported for external integrations.\n", "type": "string", "x-nullable": true, "example": "string" }, "presenceType": { "type": "string", "description": "Reserved for future functionality. Not currently supported for external integrations.\n", "enum": [ "CONTAINS", "TRACES" ], "x-nullable": true, "example": "CONTAINS" } } } } }