Hello @joeb2880
Thanks for reporting this.
We’ve seen a few similar cases where merchants noticed duplicate emails and stock deductions. A recent thread on the topic can be found here. This seems to be caused by a conflict or third-party interference. However, we haven’t yet received any system status report from affected users to confirm a pattern and identify the root cause.
Please follow these steps to share your system report with us:
- Go to
WooCommerce → Status in your site’s admin area
- Click “Get system report” and then “Copy for support”
- Paste the report into our PrivateBin (set expiration to 1 week)
- Share the link here so we can analyze the environment in detail
We’re currently gathering data to see if there’s a specific combination of plugins, caching behavior, or email trigger logic involved. Your report would help move that forward.
Alternatively, to speed this up, we suggest you contact us directly for further assistance. You can open a ticket with our service desk. Here’s how you can request support: Request Support.
Please make sure to include the URL of this thread in your ticket for reference.
Kind Regards,
Krystian
Hi Krystian,
Thanks, here’s the privatebin
Have also submitted to the service desk.
Cheers
Same – apparently roll back to 3.1.0 if you want a quick fix:
https://github.com/woocommerce/woocommerce-paypal-payments/releases/tag/3.1.0
but they’re working on a fix to the current version
That’s a shame, maybe rolling back even further? EDIT – I get errors trying to rollback to 3.0.9, so gonna go for 3.1.0 for now.
The developer is being very responsive with me over email so I trust it will eventually be resolved, but it’s incredibly frustrating at the moment to keep having to modify my stock counts as they get double reduced.
-
This reply was modified 6 months ago by
joeb2880.
Hello @mambojuice @cranewest
Please avoid replying in other users’ threads and create your own instead, as this goes against the WP.org forum rules, simply your post might get removed.
But on topic, as optics on this issue changed recently:
We’ve made some progress on this issue and have identified the cause. The fix is currently being worked on, and I’ll share the updated package with you as soon as it’s ready.
Sorry for the inconvenience, and thank you for your patience.
Kind regards,
Krystian
@cranewest: As already mentioned, you should not post your own issues in other topics. Likewise, you should not share private communications here in the forum.
https://wordpress.org/support/guidelines/#we-reserve-the-right-to-manage-the-forums-to-the-best-of-our-ability
Your posts have therefore been archived.
@mambojuice and @stevejonk: also.
-
This reply was modified 5 months, 4 weeks ago by
threadi.
-
This reply was modified 5 months, 4 weeks ago by threadi.
Hi @inpsydekrystian, thanks for looking into this issue so promptly. Do you know when a patch will be released for this issue?
Hi, I see last week the plugin updated to 3.3.0 – this still hasn’t fixed this issue for me!
any update ? same problem from my side
Hello @joeb2880 & @mikecastrodemaria
We have a package which should resolve the problem.
Feel free to open a new thread or submit a ticket through our service desk. Please include the URL of this thread in your ticket for reference.
Kind regards,
Krystian
