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).

• Only 2 levels of modifiers will be supported for mobile ordering: ADD and NO. Additional modifier multipliers (more granular levels of customization such as ‘heavy ketchup’, ‘light ketchup’) won’t be supported for mobile ordering in the initial scope.

• 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 under item → Options.

  • 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:.

• 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.

• To understand if a modifier document in Sanity is ‘'Add’' and ‘'No’' to be able to assign the correct priceSequence, the UI selections for these options in Sanity should be exposed to Khumbu. the UI selections for these options in Sanity should be exposed to Khumbu.

  • Question: Will we be relying on some common interface with Khumbu like add-delivery/no-pickup or will we send actual PLUs like remove bacon 300-1-3 for example. In the second case we would need to maintain a translation between price sequence and modifier variant + service mode?

• 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).

Open questions to answer in the implementation:

• Whitelabel changes to consume prices of modifiers since we won't manage it the way we do now - assigning separate PLU per modifier multiplier

• how are we going to handle the mapping between Sanity toggles and price sequences for modifier multipliers (Add/No + service modes)

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.

Webhooks

• Details of all notifications (webhooks) are available in the API documentation here and here.

• For menu P&A changes:

  • We subscribe to the Configuration Notification webhook.

  • Configuration notification runs on a scheduled job every 15 minutes for pricing changes, whereas it is near real-time for availability changes.

  • The notification doesn't specify what item(s) have become unavailable at a store-level, the whole menu needs to be fetched.

  • Price update can take up to 30min to get to the restaurant. CALC is a cloud call, POST will have old price. A manual update can be forced using the “Update” button in the POS.

• For order status changes:

  • We subscribe to the Check Notification webhook.

  • Order statuses depend on the KDS setup in the store. 2 statuses are received in most cases: Submitted & Done

  • Check notification statuses are based on what happens in the KDS.

  • On the post a transaction, we must say notificationOption - “enabled”: true. This means that when the check is submitted, it will track notification from KDS.

• There is no webhook to get store status updates.

• Q&A

  • How do we know that an order has been cancelled (voided) at the POS? Is there a notification for that? → Only a check that was sent in an open state can be cancelled via STS.   If a check is voided after it has been closed there is no notification.

  • What POS action triggers each of the following notifications: Uninitialized, Submitted, Prepared, Packaged?

  • Uninitialized - No notifications options enabled

  • Submitted - Check sent with notifications options enabled

  • Prepared - When all prep KDS have bumped their orders (if using)

  Packaged - When expo KDS has bumped the order

  ?

  • Uninitialized - No notifications options enabled

  • The submitted status indicates that the order has been sent to the kitchen for preparation. 

  • The prepared status indicates that the order has been prepared and is pending packaging. 

  • The packaged status indicates that the order has been packaged and is ready for pick up. 

  • You explained that the configuration notification runs on a scheduled job every 15 minutes for pricing changes, and that the price update can take up to 30min to get to the restaurant. If I understood correctly, the restaurant can work around this time lag via the manual update using the “Update” button in the POS. Is there a similar workaround for digital to avoid price mismatch during that up-to-15-minutes gap period? → There is no way to speed up the process for the application cache to update in the cloud.

  • If an order is injected with a pickupTime in the future, can it be manually sent to the kitchen (‘fired’) from the POS? If so, will we get notified of that status change? –> If you use pickupTime for a future dated check, whenever that check is fired, you will receive a submitted response to your webhook URL. That being said, I (Oracle colleague) would consider using fireTime.