Custom checkout fields

Overview

Checkout fields let you collect additional information from attendees at the time of purchase. The fields appear on the checkout form below the standard name and email inputs. Responses are stored per ticket and are included in the CSV export.

Adding a checkout field

1. Open the event and click the Checkout fields tab.
2. Click Add field.
3. Fill in the field settings:

Setting	Required	Description
Label	Yes	The question or field name shown to the attendee (e.g. T-shirt size, Dietary requirements).
Field type	Yes	Controls the input rendered on the form (see field types below).
Placeholder	No	Hint text shown inside the input before the attendee types.
Required	No	When checked, the attendee cannot complete checkout without filling in this field.
Options	Dropdown only	List of choices for a dropdown field — one option per line.

1. Click Save field.

Field types

Type	Input rendered	Best for
Text	Single-line text input	Short answers: name, shirt size, reference number
Long text	Multi-line textarea	Open-ended answers: special requests, notes
Dropdown	Select menu	Fixed list of choices: age group, meal preference
Checkbox	Checkbox	Single yes/no consent or agreement
Phone	Phone number input	Mobile number for WhatsApp or SMS contact
Number	Numeric input	Quantities or numeric IDs
Date	Date picker	Birthdates or specific dates

Reordering fields

Fields are displayed in Position order. Edit a field and change the position number to adjust where it appears in the form. Lower numbers appear first.

Editing and deleting fields

• Edit: click the pencil icon next to the field to update any setting.
• Delete: click the trash icon to permanently remove the field. Existing responses stored against this field on past orders are also removed.

Viewing responses

Checkout field responses are visible on the attendee list (each field appears as a column) and in the CSV export. Fields are shown in position order.

Edge cases / gotchas

• Checkout fields are per event, not global. Each event has its own independent set of fields. There is no way to copy fields between events at this time.
• Changes affect future purchases only. If you add or modify a field after some attendees have already purchased, existing ticket records will show a blank response for that field.
• Dropdown fields require at least one option. Saving a dropdown without at least one non-blank option will fail validation.
• Required fields block checkout. If you mark a field as required after some attendees have already purchased, those past records are unaffected — the requirement only applies to new purchases.