Page Comparison

Table of Contents

...

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

    Jira Legacy
    server System Jira serverId 255417eb-03fa-3e2f-a6ba-05d325fec50d key IBFEC-1505

    • 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

...

• Get the promotional Combo/Picker from the incentives array (configured on the Config Offer document) by adjusting the graphql query to get the whole item

• Transform the item and add it to the cart:

  • Use the transformMenuObjectToCartItemto convert the item configured on In-App Benefits

    • This method will be responsible for getting the price, modifiers, etc

    • This method needs to be properly filled out to get the correct data

    • Use ProductWizardUtils.ComputeSelectedOption to transform the itens correctly. This is important for Picker. The method will convert the Picker to a regular item

    • Use transformUserSelectionsComboToComboSlotSelections together with ProductWizardUtils.SetDefaultSelectionsto get the default values for a Combo item. As we are adding the offer Combo directly through the cart, we need to “select” the defaults for the user. This is important because we need the information in Recent Orders, etc.

  • Use the upsertCart from useOrderContext to add the promotional item to the cart

Problem with this solution: the Combo/Picker that comes from the Config Offer document will not have the vendorConfigs for the children items (sub-items) and without this information, when we add the item to the cart, we'll have only the main item, without the sub-items/modifiers.From what I understood, if an item doesn’t have the vendorConfig information, it will be considered invalid.

...

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?

...

A: We should keep the default behavior if possible:

...

• Offer configuration (invalid PLU in Sanity)

• PLU not configured or is not available for the selected restaurant

In this task,