The short answer
On One Ticket, add a question to the event under Questions at checkout. Make it a dropdown for the common answers, such as None, Vegetarian, Vegan, Gluten free, Dairy free, and add a free-text question for allergies so nobody has to fit a serious allergy into a list. Mark either one required and a ticket cannot be bought without an answer.
Ask it of the right ticket. A question can belong to one ticket type, so a dinner ticket asks about food and a drinks-only ticket does not.
The answers sit against each order in Orders and in the attendee CSV, which is the list the kitchen needs. Export it the day before, after the late bookings.
Which fits your event?
Start from the one requirement that decides it.
| Your main requirement | Start with |
|---|---|
| A buffet where everything is labelled | A line in the description |
| A seated dinner, a supper club or a gala | A required question at checkout, on One Ticket |
| Only some tickets include food | A question on those ticket types only, on One Ticket |
| Ten friends at a restaurant | A message in the group chat |
A question nobody can skip gives the kitchen a complete list. A form sent later gives it two thirds of one.
How it works in practice
Nothing here is food safety advice. Ask the venue and the kitchen how they want allergies reported.
| What you set | What it does |
|---|---|
| A required dropdown | Every ticket has an answer: none, vegetarian, vegan, gluten free |
| A free-text allergy question | Room for the answer that matters most |
| Asked on one ticket type | Dinner tickets ask; drinks-only tickets do not |
| The attendee export | One list for the kitchen, by name |
One Ticket for a recurring room
Everything below follows from one decision: a series is one object, not a list of dates.
| Feature | What it does |
|---|---|
| Who keeps coming | Roll call, after every session of a series: who is new, the regulars and who has stopped coming, by name, with an address to write to |
| Subscriptions | One subscription covers every session in a series. Each night's ticket is minted ahead of time |
| Paid out | Every ticket is charged to your own Stripe account. It is paid out to your bank two days after each event, or as it sells on request through One Ticket's trust system |
| Fees | You keep 100% of your ticket price. Buyers pay a small booking fee: a platform tier of 35c to $1.45 a ticket, then 1.5% of the price above $100, plus card processing. On a $25 ticket that is $1.45 all in, so the buyer pays $26.45. Free tickets cost nothing |
| Refund if it changes | Move the date, start time or place after people have booked and every one of them can refund in full, booking fee included, until it starts, whatever your refund policy says. You are warned before you save, and everyone booked is emailed the new details |
| Refund requests | On a case-by-case event the buyer asks from their ticket. You have 3 days to refund or decline; a request nobody answers goes to One Ticket support, and your payouts are held until it is settled |
| Scam protection | Our emails carry none of an organiser's own links or phone numbers, and a new organiser's money is held until after the event |
| Verified tick | On every plan, earned by selling here: 3 past events that sold tickets, 25 tickets, payouts verified, no chargebacks and no ignored refund requests. Checked every hour; a chargeback or an ignored request takes it away at once |
| Your page | Your colours, your title font, your cover. Nobody else's event on it |
| Not included | A marketplace. There is no search page and no audience to sell into; the people are the ones you bring |
Answers to your questions
Can I make dietary requirements a required question?
Yes. A required question must be answered before a ticket can be bought.
Can I ask only on tickets that include food?
Yes. A question can belong to a single ticket type.
Where do the answers go?
Against each order in Orders, and into the attendee CSV export.
What kind of questions can I ask?
Dropdowns with your own options, and free-text questions, each optional or required.