Custom fields let you collect extra information about your patrons — accessibility needs, dietary restrictions, t-shirt sizes, or anything venue-specific. Fields live on the patron record and can optionally appear at checkout.
Go to AdminVenues[venue]Custom Fields to manage your fields.
Field types
| Type | Use it for |
|---|---|
| text | Free-form short answer |
| number | Numeric input |
| date | Date picker |
| boolean | Yes/No switch |
| select | Single choice from a picklist |
| multiselect | Multiple choices from a picklist |
The type is fixed after creation — you cannot change a select into a text field later.
Creating a field
- Click New field at the top right.
- Enter a Label (shown to admins and box-office staff). The key is generated from the label and is permanent — for example, "Seating Preference" →
seating_pref. - Choose a Type. For select and multiselect, fill in Options (one per line).
- Add Help text (optional) — the explanation shown under the field.
- Switch on Required if the field must be answered before checkout can proceed.
- Switch on Show on patron page to display the field on the patron detail page.
- Switch on Ask at checkout if buyers should fill it in when buying. A Buyer-facing label (optional) box appears — use it when the wording your staff need is not the wording a buyer needs.
- Set a Sort order if you care where it sits among your other fields.
- Click Save.
The Fields table lists every field with its label, key, type, and a tick under Patron page and Checkout where each applies. Edit reopens the dialog; the Active switch on the row turns a field on and off.
Checkout behavior
If Ask at checkout is on, the field appears above the Pay button in the public checkout. Required fields prevent payment until the buyer fills them in.
After purchase, answers appear as colored badges on the event's Attendees page — useful for door staff to identify patrons who need specific seating or accommodations.
Deactivating a field
Fields are never deleted — deactivate instead, with the Active switch on the field's row in the Fields table. An inactive field disappears from new checkouts and the patron page, but every answer already collected is kept and still appears in exports.
A required checkout field adds friction to every ticket purchase. Use required fields sparingly — access needs, for example, work well as optional fields with clear help text.
Nonprofit venues start with two ready-made fields, inactive and tagged Suggested in the list: Access requirements (select) and Order notes (text). Flip their Active switch when you want them.
Reindex, next to New field, rebuilds the search index over your patrons' custom-field values. Use it if a field you just added is not yet filterable on the patron list.
Create an optional "T-shirt size" select field with options S, M, L, XL. Turn on "Ask at checkout." Test it in a public checkout tab and confirm the question appears. Then deactivate the field and confirm the checkout no longer shows it.