Custom Forms — an add-on for the Tickera plugin

Capture what you need
at checkout, on the ticket, in the app.

Drag-and-drop form builder for Tickera. Add text, dropdowns, checkboxes, radios, textareas to your checkout — collect t-shirt sizes, meal choices, special-access needs, accommodation info. Every answer lands in the WP admin, on the ticket itself, in the Checkinera app, and in your CSV/PDF exports.

  • Drag & drop builder — no coding, no shortcodes
  • Buyer-level fields and attendee-level fields — separate forms
  • Show fields on the ticket template — print attendee data on PDF
  • Field data flows into Checkinera app, PDF and CSV exports
Or get Bundle — $199/yr

Included in Bundle & Lifetime

What it does

Six ways to ask
a buyer something.

Every field type WordPress site owners actually use. Build it once, attach it to your event, the form lives on the checkout page.

Text input

Single-line or multi-line. Required or optional. Default value, placeholder, validation rules — standard WordPress form behavior.

Checkboxes

For consent, multi-select, dietary needs, accessibility requests. Each checkbox option saves separately on the order.

Radio buttons

Single-choice answers — meal type, t-shirt size, age range. Cleaner than a dropdown for short option lists.

Dropdowns

Country, time slot, ticket category — long option lists collapsed into one select element.

Textareas

Free-form answers — dietary notes, accessibility details, “anything else we should know” catch-all.

Column layout

Stack fields full-width, side-by-side, or in three columns. Control the order in the builder, save, the form respects it.

In the WP admin

The form builder
in motion.

01 · Build the form

Drag, drop, label, done.

Open the Custom Forms admin screen, drag the field type you want from the sidebar onto the canvas. Label it, mark required or optional, set placeholder text, choose where it displays (admin only / Checkinera app / both / on the ticket).

  • Multiple field types — text, textarea, checkboxes, radio buttons, dropdowns
  • Per-field placement control — admin, app, ticket
  • Reorder by drag — no save-and-refresh dance
Custom Forms add-on — form builder admin screen with drag-and-drop fields
02 · Buyer vs attendee fields

Two forms in one tool.

The buyer fills out the buyer form once (their name, email, billing details). Each ticket holder fills out the attendee form separately (their name, dietary, accessibility). Buying 4 tickets? You get 4 attendee forms in a row, one buyer form at the top.

  • Buyer form — one per order, billing-style
  • Attendee form — one per ticket purchased
  • Both saved on the order, both viewable in admin
Custom Forms add-on — standalone attendee form rendered on the Tickera checkout
03 · On the front-end

Themed to match your site.

The form inherits typography, colors, and spacing from your WordPress theme — no inline styles to fight, no “form plugin look”. If your theme uses Hanken Grotesk and a 12px border-radius, so does the form.

  • CSS-clean, no inline styles imposing a look
  • Responsive grid — stacks on mobile, columns on desktop
  • Works with Bridge for WooCommerce — renders on the WC checkout
Custom Forms add-on — front-end form rendered on the Tickera event checkout
What people collect

Eight things every
organizer asks at checkout.

T-shirt sizeS / M / L / XL via radio buttons
Meal preferenceVeg / vegan / standard for catering
AccessibilityWheelchair, sign language, hearing loop
VIP add-onsBackstage tour, M&G, signed merch
Company nameFor conference badges + invoice
Workshop choicePick a track — A / B / C session
AddressWhere to ship the physical badge
Emergency contactName + phone for festivals/sports
Common questions

Things people ask
before they buy.

Where does the collected data go?
Wherever you set on a per-field basis. Always saved to the order in the WP admin. Optionally displayed in the Checkinera check-in app, optionally printed on the PDF ticket, optionally included in the CSV Export or PDF export. You decide per field.
Can I print the answer on the ticket?
Yes. Turn any form field into a ticket-template element in the Tickera ticket designer — the field value renders on the PDF ticket exactly where you place it. Useful for printing attendee name, meal choice, table number, badge category, etc.
What’s the difference between “buyer” and “attendee” forms?
A buyer is the person paying. An attendee is the person using the ticket. Buying 5 tickets? One buyer form (billing details) + 5 attendee forms (one per ticket). Both can be customized independently.
Does it work with Bridge for WooCommerce?
Yes. When you sell through Bridge for WooCommerce, Custom Forms renders directly on the WooCommerce checkout page. Field values are saved on the WC order, exported via WC, and printed on tickets as usual.
Can I make a field required?
Yes — mark each field as required or optional. The form blends seamlessly with your theme’s design so it looks native at checkout.
What does it cost?
$69/year as a standalone. 0% per-ticket commission, like every Tickera add-on. Or free with the Bundle ($199/yr) or Lifetime ($399 once).

Ask once.
Use it everywhere.

$69 a year. Unlimited forms, unlimited fields, unlimited orders. The data flows to the order, the ticket, the check-in app and your CSV exports automatically. Zero per-ticket fee, ever.

Or get Bundle — $199/yr
14 years of receipts·365,285 downloads·$0 commission, ever
Tickera
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.