Custom checkout questions

Every event can define its own list of custom questions that appear on the checkout page. Use them to collect anything you need beyond the standard name-and-email — dietary preferences, attendee names for named tickets, t-shirt sizes, accessibility needs, “how did you hear about us”, a required age confirmation.

You manage questions per-event from the event editor in the admin dashboard. Answers arrive with every paid order — in the admin order detail page, in the CSV export, and in webhook payloads.

Two scopes: per order or per attendee

Every question is asked in one of two ways:

Per order — asked once per checkout, no matter how many tickets. Good for things that apply to the whole booking: “Dietary preferences”, “How did you hear about us”, “Any accessibility needs”.
Per attendee — asked once per ticket. The form repeats N times when the buyer purchases N tickets. Good for named tickets, t-shirt sizes, individual meal choices — anything where each person has their own answer.

A 3-ticket order with a per-attendee “T-shirt size” question will show the buyer three separate size dropdowns at checkout — one per ticket — before they pay.

Field types

Four input types cover the common cases:

Type	Renders as	Use for
Short text	Single-line input	Names, short free-form answers
Long text	Multi-line textarea	Addresses, notes, longer comments
Dropdown	Select menu	T-shirt sizes, meal choices, predefined lists
Checkbox	Single checkbox	Consents, confirmations, yes/no flags

For dropdowns, you enter the options as a list — one per line — in the question editor.

Required vs. optional

Each question has a Required toggle. When on, the buyer can’t complete checkout without providing an answer — the browser blocks the submit and the server rejects anything that slips through. When off, the question is a nice-to-have and blank answers are stored as empty.

For dropdowns, buyers can only submit one of the options you defined — arbitrary text is rejected.

Setting up a question

Open the event in the admin dashboard
Scroll to Custom checkout questions
Click Add question
Fill in the label (what the buyer sees), pick a type and a scope, and toggle Required if needed
Save — the question appears on the checkout page immediately

You can reorder questions by drag-and-drop — the order you set is the order buyers see.

Where answers appear

Admin order detail — answers show up on each order’s detail page, grouped by scope. Order-scope answers appear once; attendee-scope answers appear under each individual ticket.
Attendee CSV export — from the event’s actions menu, pick Export attendees (CSV). You get one row per ticket with customer info, ticket title, redemption status, and all custom answers as extra columns. Rows are sorted by customer email so all tickets for one buyer stay together — ready for check-in lists, catering sheets, or t-shirt orders.
Webhooks — order events (order.paid, order.refunded, order.cancelled) include a custom_field_answers array at the order level and per item. See the webhook docs for the exact shape.

Renaming and deleting questions

Renaming a question’s label is safe at any time. Answers are linked to the question by internal ID, not by label, so existing orders keep their answers and the new label appears everywhere from the next load.
Deleting a question stops asking it going forward. Answers already collected stay in the order record but are no longer shown in the admin, CSV, or webhook payloads. If you need to recover them, restore the question with the same label — but note that a new question gets a new ID, so historical answers still won’t re-associate. If in doubt, archive (remove from future checkout) by setting Required off and keeping the question around rather than deleting.

Tips for writing good questions

Keep labels short and specific. “T-shirt size” beats “Please choose your preferred t-shirt size from the options below”.
Only require what you actually need. Every required field adds friction. If you’ll accept blank answers, mark it optional.
Use help text for context. The optional help text shows below the input — use it for clarifications like “European sizes, eur fit runs small”.
Use per-attendee for things that vary per person. Don’t ask “Attendee names” once on a group booking with a textarea — use a per-attendee text question and get a clean list back.