Oracle Config

This page is a draft.

This page explains how to configure menu structures in the RBI platform’s content management system (Sanity) and in Oracle.

Content

This document details the recommended menu structure in Sanity and Oracle.

Following the recommended approach will results in a faster rollout and less issues. Additionally, new RBI features will be developed against the recommended structure.

In general, the PLU Mapping (Vendor Configs) is where the PLU configurations are done within Sanity. The PLU, Definition Sequence and Price Sequence fields are the 3 Oracle attributes that are relevant while distinguishing across different items and service modes.

Items are the single orderable products that will be displayed in the platform, such as Whopper® Burger or Coca Cola Medium.

Item content configurations will be the same as any other POS except for the PLU Mapping (Vendor Configs), for those please refer to the Item page.

For Definition Sequence and Price Sequence fields, you (the operator/FZ) will not need to do item-level configurations in Sanity. Just for your information:

Different pricing sequences will be used to distinguish between service modes (e.g. Whopper vs Whopper Delivery).
Definition sequence will be kept constant to a value of 1.
The same PLU will be used for both service modes.

Service mode	Example PLU	priceSequence	definitionSequence
In-restaurant	1234	1	1
Delivery	1234	2	1

In your brand and country Sanity environment, you will see the Service Mode Groups (In-restaurant and Delivery) and POS used. For each Service Mode Group (In-restaurant and Delivery), you will need to configure the correct PLU. Oracle - In-Restaurant and Oracle - Delivery dropdown needs to be expanded for Oracle PLU Mapping for each service mode respectively:

ConstantPLU PLU type will be used for each item with pricing. A ConstantPLU has a one-to-one relationship with a given Product:

Meals like Medium Whopper® Meal (Burger + Medium Fries + Drink) or Large Whopper® Meal (Burger + Big Fries + Big Drink) are defined by Combos and Combo Slots within Sanity. The term combo is also often used interchangeably with meals.

Combo content configurations will be the same as any other POS except for the PLU Mapping (Vendor Configs), for those please refer to the Combo page.

For Definition Sequence and Price Sequence fields, you (the operator/FZ) will not need to do combo-level configurations in Sanity. Just for your information:

Different pricing sequences will be used to distinguish between service modes (e.g. Whopper vs Whopper Delivery).
Definition sequence will be kept constant to a value of 1.
The same PLU will be used for both service modes.

Service mode	Example PLU	priceSequence	definitionSequence
In-restaurant	1234	1	1
Delivery	1234	2	1

In your brand and country Sanity environment, you will see the Service Mode Groups (In-restaurant and Delivery) and POS used. For each Service Mode Group (In-restaurant and Delivery), you will need to configure the correct PLU. Oracle - In-Restaurant and Oracle - Delivery dropdown needs to be expanded for Oracle PLU Mapping for each service mode respectively:

sizeBasedPlu PLU type will be used for each combo with pricing where:

PLU: The PLU for the general combo.
Size: The size of the combo (e.g. Large).
Different combo sizes ('large', 'medium', 'small') will share the same PLU.

Considering also the comboslots, the overall combo PLU structure for Oracle will be as follows:

Combo structure

Combo PLU

Main Item PLU

Comboslot PLU

Comboslot item PLU

The combo document is structured as follow:

Main item
- Item (Hamburger).
Options
- Sides comboslot – contain available sides (e.g. fries or onion rings).
- Drinks comboslot – contain available drinks (e.g. Fanta, Coca-Cola…).

The combo document uses a sizeBasedPLU.

The main item in the combo is an item document, which uses a separate constant PLU.

All comboslots in the combo use the Ignore PLU:
- Large sides
- Large drinks

Comboslots have a list of available items linked.

Since these comboslot options are items, they will have their own Constant PLU.

Large sides have several options – e.g. large fries with its own constant PLU.
Large drinks have several options – e.g Frozen Strawberry Fanta.

Modifiers allow guests to customize items. They can be added, removed, increased or decreased. For example, you can remove lettuce, tomato and pickles from a Whopper.

Most of the modifier content configurations will be the same as any other POS except for the PLU Mapping (Vendor Configs) and configurations for modifiers and modifier multipliers within Item → Options, for the shared content configurations please refer to the Modifier page.

For Definition Sequence and Price Sequence fields, you (the operator/FZ) will not need to do manual configurations. Just for your information:

priceSequences will be used for determining the ADD and NO modifiers, as well as pricing across service modes.
Definition sequence will be kept constant to a value of 1.

Example PLU

priceSequence

definitionSequence

A single PLU per modifier, e.g. 123456.

priceSeq 2 = In Restaurant Add

priceSeq 3 = In Restaurant No

priceSeq 6 = Delivery Add

priceSeq 7 = Delivery No

1 in all cases.

Only 2 levels of modifiers are supported for mobile ordering: ADD and NO. Additional modifier multipliers (more granular levels of customization such as ‘heavy ketchup’, ‘light ketchup’) are not supported for mobile ordering at this time.

In your brand and country Sanity environment, you will see the Service Mode Groups (In-restaurant and Delivery) and POS used. For each Service Mode Group (In-restaurant and Delivery), you will need to configure the correct PLU. Oracle - In-Restaurant and Oracle - Delivery dropdown needs to be expanded for Oracle PLU Mapping for each service mode respectively:

ConstantPLU PLU type will be used for each modifier, no PLUs will be defined for modifier multipliers:

Additionally, a single Sanity document (page) will be used for each modifier, with a shared single PLU used for both in-restaurant and delivery service modes.

All modifiers for a given item will be configured under Item --> Options:

ADD and NO values for modifiers will also be available under Item --> Options via a UI selection option by default for all modifiers added:

[IMAGE WITH THE NEW UI COMPONENT FOR ADD/NO]

Note that the above UI selection options can be used only for the Oracle POS. They cannot be used for other POS vendors such as NCR.

Scenario	UI Configuration
If a guest can remove a modifier from an item and can also add more.	Both the Add and No UI selections will be selected/turned on.
If a guest cannot remove a modifier from an item but can still add more of it.	The Add UI selection will be selected/turned on.
If a guest can remove a modifier from an item but cannot add more.	The No UI selection will be selected/turned on.
If a guest cannot do anything about a modifier from an item.	No need to add that modifier under Item --> Options.

Note that the deviations are❗not recommended❗unless it is mandatory since the recommended approach will results in a faster rollout, less issues and new features will be built based on the recommended structure.

In the case of items, combos and modifiers you can also distinguish between service modes by using:

Different PLUs per service modes.

or,

Different definition sequences per service mode.

The approach needs to be the same for all structures – i.e. you can’t use PLUs for items and definition sequences for combos.

Item

Sanity Config

Combo

Sanity Config

Oracle Config

Modifiers

Sanity Config

Oracle Config

Reward

Sanity Config

Oracle Config

Offers

Sanity Config

Oracle Config

Deviations from the Recommended Menu Structure

Service modes