Menu - Agreements
Contents
- 1 Oracle Symphony API Guide
- 2 Fiscal Integrations
- 3 Pricing & Availability per Service Modes on a Restaurant-level
- 4 Summary for Pricing & Availability
- 5 Modifiers
- 6 Combo Pricing
- 7 Sugar Tax & Fees
- 8 Order Firing & Cancelation
- 9 Webhooks
- 10 Restaurant Availability
- 11 Cache for Restaurant Availability & Menu
- 12 References
- 13 Offers and Rewards
Oracle Symphony API Guide
https://docs.oracle.com/en/industries/food-beverage/simphony/19.4/stsgg/F56815_08.pdf
Fiscal Integrations
Fiscal integrations will change market by market. There’s no standard.
Pricing & Availability per Service Modes on a Restaurant-level
Terminology & overview: Oracle POS - Standards
Availability Management
GET Menus: check for PLU + DefSeq + PriceSeq to verify if item is active or not in the restaurant. Items that are not active are unavailable. However, this endpoint doesn’t take restaurant-level availability into account fully.
To retrieve unavailable items per store, we need to make another call to the GET Unavailable endpoint, which returns the list of unavailable items. Hence, whenever we build the store menu (after a guest selects a restaurant in the platform), we need to call both endpoints to determine availability on a store-level. Unavailable items from GET Unavailable must be removed from the active list retrieved from GET Menus.
Call GET Menu - using v1/menus (Khumbu already does)
Call GET Unavailable endpoint --- using (menus/items/unavailable) (Khumbu already does)
Actively listen to Configuration Notifications webhook for changes to availability (notifications API) (Khumbu doesn't do this currently.)
If an item is unavailable in this endpoint, is means it is unavailable in all service modes.
Note that the Configuration Notification will only indicate there’s been a change in availability but will not specify what items are impacted by the change (additional details on the webhooks section).
Operators in the restaurant manage items availability on a store-level using the POS, Oracle POS only supports that on store-level for both service modes - not distinguishing availability per service mode (pick-up and delivery).
Assumption: In general, menu item availability is not managed differently per service mode on a store-level, meaning availability for pick-up and delivery is generally the same.
For specific items whose availability is different for pickup and delivery within the same store, the following will be the suggestion to the operator:
Menu Product Type | priceSequence | definitionSequence |
---|---|---|
Item | Delivery → 2 In-restaurant → 1 | 1 for both Delivery and In-restaurant. |
Combo | Delivery → 2 In-restaurant → 1 | 1 for both Delivery and In-restaurant. |
Modifier | priceSeq 2 = In Restaurant Add priceSeq 3 = In Restaurant No priceSeq 6 = Delivery Add priceSeq 7 = Delivery No | 1 for both Delivery and In-restaurant. |