The Events Calendar Event Tickets Plus

Ticket sales and event registration sit inside the WordPress event workflow with this add-on for The Events Calendar. It is aimed at organisers who need to publish an event, offer more than one admission option, take payment, and keep registration details alongside their event content. The scope covers both in-person and virtual events, so the same ticketing approach can support a local gathering or an online session.

Ticketing in context

The central strength is its connection with The Events Calendar. Events and tickets are handled as related parts of the same system rather than as separate publishing tasks. Organisers can create ticket types for different audiences and prices, then associate those options with an event. General admission, VIP and early-bird tickets are specifically supported, giving a basic structure for staged pricing and differentiated access.

Payment support is built into the sales process. The feature list names PayPal and Stripe among the available gateways, while the product summary also highlights integration with a PayPal business account. That gives organisers a route from registration form to paid booking without relying solely on manual payment handling.

Useful controls

• Multiple ticket types, including general admission, VIP and early-bird options.
• Payment gateway support including PayPal and Stripe.
• Attendee management for tracking ticket sales and registrations.
• Discount codes and promotional offers for campaign-based ticket sales.
• Recurring events with ticket sales managed for each occurrence.
• Mobile-friendly ticket purchasing for attendees.
• Reports covering ticket sales and attendance trends.

These controls cover the operational details that matter after an event is published. Discount codes provide a direct way to run promotional offers, while attendee management gives the organiser a place to follow registrations from the WordPress dashboard. The reporting layer is oriented towards sales and attendance trends, which helps connect ticket activity with the performance of an event programme.

Recurring event handling

Recurring events are a notable inclusion because each occurrence can have its own ticket sales. That suits classes, talks, or other repeated sessions where capacity and demand need to be considered per date rather than only at the series level. It also gives organisers a way to use one event structure while retaining separate registration activity for its individual occurrences.

The mobile-friendly purchasing experience matters for attendees arriving from phones, social posts, or event reminders. It does not change the underlying event model, but it keeps the buying side focused on selecting a ticket and completing registration rather than requiring a desktop-only process.

What to weigh

The first trade-off is dependency on The Events Calendar. This product is designed as an extension of that event-management setup, so it makes most sense for a site already using that ecosystem; it is not a general-purpose ticket shop detached from an events calendar. Choosing it therefore ties event publishing and ticket sales to the same product family.

The second is administrative complexity as the ticket structure grows. VIP, early-bird, discount and recurring-event options are useful, but each adds another rule to maintain. Separate occurrences also require attention to sales and registration records, while payment gateways bring their own account and transaction configuration. The reporting tools cover sales and attendance trends, but the supplied feature list does not establish a broader analytics or venue-management system.

Who it suits

This is a practical fit for event organisers, businesses, and individuals who want ticket sales attached to WordPress events rather than handled through a separate registration service. It is particularly suited to sites running several ticket categories, promotional offers, recurring sessions, or a mix of paid and registration-based events. Sites that only need a simple event listing, or that want a standalone commerce system without The Events Calendar, have less reason to choose this approach.