| Note |
|---|
This page is a draft. |
| Info |
|---|
This page explains how to configure menu structures in the RBI platform’s content management system (Sanity) and in Oracle. |
Content
| Table of Contents | ||
|---|---|---|
|
...
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.
...
Item
Items are the single orderable products that will be displayed in the platform, such as Whopper® Burger or Coca Cola Medium.
Sanity Config
| Info |
|---|
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 manual configurations. 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.
Menu Product Type | priceSequence | definitionSequence |
|---|---|---|
Item | Delivery → 2 In-Restaurant → 1 | Delivery → 1 In-Restaurant → 1 |
In your brand and country Sanity environment, you will see the Service Mode Groups (Pickup and Delivery) and POS used. For each Service Mode Group (Pickup 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:
| Info |
|---|
(To be confirmed) priceSeq and definitionSequence configurations will be managed globally for all items, it won’t be necessary for operators to configure these values item-by-item. |
Oracle Config
Modifiers
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.
Sanity Config
| Info |
|---|
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 those 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:
Only 2 levels of modifiers will be supported for mobile ordering: ADD and NO. Additional modifier multipliers (more granular levels of customization such as ‘heavy ketchup’, ‘light ketchup’) won’t be supported for mobile ordering in the initial scope.
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.
Menu Product Type | priceSequence | definitionSequence |
|---|---|---|
Modifier | priceSeq 2 = In Restaurant Add priceSeq 3 = In Restaurant No priceSeq 6 = Delivery Add priceSeq 7 = Delivery No | 1 in all cases. |
In your brand and country Sanity environment, you will see the Service Mode Groups (Pickup and Delivery) and POS used. For each Service Mode Group (Pickup 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:
...
[IMAGE WITH THE NEW UI COMPONENT FOR ADD/NO]
Oracle Config
Combo
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.
Sanity Config
| Info |
|---|
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 manual configurations. 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.
Menu Product Type | priceSequence | definitionSequence |
|---|---|---|
Combo | Delivery → 2 In-Restaurant → 1 | Delivery → 1 In-Restaurant → 1 |
In your brand and country Sanity environment, you will see the Service Mode Groups (Pickup and Delivery) and POS used. For each Service Mode Group (Pickup 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. Different combo sizes ('large', 'medium', 'small') will share the same PLU:
...
Oracle Config
Reward
Sanity Config
Oracle Config
Offers
Sanity Config
...
Contents
| Child pages (Children Display) | ||
|---|---|---|
|