Table of Contents
...
IBFEC clone card:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
...
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
...
notify the user about that
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. How this flow will be step by step:
The user enters a promo code and click at the apply button
If the entered promo code was already redeemed/unlocked we’ll close the “Add promo code” modal (we’ll not add a duplicated offer as we do today) and then we’ll show the toast with a proper message
Instead of show “Promo Code added to Offers”, in this case that we are fixing, 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
...
In my opinion, I do not see any problem with this solution
Technical flow proposal
Add a validation flow that will start when the user tries to “apply” an offer that he already has on his list
If the offer already exists in the list, we’ll not redeem another one and will show a toast notifying the user about that (the proposal example above)
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
If you not agree with the proposal feel free to raise another