Negative Values Allowed in Discount, Tip, Price and Addons Fields

Open

#1,652 opened on Jun 11, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 58/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: javascript, react-native
Domain: frontend

Research direction

Start in the Enatega Multivendor Admin Dashboard forms for discount, tip, price, and addons, then reproduce the issue by entering a negative value such as "-10". Done means each financial field rejects negative values and displays an error or validation prompt.

Written by the indexing model from the issue text.

Description

Description:
During testing of the Enatega Multivendor Admin Dashboard, a critical issue was identified where fields such as discount, tip, price and addons allow the entry of negative values. This behavior is inconsistent with standard practices and poses a risk to accurate financial calculations, potentially leading to incorrect order totals and financial discrepancies.

Steps to Reproduce:
Log in to the Enatega Multivendor Admin Dashboard.
Navigate to sections where fields for discount, tip, price or addons are present.
Attempt to enter a negative value (e.g., "-10") in any of these fields.

Expected Behavior:
The application should restrict the entry of negative values in fields related to financial transactions, such as discount, tip, price and addons. An error message or validation prompt should be displayed, indicating that negative values are not allowed.

Actual Behavior:
The application allows the entry of negative values in fields such as discount, tip, price and addons without providing any error or validation message.

image

Activity

Dominant language: JavaScript
Stars: 0
Forks: 0
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing 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.