BookingWizz Event Tickets Add Ons extend the BookingWizz booking script with a ticket designer and a PDF delivery mechanism, so that a confirmed event booking produces a branded, information-rich ticket rather than a plain confirmation email. The add-on is aimed at site owners already running BookingWizz who sell seats, entries or admissions and want the ticket itself to look like part of the service. It is a companion plugin rather than a standalone product, priced at $19 on ThemeForest.
What the BookingWizz Event Tickets Add Ons actually add to a booking flow
The core of the plugin is a template builder. Rather than sending every attendee an identical, text-heavy confirmation, the administrator can design a ticket layout and decide which fields appear on it. That control matters more than it first appears: a ticket is often the only physical or digital artefact a customer keeps from an event, and it is frequently presented at a door, scanned by staff, or printed at home on whatever paper is available.
Several capabilities follow from that design goal.
- Layout control. The ticket’s arrangement is editable, which means the visual hierarchy can be set deliberately — event name and date prominent, terms and conditions small, rather than whatever order a default template happens to use.
- Customer information fields. Booking data can be placed onto the ticket, so the attendee’s name, booking reference or other captured details travel with the ticket itself. This is what makes a ticket verifiable at the door rather than merely decorative.
- Logo and background upload. Branding assets can be applied directly, so the ticket carries the organiser’s identity instead of the software’s.
- Selective field display. Individual pieces of information can be toggled on or off per template, which allows different ticket types — a general admission pass versus a VIP pass, for example — to carry different levels of detail.
- Unlimited templates. There is no cap on the number of ticket designs, and a template can be assigned to any individual event. In practice this means a venue running several recurring event series can maintain a distinct look for each without rebuilding anything.
- PDF delivery by email. Once a booking is confirmed, the customer receives the ticket as a PDF attachment. This is the mechanism that turns the design work into something the attendee actually holds.
The PDF route is a sensible choice for a PHP booking system. PDFs render consistently across devices, print predictably at A4 or Letter, and can be saved offline — which matters at venues with poor mobile reception, where a browser-based ticket may fail to load at exactly the wrong moment.
Where BookingWizz Event Tickets Add Ons fit, and where they do not
The clearest fit is an existing BookingWizz installation that already handles event reservations but stops short at the door. If bookings arrive as emails containing a reference number and staff are checking names against a printed list, this plugin closes that gap without replacing the underlying booking engine. Small venues, workshops, training providers, conferences with a few hundred attendees, and community organisations running ticketed gatherings all sit comfortably in that description.
A second fit is the multi-series operator. Because templates are unlimited and assignable per event, an organisation running a comedy night, a lecture programme and a seasonal market under one BookingWizz installation can give each its own ticket identity. That is a branding requirement rather than a functional one, but it is the kind of detail that separates a professional-looking operation from an improvised one.
There is also a compliance angle. Some events need attendee names printed on tickets for access control, and some need specific terms visible on the ticket itself. Selective field display handles both without a developer.
The wrong choice is equally specific. Anyone not already running BookingWizz should look elsewhere: this is an add-on, not a booking system, and it does nothing without the parent script. Anyone whose events are free, unticketed, or managed entirely through a third-party platform such as a large event marketplace will find no use for it, because the ticket would be generated twice. And anyone running a BookingWizz version older than 6.0.0 cannot install it at all — the vendor states compatibility with v6.0.0 and later only, which is a hard floor rather than a recommendation.
Strengths and limitations of the BookingWizz Event Tickets add-on
Strengths
- Template design, field selection and branding all sit in the administration area, so no code editing is required to produce a custom ticket.
- Unlimited templates with per-event assignment gives genuine flexibility for operators running several distinct event brands.
- PDF attachment delivery is robust, offline-friendly and printable — a better fit for venue check-in than a link to a web page.
- The price is low relative to the work it replaces. Commissioning a bespoke ticket generator would cost far more than $19.
- Installation is a file upload into the BookingWizz plugins directory followed by activation in the admin settings, which is within reach of anyone comfortable with FTP or a hosting file manager.
- The changelog shows the plugin was updated to support BookingWizz v6.0.0 and to add PHP 7+ support, and a subsequent release fixed a PDF export bug reported by a contributor — evidence of maintenance rather than abandonment.
Limitations
- Compatibility is narrow by design. The vendor states BookingWizz v6.0.0 and later only, so the add-on is unusable on earlier versions with no documented workaround.
- The most recent entry in the changelog is from June 2020. That is a long gap, and while the plugin may still function correctly, buyers should treat the absence of recent releases as a signal to test thoroughly against their current PHP and BookingWizz versions before relying on it.
- Delivery is PDF-by-email only. There is no stated support for wallet passes, QR or barcode generation, or a scannable check-in workflow, so anyone expecting door-scanning functionality will need a separate solution.
- No sales figures are disclosed on the listing, so there is no volume of buyer feedback to draw on. That makes the plugin harder to assess than a product with a long review history.
- Because it is an add-on, its quality is partly constrained by BookingWizz itself. Any limitation in the parent script’s booking data — the fields it captures, how it handles refunds or transfers — carries through to what can appear on a ticket.
How BookingWizz Event Tickets Add Ons compare with the wider category
Ticket generation for self-hosted booking systems generally falls into three approaches. The first is a dedicated ticketing platform, which brings scanning, analytics, payment processing and attendee management but also takes a per-ticket fee and moves the customer relationship onto someone else’s domain. The second is a general-purpose PDF or invoice plugin, which can produce a document but has no concept of an event, a template per event, or booking data fields. The third is a purpose-built add-on like this one.
Against a dedicated platform, the trade-off is clear: this plugin keeps everything on the operator’s own installation and costs a one-off $19, but it does not attempt check-in scanning, live attendance reporting or resale handling. Against a generic PDF plugin, it wins on relevance — the template knows what an event is and can pull booking fields automatically — but loses on breadth, since a general document tool can also produce invoices, receipts and certificates.
The honest positioning is that this is a finishing touch, not a ticketing infrastructure. It makes an existing BookingWizz installation look and behave more professionally at the point of delivery. It does not turn BookingWizz into a full event management platform, and buyers expecting that will be disappointed.
Frequently Asked Questions
Does BookingWizz Event Tickets work without BookingWizz installed?
No. It is an add-on plugin that extends the BookingWizz booking script and has no standalone function. Installation places the files inside the BookingWizz plugins folder and activation happens from the BookingWizz administration settings page, so the parent script must already be present and running.
Which version of BookingWizz does this plugin support?
The vendor states that it works with BookingWizz v6.0.0 and later only. Earlier versions are not supported, and no workaround is documented. Buyers on an older BookingWizz release would need to upgrade the parent script before this add-on could be used, which is worth confirming before purchase.
How are event tickets delivered to customers?
Tickets are sent as a PDF attachment in the confirmation email. The customer receives a file they can print or save for offline access, which is convenient at venues with unreliable mobile data. The vendor does not state any alternative delivery method such as a download link or in-account ticket view.
Can different events use different ticket designs?
Yes. The plugin supports an unlimited number of ticket templates, and a template can be selected for any individual event. Combined with the ability to control which information appears on each design, this allows separate event series to carry their own branding and their own level of detail.
Verdict on the BookingWizz Event Tickets add-on
This is a narrow, inexpensive utility that does one job well for a specific audience. Anyone already running BookingWizz v6.0.0 or later and selling ticketed events should find it a straightforward upgrade: the template designer, per-event assignment and PDF delivery cover the essentials of professional-looking ticketing without touching code. The $19 price makes the decision low-risk.
Buyers on an older BookingWizz release, or those who need barcode scanning, wallet passes or attendance analytics, should look at a dedicated ticketing platform instead. The plugin’s last documented release dates from 2020, which is a genuine reason for caution, and the absence of disclosed sales figures means there is little buyer history to lean on. Testing on a staging installation before committing is the sensible approach.
