RBI and Oracle handle PLUs in a different manner. While RBI scopes their PLUs by service mode, Oracle uses price sequence and definition sequence.

Besides the service mode scoping, price sequence and definition sequence are used by Oracle to handle adding/removing modifiers from items. RBI does it via the quantity attribute in it’s payloads.

This document will go over how to perform the correct mapping between those two different platforms.

The requirements are divided by the scope of product type.

For each product type, there are specific requirements related to Menu Sync and to Order Pricing.

One important thing to highlight that is global:

1. Price Sequence and Definition Sequence vary per market/brand and it’s respective mapping to RBI’s service modes must be configurable on Khumbu’s end.

2. For order pricing, Khumbu will always receive the same PLUs it provided for RBI, so it will have to perform the reverse conversions into Oracle’s definition sequence and price sequence.

For pricing items, Khumbu will receive RBI’s service modes and PLUs and must perform the reverse conversion into Oracle’s price sequence and definition sequence.

Combo’s behave slightly different when compared to items.

Oracle uses dynamic combos with single PLU for the combo, while RBI uses the concept of size based PLUs.

To map Oracle dynamic combos into RBI’s size based PLUs, the Size information on Oracle’s combo meal groups should be used. The equivalence between RBI size based plus and and Oracle’s combo meal group size information can vary per market and should be configurable. As an example, we’re considering:

Size 1 = small

Size 2 = medium

Size 3 = large

Size 4 = kids

For pricing combos, Khumbu will receive RBI’s service modes and PLUs and must perform the reverse conversion into Oracle’s price sequence and definition sequence.

The combo PLU will contain the size based concatenation from RBI.

In the modifiers topic, Oracle uses different definition sequence and price sequence to distinguish between adding/removing modifiers.

In contrast, RBI will handle adding/removing modifiers through the quantity field when pricing an order. E.g.: modifiers with 0 quantity are supposed to be removed. This is currently a work in progress by RBI and should be available soon.

This means that RBI is not aware of the Oracle’s concept of ‘NO’ to a modifier.

In the current setup, Loyalty Offers and Rewards are configured as ComboMeals in Oracle, the same as how to configure RBI Combos. However Offers and Rewards could be treated differently from the Combos, we agree that Family Groups are used to differentiate them from Combos. But the Family Groups vary between markets, they need to be configurable on Khumbu side.

There are two different Offers as following.

• Offer with Combo as benefit

The Offers with different size of Combo are configured in different ComboMeal as the corresponing size in Oracle, means they have different Oracle PLUs, no size based PLU mapping is needed in the Menu Sync.

• Offer with Item as benefit

The Offers are configured using ComboMeal with single PLU, but the dynamic sizes is not needed. In this case, no size based PLU mapping is needed.

For pricing Offers, Khumbu will receive RBI’s service modes and PLUs and must perform the reverse conversion into Oracle’s price sequence and definition sequence.

Khumbu will receive only the Oracle PLU (without the size based concatenation), for the following two types of Offers

Offer with Combo as benefit

In the structure, the size-based PLU of the benefit Combo is also sent, then the size of the Offer ComboMeal can be reversed by using the size-based PLU of the benefit Combo.

Offer with Item as benefit

The size of the Offer ComboMeal can be reversed using the default size set in Oracle.

Rewards are configured as same as Offers in Oracle, so the behavior is the same as Offers. There are also two different Rewards, Reward with Combo as benefit and Reward with Item as benefit.

For pricing Rewards, Khumbu will receive RBI’s service modes and PLUs and must perform the reverse conversion into Oracle’s price sequence and definition sequence.

Khumbu will receive only the Oracle PLU (without the size based concatenation), for the following two types of Rewards

Reward with Combo as benefit

In the structure, the size-based PLU of the benefit Combo is also sent, then the size of the Reward ComboMeal can be reversed by using the size-based PLU of the benefit Combo.

Reward with Item as benefit

The size of the Reward ComboMeal can be reversed using the default size set in Oracle.

Discounts are configured using discount in Oracle, where the discount has no price sequence, definition sequence, nor price. So there is no mapping in Menu Sync and Order Pricing.

Discounts are not needed to be included in the menu sync.

For pricing items, Khumbu will receive RBI’s service modes and PLUs, but no transformation is needed, the discount PLU sent from RBI can be used.