Oracle Config - Combos
Contents
- 1 Oracle Configuration
- 1.1 Combo Configuration
- 1.1.1 Dynamic Combos
- 1.1.2 Combo Naming conventions
- 1.1.3 (Combo) Menu Item Master
- 1.1.4 (Combo) Menu Item Definition
- 1.1.5 (Combo) Menu Item Price
- 1.1.6 Combo Meal Groups
- 1.1.7 Combo Meal
- 1.1.8 Combo sizing
- 1.1.8.1 Charging for larger size side
- 1.2 Pricing & Availability
- 1.2.1 Combo Menu Item
- 1.2.1.1 Menu Item Master
- 1.2.1.2 Menu Item Definition
- 1.2.1.3 Menu Item Price
- 1.2.2 Combo Meal Group (Main Item)
- 1.2.3 Combo Meal Group (Main Item)
- 1.2.4 Combo Meal Group (Drinks Group)
- 1.2.4.1 Default Item for In Restaurant Orders
- 1.2.4.2 Default Item for Delivery Orders
- 1.2.4.3 Item with upcharge
- 1.2.5 Combo Meal Group (Sides Group)
- 1.2.6 Combo Meal
- 1.2.1 Combo Menu Item
- 1.1 Combo Configuration
- 2 Sanity Configuration
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.
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.
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
Dynamic Combos
RBI and Oracle recommends using Dynamic Combo Meals, that means having a single Combo Meal which sides (side and drink) can be upgraded from Small to Medium and to Large.
Hence, we would have only one Whopper Combo whose sides can be upgraded form Small to Medium and Large.
Combo Naming conventions
The Combo Meal name should have the same name as its Main Item suffixed by the word “Cmb”.
If the combo main item is a Whopper then the combo name should be Whopper 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.
Major Group: See brand specific Major Group standards.
Family Group: See brand specific Family Group standards.
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 & 1st and 3rd Party Delivery (Price Sequence will differentiate the channel)
Other Sequences could be used in case different behavior is required for different service modes or order channels. See Menu Item Price section below.
Sequence 1: In Restaurant & 1st Party Delivery (Price Sequence will differentiate the channel)
Sequence 2: 3rd Party Delivery and 3rd Party non integrated/manual 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:
1002 - Combos Lunch
or
1004 - Combos Breakfast
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>
Service mode | Definition Sequence | Price Sequence |
---|---|---|
In-restaurant | 1 | 1 |
1P Delivery | 1 | 2 |
3P Delivery | 1 | 3 |
3P Delivery non-integrated | 1 | 4 |
If you need different behavior for 3P delivery and 3P delivery non-integrated, you can use a different definition sequence.
For example,
3P delivery could use Definition Sequence 2 and Price Sequence 1.
3P non-integrated could use Definition Sequence 2 and 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.
NOTE: Simphony only allows a total of 9,999 Combo Meal Groups.
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)
Set the Ala Carte Item to be the default for all Order Types including “no” Order Type: 1, 2, 3, 4, 5, 6, 7, 8, 9
When necessary, set the amount to be charged for the item inside the combo using the price tab.
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, Lunch Sides, Breakfast Sides, Small Sandwiches, …
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)
For the Item that will be selected by default when the combo is sold, set the options to make the item default for all Order Types including “no” Order Type: 1, 2, 3, 4, 5, 6, 7, 8, 9
Sizing: For each item in the group set the equivalent item for size 1 (Small), 2 (Medium) and 3 (Large)
Set the size only if the Item of the equivalent item size is included in the group.
Size 4 (Kids) can also be used.
Premium items like Milk Shakes may not have sizes, hence do not set any size.
When necessary, set the amount to be charged for the item inside the combo using the price tab.
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.
Primary must always be the group that contains the main item of the combo.
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.
The Size on Dynamic Combos is achieved through Size Item 1 to 4 in the Combo Meal Group configuration of each Combo Group Item.
Size 1 = Small
Size 2 = Medium
Size 3 = Large
Size 4 = Kids
Charging for larger size side
The amount charged for each item inside the Combo Meal is set the Combo Meal Group configuration of each Combo Group Item that needs to be upcharged.
Most of the markets will use the Combo Meal Price as the price of the combo including the default Combo Group Items and will set prices for the Combo Group Items that needs to be upcharge.
In some other markets, the Combo Meal price may be zero and each Combo Group Item will have a price defined to compose the Combo Meal price.
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
Menu Item Definition
Menu Item Price
The Whopper Combo have price 139.00 for In Restaurant (Definition Seq 1 and Price Seq 1) and price 149.00 for 1p Delivery (Definition Seq 1 and Price Seq 2).
This also means the Combo is available for both In Restaurant and 1p 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 (Main Item)
Combo Meal Group (Drinks Group)
Default Item for In Restaurant Orders
Default Item for Delivery Orders
Item with upcharge
Combo Meal Group (Sides Group)
The sides group follows same rules as the 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 ispriceSeq
2).Definition sequence kept constant to a value of 1.
Example for a large combo:
Service mode | Example PLU | definitionSequence (applied automatically) | priceSequence (applied automatically) | Size |
---|---|---|---|---|
In-restaurant | 1234 | 1 | 1 | Large |
1P Delivery | 1234 | 1 | 2 | Large |
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:
Combo structure | Combo PLU | Main Item PLU | Comboslot PLU | Comboslot item PLU |
---|---|---|---|---|
The combo document is structured as follow:
| The combo document uses a sizeBasedPLU.
| The main item in the combo is an item document, which uses a separate constant PLU because it’s an item. Guide on items: Oracle Config - Items
| Comboslots documents contain references to the comboslot items. In the combo, these documents use the Ignore PLU as they’re not needed by the POS.
| As mentioned, comboslots have a list of available comboslot items linked. Since these are items, they will have their own Constant PLU.
|