...
Modifiers allow guests to customize items. They can be added, removed, increased or decreased. For example, you can remove lettuce, tomato and pickles from a Whopper.
Oracle Configuration
Condiments are a type of menu item that describes the preparation of another menu item. Condiment menu items can include traditional condiments placed on food such as ketchup, mustard, and mayonnaise. They may also include
...
ingredients found in a menu item which a guest may add or exclude from their order, such as onions or tomatoes. Condiments can also represent preparation instructions about how an item is prepared such as meat temperature for a steak (rare, medium, or well), egg preparation (scrambled, sunny side up, or over easy), and special requests like sauce on the side.
Condiments are added to other menu items; they cannot be added on their own. The item a condiment is added to is the parent item, while the condiment is a child item.
Dynamic Modifiers
RBI and Oracle recommends using Dynamic Modifiers, that means having a single Menu Item for the condiment and use Condiment Prefixes.
Hence, we would have only one Bacon with Condiment Prefixes No, Add and Sub instead of having one Condiment No Bacon and another Condiment Add Bacon.
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 item 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: 6 - Modifiers
Major Group: 6000 - Condiments
Family Group: 60002 - Condiments
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.
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 & Delivery (Price Sequence will differentiate the service mode)
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: Each Condiment will have its own Menu Item Class created as defined in the next section.
Print Class Override: 0
Menu Item Price
Level: Enterprise/brand/country/<price tier zone>
Price Sequence
Definition Sequence | Price Sequence | Modifier |
|---|---|---|
1 | 1 |
|
1 | 2 | Add (In Restaurant) |
1 | 3 | No (In Restaurant) |
1 | 4 | Sub (In Restaurant) |
1 | 5 |
|
1 | 6 | Add (Delivery) |
1 | 7 | No (Delivery) |
1 | 8 | Sub (Delivery) |
Optionally, in case more flexibility is required meaning different behavior for the Menu Item sold in different modes then different Definition Sequences can be used.
Definition Sequence | Price Sequence | Modifier |
|---|---|---|
1 | 1 |
|
1 | 2 | Add (In Restaurant) |
1 | 3 | No (In Restaurant) |
1 | 4 | Sub (In Restaurant) |
1 | 5 |
|
1 | 6 | Add (1p Delivery) |
1 | 7 | No (1p Delivery) |
1 | 8 | Sub (1p Delivery) |
2 | 1 |
|
2 | 2 | Add (3p Delivery) |
2 | 3 | No (3p Delivery) |
2 | 4 | Sub (3p Delivery) |
2 | 5 |
|
2 | 6 | Add (3p manual Delivery) |
2 | 7 | No (3p manual Delivery) |
2 | 8 | Sub (3p manual Delivery) |
Condiment items availability
Condiments are defined as Menu items in Simphony and Condiment availability follows same rules as Ala Cart items.
A special attention is required on how condiment price sequences are defined, see Availability & Pricing Rules. In this perspective apart of being available in the restaurant or in the channel, a condiment will also be available or not available in a “modifier mode”, Default, Add, No, …
Example of a charged condiment, see that 9011005 is available and charged in Restaurant and Delivery and is charged at $19 when Added to an Ala Carte item in an In Restaurant Order and at $22 when Added to an Ala Carte item in an In Delivery Order. Same Item is also available at No and Sub modifier levels.
...
Example of a non charged condiment, see that 9012007 - Lettuce is not charged even when Added to an Ala carte item.
...
Example of condiment not available, see that 9005006 - Hot Cake has no price set hence it is not available.
...
Default condiments
The Ala Carte items are formed by a list of ingredients or condiments that we normally call the recipe. In Simphony the recipe is called Default Condiment.
The Default Condiment is configured on EMC as a Condiment Set and is linked to the Menu Item as default Condiments.
Condiment set should be created with same Number and same name as the Menu Item.
...
Then associated with the Menu Item.
...
A condiment that is part of the Ala Carte item default recipe must be included in a Condiment Set associated to to the Ala Carte item as Default Condiment however it is only available if the Menu Item related to the condiment is available.
A default condiment is only charged if the quantity is increased from the default, the price charged for the condiment in the Ala Carte item is the price of the condiment Menu Item in the “modifier mode” and the channel, the price then must be multiplied by the quantity added to calculate the total.
Condiment Groups
As the name states, Condiment Groups are groups of condiments used to define what condiments can be added or removed from the classes of Ala Carte Items.
RBI have defined a list of condiment groups based on the classifications of the Ala Carte products for each brand, the list of condiment groups is used to associate condiments to combo groups as Member Condiments and Ala Carte items to Combo Groups as Allowed Condiments.
Association is made through Menu Item Class, each Condiment has its own Menu Item Class, the reason for having one Menu Item Class per condiment is to create flexibility and allow condiments to be associated to multiple groups in any combination.
The Menu Item Class of the condiment is associated to the list of Combo Groups the condiment will participate as a Member.
Note that default condiments must be included in the Member Condiment Groups of the Ala Carte item class in order to the condiment to be displayed in the POS.
...
In the other hand, Classes for Ala Carte items are created by the class of Ala Carte items.
RBI have defined a list of Menu Item Classes based on the classifications of the Ala Carte products for each brand and Ala Carte products are associated to their Menu Item Class based of the classification of the product.
The Condiment Groups that will be available for the Class of Ala Carte products are associated with the Menu Item Class as Allowed Groups.
...
Sanity Configuration
| Info |
|---|
Most of the modifier content configurations will be the same as any other POS except for the PLU Mapping (Vendor Configs) and configurations for modifiers and modifier multipliers within Item → Options, for . For the shared content configurations please refer to the [DEPRECATED] Modifier page. |
For Definition Sequence and Price Sequence PrefixID fields, you (the operator/FZ) will not need to do manual configurations. Just for your information:
priceSequences will prefixId will be used for instead of the priceSequence for determining the ADD and NO modifiers, as well as pricing across for in-restaurant and delivery service modes. PrefixIDs are not fetched from Oracle, static values are provided per brand/market.
Definition sequence will be kept constant to a value of 1.
Example PLU | definitionSequence | priceSequenceprefixID |
|---|---|---|
A single PLU per modifier, e.g. 123456. | 1 in all cases (1P). | priceSeq 2 prefixID 9001002 = In Restaurant Add priceSeq 3 prefixID 9001001 = In Restaurant No priceSeq 6 prefixID 9001022 = Delivery Add priceSeq 7 prefixID 9001021 = Delivery No |
| Info |
|---|
Only 2 levels of modifiers are supported for mobile ordering: ADD and NO. Additional modifier multipliers (more granular levels of customization such as ‘heavy ketchup’, ‘light ketchup’) are not supported for mobile ordering at this time. |
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 modifier, no PLUs will be defined for modifier multipliers:
...
Additionally, a single Sanity document (page) will be used for each modifier, with a shared single PLU used for both in-restaurant and delivery service modes.
All modifiers for a given item will be configured under Item --> Options:
...
[IMAGE WITH THE NEW UI COMPONENT FOR ADD/NO]
| Note |
|---|
Note that the above UI selection options can be used only for the Oracle POS. They cannot be used for other POS vendors such as NCR. |
...
Scenario
...
UI Configuration
...
If a guest can remove a modifier from an item and can also add more.
...
Both the Add and No UI selections will be selected/turned on.
...
If a guest cannot remove a modifier from an item but can still add more of it.
...
The Add UI selection will be selected/turned on.
...
If a guest can remove a modifier from an item but cannot add more.
...
The No UI selection will be selected/turned on.
...
If a guest cannot do anything about a modifier from an item.
...
This is the structure of modifiers in Sanity:
...
Items contain options (e.g. Bacon), and each option has an Item Option Modifier document, which contains references to the modifier multipliers (e.g. No Bacon, Regular Bacon, Extra Bacon). Each modifier multiplier references a modifier.
| Note | ||||||||
|---|---|---|---|---|---|---|---|---|
The modifier setup experience will soon be simplified and enhanced.
|
The structure remains the same, but the PLU configuration differs. As you can see in the image above, the last 3 documents contain Vendor Configs, which is where PLUs are configured.
| Info |
|---|
Note that a modifier can’t be premium and default at the same time. If a modifier is default, then it’s part of the item or combo and will bring no extra cost. |
For Oracle we will use the field PLU Configs instead. This is the required PLU configuration for Oracle:
Item Option Modifier
PLU Configs → Oracle (In-Restaurant & Delivery) → Constant PLU type → Input the single modifier PLU
Modifier Multiplier
PLU Configs → Oracle (In-Restaurant & Delivery) → Ignore PLU type
Multiplier → Set multiplier quantity (e.g. 0 for “No”). The multiplier quantity must be an integer.
Modifier
PLU Configs → Oracle (In-Restaurant & Delivery) → Ignore PLU type
| Note |
|---|
The enable-multiplier-as-quantity flag should be configured by CSM for modifiers' pricing to be calculated correctly in mobile ordering with Oracle POS.
The PLU configuration for other POS vendors will remain the same. |