Absence of Delivery Fee, Service Fee, and Minimum Order Price Options in Enatega Multivendor.

Open

#1,798 opened on Jul 17, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 35/100

Issue type: Feature
Clarity: Needs clarification
Activity status: Quiet
Tech stack: javascript, react-native
Domain: full-stack

Research direction

Start by locating the settings or configuration screens and the pricing logic for orders in the Enatega Multivendor application. Clarify how delivery fees, service fees, and minimum order price should be stored and applied before implementation. Done means users can add, configure, and modify all three options and see them reflected in pricing.

Written by the indexing model from the issue text.

Description

Issue: Lack of Delivery Fee and Service Fee Configuration Options in Enatega Multivendor
Description:
The Enatega Multivendor currently lacks essential configuration options for setting and adjusting delivery fees and service fees. Users require the ability to configure these parameters according to their business requirements.

Impact:
Configuration Limitations: The absence of these options restricts the flexibility and adaptability of the platform for businesses.

User Expectations: Users expect to have control over delivery and service fees, and the lack of these options may affect their ability to effectively manage their services.

Steps to Reproduce:
Access the Enatega Multivendor application's settings or configuration options.
Attempt to set or modify delivery fees and service fees.
Observe that there are no options available for configuring these parameters.
Expected Resolution:
It is essential to implement the functionality to add, configure, and modify delivery fees and service fees within the Enatega Multivendor application or website. This will provide businesses with greater control and flexibility over their pricing structure, enhancing user satisfaction and the adaptability of the platform.

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.