[NerdySupportExpert Moumita]

Hi @Picflick,

Thank you for following up on this.

In the latest version, we’ve completely rebuilt the membership flow from scratch. If you check our demo, you’ll notice that subscription plans are now created and managed directly via Stripe and PayPal, rather than relying on WooCommerce subscriptions.

At the moment, coupon/discount support has not yet been implemented. This is because the new system follows how Stripe and PayPal handle subscription products, and we are aligning our discount logic accordingly instead of using WooCommerce’s coupon system.

We do plan to introduce discount support, but it will be designed in line with how these payment gateways manage subscriptions.

We’ll keep you updated as we progress on this.

[NerdySupportExpert Moumita]

Hi @Picflick,

Thank you for your detailed explanation—we completely understand your concern here.

You are absolutely right that upgrading to 5.0.0 will not automatically correct any existing historical data inconsistencies. Since this issue seems to be pre-existing, debugging it directly on the older version can be quite complex due to the legacy data structure and how records were maintained.

That said, if you choose to migrate to MultiVendorX 5.0.0, the system will handle migration of:

All vendors → converted into stores
Their associated commission data

During migration, commission is recalculated based on order status:

Orders with Completed / Processing status → treated as commission paid
Any commissions not marked as paid in version 4.2.42 → reflected in the store wallet balance

Additionally, MultiVendorX 5.0.0 provides a Custom Gateway option, which allows you to manually adjust store balances if needed. This can be helpful in cases like yours where certain vendors are showing inflated or incorrect amounts. You can refer to this here:
https://prnt.sc/CLiHPJGj00ws

Given the nature of the issue, a structured migration followed by adjustment may be a more reliable approach than trying to reconcile inconsistent legacy data directly.

Please let us know how you’d like to proceed—we’re happy to guide you through the migration and correction process.

[NerdySupportExpert Moumita]

Casper, you can temporarily change the store’s payout method from Stripe to Bank Transfer via MultiVendorX → Stores → Edit Store. See this screenshot:
https://prnt.sc/Gg1BuNeaeKN6

Then go to Disburse Payment, enter the amount (e.g., 200), and release the funds. Refer to this screenshot:
https://prnt.sc/XhFyYBf_apGT

Since this is a bank transfer method, no real money will be transferred. You can switch the payout method back to Stripe afterward.

[NerdySupportExpert Moumita]

Casper, you can temporarily change the store’s payout method from Stripe to Bank Transfer via MultiVendorX → Stores → Edit Store. See this screenshot:
https://prnt.sc/Gg1BuNeaeKN6

Then go to Disburse Payment, enter the amount (e.g., 200), and release the funds. Refer to this screenshot:
https://prnt.sc/XhFyYBf_apGT

Since this is a bank transfer method, no real money will be transferred. You can switch the payout method back to Stripe afterward.

[NerdySupportExpert Moumita]

That’s a great question Casper!

In MultiVendorX 5.0, we’ve introduced a feature called Custom Gateway:
https://prnt.sc/4kf2o4Ed7OuX

Using this, you can manually update the wallet balance. It seems this isn’t functioning correctly at the moment. We’ll share the working flow with you by tomorrow so you can use it properly:
https://prnt.sc/nKuSn6Mj561-

[NerdySupportExpert Moumita]

Hi @l.gan, We’ve thoroughly checked this issue, and we can confirm that it is not coming from our plugin.

From our investigation, the error appears to be caused by Cyr to Lat plugin.

Similar issues have also been reported here: https://wordpress.org/support/topic/the-rest-api-encountered-an-unexpected-result-15/

We recommend reaching out to the Cyr to Lat plugin author for further assistance, as they would be better equipped to investigate and resolve this conflict.

Please feel free to reach out if you need any help from our side.

[NerdySupportExpert Moumita]

Hi @l.gan,

We’re sorry to hear that you’re facing this issue.

We tested the migration on our end but were unable to reproduce the error. Since the issue seems specific to your setup, we’ll need to replicate your environment to properly identify the root cause.

It would be very helpful if you could share a database dump of your site, preferably from before the upgrade. Alternatively, access to a staging site along with its database backup would allow us to run the migration and investigate the issue more closely.

We understand that you may want to use a rollback version for now. However, we strongly recommend moving to MultiVendorX 5.0, as it introduces a major structural upgrade built on a modern React-based framework. All future updates and improvements will be based on this version.

To ensure your site transitions smoothly to 5.0, it’s important for us to understand why this issue is occurring specifically in your case.

For context, 1000+ sites are already using this version successfully, with only a few isolated issues reported. Your support in sharing the required data will help us resolve this faster and ensure a stable experience.

Looking forward to your response.

[NerdySupportExpert Moumita]

Thank you @kevajo, for allowing us to review your staging environment.

After performing a detailed check on your setup, we have identified a few issues that are important for us to address before we proceed with the official release of the plugin. Fixing these will help ensure that the migration process works smoothly for all users upgrading to the new version.

Since your current staging site has already been migrated to the latest version, we no longer have access to the original database state prior to migration, which makes it difficult for us to fully investigate and reproduce the issue.

To help us proceed, could you please share a database dump of your site with us?

Alternatively, if possible, you may provide two separate environments:

One site where we can run the migration process ourselves
Another site that contains the original database (pre-migration) so we can compare the data before and after migration

This will allow us to properly analyze the issue and implement the necessary fixes before the release.

Please let us know which option would be more convenient for you. Once we receive the database or access to the environments, we will continue the investigation immediately.

Thank you for your cooperation and support.

[NerdySupportExpert Moumita]

Hello Pickflick, add this css to remove the download csv option, from MultiVendorX >> Settings >> Seller Dashboard >> Custom CSS :

form#mvx_order_list_form .mvx-action-container {
    display: none;
}

[NerdySupportExpert Moumita]

Hi @Phillip May, We’re happy to let you know that support for mile-wise distance shipping, as requested by you, has been added.

This enhancement is currently available on our GitHub and will be included in a future official update. In the meantime, you can download and install the updated plugin using the link below:https://github.com/AnkanLayek/MultiVendorX/archive/refs/heads/main.zip.
To install it:

— Go to WP Admin > Plugins and delete the currently installed MultiVendorX plugin.

— Download and unzip the GitHub plugin.

— Rename the unzipped folder to dc-woocommerce-multi-vendor.

— Re-zip the renamed folder.

— Upload and install the zipped plugin via your WordPress dashboard.

Once installed, please test the shipping flow on your end and let us know how it goes.

[NerdySupportExpert Moumita]

Hello @lukmancoolpatel.313, thanks for your query.

You need to add your custom fields by overriding the products.php template via yourtheme/MultiVendorX/vendor-dashboard/product-manager/products.php. You will get the overriding fields in our template file.

Now in order to add the functionalities for these filter, use this filter mvx_datatable_product_list_query_args

[NerdySupportExpert Moumita]

@Phillip May, We’d like to take a moment to clarify a few points and provide a transparent view.
You’ve been using MultiVendorX for the past six months, during which our support team has consistently responded to your queries and provided assistance to the best of our abilities. We have resolved the issues you have mentioned. The enhancements you requested were acknowledged and shared with our development team—just as we do with all user feedback aimed at improving our platform. In fact, work on some of these enhancements is already underway, and we hope to roll them out in the near future.
Throughout this period, we’ve done our best to support you within the scope of our policies.
Additionally, we have checked with our refund team and, as of now, no refund request has been received from your end.
That said, we remain committed to helping you get the most out of your MultiVendorX experience and we are always there to assist you further.

[NerdySupportExpert Moumita]

Hi @Phillip May, For any refund-related concerns, we kindly request you to reach out to our refund team directly, as they are best equipped to help you.
You can find all their contact details here: https://multivendorx.com/refund-policy/.

[NerdySupportExpert Moumita]

Hi @Phillip May, Please know that it has never been our intention to make you feel ignored or misled. As mentioned earlier, our development team has already been assigned to work on the requested enhancements, and we sincerely hope to roll them out soon.

That said, we want to be transparent that our support team does not have control over refund decisions. If you’d like to request a refund, we kindly ask you to reach out directly to our refund team, who will be in a better position to assist you with this matter.

[NerdySupportExpert Moumita]

Hello @Phillip May, We’re really sorry to hear about your frustration — and we truly appreciate you sharing your concerns.
Please rest assured, it was never our intention to leave issues unresolved. A team was actually assigned last week to work on improvements for Appointment products. To keep things organized, we marked related threads as closed, with plans to update users once fixes are released.

We understand how that may have felt dismissive, and we’re working to improve our communication moving forward. Your feedback matters, and we’re committed to keeping you informed as updates roll out.

To address your concerns directly, here’s a quick clarification:
🔹 Appointment Time Form Too Small (https://multivendorx.com/support-forum/topic/appointment-time-form-too-small/)
>> We have already provided you with a fix for the CSS issue and a custom code for the resolution of the conflict with the Product addon and WooCommerce appointment.

🔹 Appointment vs Booking (https://multivendorx.com/support-forum/topic/appointment-vs-booking/)
>> We understand your preference for the Booking module and respect your decision to proceed with the option that aligns better with your needs. However, if you need any further assistance please do let us know.

🔹 GeoMarketplace Compatibility (https://multivendorx.com/support-forum/topic/geomarketplace/)
>> As mentioned earlier, this is a third-party plugin that we haven’t officially tested. In such cases, we recommend reaching out to the plugin’s developers for compatibility queries, as they are best equipped to provide accurate assistance.

🔹 Shipping Options / ShipStation (https://multivendorx.com/support-forum/topic/shipping-options/)
>> As shared earlier due to our developer account with ShipStation being restricted, we requested access to your account so we could investigate the issue further. So again we will request you to share your shipstation account details with us if possible so that we can assist you accordingly in resolving any issue you are facing on your end.

Throughout every interaction, our goal has always been to assist you and provide solutions wherever possible—even when the challenges involve third-party plugins beyond the scope of our own. While we understand there may have been some frustration along the way, we want to reassure you that we’ve always been here to support you.

If there’s anything still unresolved or if you need further help with any aspect of the plugin, please don’t hesitate to reach out. We’re here and ready to assist you in every way we can.

[Author]

Posts