Commission Rates Saving Issue with Missing Status in Enatega Multivendor Admin

Open Beginner friendly

#1,718 opened on Jun 23, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 68/100

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

Research direction

Start by locating the Enatega Multivendor Admin flow for managing and saving commission rates, then reproduce the missing feedback described in the issue. The work is done when saving displays a confirmation status for successful updates and communicates errors when the operation fails.

Written by the indexing model from the issue text.

Description

Description:
When attempting to save commission rates in the Enatega Multivendor Admin, the rates are successfully saved; however, there is no corresponding status displayed, creating ambiguity for users. This lack of status information makes it challenging for administrators to verify whether the changes were applied successfully or if there were any errors during the process.

Steps to Reproduce:
Log in to the Enatega Multivendor Admin.
Navigate to the section for managing commission rates.
Modify or set new commission rates.
Save the changes.

Expected Behavior:
After saving the commission rates, a status message should be displayed confirming the successful update. This status information is crucial for administrators to ensure that their changes were applied as intended.

Actual Behavior:
Commission rates are saved successfully, but there is no accompanying status message, leaving users uncertain about the outcome of the operation.

13.12.2023_14.47.23_REC.mp4

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.