Creating Ticket Type as WooCommerce product

Creating Ticket Type as WooCommerce product

If you’ve used Tickera before switching to Bridge for WooCommerce, you’ll notice things look quite different when it comes to creating ticket types. Don’t worry - it’s not complicated, just more flexible. WooCommerce brings a lot of power to the table, and we’re simply harnessing that to make your ticket sales smoother and more customizable.

Before you begin, make sure the following three plugins are installed and activated:

• Tickera - the core event ticketing system
• Bridge for WooCommerce - the add-on that connects Tickera with WooCommerce
• WooCommerce – the e-commerce engine that powers your store

Once these are active, you’re ready to create ticket types directly within WooCommerce.

After installing WooCommerce, you’ll notice two new menu items in your WordPress dashboard: WooCommerce and Products. For creating ticket types, you’ll be working exclusively in Products.

Click Products -> Add New, and you’ll land on the familiar “Add Product” screen - only now, it’s your gateway to creating a fully functional ticket type.

Creating a simple ticket type

Let’s start with the basics.

At the top, you’ll find the Product Name field - this will become the name of your ticket type (for example, “General Admission” or “VIP Pass”). Below that is a large text box for the product description. You can leave it blank or add details about the ticket - entirely up to you.

The real action starts below, in the Product Data section.

By default, WooCommerce sets this to Simple product, and that’s exactly what we need for a basic ticket type. You’ll also see two checkboxes labeled Virtual and Downloadable - leave those unchecked.

Under the General tab, you’ll find:

• Regular Price - The price of your ticket.
• Sale Price - An optional discounted price. You can even schedule when the discount is active, perfect for Early Bird offers.

Enabling “Product is a Ticket” option

Once you check the Product is a Ticket box, a new set of options will appear below - these settings are what turn a regular WooCommerce product into a functional Tickera ticket type.

Here’s what each of them does:

Event - Choose the event this ticket type belongs to. Every ticket must be tied to an event, so make sure the event is already created in Tickera before you get here.

Ticket Template - Pick which ticket template will be used for tickets purchased under this product. You can select Default or any custom template you’ve created in the Ticket Templates section.

Allow ticket check-out - Enable this option if you want to allow attendees to check out (for example, if you need to track both entry and exit). Leave unchecked if you only need standard one-way check-ins.

Available dates for ticket selling – Define when tickets can be purchased.

• Open-ended means tickets will be available indefinitely until you disable or sell out.
• During selected date range lets you specify start and end dates for ticket sales (ideal for early-bird or limited-time sales).

Check-ins per ticket - Control how many times each ticket can be scanned. The default is Unlimited, but you can limit it to a specific number — handy for multi-day events or passes that allow multiple entries.

Limit check-ins on time basis - Enable this if you want to restrict when check-ins can occur. Once checked, an additional option appears below.

Available dates / times for check-in - Determine when the ticket can be checked in. You can choose between:

• Open-ended - No time restrictions.
• During selected date range - Only valid for check-in within specific dates.
• Within the following time after order is placed - Useful for short-term passes (e.g., 48 hours after purchase).
• Within the following time after first check-in - Great for multi-day passes (e.g., valid 3 days after first scan).
• When the event starts - Limits check-in strictly to the event date and time.

Other WooCommerce product options

On the right side, you can assign Product Categories, Tags, and a Product Image. These behave exactly like they do for regular WooCommerce products, except now they represent tickets.

When you’re done, click Publish - and that’s it! You’ve created your first WooCommerce-based ticket type.

For most use cases, that’s all you’ll need. But WooCommerce offers much more flexibility, so let’s take things up a notch.

Creating variable ticket types

Sometimes, you’ll want multiple versions of the same ticket - for example, Adult, Child, and Student tickets, each with different prices. That’s where Variable Products come in.

Go back to the Product Data dropdown and change Simple product to Variable product. You’ll notice that the price fields disappear. That’s normal - WooCommerce assumes each variation will have its own price.

Check the Product is a Ticket box and fill in the event, check-in limits, and template just like before.

Now, scroll down and open the Attributes tab. From the dropdown, choose Custom product attribute and click Add.

Give your attribute a name (for example, “Type”) and enter the options separated by a vertical bar:
Adult | Child | Student

Make sure both Visible on the product page and Used for variations are checked, then click Save Attributes.

Hey, congrats! You're half way there!

Next, head to the Variations tab (right below Attributes).

Once there, you will notice that an arrow is pointing to the Generate variations button so you should just click that very button.

Now you can expand each variation to configure it...

• Set an image (optional)
• Add an SKU (optional)
• Set the Regular Price (mandatory)
• Add a Sale Price (optional)
• Update stock or availability if needed

Of course, the main reason for using a Variable Product setup is to sell the same ticket type in multiple pricing variants — all tied to the same ticket type but priced differently.

This approach is especially useful when you’re using the Seating Charts add-on and want to offer multiple price levels for the same seat (for example, Adult, Student, or VIP pricing). To see this in action, take a look at our tutorial video below.

And with that, we're now finished. You’ve just created a ticket type with multiple variations, all fully connected to your event in Tickera.

A few final notes

Even though you’re working inside WooCommerce, everything under the hood still runs through Tickera. The Bridge for WooCommerce handles the sync between both systems - ensuring tickets are generated, sent, and check-ins are tracked exactly as they would be in standalone mode.

If you ever switch back from WooCommerce to standalone Tickera, keep in mind that the two modes don’t share ticket data. Tickets sold in standalone mode won’t appear in WooCommerce (and vice versa). So if you plan to use Bridge for WooCommerce, it’s best to decide that before starting ticket sales.