Hi @carlopus
Do the legacy reports also show doubled values?
If not, you can re-import your data and see if that helps: Analytics > Settings > Import Historical Data > Delete Previously Imported Data
I am using WCMP multivendor plugin,
Where it creates 2 Orders for single order ( Main order & Suborder for each Vendor).
find here https://prnt.sc/sjwz31
SO woocommerce REPORT considering it as 2 different orders and showing doubele Sales Value in Report section. https://prnt.sc/sjwxuh
How to fix it ?
@nikhilbhoyar Yep, that’s exactly what I’m getting. And no, re-importing the data does not help. Also no, the legacy reports are correct.
Hi @carlopus, thanks for the additional information. Just to clarify, you’re saying that you’re using multivendor plugin that is creating a sub-order for each order? If so, that is likely where the problem lies. WooCommerce Admin will count every order and has no concept of sub-orders.
@apmwebdev that’s correct. It’s a known issue for WCMP and there are many, many complaints on their support forums referencing it. Their response, in a nutshell, is “That’s how our plugin works”.
I’m planning to delete WCMP but can’t yet (multisite network, deep integration, etc). In the meantime, I’ve removed all associations with vendors in WCMP and the sales numbers are now accurate.
Thanks for following up.
Carl
Hello @carlopus & @apmwebdev,
This is Purnendu from WC Marketplace Team.
Yes, this is a known issue to us and we are working on the issue already. You can check, we already opened one ticket for the same here – https://github.com/wcmarketplace/dc-woocommerce-multi-vendor/issues/334
As we are facing difficulties in finding proper hook / filter on WooCommerce Admin to exclude suborder data, it’s taking some more time to release a fix. However, we are assuring you it will be fixed on our next release 3.5.2.
You can check the update on GitHub itself. Looking forward to your cooperation.
I sincerely apologize for the inconvenience caused by us.
@purnendu thanks for the update.
Good to know @purnendu, thanks for the info!
As this issue is due to a known conflict with a third-party plugin, I’m going to go ahead and mark the thread as resolved. Feel free to reach out again if you have any further questions!
