Page Comparison

STS Gen2

• In the Get Menus call we will get all products deployed for a particular store for a particular revenue center.

• Items can be tagged – e.g. all kiosk items can be tagged as ‘kiosk products’. Tagging can be used to filter out categories of food (e.g. meals, LTOs…). Filtering lets you perform bulk actions. E.g. we can only retrieve specific menu items from the POS.

• Cloud Assist Service is in charge of ensuring standardization of PLUs.

Managing Pricing & Availability per Service Modes on a Restaurant-level

1) Pricing

Different pricing between service modes will be managed by priceSequence within the same definition.

• (TBD) pricingSequence = 1 --> pick-up SM

• (TBD) pricingSequence = 2 --> delivery SM

2) Availability

GET Menus call returns all items for a given store, it doesn't take availability into account. To retrieve unavailable items per store, we need to make another call to the 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:

1. Call GET Menu - using v1/menus (Khumbu already does)

2. Call GET Availability endpoint --- using (menus/items/unavailable) (Khumbu already does)

   1. Actively listen to webhook for changes to availability (notifications API) (Khumbu doesn't do this currently.)

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.

Assumption: In general, menu item availability is not managed specifically differently per service mode (on a store-level).

For specific items whose availability is different for pickup and delivery within the same store, the following will be the suggestion to the operator: