...
| Table of Contents | ||
|---|---|---|
|
API Actions
After guests have selected a store for in-restaurant orders or inputted a delivery address (different service modes), they will navigate through the menu. For menu content, Sanity is the source of the truth. For pricing & availability (P&A), the source of truth is either the POS or the Digital Operations Portal (DOP) depending on the integration in your brand/market.
...
| Info |
|---|
Note that the in-restaurant menu uses the same PLUs as what’s being referred to as Pick-Up menu in the API documentation. Pick-up Service Mode Group is the same as In-restaurantThe menu content is mostly managed on a brand/market-level whereas pricing & availability is more granularly managed on restaurant-level. Brand Menu refers to the global menu in a given brand/market, whereas store menu refers to the restaurant-level menu for pricing & availability. |
API Actions - Brand Menu
GET Brand Menu
Get full brand-menu for a channel. The brand-menu is not store specific, but it is the source of content used to generate the store-menu. Differently from the store-menu, the brand-menu does not have any price and availability information.
To ensure guests are seeing the correct pricing and availability, the POS must send us the PLU-price key/value pair, indicating whether PLU is available or not for the specific store and service mode (delivery or pickup). Receiving data for each service mode is needed even for POS where availability of menu items are not managed differently for service modes on restaurant-level.
API Actions - Store Menu
| Info |
|---|
Note that the in-restaurant menu uses the same PLUs as what’s being referred to as Pick-Up menu in the API documentation. Pick-up Service Mode Group is the same as In-restaurant. |