Menu - Agreements

Contents

Fiscal integrations will change market by market. There’s no standard.

Khumbu will concatenate 3 IDs for items, combos, modifiers: PLU-DefSeq-PriceSeq.

For items:

1 dimension - service modes.
We can distinguish between service modes using any of the 3 IDs.
Recommendation: Use priceSeq and constantPLU, keep definitionSequence constant.

For modifiers,

2 dimensions - service mode and quantities (multipliers).
We can distinguish between service modes and multipliers using a combination of the 3 IDs.
Recommendation: Use priceSeq and single constantPLU per modifier, keep definitionSequence constant, no PLUs to be defined for modifier multipliers separately.

For combos,

2 dimensions - service mode and size.
We can distinguish between service modes and size using a combination of the 3 IDs.
Recommendation: use priceSeq for service mode, and sizeBasedPlu ID ('large', 'medium', 'small') to distinguish size. Same PLU is used for different combo sizes.

Configuration in Sanity (to be determined)

Suggestion: Configuration in Sanity at a brand/market-level which abstracts the definition and price sequence from the operator.
- Pros:
  - The operator only inputs the PLU.
- Cons:
  - Modifiers use other priceSeq.
  - Not seeing the full PLU in Sanity also complicates debugging.
Alternative: Showing the breakdown of the 3 fields in Sanity (PLU, DefSeq, PriceSeq).
- Pros:
  - More intuitive for operators and removes any 'middleware' logic from Sanity.
- Cons:
  - More prone to operator errors, likely more work for operators as well.
  - Additional development work to extend the Sanity UI and ensure consistency.

RBI sends the delivery amount to Oracle under serviceChargeId. Oracle will return it as part of the pricing call and accepts is as injection.
We can use multiple serviceChargeId – e.g. delivery fee ($) and service fee (%).
https://docs.oracle.com/en/industries/food-beverage/simphony/19.4/stsgg/F56815_08.pdf (page 123)