Oracle Config - Items
- Silva, Carlos
- Benet, Anton
- Yildirim, Semih
- Marrara, Jean
Contents
Items are the single orderable products that will be displayed in the platform, such as Whopper® Burger or Coca Cola Medium.
Oracle Configuration
Ala Carte Items are dishes that can be ordered separately, rather than as part of a set or package. The list includes, but is not limited to sandwiches, beverages and sides.
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: See brand specific Reporting Group standards: BK - Reporting Groups
Major Group: See brand specific Major Group standards: BK - Major Groups
Family Group: See brand specific Family Group standards: BK - Family Groups
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 & 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: See brand specific Menu Item Class standards.BK - Menu Item Classes
Print Class Override: 0
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.
Pricing & Availability
The price of an A la Carte item is price defined in the Menu Item Price section above. Both Definition Sequence and Price Sequence are used to determine the price that should be charged for an Item in a specific channel.
Apply the same logic of the pricing to verify the item availability. Availability is determined solely by the availability of the Menu Item Price. The Menu Item availability is based on the existence of a valid and not expired price.
In the example below the Whopper is available in restaurant, delivery and at non integrated delivery.
The price to be charged is 109 for in restaurant and 119 for delivery and manual delivery.
Notice that prices are set and Effectivity is active and not expired.
In the next example the 2102002 - Sm Regular Pepsi is only available to be ordered in restaurant and price is 39.
In the next example the item 1001137 - Chipotle Stacker King is available from 1/1/2025 to 3/31/2025. It is not available before 1/1/2025 and after 3/31/2025.
Sanity Configuration
Item content configurations will be the same as any other POS except for the PLU Mapping (Vendor Configs), for those please refer to the Item page.
For Definition Sequence and Price Sequence fields, you (the operator/FZ) will not need to do item-level 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.
Service mode | Example PLU | definitionSequence | priceSequence |
|---|---|---|---|
In-restaurant | 1234 | 1 | 1 |
1P Delivery | 1234 | 1 | 2 |
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 item with pricing. A ConstantPLU has a one-to-one relationship with a given Product: