Different pricing between service modes will be managed by priceSequence within the same definitionSequence. Applicable for all products (item, combo, modifier). 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: Call GET Menu - using v1/menus (Khumbu already does) Call GET Availability 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.)
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: |