Default ticket preferences

[MangoldCreative]

Hello. I actually have several questions. We’re building out a ticketing system for our client (they purchased the plugin, but I’m posted in my account so I get the notifications). They will be selling tickets for concert events. Most all events will have the same ticket options: General Admission, Early Bird, Premium, etc. I’ve noticed that when you create tickets for events, It creates products from those tickets names, so if I, say, create 10 events all with General Admission, Early Bird, Premium, won’t I then have 10 products named “General Admission,” 10 products named “Early Bird,” and 10 products name “Premium”? That’s going to be really hard to keep track of if that’s the case. Is there a best practice for this scenario? So would each ticket name need to be unique so that you can find what you’re looking for under Products?

I’m also not seeing any way to set up default ticket types that can be added to multiple events without having to manually build them out every time. The only option that seems to be repeatable is fieldsets. That’s really time-consuming. Also, all tickets will use the same general header image, but that seems to have to be manually added for every event ticket as well. Hoping to get some advice in these matters. Thanks!

[Sky]

Hi there,

Thanks for reaching out. I will try to help with your questions.

Regarding the naming: There generally isn’t much if any need to interact with the tickets within WooCommerce. The tickets are generated from within the event, and stock management, attendee information, and any edits would happen from within the event admin page.

Unfortunately, the ticket images and the ticket types need to be added manually on each event. I know some people have tried to create a “template event” with tickets already created to use as a “clone” with a plugin, but this doesn’t work because the tickets have their own unique ids. The tickets on every event wind up being the same batch of tickets, breaking capacity and attendee functionality.

Sorry I didn’t have better news for you on that one.

Hope this helps! Please let me know if you have any additional questions about this.

Thanks,
Sky

[MangoldCreative]

Thanks for getting back to me. I’m going to bypass the WooCommerce Shop products and instead use your calendar shortcode with the category filter. But it would be nice, for future development, if instead events because the products and the ticket types are product variations. That’s how FooEvents works. But at least if at some point you could add the ability to build out default ticket types you could easily apply to events rather than manually building those out every time…that would be awesome! 😉

[Sky]

Hi again,

Feel free to make any suggestions you have for features or functionality over at our User Voice forum. If enough people vote on an idea, it may be considered for a future release.

Let me know if you have any additional questions about this.

Thanks,
Sky

[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