Checkout always collects a name, an email address and a phone number. Everything else is up to you. Registration questions, on the event page, is where you decide what else a buyer is asked — a t-shirt size, a date of birth, an emergency contact, a waiver they have to tick.
Answers land on the attendee list about the attendee list and in its spreadsheet export.
Adding a question
From Events, open the event and find Registration questions. Press Add question.
Question — what the attendee reads above the box. Write it the way you would say it out loud: "T-shirt size", not "tshirt_size".
Answer type — how they reply. Short text for a name, Choose one for a size, Date for a date of birth, Tick box for a waiver. The full list is below.
What this is — optional. Most questions need nothing here. It exists so we can apply a rule that has to find one particular answer — an age limit reading a date of birth, a stock count reading a t-shirt size — without guessing from how you worded the question. Picking one changes nothing about how the answer is collected or stored.
Only one question per event can claim each meaning. If you mark the wrong one, set it back to Nothing in particular before marking the right one.
Help text — optional, and worth using more often than you would think. It is the line under the box, and it is where a sizing chart, an example, or "bring this ID to the venue" belongs.
Ask this — for every ticket, or once for the whole order. This one matters; see below.
Required — checkout will not continue until it is answered.
As you fill the form in, the panel underneath shows exactly what the buyer will see. It is the same control that renders on the real checkout page, not a mock-up of one.
For every ticket, or once per order
Somebody buying four tickets answers a per ticket question four times and a per order question once.
Get this one right the first time
Once a question has answers you cannot move it between the two, because the answers are attached to whichever it already was. You would have to archive it and start a new one.
The test is who the answer is about:
- Per ticket — anything about the person attending. A size, a date of birth, a meal choice, an emergency contact. This is the right answer far more often than not.
- Once per order — something about the booking as a whole. A company name for the invoice, a purchase order number, how they heard about you.
An emergency contact asked once per order is the buyer's own contact — which is no use at all if the person who needs help is one of the other three people on the booking.
The answer types
Options, for the two choice types
Type an option and press Enter. Repeat. Press the × on one to take it out again.
Adding an option is always safe, whenever you do it. Removing one is safe only until somebody picks it — after that we refuse, and tell you which option it was. The reason is that an answer sitting outside the current list quietly stops being counted, so your totals would be wrong with nothing to show for it.
Limiting how many can pick an option
Each option has a box beside it for a limit. Leave it blank and the option is unlimited; put
250 next to M and checkout stops offering it once about 250 people have chosen it.
This is what sizes a merchandise order: set the counts you actually ordered, and buyers pick from what is left rather than from a list where three sizes ran out weeks ago.
A limit is approximate
Two people checking out at the same moment can both take the last one. The limit is there to size an order, not to guarantee a count — unlike ticket capacity, which is exact.
The reason is deliberate: making it exact would put a lock on the payment path for every buyer. Overselling a ticket means somebody paid and cannot get in; overselling size M means ordering a few more mediums.
Removing an option removes its limit with it.
Asking only some buyers
If your event has more than one ticket type, each question gets a row of tick boxes. Leave them all clear and everybody is asked. Tick some and only those buyers see it.
Buyers only ever see the questions attached to what is actually in their cart, so somebody buying a spectator ticket is not asked their running category.
Changing a question later
Edit reopens the form. What you can change depends on whether anybody has answered yet — the panel shows an answer count on each question so you can tell at a glance.
The locked ones are locked because the answers are already stored in a shape that matches the old setting. Changing it would not convert them — it would leave them there, unreadable, and nothing would look broken until you opened the export.
When you need one of those changes, archive the question and add a new one.
Archiving, and why nothing is deleted
Archive takes a question off the form. New buyers stop seeing it; everyone who already answered keeps their answer, and it still appears on the attendee list and in the export, marked as archived.
There is no delete, on purpose. Deleting a question would take every answer with it, including from orders placed months ago. Restore puts an archived question back on the form.
Reordering
The up and down arrows on each row move a question. The order here is the order buyers see, and it is also the column order in the export.