Creating tickets with Event Tickets and Event Tickets Plus is easy and fast. This page walks you through the process to make tickets on your site’s posts, page, or events. The article is divided up into two main parts:
- Setting up basic tickets – creating basic tickets with a specific or unlimited capacity
- Shared Capacity – creating two or more tickets which pull from a shared capacity for the event
You can get a quick overview of using Block Editor with Tickets in An Introduction to Tickets Blocks.
Setting up Basic Tickets
Tickets can be added to posts, pages, or events. In the Classic Editor, you will find the Tickets meta box below the main content of the post type:
In the Block Editor, default Ticket blocks or RSVP blocks may appear if you are creating an event. Otherwise, you can add a Ticket and RSVP blocks to the main content:
For this example, we’ll create a basic ticket with a capacity for this ticket only. (Using a shared capacity for two or more tickets is discussed in another section below.)
When clicking on the + New ticket button you will be presented with some additional options:
In this example, we are using Event Tickets Plus with WooCommerce. Since we want to make a purchasable ticket, we click + New Ticket. If you want to collect attendee RSVPs without selling tickets, you can click + New RSVP instead – in which case you’ll want to read over our RSVP tutorial instead.
If you are using Event Tickets only and are selling using Tribe Commerce, then you will only see one capacity option as shown in this screen.
Clicking on Advanced will show the following additional fields.
Many of the fields in the tickets meta box are self-explanatory, but let’s run through each just to be sure.
- Type lets you set a unique name for the ticket type – which might be something like Standard, Adult, Concession, etc.
- Price controls the price of each ticket. If the tickets are not going be sold – but rather you are going to give them away for free – you can leave this field blank or set it to 0.
- Capacity is the number of tickets that are available: if you leave this blank it is assumed that there is no limit and customers can buy as many as they would like. If you have a limited number of spots for your event, you’ll want to make sure to set this accordingly.
- Ticket description is optional, but it’s a good space to add any information customers might be interested in, such as bring waterproof jackets or not recommended for children. You can choose to show or not in the front end ticket form.
- Start sale dictates when the tickets are available for sale. If you’re making tickets on a post or page, this field is required. If you are making tickets on an event, you don’t need to set this field – by default sales will start when you publish the event or ticket.
- End sale does the reverse – you can set this to a date after which the tickets should no longer be available for customers to buy. As with the start sale field, setting this is optional for events and the default is to stop sales when the event itself starts.
- SKU lets you set a unique code to help identify the tickets. This is another optional field and is of most use to merchants with an existing stock-keeping unit system.
By default, the name and contact information of the person buying the tickets is collected during the purchase process. If you want to collect additional information (such as names of all attendees, t-shirt sizes, etc.) then you can implement the Attendee Information feature (Available only with Tickets Plus) by clicking + Attendee Information. This feature is explored in another article, and this walkthrough assumes that you do not need to collect additional information.
As soon as you’re ready, simply click on Save/Update Ticket and you’re done … and never fear, if you make a mistake you can correct it by clicking on the edit link (pencil icon) later on:
A Quick Note about the Ticket Form
If the tickets are for sale but just sold out, then the form will still show. But purchasing tickets won’t be possible, and there will be an “Out of Stock!” message as shown in this screenshot.
What about if the tickets are not sold out, but are only going to be sold between certain dates, and a website visitor views the event page outside of that time window? In this case, the ticket form will not show up at all. A simple “Tickets are not yet available”-type message will be displayed instead, as shown in this screenshot.
Shared capacity and ticket settings
The shared capacity feature allows you to sell multiple tickets that all come out of one pool of stock. For example, say you have a venue which has 100 seats, and you are selling three different price tickets for children, adults, and seniors. If you listed the capacity of each ticket at 100, you might accidentally sell over 100 total tickets, and run out of seats. Instead, you can set a Shared Capacity of 100 for the event. Your attendees can choose to buy any of the three ticket types, but only up to 100 individual ticket sales.
To enable the shared capacity for your event, click the Settings button in the tickets meta box. A field will appear for Shared Capacity. Edit that number to your event capacity. In the example described above, that number would be 100.
If you display attendees on the front of your site, attendees can participate in the Public Attendees List. We are excluding users from the Public Attendees List if the attendees are not displayed on the front of your site. If you are displaying attendees, we default the option for users to be excluded (opted-out) by default while we work on creating an opt-in method (rather than the current opt-out only option).
When you click + New Ticket the new ticket fields will display. In addition to the basic options outlined in the section above, you’ll see the Capacity options.
If you want your ticket to share the capacity for your event but also impose a sales limit on it (for example, if you want to only allow up to 50 children at your event out of your shared capacity of 100 attendees) you can Sell up to a certain number of tickets.
Once you’ve configured your ticket, hit the Save Ticket button and you’re all set. As your tickets start to sell, the stock for all tickets in global stock will decrease accordingly.
? Event Tickets 4.7 incorporates Tribe Commerce functionality which enables you to sell tickets using a PayPal Business account. We recommend running only one ecommerce functionality at a time. If you need to run multiple, we highly recommend that all tickets for one event use the same ecommerce platform, which you can select from the ticket editor settings.
Next up we recommend that you learn about managing ticket orders and attendees as well as reviewing How Event Tickets are Calculated. As ever, if you have any further questions please don’t hesitate to connect with the team via our help desk.
See Common Stock Issues for help troubleshooting.
Linking to the Tickets Form
Event Tickets Plus has a built-in anchor link so that you can link users directly to the ticket sales form on a single event page. (⚠ Please Note: This is only true for tickets being used on the “event” post type—tickets on “posts”, “pages”, and other post types will not have this anchor link at this time.)
The default link to the ticket form is yoursite.com/[event-slug]/[event-slug]/#buy-tickets. For example: yoursite.com/event/rock-concert/#buy-tickets.
If you’re not sure how to construct the link, go to your event’s page and add #buy-tickets to the URL. Then copy the full text of your browser’s URL field, and that’s the link to the tickets form.