SupportCandy Print Tickets

SupportCandy Print Tickets is an add-on centred on one clear job: putting print functionality on a ticket page. The supplied description presents it as an event ticketing tool as well, with printable and PDF tickets, ticket templates, multiple admission types, purchase-triggered generation, inventory controls and sales reporting. That makes it more than a browser print button, although the boundary between the print add-on and the wider ticket workflow is worth examining before adoption.

What it covers

The core proposition is straightforward. An organiser creates or manages an event ticket, and the customer receives a version intended for printing or sharing. The feature list specifically mentions PDF generation, which is a practical format for sending a ticket by email or keeping a copy outside the site. Automatic generation after purchase confirmation also places ticket creation at a defined point in the customer journey rather than leaving attendees to assemble their own documents.

Templates are intended to carry event branding and theme styling into the printed result. Support for general admission, VIP and other ticket types gives an event more structure than a single undifferentiated pass. The stated integration with popular event management plugins is also important: an add-on of this kind is most useful when ticket records and event data remain connected to the existing site rather than being recreated for printing.

Useful ticket controls

• Customisable ticket templates for branding and event presentation.
• PDF ticket generation for printing and email sharing.
• Multiple ticket types, including general admission and VIP.
• Automatic ticket generation after purchase confirmation.
• Real-time inventory management intended to reduce overselling.
• Sales and attendance reports for reviewing ticket activity.
• An interface described as suitable for both administrators and customers.

That combination gives the add-on a wider operational role. Inventory handling addresses availability, while reporting covers the organiser’s view after sales have taken place. The customer-facing side is not limited to a back-office print command either; the description explicitly includes attendee use and sharing by email.

Fits an existing workflow

The strongest use case is an event site that already has a ticket or purchase process and needs a physical output for attendees. A branded PDF is useful for guests who prefer paper tickets, while multiple ticket categories keep VIP and general admission records distinct. Organisers also get a stated route from purchase confirmation to ticket creation, inventory tracking and attendance reporting.

The interface claim is modest but relevant. Administrators need controls for ticket templates, types and stock, while customers need access to the finished ticket. The product’s value therefore rests on keeping those two sides connected: the organiser manages the event data, and the attendee receives a usable document.

What to weigh

The first reservation is scope clarity. The short summary describes a SupportCandy add-on that adds printing to a ticket page, while the longer feature list describes a broader event system with purchase-triggered generation, inventory management and attendance reports. Those are materially different expectations. Sites looking only for printable output should establish which capabilities belong to the existing SupportCandy setup and which are supplied by this add-on.

The second trade-off is that the feature list does not identify the supported event management integrations, template controls or reporting details. “Popular” integrations is not the same as naming a compatible plugin, and the description gives no information about fields available in a PDF, attendance-report breakdowns or inventory rules. That leaves more configuration and compatibility questions for an organiser to resolve before committing the ticket workflow to it.

Who it suits

SupportCandy Print Tickets suits event organisers who need branded paper or PDF tickets alongside an existing WordPress ticket process. It is particularly relevant where events use more than one ticket class and where inventory and attendance records matter as much as the printable document. It is less compelling as a standalone event platform on the information supplied: its clearest, most defensible role is extending a ticket page with structured, shareable output.