Hey pstidsen,
Amber here, thanks for contacting SkyVerge about our Sequential Order Numbers plugin! I’m happy to help! 🙂
I understand that when you have HPOS active, when you process a refund, it seems that a new order is created. My sincere apologies that this is happening, let’s take a look!
Our plugin was compatible with HPOS since version 1.5.4.
May I ask what version you are currently using?
Also, for the old and new order, could you send me a screenshot of the order notes (on the right hand side)? Feel free to color out any personal information that you wish to not make public on this post.
All the best,
Hi @amberskyverge
Thanks for your reply. We are running on version 1.11.0 currently.
Order notes for the original order which is refunded: https://app.screencast.com/3xQ3o9pq3f4Ld
The new order is totally empty, without any order notes: https://app.screencast.com/eLFeJPxrnHaf7
Please also note, that the order number is wrong at the new “refund order”.
Best Regards,
Peter
Hey Peter,
Thank you for sending over the wonderful screenshots of what’s happening. I tested this on my local site to see if I was able to duplicate the issue you are having. When I refunded an order, with only WooCommerce and Sequential Order Numbers enabled, it processed the refund as expected but I wasn’t able to duplicate a new order being created. This being said, I believe there might be a conflict with another plugin you have, so let’s test that next.
You can learn more about conflict testing here.
This is best done using a staging site to make sure that it doesn’t affect your live site. If you don’t have a staging site, you can also use the free Health Check plugin to simulate this testing on your live site. This will let you run through these steps for your user account only, without impacting what your customers see on the front end.
Could you please try disabling all your plugins except for WooCommerce and Sequential Order Numbers?
Then run a test to see if you’re still having the issue. If this fixes the issue, you can try re-enabling your plugins one by one to find out which one is causing the issue.
If the issue still occurs after all the plugins have been disabled, then this may be a theme conflict and you can try temporarily reverting to a default theme such as Storefrontto see if that solves the problem.
Would you be able to give that a try and let me know what you find?
Thanks 🙂
All the best,
Amber 🙂
Hey there,
It has been a long time since we heard from you, so I’m going to mark this topic as resolved.
If you’re still experiencing issues please take a look at our FAQs for more information and create a new thread if you have further questions.
Thanks,
Amber 🙂