WooCommerce ticketing for non-profit festival website

Hello,

I’m currently looking for a web developer that has proficient experience with WordPress, Elementor, WooCommerce and Advanced Custom Fields to help set up a ticketing system on a website for a non-profit, heritage trail event that’s happening in Glasgow here in mid/late September.

The ticketing system needs to be set up within the next 2-3 weeks. I myself have done a lot of the work on this website, taking over from a previous developer who sadly passed away earlier this year. The site itself will be undergoing a major rebuild after this year’s festival, so there’s potential for future work there for the right candidate.

At this point in time my own client workload is too busy to focus on this project, and ideally I’d be looking for someone that can take this project on that has experience working in the software packages mentioned above.

The site is to launch the programme for the festival on August 7th, with the ticketing launching on Sept 1st, however, we’re looking to have the ticketing system up 1-2 weeks before that so the festival team can create the ticket products ahead of the launch.

So here’s the technical brief:

We already have WooCommerce installed and are currently setting up the basic configuration at the moment. Here’s the additional tasks to the above that we’re looking to have the right candidate work on for this project:

⁃ We currently have FooEvents (https://www.fooevents.com/) installed for the ticketing features, allowing for extra features specific to ticketing in WooCommerce, including the creation of the actual tickets. We're open for suggestions here if the right candidate feels there's a better WooCommerce ticketing solution based on this brief.
⁃ Each Ticket product would have a list of attendees per event. This list should allow for the ability to (a) export a list of attendees and (b) to email attendees with news on the event, or if the event gets cancelled.
⁃ As all the events are free, rather than showing “£0.00” as the price, changing that to just say “Free”

The website will have a programme section, which is mainly grids built in Elementor that pulls in each “activity” in the festival from 4-5 custom post types (Buildings, Events, Trails, etc.), with each submission on these being created by Elementor templates that are assigned to each custom post type.

These templates would have additions to them with the ticketing system in place. Each activity would be linked to the relevant ticket product by way of ACF relationships which would allow:

⁃ The insertion of an “Add To Cart” interface on each activity, referencing the ticket Product.
⁃ A “Sold Out” notice to show on each activity if the stock level of the ticket gets all used up.

We can provide a more detailed brief but that’s the general overview for this project. All ticket products would be created by the festival staff so it’s mainly setting up the functionality as listed above, making sure it works correctly, fixing bugs and then it just gets handed off to the festival team to fill in the content.