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. Buyers can answer at checkout or later from their order page. Current answers appear in the admin order detail and CSV export, and are included when order webhooks are generated.

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, optional, or completed later

Each question has a Required toggle. By default, a required question blocks checkout until the buyer answers it. An optional question can stay blank.

Turn on Answer after purchase for a required question when the answer is needed for the event but not necessarily known during checkout. The field stays visible without blocking payment. Missing answers are highlighted on the buyer’s order while editing is open and remain visible in the organizer’s open-answers worklist after the deadline.

Every question also has an optional Changeable until deadline, entered in the event’s timezone. Leave it blank to use the event start, or choose an earlier time. Buyer editing always closes at the event start at the latest, even if you move the event earlier. Before the deadline, buyers can complete or correct order- and attendee-level fields from their order page. Existing required questions still block checkout unless you enable later completion, but their submitted answers can also be corrected before the deadline.

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

Buyer completion and organizer follow-up

The buyer completes the answers for the whole group. They open the existing order link from their confirmation email or sign in passwordlessly and choose Purchases. Editing is available for orders with valid tickets; cancelled admissions cannot be edited by the buyer.

For every event, Open answers lists missing required answers that allow completion after purchase, grouped by buyer and order. It shows which person and question are still open, the recorded contact status, and which deadlines have passed. Cancelled admissions are excluded. After a deadline, the buyer can no longer edit that answer, but organizers can still correct it from the order.

Reminders for missing answers are manual. The worklist opens a prepared email in your email app. After contacting the buyer, record the sent or received email, phone call, or in-person conversation on the order’s worklist entry. Opening the email alone does not change the contact status. You can also add internal notes; these appear in the customer timeline without marking the buyer as contacted.

Setting up a question

Open the event in the admin dashboard
Scroll to Custom checkout questions
Click Add question
Fill in the label, pick a type and scope, and choose whether it is required, can be completed after purchase, and has a custom deadline
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.
Buyer order page: buyers can complete or correct answers until each question’s deadline. Missing required answers that allow later completion are highlighted while editing is open.
Open-answers worklist: organizers see missing required answers that allow later completion, contact status, deadlines, and a direct route to email or edit the order.
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. Completing or editing answers does not trigger a separate webhook or update an already generated payload. Use a fresh attendee CSV export to retrieve later answers. 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 removes it from checkout, answer displays, CSV exports, and newly generated webhook payloads. Stored answer values remain on the order, but creating another question with the same label does not reconnect them because it gets a new ID. Export answers before deleting a question if you need to retain them. Turning Required off keeps the question and its answers visible; it makes the question optional.

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.