Global stock isn’t restored after refund

[Simeon Rowsell]

Hello,

I have the same issue (or very similar anyway) that Hilary had on this thread and was wondering if you’ve any more details on the bug fix for this please?

In my case, the individual stocks of the tickets is restored but not the global. So for example, I have two tickets setup for the same event, “Adult” and “Child”, with a global stock of 10. If I purchase 3 adults and 7 children, all tickets sell out correctly. But then when I refund them from WooCommerce only their individual stocks are updated and not the global. So I end up with 3 adults in stock and 7 children in stock, and I can’t, for example, then purchase 4 adults, as the global stock isn’t working.

My fix for now is just to go and update the global stock manually after a refund, although this is clearly not a long-term solution.

Thanks for your help!
Sim

[Barry]

Hi Sim!

Thanks for contacting us and my apologies for any inconvenience you’ve experienced so far.

To the best of my knowledge, however, what you’ve described is in fact intentional (or at least, was originally what we intended).

To explain: if you refund the purchase of a regular WooCommerce product – or indeed if you cancel an order – no re-stock will automatically take place.

What we’re doing with tickets follows that basic model (one where manual intervention in an order necessitates manual adjustment of the inventory levels) and makes sense in a lot of cases – as a refund or order cancellation does not automatically mean that the tickets are revoked.

With that said, it does sound like George noted this was a bug so we may have changed our stance on this one. What I’ll do is check in with him (as I can’t immediately locate the relevant bug report) and get back to you.

Thanks for your patience in the meantime!

[Barry]

Hi again Sim:

So I was a little behind the curve with my last response. This remains a valid bug that we haven’t yet had time to progress, but it is very much on our radar and we should be able to address this in an upcoming maintenance release.

[Simeon Rowsell]

Hi Barry,

Thanks for getting back to me on this. Ok cool. Is there any way I can be notified when this is fixed? It would be great if this could be looked at soon but I appreciate there’s probably lots of other fixes going on too.

Many thanks,
Sim

[Barry]

Is there any way I can be notified when this is fixed?

Absolutely.

I’ve attached this topic to the bug report on our internal tracker – and we’ll do our best to update this and any other linked support topics as soon as the fix is released.

It would be great if this could be looked at soon but I appreciate there’s probably lots of other fixes going on too.

We do have a lot going on but we also strive to turn these things around as quickly as we reasonably can. As you’re aware, this isn’t the only support topic created with reference to this bug and we’ll prioritize accordingly 🙂

[Nico]

Hi there,

Just wanted to share with you that a new maintenance release (for the Week of 1st May 2017) is out, including a fix for this issue 🙂

Find out more about the release → https://theeventscalendar.com/maintenance-release-week-1st-may-2017/

Please update the plugins and let us know if the fix works for your site,
Best,
Nico

[Support Droid]

Hey there! This thread has been pretty quiet for the last three weeks, so we’re going to go ahead and close it to avoid confusion with other topics. If you’re still looking for help with this, please do open a new thread, reference this one and we’d be more than happy to continue the conversation over there.

Thanks so much!
The Events Calendar Support Team

[Author]

Posts