Can I have more than one buyer form
you want different checkout forms based on which event the buyer is purchasing for — a hotel-pickup form for guests of one event, a dietary-preference form for another. Tickera supports this at the attendee level, but not at the buyer level. Here’s the distinction and the working pattern.
Buyer form vs. attendee form
In Tickera’s Custom Forms add-on, there are two form types:
Buyer form
Asked once per order, of the person paying. Captures things that don’t vary by ticket — billing phone, company name, marketing opt-in, invoice request. Only one buyer form can be active at a time, and it applies to every checkout regardless of which tickets are in the cart.
Attendee form
Asked once per ticket, of the person attending. Captures things that do vary — meal preference, t-shirt size, accessibility need, hotel arrival date. Attendee forms can be associated to specific ticket types, so a buyer purchasing two tickets to Event A and one ticket to Event B sees the Event A attendee form twice and the Event B attendee form once.
So: only one buyer form, multiple attendee forms
If you need event-specific fields collected from the buyer, you have two options:
Option 1: keep the buyer form generic
Put only universal questions in the buyer form (phone, company, opt-in). Move event-specific questions into the attendee form for that event’s ticket types. Most events fit this pattern fine because the event-specific data really is per-attendee anyway.
Option 2: collect event-specific buyer data via attendee form, on the first ticket only
For events that have a one-buyer-only purchase pattern (typically only one ticket per order), put the “buyer” fields into the attendee form. Each order then asks them once. Not as clean, but workable.
Option 3: use Bridge for WooCommerce + conditional checkout fields
In Bridge mode, WooCommerce owns checkout and there are mature checkout-extension plugins (Checkout Field Editor, Cartflows, FunnelKit) that let you show/hide fields based on cart contents — including which product/event is being purchased. More setup, but full conditional logic. See Bridge for WooCommerce.
What the buyer form is and isn’t good for
- Good for: phone number, company name, billing address, VAT/tax ID, newsletter opt-in, source of referral, agree-to-terms checkbox.
- Bad for: meal preferences (those are per-attendee), event-specific arrival times, ticket-specific notes — those belong in attendee forms.
Related
Was this article helpful?
Yes — great. No or partially? Tell us what was missing — we read every message and use it to improve these docs.