2 dimensions - service mode and quantities (multipliers). We can distinguish between service modes and multipliers using a combination of the 3 IDs. 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 modifier. 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.
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. -20241031-101500.png?version=1&modificationDate=1730369764277&cacheVersion=1&api=v2&width=380) -20241031-101503.png?version=1&modificationDate=1730369763758&cacheVersion=1&api=v2&width=372) |