Default/legacy behavior to apply different Config Offer types through offers page

Today the promotion code only supports Config Offer type Combo, Picker and Offer Discount.

Offer Combo/Picker

The behavior will be the same: when adding to the cart the user will be redirect to the menu item to configure the item and then apply to the cart:

Offer picker.mp4

Offer Discount

Different from Offer Picker or Offer Combo, the Offer Discount is added directly to the cart when applied. The user don't need to be redirected to the menu page.

Discount Offer demonstration.mp4

Config Offer type that we support today at checkout page

Offer Discount: This is the only offer that we are supporting on the checkout page today
Combo and Picker: Not supported today
- Current limitation: we need to bring the necessary logic for the other types of Config Offer to the checkout page when applying a promo code through our new feature/field
- We are analyzing this subject on a PoC: IBFEC-1505 - Getting issue details... STATUS
  - The PoC will be useful to prove if we'll be able to bring the necessary logic and detect if this can cause any problems to the checkout page or the offers page legacy logic

PoC results and proposal of solution

Work in progress - to be filled

Assumptions and business rules

Questions and assumptions

Q: Today, when we redeem a promo code offer that has the type Combo/Picker on the offers page and the user clicks to add the offer to the cart, the application will redirect the user to the menu item (combo/picker) for the selected offer. On the menu page, the user can customize the Combo/Picker if allowed. If the user adds a Config Offer that has this type (Combo/Picker) through the checkout page, he'll not be able to customize the item. What will we do here? Can we consider the default options for the Combo/Picker?

Offer customization.mp4

A:

Business rules