Hi there,
I’m sorry to hear you’re experiencing a data discrepancy. Could you please confirm if this issue started after upgrading to the latest version on your end?

Hi there, Thank you for getting back to us. We kindly request you to update to the latest version and check if the issue still persists on your end.
We look forward to hearing from you once you’ve tested it with the updated version.

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.