Contents

Oracle Configuration

A combo meal consists of a menu item that combines two or more items into a group and is used by the restaurant to increase sales by bundling multiple items. Offering a lower price for the combo than ordering each item individually is also very common to promote the combos.

In RBI we are currently using Simphony Combo Meal structures to also define Coupons, Offers and Rewards, In this chapter we will only talk about regular combo meals, the other usages of the Simphony Combo Meal structure will be handled in specific sessions.

Combo meals are formed by a regular menu item (just like an Ala Carte item) that defines the behavior and price of the combo and a combo meal structure with combo meal groups that defines the combo composition.

Combo Configuration

Naming conventions

Sizes

The size abbreviation should suffix the name of the Combo and prefix the combo abbreviation.

Small = Sm

Medium = Md

Large = Lg

Combo word

Combo abbreviation should suffix the size abbreviation or the name of the combo if the combo does not have a fixed size.

Combo = Cmb

(Combo) Menu Item Master

Level: Brand Level (Enterprise level/Brand). The reason is to create standardization of the Menu Items across the brand and for all countries and Franchisees.

Record Number: Next available Object Number. RBI decided to not use any ranges to divide products by family or by type.

Name: The name of the combo in English. The Name will be used in the reports.

Name 2: Not in use.

Name and Name 2 Translations: Set translations for all languages in the same level as the Menu Item Master. The Translations will be used in the reports.

Reporting Group: See brand specific Reporting Group standards.

https://rbictg.atlassian.net/wiki/spaces/IRT/pages/5137399868

Major Group: See brand specific Major Group standards.

https://rbictg.atlassian.net/wiki/spaces/IRT/pages/5135958074

Family Group: See brand specific Family Group standards.

https://rbictg.atlassian.net/wiki/spaces/IRT/pages/5137858606

Master Group: Not in use. Set to 0 - none.

Effectivity Group: 99999 - Disabled. All Menu Items will be disabled by default. Items can be enabled at country and/or Franchisee level.

(Combo) Menu Item Definition

Level: Brand Level (Enterprise level/Brand). The reason is to create standardization of the Menu Items across the brand and for all countries and Franchisees.

Definitions:

Sequence 1: In Restaurant

Sequence 2: Delivery

First Name: Name displayed in workstation, KDS Displays, guest checks, customer receipts, and order device output. Use the Standard Name convention and set the name in English.

Second Name: Not in use.

Third Name: Not in use.

Long Descriptor: Not in use.

Menu Item Class:

Print Class Override: 0

Menu Level Availability: All levels

Menu Levels Tab: Nothing should be selected

Default Condiments: No Default Condiments should be assigned

(Combo) Menu Item Price

Level: Enterprise/brand/country/<price tier zone>

In Restaurant price: Definition Sequence 1 + Price Sequence 1

Delivery price: Definition Sequence 2 + Price Sequence 1

Manual (non integrated) Delivery Price: Definition Sequence 2 + Price Sequence 2

Combo Meal Groups

Main Item (single item) Group

Level: Brand Level (Enterprise level/Brand). The reason is to create standardization of the Menu Items across the brand and for all countries and Franchisees.

Record Number: use the last four (4) digits of the Object Number Ala Carte Menu Item that will be the Main Item of the combo.

Name: Use same name as Ala Carte Item

Name Translations: Set translations for all languages in the same level as the Combo Meal Group.

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, set quantity as needed (normally 1)

Sides/Drinks (multiple items) Groups

Level: Brand Level (Enterprise level/Brand). The reason is to create standardization of the Menu Items across the brand and for all countries and Franchisees.

Record Number: Next available Object Number starting from 1. RBI decided to not use any ranges to divide products by family or by type.

Name: Use a name that describe the group, examples: Soft Drinks, Hot Drinks, Sm Soft Drinks, Sides, Sm Sides, Md sides, Select Small Sandwich, …

Name Translations: Set translations for all languages in the same level as the Combo Meal Group.

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

Add the Menu Items that will be part of the Combo Meal Group to the list of Items, set quantity as needed (normally 1)

Combo Meal

Level: Brand Level (Enterprise level/Brand). The reason is to create standardization of the Menu Items across the brand and for all countries and Franchisees.

Record Number: Next available Object Number. RBI decided to not use any ranges to divide products by family or by type.

Name: Use the same name as the main item and suffix with word “Cmb”.

Name Translations: Set translations for all languages in the same level as the Menu Item Master. The Translations will be used in the reports.

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

Check Option Bits

• 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 required (Main, Sides, Drinks), set quantities as required.

Combo sizing

Oracle Simphony uses the concept of dynamic combos where sides (sides, drinks, etc) can be upgraded (larger size) independently. This means one combo PLU fits all sizes.

However, RBI Digital platform requires different combo PLUs for different combo sizes.

Hence, currently and until we do not have alignment we are creating 4 PLUs for each combo, the SM, MD and LG for the RBI Digital and the dynamic for POS and Deliverect.

Pricing & Availability

The price of a Combo is composed of the price of the Combo item itself (1) summed with the price of each Combo Group Item that is selected or defaulted for the combo (2).

The price of the Combo item is retrieved using the Menu Item Master Record Number defined in the Combo Meal structure, the Menu Item Master Record will point to the Menu Item Definition and the Menu Item Price that should be used to retrieve the Combo price (1). For the Combo price, both Definition Sequence and Price Sequence are used to determine the price that should be charged for the Combo in a specific channel.

The price of the Combo Group Item is retrieved from the Combo Meal Group, each item in the combo meal group may have defined a price to be charged when the item is sold inside the Combo (2). It could be an upcharge price, for instance when upgrading the drink from Small to Medium or could be the absolute price to be changed for that item.

Combo price total = (Combo) Menu Item Price (1) + sum of(for each(combo group in combo).items[selected or defaulted].price (2)))

Apply the same logic of the pricing to verify the Combo availability. Availability is determined solely by the availability of the Menu Item Price (of the Combo Menu Item Master). The Combo availability is based on the existence of a valid and not expired price.

To evaluate the availability of the Items in the combo groups apply the same logic that would be applied for the Ala Carte Menu Item related to the Item in the group. In case the item is not available it should be disabled as a selection in the combo group.

Let’s look at an full configuration of a Combo using the Whopper Combo as an example.

Combo Menu Item

Defines the price and the behavior of the combo.

Menu Item Master

Open

Menu Item Definition

Open

Note that the Whopper combo has two definitions, 1 = In Restaurant and 2 = Delivery.

Menu Item Price

The Whopper combo also have price defined for definition 1= In Restaurant at 144.00 and 2 = Delivery at 169.00.

This means the Combo is available for both In Restaurant and Delivery. 

Combo Meal Group (Main Item)

Note that the Combo Meal group for the Main item, the Whopper only have one item on it, which means no selection is required, the Whopper will be selected by default, and there is no price set for the Whopper in the group which means the Whopper will not be charged in the combo, the price of the Whopper is incorporated in the combo price.

This does not mean that the Whopper is available or not Available. To check Availability of the Whopper one should check the availability of the Menu Item 1001001 as defined in https://rbictg.atlassian.net/wiki/spaces/IRT/pages/5068816435.

Combo Meal Group (Drinks Group)

Combo Meal

Sanity Configuration

The operator only needs to configure the PLU and size for the combo, which will be the same for both service modes.

The operator will not need to do combo-level configurations in Sanity for Definition Sequence and Price Sequence fields. Just for your information, Sanity will use:

• Different pricing sequences to distinguish between service modes (e.g. Whopper is priceSeq 1, vs Whopper Delivery which is priceSeq 2).

• Definition sequence kept constant to a value of 1.

Example for a large combo:

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 (side 1 and side 2), the overall combo PLU structure in Sanity will be as follows: