Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

REFUNDS - OPTION ADMIN SETTINGS - DECIDE WHO REFUND ADMIN COMMISSION - [STRIPE EXPRESS: Default Automatic Refund Validation by Admin] #2267

Open
Sophie-2e opened this issue May 7, 2024 · 2 comments

Comments

@Sophie-2e
Copy link

Sophie-2e commented May 7, 2024

Is your feature request related to a problem? Please describe.

[FEATURE REQUEST] - Related to Dokan Support Ticket #56186 and #58242

Context:

  1. Based in Europe, it is mandatory to have 30 days warranty on all products, so 30 days to refund an order.
  2. using Stripe Express:
    a. Default behaviour: Refund got automatically accepted in Admin side
    b. Option that admin pays stripe fee for the seller

CURRENT DEFAULT BEHAVIOUR: If the seller refunds an order, the admin loses the commission.

This makes sense when the marketplace is a MVP and is not established yet, as the admin is putting marketing efforts (seo, sea, social media promotion, efficient UX etc...) so there is no specific added value yet. Then why not, the admin can only take a commission when the seller successfully makes a sale and under the condition that no refund has been issued to the customer.
Even though, it still has limitations:

  1. when the admin and the sellers use Stripe Connect: the refund is automatically accepted in the admin side with Stripe Express, so the admin cannot refuse any refund if the admin does not agree.
  2. when the admin is paying stripe fee for the sellers: the admin is losing money if the order is refunded as there is a Stripe fee for processing payment order and then refund the order, so if admin also loses the commission, his/her balance becomes negative on the refunded order. So not fair for the admin.

On top of it, once the marketplace is established it does not make sense. It is not fair for the admin to lose the commission as the marketplace admin is mostly in charge of making the marketplaces known and promoting sellers and products on the marketplace across internet with various techniques from SEO, to good UX, to social media promotion and SEA so admin should keep the commission because the goal of the admin is that seller succeed to make the sale. Then, it is the responsibility of the sellers to sell good products to satisfy customers; and so if the customers are not satisfied with the products once they have received them. The seller should take full responsibility.
It is thanks to admin-marketing efforts, as the sale would have never been possible if the admin had not built a strong marketplace and made sure it became a known platform where people go to shop.

Describe the solution you'd like

In Dokan Settings > Selling Option Settings > Commission section > have an option that can enabled by admin 'Refund Admin Fee Recipient' such as we have for Shipping Fee Recipient, Product Tax Fee Recipient and Shipping Tax Fee Recipient:

Screenshot 2024-05-08 at 01 15 05

With this option, the admin can decide what the best is for the marketplace according to the marketplace settings/environment/development stage.

Describe alternatives you've considered

None

Additional context

No response

@mralaminahamed mralaminahamed added 💰 StripeExpress Needs: Discussion Some decisions are needed for this task to be done and removed 💰 StripeExpress labels May 9, 2024
@mralaminahamed
Copy link
Member

need discussion with @mrabbani vai.

@mralaminahamed mralaminahamed added Type: Enhancement Analysis and removed Needs: Discussion Some decisions are needed for this task to be done labels May 14, 2024
@mrabbani
Copy link
Contributor

@imtiaz-pranto vi, I think that we need to analyse this feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants