Documentation for "Menu Hierarchy"
Answered
Recently we had an issue where, when pulling a menu from the menus API, we were getting an unexpected GUID for one of the modifier groups (that is, it wasn't what we saw in the menu builder). This was for a restaurant chain with multiple "Targets" for the same item, each with its own GUID. When we reached out to support, we were told:
"When pulling the GUID it will follow the menu hierarchy to determine which item to pull. This GUID is specifically versioned for this group, putting it at the top of the hierarchy causing it to be the item GUID pulled for API."
We'd love to have some reference documentation on how exactly the GUID sent in the API response is determined.
-
Hi Matt!
I'll take a look at this in more detail to see if the menus API and Toast Web UI are behaving in an expected manner or if there's an additional issue to be addressed. From there, we'll determine if we need to notify our engineering team, update our documentation, or both.
I've created a support ticket so we can talk in greater detail about the specific restaurant and item.
0 -
To keep our forum updated, I've added a ticket to our documentation backlog about clarifying the differences between Toast Web and our menus API.
To illustrate, say a restaurant management group creates a menu item that is maintained at the corporate level, meaning that the item is present at all locations. Then, location A makes a new version of this item that applies to just their one location.
The menus API will return the location-specific version of the item, because it is the most specific version that applies to this location. However, Toast Web will display both versions (the corporate version and the location-specific version) in case anybody needs to update the corporate-level item in the future.
We'll work on updating our documentation to reflect this information.
0
Please sign in to leave a comment.
Comments
2 comments