...
For pricing & availability (P&A), this document focuses on the scenarios where the source of truth is either the POS or the Digital Operations Portal (DOP) depending on the integration in your brand/market.
| Info |
|---|
The menu content is mostly managed on a brand/market-level (e.g. Burger King UK) whereas pricing & availability is more granularly managed on restaurant-level. The Brand Menu refers to the global menu in a given brand/market for content, whereas the Store Menu refers to the restaurant-level menu for pricing & availability. |
Before moving into the API Actions, there are 3 important parameters to clarify:
Channel - The touchpoint where the guest interacts with our platforms. For example, whitelabel (web and mobile), Kiosk, Glovo, UberEats. For Menu API actions, this parameter is a string without pre-defined enums.
Service mode - The mode (way) the guests are being served. In most Menu API Actions, this parameter is an enum. While some APIs have these enums defined on a higher-level with values
"pickup""delivery", some have it on a more granular level with values"CURBSIDE""DELIVERY""DRIVE_THRU""EAT_IN""TABLE_SERVICE""TAKEOUT"."pickup"refers to In-Restaurant in general (Pickup, Dine-In, Drive-Thru, Table Service, Curbside).Store Id - A unique identifier within RBI for each restaurant.
API Actions - Brand Menu
GET Brand Menu Endpoint
...