Content Comparison

Modifiers

• 2 dimensions - service mode and quantities (multipliers).

• We can distinguish between service modes and multipliers using a combination of the 3 IDs.

  • Most markets support 2 levels of modifiers for mobile ordering: ADD and NO.

    • Remove (“No”). No multiples available.

    • “Add”, which will have several quantities (multiples for each quantity – e.g. 1x ketchup, 2x ketchup).

• priceSequences will be used for determining the ADD and NO modifiers, as well as pricing across service modes:

  • priceSeq 2 = In Restaurant Add

    priceSeq 3 = In Restaurant No

    priceSeq 6 = Delivery Add

    priceSeq 7 = Delivery No

• A single Sanity document will be used for each modifier, with a single PLU used for both in-restaurant and delivery service modes.

• For Add and No, a toggle will be added to the Sanity document for the item.

  • Option 1 (tentative):

    • A single modifier document called Ketchup in Sanity.

    • If a given item needs to have Ketchup, it is added under Item --> Options as it is currently done (example here).

    • 

    • Upon clicking on Ketchup under Options, today we see additional Options (Item --> Options --> Options) for ketchup (its modifier multipliers):

    • 

    • Instead of defining Add and No modifier multipliers and adding via Item --> Options --> Options, we will have a selection option for Add and No under Item --> Options, available by default for all modifiers added.

      • If a guest cannot remove a modifier from an item but can still add more of it --> We will have the Add toggle turned on.

      • If a guest can remove a modifier from an item but cannot add more --> We will have the No toggle turned on.

      • If a guest can remove a modifier from an item and can also add more --> We will have both Add and No toggles turned on.

      • If a guest cannot do anything about a modifier from an item, no need to add that modifier under Item --> Options. 

    • Later on, additional toggles (or any other UI mechanism) can be added to allow for multiples of Add (light, heavy, 2x, 3x.).

    • Note: The new toggles will be specific to Oracle POS in order to not introduce breaking changes for existing markets. For example, BK UK having both NCR that uses Modifier Multiplier, and Oracle that will use the toggles. For NCR, the PLUs will be sent from the modifier multiplier document as it is done today and new toggle values won’t be sent. For Oracle, the modifiers will be managed via toggle values.

• No PLU defined for modifier multiplier.

• Similarly, for management of modifier multipliers beyond the ADD and NO values for modifiers (light, heavy), other pricing sequences or definitionSequence can be used later.

• Different quantities of modifiers (e.g. 2 bacons) will be managed with the Quantity field.

• Khumbu will manage the mapping for PLU+definitionSeq+PriceSeq as shown in phase 2 on the slide deck.

  • In cases where a modifier is not available in delivery service mode specifically (while available for pickup), this could be managed via empty vendor config in Sanity for display in whitelabel. (The pricing for the modifier will still be managed via the mapping with Khumbu).

Alternative to using PricingSequence or DefinitionSequence for Multipliers - the Quantity Field: This will be enabled by RBI Tech platform by utilizing the multiconstant PLU solution. Having the multiconstant PLU solution work will require additional engineering effort (e.g. there are gaps in partnersAPI, and potentially Menu Service in general).

To improve the experience of the operator, a single Sanity document should be used for management of modifiers on Sanity later on. Therefore, removing the modifier multiplier document from Sanity completely.