Checkout Questions
Help articles may not be fully accurate — they can lag behind the app due to frequent updates and automated translation. If in doubt, please contact support.
On this page
Checkout questions are your own questions, asked once per order at checkout — dietary requirements, a company name for the badge, which workshop somebody wants. They sit alongside the standard fields and the answers travel with the order. Find them under Manage → Details & dates → Checkout questions.
What you can do here
- Add a question — a label, a type, whether it is required, and a placeholder hint where the type has a text box.
- Choose the type — short text, email, phone, long text, dropdown, radio buttons, or checkboxes.
- Edit or delete a question, and reorder them.
- Read the responses — how many people answered each question, and for the choice types a count for every option.
- Download the answers — one file with a row per order, and one with a row per option.
The question types
- Short text, Email, Phone — a single line. Email and phone are checked for a plausible format.
- Long text — a box for a sentence or two.
- Dropdown — one choice from a list, collapsed until opened. Good for a long list.
- Radio buttons — one choice with every option visible at once. Good for two to five options, where you want the buyer to see the whole set.
- Checkboxes — any number of choices, including none.
How the answers reach you
- The buyer answers at checkout. A required question stops the order until it is answered.
- The answers are stored with the order and shown on it, so anyone working the orders list can see them.
- The Responses panel on this page counts them: how many answered, and for a choice question how many picked each option.
- Answers CSV gives one row per order and one column per question — the file to hand a caterer or a badge printer.
- Summary CSV gives one row per question and option with its count — the file for a headcount.
Good to know
- Questions are asked once per order, not once per ticket. If you need something from every attendee by name, switch on per-ticket attendee details instead.
- A question belongs to one event. Running the same conference again means adding the questions to the new event.
- The counts and both downloads cover confirmed and approved orders. A cancelled order is somebody no longer coming, so counting their dietary requirement would send the wrong number to the kitchen.
- Changing a question’s type clears its options, because the old ones may make no sense for the new type. Answers already given are untouched.
- If you remove an option people had already chosen, the summary still lists it, marked as no longer an option, so the historic count is not silently lost.
- The downloads sit behind the same permission as the orders export, since the answers are personal data belonging to your attendees.
Troubleshooting
- A question is not appearing at checkout — a question saved with an empty label is skipped rather than blocking the form. Reopen it and give it a label.
- The response count is lower than the number of orders — expected for an optional question, and expected for any question added after selling started: orders placed before it exists have no answer to give.
- “Can I ask each attendee separately?” — not with these. Use per-ticket attendee details for anything that belongs to a person rather than to the order.