Issues with Stock Count After 4.04 Update

[wineschool]

I just updated to 4.0.4 and am having a different stock issue than has been reported so far.

The stock inventory in woocommerce shows zero:

The stock inventory in Events Calendar Pro shows 14 available:

Here is a live link: http://www.vinology.com/class/greatest-wines/

This doesn’t happen on all events, only ones where attendees were deleted from the attendee list.

[Josh]

Hey Keith,

Thanks for reaching out to us!

Would you mind clarifying the steps taken up to this point? Unfortunately, based on the original post, it sounds like this might actually be working as expected however I can see where there could be a way we could make this process better within the plugin.

If the attendees were just removed from the list, their ticket purchases would still be considered complete within WooCommerce and would need to be refunded/removed within WooCommerce as well for that to match up. It sounds like this may be the confusion here? If so, I can definitely see where we could potentially make some changes or prompts to clarify that one a bit.

Thanks!

[wineschool]

To clarify:

1. This issue began with the 4.0 update. Prior to the update, this behaviour did not occur in 3.*.

2. The inventory in Event Tickets Plus show a different inventory than the inventory in the Woocommerce product. As an example, I have 4 tickets showing in ETS, but when I click on “edit in Woocommerce” it shows that there are only 1 tickets remaining.

I am not sure how this could be standard behaviour. ETS and Woo should not be showing different inventories for the same product.

The photos I supplied also show the problem at hand.

• This reply was modified 10 years, 3 months ago by wineschool.

[Josh]

Hey Keith,

After doing some further testing, it looks like there is another issue going on in addition to this problem that may be causing some confusion. I’ve created an internal bug ticket for tracking an issue where ticket purchases reduce the total starting stock rather than just the available stock.

The issue with inconsistencies between the two stock amounts (and I’ll review this behavior with our developers to verify or see the options for altering this) comes when attendees are deleted manually from the attendee list. In this case, there is still potentially a completed order (ticket paid) that has yet to be refunded. Once the deleted tickets are refunded, the stock amounts should equal back out.

If this is the case, I definitely understand the confusion and need for adding additional prompts or information to this process.

Let me know if this helps.

Thanks!

 

[wineschool]

Looks like we are narrowing in on the issue. On occasion, attendees are deleted manually from the attendee list.

Howwever, this behaviour isn’t simply when people are deleted from the attendee list. It also happens when I add or remove seats from an individual ticket.

[Josh]

Hey Keith,

I want to make sure I’m understanding the different potential issues here, do you mind clarifying that last sentence:

It also happens when I add or remove seats from an individual ticket.

Is this in reference to refunding tickets from an order?

Thanks!

 

[wineschool]

Just deleting from the attendee list. NOT refunding via WooCommerce. We don’t refund tickets through Woo, so that is not the issue.

[Josh]

Hey Keith,

I believe this brings us back to the original comment. No doubt there is definitely some confusion here that needs to be addressed on our side with how the plugin works in this regard.

However, currently even if an attendee is deleted from the attendee list they are still associated with a completed/paid purchase within WooCommerce. The best option for keeping everything consistent right now would be to “refund” tickets via the associated WooCommerce order rather than deleting them from the list.

Thanks!

[wineschool]

This reply is private.

[Josh]

Hey Keith,

I’m terribly sorry for the frustration and confusion I have caused within this thread.

With version 4.0 we completely revamped our approach to Tickets in general. We moved the core of the functionality to it’s own plugin (https://wordpress.org/plugins/event-tickets/) and created a single premium ticketing plugin to cover support for the cart solutions such as WooCommerce. With this there appears to have been some changes to the way stock is handled that unfortunately impacts the way you’re wanting to manage the tickets and deleting of attendees.

I’ll be completely transparent here. I’ve brought the issues mentioned here up with our team and there are still some questions that need to be answered when it comes to handling ticket stock.

There are definitely bugs in the process, I do not disagree with you there, and I’ve created an internal bug ticket and logged this information which also covers establishing set guideline for how we will handle stock throughout the sales process as well as attendee management processes (which you’re facing now).

I’ve added this thread to that ticket and you’ll be notified here as we make progress on that ticket. However, I do want to continue to set expectations that the ability to delete attendees without modifying the originating transaction (via a refund) may not be possible even once we implement these changes. If this continued to be the case, someone would have the ability to have completed transaction selling 100 tickets to an event that only 10 seats.

I apologize again for this issue.

Thanks!

[Benjamin Thomas]

Hi,

The stock quantities are not functioning correctly. Whenever a ticket is purchased, stock quantity is reduced by 2 items instead of 1. Moreover, the original total stock quantity is also affected.

So for example:

If my original stock is 200 tickets and I purchase 1 ticket, the stock changes to ‘198 out of 199 available’ – the minus 2 deduction is incorrect and the ‘out of 199 available’ is misleading.

I am running the following plugin versions: Event Tickets Plus Version 4.0.4 Events Calendar Version 4.0.5

Please advise.

Kind regards,

Ben

[wineschool]

It sounds like your team is thinking in too linear a way in regards to how tickets are sold.

There are many reasons an event organizer would want to remove a person from attendance without refunding their money. For instance, many events are non-refundable. Or perhaps the attendee is transferred from one event to another.

This is a substantive change of logic from your previous ticketing system. It is one that is throwing my organization into chaos. There really shouldn’t be a change this substantial with the underlying logic. I’ve read all the blog entries and nothing prepared me for this.

My ticketing needs are simple: I sell 20 seats to each and every event. I need to be able to remove people from the attendee list without that affecting the inventory counts. That is something I have been able to do for years with your plugins.

If I can’t do that, perhaps a workaround? I am thinking of a cell on the attendee list for Customer Notes? That way, I can make a notation that certain people wouldn’t be attending.

[Josh]

Hey Benjamin,

That is a documented bug and you should receive notification here on this thread as we make progress on that one. If you have any further questions we’d ask that you’d open a new thread so we can address your questions directly.

Hey Keith,

I can definitely understand the frustration here. You could modify the table columns to include an additional column for adding information or noting a removed user without refunding or removing them directly from the list. For the content of the column, I’ve used this information for Ajax powered checkboxes in an admin column in the past. It would need a little customization along with updating the meta to fit with the attendee information.

Let me know if this helps.

Thanks!

[Benjamin Thomas]

Hi Josh, thanks.

Any ETA for the fix?

Kind regards,

Ben

[wineschool]

Josh,

I offered the idea in the hope that your team would implement it as a possible work around. At the very least, a detailed tutorial on customizing the attendee list would go a long way in fixing the problems this update has caused.

[Author]

Posts