Contents

Overview

Offers 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, offers 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 offers.

Using combos is a workaround and will be replaced by discounts once the Oracle issues are resolved. To minimize impact to business operations, the RBI Platform allows combo-based and discount-based offers 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 offers

Oracle

Single Item/Ala Carte Offers

A Menu Item Offer may be composed of one or more menu items and may also include selections of items like drinks and sides.

Even if an offer includes only one menu item it will still be configured as a combo meal in Simphony, very similar to the Ala Carte Menu Item Reward.

Ala Carte Offer

Menu Item Master

• Setup the Menu Item Master for the offer combo.

  • Hierarchy:

    • DMTE: Enterprise/brand

  • Object Number: Use the next number available, if you use ranges use the next number available in the range you are using for your Digital Offers .

    • DMTE BK Example: Use the next number available in the range 5000000 - 5999999.

  • Name: Use the name provided by the Marketing team.

    • Example $3 Whopper.

  • 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: 5002 - Digital Promotions

  • 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 the name provided by the Marketing team.

    • Example $3 Whopper.

  • Menu Item Class: Associate to the Menu Item Class used for combos of the same class you are creating

    • DMTE BK Example: 1401 - Fd Bundles Main

  • SLU: 0 - Set according to your POS screen layout

    • DMTE BK Example: 925 - Digital Coupons

  • NLU Number: if Offer can be redeemed through a coupon then NLU field must contain the number of the Coupon

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

  • 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: Set the price as defined by the Marketing team

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

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: Use same number used to create the Menu Item Master of the Offer

    • Example 5000107

  • Name: Use same name used in the Menu Item Master created for the offer.

    • Example 3$ Whopper.

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

    • Example 5001007 - $3 Whopper

  • Check Option Bits

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

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

    • DMTE BK Example: 1001 - Whopper

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

Multiple Items Offer

Multiple Items Offers are setup same way as Ala Carte Offers, the only difference is that it will include more Combo Meal Groups. Each Combo Meal Group standing for an included item or a selection of items.

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

Discount-based offers

Oracle

For offers we need a distinct discount ID per offers 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.

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: