Context

In a few markets, Oracle and RBI have differing approaches to pricing combos, leading to challenges in displaying a coherent pricing structure. Specifically:

  • RBI uses a fixed price for combos, with additional charges applied based on user selections of drinks and sides.

  • Oracle, in certain markets, does not have a set price for combos; instead, combo prices are calculated based on the main item price plus the prices of the selected sides.

This document outlines the requirements for adapting the current system to resolve these discrepancies and ensure accurate pricing display at both the Section level and the Product Page.

Combos at RBI are configured as follows:

Both main item and combo slots are references to items at the Menu.

The following structure will be used as examples for each of the requirements.

image-20250217-185710.png

Requirements

Menu Price Sync

This refers to syncing the prices from the POS to RBI via Partners-API.

The main requirements lie on the idea that:

→ Some processing needs to be done at the price for the combo

→ Some processing needs to be done at the combo slots price

To do it, Khumbu needs to know two things:

→ What is the default comboslot

→ What items compose a comboslot

How Khumbu should retrieve this information, the options being:

  1. From Sanity via the Get Brand Menu endpoint

  2. Directly from Oracle (if such a capability exists, Jean mentioned it might not.)

Note that the FZ and Sanity operators will ensure that the default combo slot is the cheapest one, this will be a requirement for this solution. Explained in more detail at https://rbictg.atlassian.net/wiki/spaces/TRX/pages/5532286978/Combo+Price+Requirements+to+Khumbu#Configuration-Requirements-for-the-Operators-%26-Franchisees.

Combo and Combo Slots Pricing

Total Combo Price Calculation:

RBI expects Khumbu to provide pricing for the combo by summing Oracle’s combo price, main item price and the prices of the default combo slots.

The default combo slots should be determined using the agreed strategy based on the two options shared above.

Example 1, showcased in the picture above:

Example 2:

Example 3:

Default Combo Slot Pricing:

RBI expects Khumbu to provide a pricing of 0 for the default combo slot options. They will be considered as baseline of pricing for combo slots.

Example:

Combo Slot Pricing Adjustments

For comboslots, we expect to receive the price that we should add to the total combo price.

If the comboslot is included in the base combo, then price is 0 (e.g. Fanta).

If the comboslot is premium, then price will be higher than 0 (e.g. Red Bull).

What are the combo slot options should be defined using the agreed strategy from the 2 options above.

Example:

PLU Concatenation for Pricing Combo Slots

RBI expects to receive its price using PLU concatenation in the following manner: ${comboPlu}-${comboSize}-${mainItemPlu}-${comboSlotPlu}.

Example:

Configuration Requirements for the Operators & Franchisees