Contents

Overview

Rewards will be mapped to Oracle Discounts. However, during testing, RBI found issues with the Oracle API that prevent the use of discounts at this stage. These issues are expected to be solved by Oracle by the end of Q1 2025. In the interim, rewards need to be configured in Oracle as combos. Sub-sections of this document below cover the Oracle and Sanity configuration for both combo-based and discount-based rewards.

Using combos is a workaround and will be replaced by discounts once the Oracle issues are resolved. To minimise impact to business operations, the RBI Platform allows combo-based and discount-based rewards to co-exist, which means that Franchisees will be able to decide when they want to switch from combo-based to discount-based.

Combo-based rewards

Oracle

REWARDS SETUP

There are two categories of Rewards; Rewards that add Ala Carte item to the transaction and Rewards that add Combo item to a transaction. Rewards that add Ala Carte menu items to a transaction leverage Combo Meals to link Rewarded Ala Carte menu items at the price indicated by the Reward (normally $0). For Rewards that add different Combo items, they are configured in different Combo Meals, means they have different Oracle PLU.

Single Item/Ala Carte Rewards

Menu Item Master

• Setup the Menu Item Master for the combo/reward.

  • Hierarchy:

    • DMTE: Enterprise/brand

  • Object Number: prefix the Ala Carte item Object Number with 5.

    • Example Whopper is 1001001, the Whopper Reward will be 51001001.

  • Name: Use same name as Ala Carte Item and suffix with the word reward.

    • Example Whopper becomes Whopper Reward.

  • Major Group: Associate to the Major group used for your Bundles/Promotions

    • DMTE BK Example: 5000 - Bundles

  • Family Group: Associate to the Family group used for your Rewards, create one if necessary

    • DMTE BK Example: 5006 - Loyalty Rewards

  • Report Group: Associate to the Report group used for your Bundles/Promotions

    • DMTE BK Example: 5

  • Master Group: 0 - None

Open

Open

 Menu Item Definition

• Setup Menu Item Definition for the combo/reward.

  • Hierarchy:

    • DMTE: Enterprise/brand

  • Definition Seq: The definition sequence used for the ordering channel the item will be available

    • DMTE BK Example: 1 - In Restaurant / 1 - Delivery

  • First Name: Use same name as Ala Carte Item and suffix with the work reward.

    • Example Whopper becomes Whopper Reward.

  • Menu Item Class: Associate to the Menu Item Class used for rewards

    • DMTE BK Example: 5001 - Rewards

  • SLU: 0 - None

  • Menu Level Availability: As required

    • DMTE BK Example: All levels

  • Menu Levels Tab: Nothing should be selected

  • Default Condiments: No Default Condiments should be assigned

 Menu Item Price

• Hierarchy:

  • DMTE: Enterprise/brand/country/<price tier zone>

• Setup Menu Item Price for the combo/reward.

  • Price Seq: The price sequence used for the ordering channel.

    • DMTE BK Example: 1

  • Price: $0.00.

Combo Meal Group

• Setup the Combo Meal Group for the reward if not already existing.

  • Hierarchy:

    • DMTE: Enterprise/brand

  • Number: use the last four (4) digits of the Ala Carte Menu Item Object Number.

    • DMTE BK Example: 1001 (For the 1001001 - Whopper)

  • Name: Use same name as Ala Carte Item

  • Check Option Bit “1 – Allow Discounts” in Combo Group Configuration

  • Add the Ala Carte Item (and only the Ala Carte Item) to the list of Items

    • DMTE BK Example: 1001001 - Whopper

  • Set the Ala Carte Item to be the default for all Order Types including “no” Order Type.

    • DMTE BK Example: 1, 2, 3, 4, 5, 6, 7, 8, 9

  • Set the Ala Carte Item as Size Item for all Sizes

    • DMTE BK Example: Size 1 Item, Size 2 Item and Size 3 Item

Combo Meal

• Setup the Combo Meal with pricing $0 and Combo Meal Group selection for the item in the reward.

  • Hierarchy:

    • DMTE: Enterprise/brand

  • Number: prefix the Ala Carte item Object Number with 5.

    • Example Whopper is 1001001, the Whopper Reward (combo) will be 51001001.

  • Name: Use same name as Ala Carte Item and suffix with the work reward.

    • Example Whopper becomes Whopper Reward.

  • Menu Item Master: Select the Menu item Master created for the reward.

    • Example 51001001 - Whopper Reward.

  • Check Option Bits

    • 1 – Disable Auto-Combo Recognition

      • (Prevent the combo triggering without a Reward)

    • 4 – Add Side Prices to Meal Price (Optional)

    • 9 – Do not show with Combo Meal Choices

    • 10 – Keep Last Item Selected after Ordering a New Meal (Optional)

  • Add the Combo Meal Group that was created for the Reward (or reuse exiting) as the Primary Group

    • DMTE BK Example: 1001 - Whopper

    • Set Side count to 1and keep Default Menu Level and Menu Levels equals to 0.

Barcode

• Setup the Barcode and link the Barcode the menu item master for the combo meal.

  • Hierarchy:

    • DMTE: Enterprise/brand

  • Number: use same number as the Combo Meal created for the reward

    • Example 51001001

  • Barcode: use the same number used for Combo Meal, make it 12-digits padding with zeros

    • Example 000051001001

  • Link the Barcode to the Menu Item created for the reward.

    • Example 51001001 - Whopper Reward

  • Set the Definition and Price record to the zero priced record created.

Combo Item Rewards

Menu Item Master

• Setup the Menu Item Master for the combo/reward.

  • Hierarchy:

    • DMTE: Enterprise/brand

  • Object Number: prefix the Combo item Object Number with 5.

    • Example Whopper Combo is 1001002, the Whopper Combo Reward will be 51001002.

  • Name: Use same name as Combo Item and suffix with the word reward.

    • Example Whopper becomes Whopper Reward.

  • Major Group: Associate to the Major group used for your Bundles/Promotions

    • DMTE BK Example: 5000 - Bundles

  • Family Group: Associate to the Family group used for your Rewards, create one if necessary

    • DMTE BK Example: 5006 - Loyalty Rewards

  • Report Group: Associate to the Report group used for your Bundles/Promotions

    • DMTE BK Example: 5

  • Master Group: 0 - None

Menu Item Definition

• Setup Menu Item Definition for the combo/reward.

  • Hierarchy:

    • DMTE: Enterprise/brand

  • Definition Seq: The definition sequence used for the ordering channel the item will be available

    • DMTE BK Example: 1 - In Restaurant / 1 - Delivery

  • First Name: Use same name as Combo Item and suffix with the work reward.

    • Example Whopper Combo becomes Whopper Combo Reward.

  • Menu Item Class: Associate to the Menu Item Class used for rewards

    • DMTE BK Example: 5001 - Rewards

  • SLU: 0 - None

  • Menu Level Availability: As required

    • DMTE BK Example: All levels

  • Menu Levels Tab: Nothing should be selected

  • Default Condiments: No Default Condiments should be assigned

Menu Item Price

• Hierarchy:

  • DMTE: Enterprise/brand/country/<price tier zone>

• Setup Menu Item Price for the combo/reward.

  • Price Seq: The price sequence used for the ordering channel.

    • DMTE BK Example: 1

  • Price: $0.00.

Combo Meal

• Setup the Combo Meal with pricing $0 and Combo Meal Group selections equals to the selections of the original combo.

  • Hierarchy:

    • DMTE: Enterprise/brand

  • Number: prefix the Combo item Object Number with 5.

    • Example Whopper Combo is 1001002, the Whopper Combo Reward will be 51001002.

  • Name: Use same name as Combo Item and suffix with the work reward.

    • Example Whopper Combo becomes Whopper Combo Reward.

  • Menu Item Master: Select the Menu item Master as the Menu Item Master created for the reward combo.

    • Example 51001002 - Whopper Combo Reward

  • Check Option Bits

    • 1 – Disable Auto-Combo Recognition

      • (Prevent the combo triggering without a Reward)

    • 4 – Add Side Prices to Meal Price (Optional)

    • 9 – Do not show with Combo Meal Choices

    • 10 – Keep Last Item Selected after Ordering a New Meal (Optional)

  • Combo Meal Groups: Add same groups as the Original combo.

    • For the Side Group and Drink Group, it should be consistent with the Combo size that the Reward intents to have. For example, if a Small Combo should be contained, the Side Group should be Sides (S), and the Drink Group be Drnk (S).

Barcode

• Setup the Barcode and link the Barcode the menu item master for the combo meal.

  • Hierarchy:

    • DMTE: Enterprise/brand

  • Number: use same number as the Combo Meal created for the reward

    • Example 51001002

  • Barcode: use the same number used for Combo Meal, make it 12-digits padding with zeros

    • Example 000051001002

  • Link the Barcode to the Menu Item created for the reward.

    • Example 51001002 - Whopper Combo Reward

  • Set the Definition and Price record to the zero priced record created.

Sanity

For Definition Sequence and Price Sequence fields, you (the operator/FZ) will not need to do 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.

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 reward. A ConstantPLU has a one-to-one relationship with a given Product:

Discount-based rewards

Oracle

For rewards we need a distinct discount ID per reward with a price associated to it. The only exception is with cart level discounts that only need a discount ID associated to it. For cart level and product discounts logic is done in the app to calculate prices of the basket.

Sanity

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 Discount ID that was configured in Oracle. 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 Discount ID. A ConstantPLU has a one-to-one relationship with a given Product: