Table of Contents
...
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.
...
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