Tickera - Custom Forms

The person who pays for the ticket is not always the one sitting down to dinner

Selling tickets is the easy part. The hard part comes later: finding out which t-shirt size, which meal or which accessibility help each person needs when all you have is the name and email of whoever bought. The usual result is emails chasing answers a week before the event and spreadsheets nobody keeps up to date.

Someone who buys four tickets is one person, but there are four attendees with different needs. Tickera - Custom Forms starts from that difference: one form for the buyer (once per order) and another for each attendee (once per ticket), both with fields you design yourself.

Six ways to ask, and you decide where each answer shows up

The builder is drag and drop, with no code or shortcodes. You drag the field type onto the canvas, label it, mark it as required or optional and reorder by dragging. The available types:

• Text, single-line or multi-line, with default value, placeholder and validation rules.
• Checkboxes, useful for consents or dietary needs; each option is saved separately on the order.
• Radio buttons, better than a dropdown when options are few (size, meal type).
• Dropdowns for long lists, such as country or time slot.
• Textareas for free answers like "anything else we should know".
• Column layout: full width, two or three columns, stacking on mobile.

The most useful part is per-field control: each one can be shown only in the admin, in the Checkinera app, in both or printed on the ticket. That way you don't show entry staff data they don't need. The form inherits your theme's typography and colors, so at checkout it doesn't look like a foreign form.

What to ask depending on the type of event with Tickera - Custom Forms

Conferences and congresses

Company name is useful for badges and invoices, and the workshop or session choice (A, B or C) lets you know how many people will be in each room before the day. If you print badges, you can carry the attendee category over to the ticket design.

Festivals and sports events

An emergency contact (name and phone) per attendee is the kind of data nobody remembers to ask for until it's needed. With VIP extras, such as a backstage tour or signed merchandise, you can make it clear on the order who is entitled to what.

Dinners, workshops and events with catering

Vegetarian, vegan or standard meal, accessibility needs (wheelchair, sign-language interpreter, hearing loop) and t-shirt sizes. If any field collects health data, such as allergies or disability, think beforehand about what you ask and why, because you will have to handle it carefully.

Common questions about fields, tickets and WooCommerce

Can I print an answer on the ticket? Yes. Any field can become an element of the ticket template from the Tickera designer and appears on the PDF wherever you place it: name, meal, table number or badge category.

Where does the data end up? Always on the order, inside the WordPress admin. After that, depending on what you set for each field, also in Checkinera, on the PDF ticket and in the exports.

Does it work if I sell with WooCommerce? Yes, with Bridge for WooCommerce the form appears on the WooCommerce checkout and the values are saved on the order.

Is there a limit on forms or fields? You can create as many forms and fields as you need and attach them to each event.

It needs Tickera, and CSV export requires another add-on

It is a Tickera add-on, not a general form plugin: it is no use for a contact form or for a shop that doesn't sell tickets with Tickera. To see the answers in the check-in app you need Checkinera, and CSV export depends on the CSV Export add-on. Data is collected per order, so if you want to ask an attendee something after the purchase, you will have to contact them another way.