Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Table of Contents

IREQ: https://rbictg.atlassian.net/browse/IREQ-1584

IBFEC clone card: IBFEC-1659 - Getting issue details... STATUS

Problem to be solved

Today, the user can redeem/unlock the same offer freely, and with this, we open a flaw:

  • Duplicated offers in the list

record-qa-bug.mkv

In my analysis, this is the root cause of this IREQ. When the user clicks on the second offer in the list, our logic is not prepared to handle a duplicate offer. Talking with Lopes da Costa, Valentina , we understand the following:

  • If the user redeems an offer and doesn’t use it, he should not be able to redeem the same offer again until he uses the already-redeemed one!

    • This will solve these duplication entries and also solve the bug at the same time!

      • When we developed the Promo code at checkout page X config offer type feature, I also added this functionality at the checkout. As the user is not seeing the offer list we should prevent duplication there. With this proposal we’ll keep the same behavior and consistency

PS: I tested, and this will not happen if the user changes between two different offers and then applies one or the other in sequence.

Proposal of solution

Option 1: Validate if the promo code was already redeemed and throw error

  • If the promo code already exists in the list we only closes the “Add promo code” modal and then we’ll show a toast alerting the user the he already redeem/unlocked this offer:

    • The user enters a promo code and click at the apply button

      image-20240301-184002.png

    • If the entered promo code was already redeemed/unlocked we’ll close the “Add promo code” modal and then we’ll show the toast with a proper message

      image-20240301-184235.png

    • Instead of show “Promo Code added to Offers”, in this case, we’ll show “You already have this offer activated”

    • The user will be free to select the offer at the list and then apply at the cart

Advantages

  • Complexity is reduced in this solution

  • We keep the pattern that we already had at the offers page:

    • The user needs to select the offer and then apply if wanted

Disadvantages

  • In my opinion, I do not see any problem with this solution

Option 2: Validate if the promo code was already redeemed and apply the offer for the user (author is not in favor of that)

  • If the promo code already exists in the list we select and the apply the offer at the cart

Advantages

  • We reduce steps that the user needs to do

Disadvantages

  • We will not keep the pattern that we already had at the offers page. This can be an undesired action from the user point of view as we don’t know if he only wants to redeem or if he wants to use the offer

  • For the Offer Discount type, we don’t have so much complexity, but for Combo/Picker, the legacy flow is to send the user to the menu page, where the user can choose to apply or not the offer. I think that redirecting the user without this being an action from him will be a very bad decision

Disclaimer

  • I’m trying to help us here with a path to a solution

  • I’m not a designer or specialist in UI/UX. Perhaps it will be important to validate this with someone

  • We need to validate this with Intl to guarantee that everyone will agree with the changes/fix

  • No labels