Coupon Applied But Not Displayed in Order on Enatega Multivendor Customer Website.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript, react-native
- Domain
- frontend
Research direction
Start by reproducing the coupon flow on the Enatega Multivendor customer website, then trace where the applied coupon reaches the order summary. Done means the order summary visibly shows the applied coupon and its discount after a customer applies a code.
Written by the indexing model from the issue text.
Description
Issue: Coupon Applied But Not Displayed in Order on Enatega Multivendor Customer Website.
Description:
A problem exists on the Enatega Multivendor customer website where, after a customer successfully applies a coupon code, the applied coupon is not displayed or reflected in the order summary. This issue results in a lack of clarity regarding the coupon's application and its impact on the order.
Impact:
User Confusion: Customers may be confused when they apply a coupon, but the applied discount does not appear in the order summary. This can lead to uncertainty about whether the coupon was successfully applied.
Loss of Transparency: The absence of the coupon's visibility in the order can reduce transparency in the ordering process, which is essential for trust and customer satisfaction.
Missed Savings: Customers may miss out on savings or incentives provided by the coupon, leading to potential dissatisfaction.
Steps to Reproduce:
Open the Enatega Multivendor visit the customer website.
Select items for an order.
Proceed to the order summary or checkout page.
Apply a coupon code to your order.
Observe that, after applying the coupon, the order summary does not reflect the coupon's application, and the discount is not visible.
Expected Resolution:
The applied coupon should be clearly displayed in the order summary, showing the discount and ensuring transparency in the order process.
Screenshot 2023-10-19 122710
Activity
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raymondjames090/uber-eats-app-clone-using-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2069 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2003 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raymondjames090/uber-eats-app-clone-using-react-native#2002 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#1979 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
raymondjames090/uber-eats-app-clone-using-react-native#1978 ·
All issues in raymondjames090/uber-eats-app-clone-using-react-native
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100