Versions Compared

Old Version 26

changes.mady.by.user Yildirim, Semih

Saved on

compared with

New Version 27

changes.mady.by.user Benet, Anton

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In certain markets, there are menu items whose availability can be temporarily different for different service modes on a restaurant-level. Meaning, item_1 being available for pickup and delivery normally for a given store, but temporarily needs to be made unavailable only for the delivery service mode while still being available for pickup. An example of this is packaged ice creams not being sold via delivery temporarily during heat hours but still sold on pickup. For those items, the configuration requires two distinct PLUs per service mode, as well as 2 separate Sanity menu content documents. To illustrate:

  • The market has 500 menu items in total. Menu item availability for almost all menu is managed per store for both service modes (if a menu item is not available in the restaurant for online pickup ordering, then it also won't be available for delivery).

  • There are only 10 menu items that could have different availability per store and service mode at the same time, like the icecream example mentioned above.

  • The operator configures a single PLU for 490 items, the same PLU is shared for both service modes. Availability is managed for both service modes at the same time on a store-level - always.

  • For the 10 exceptional menu items, distinct PLUs are defined per service mode - in total 20 PLUs.

  • These different PLUs then can be marked available/unavailable via the Oracle POS to manage availability differently per service mode.

  • Similarly, 2 unique Sanity menu documents are created for these items, one for each service mode. Example: Ben & Jerry's Icecream Pickup and Ben & Jerry's Icecream Delivery. Applicable pickup and delivery PLUs are then added to each document. This is different than the remaining 490 items where there is a single Sanity menu item document and the same PLU is entered for both service modes under Vendor Configs.

This setup is required for the guest application to manage the availability correctly.

 

Items

  • Oracle’s recommendation is to have 1 item (PLU) regardless of service mode.

  • Distinguishing service modes

    • Revenue Center --> Order Channel --> Order Type 

    • Revenue Center and Order Channel are only used for reporting.

    • Order channel is the source of the order. RBI does not send this.

    • Order type (eatin, kiosk, takeaway, etc.) is the destination of the order. Reporting + behavior.

      • Used for changing price level, taxes, etc. per service mode.

    • Tagging

      • 2 tags, 1 for in-restaurant and 1 for delivery.

      • Tags indicates availability per service mode

    • definitionSequence

      • Recommendation is to only use 1 definition sequence.

    • And 2 priceSequence to handle different pricing:

      • 1 In-restaurant

      • 2 Delivery

To build store menu:

  1. “Get Menus” call gives you full menu for specific store. If a restaurant does never sell ice-creams, it would not be in the get menu.

  2. “Get collection of unavailable items” gives you list of unavailable items.

Info

Oracle doesn’t support managing availability separately from in-store and delivery.

Combining both we get the available items per store per service mode.

Discuss how to handle non-integrated delivery orders.

Expand
titleRBI Partner API
Code Block
languagejson
"cart": {
        "menuSelections": [
            {
                "externalReferenceId": "801500",
                "id": "item_67165",
                "menuSelections": [],
                "price": {
                    "amount": 649,
                    "currency": "EUR"
                },
                "quantity": 1,
                "type": "Item"
            }
        ]
    }

...