The Purchase form section establishes which details are collected at the moment of purchase for every access title. It is the choice that decides whether the tickets are held by each attendee or whether they all refer to whoever books.
At a glance
- Where: Create access type or Edit access type page → Purchase form section, the last one on the page.
- Permissions: Manage ticketing.
- The two modes: Named (Separate details for every attendee.) and Transferable (One booking holder for the entire booking., the default value of a new title).
- What you get: with Named the fan fills in the Who's attending? screen for every ticket; with Transferable nothing more is asked of them.
Before you start
- The description of the section reminds you that Choose whether this admission is named or transferable. The choice and attendee details are independent of other admission types in the event.: every title has its own configuration.
- The details of the buyer (whoever places the booking) are a different configuration, at event level, called Buyer details (without an account): it is managed by the Nightify administration, not by this section.
Step by step
- Open the Purchase form section of the title. What you see: two cards, Named and Transferable, with the info icon explaining: Named: details are collected separately for each attendee. Transferable: admissions use the booking holder’s details and can be used by different people without collecting their individual details.
- Choose the mode. Tap Named if every person has to be identified, Transferable if the holder of the booking is enough. What you see: for events with a capacity of 5,000 seats or more the choice is disabled on Named with the hint For events with capacity of 5,000 seats or more, attendee details must be required.
- Set the information requested. In the Information requested from each attendee block (description: Choose the details to collect for each person using this admission.) every field of the form has a select with Inactive, Optional and Required. The meaning is: Inactive: the field is hidden. Optional: the field may be left blank. Required: the field must be completed to continue. What you see: first name and last name are fixed on Required with the padlock icon and the hint First and last name are required to identify the attendee on named tickets.
- Save the title with Create access type or Edit access type. For an event already online submit the changes with Publish changes.
Fields and options
| Field | What it means | Rules |
|---|---|---|
| Named | Details collected separately for every attendee; every ticket has its own holder. | Mandatory from events with 5,000 seats up. |
| Transferable | The tickets refer to the holder of the booking and can be used by different people. | Default value of a new title. |
| Information requested from each attendee | Which fields to fill in for each named ticket. | First name and last name always Required; the other fields of the catalogue chosen between Inactive, Optional and Required. The fields are requested for every unit bought: whoever buys three named titles fills in the details of three attendees. |
What happens next
- If there is at least one named title in the cart, after choosing the ticket types the fan goes through the Who's attending? screen: one card per ticket with Same as buyer to copy their own details and Confirm attendee to close the card; the status goes from To complete to Completed and the payment unlocks only with every card completed.
- The details of the attendees appear in the Reservations report and in the reservation detail, with e-mail and telephone shown in accordance with the marketing consent of the fan.
- The configuration is saved on the title: changing it does not modify the reservations already recorded and applies only to later purchases.
Messages and errors
| Message | Why it appears | What to do |
|---|---|---|
| Select valid attendee registration form fields. | The form submitted contains unrecognised fields (typical after a page left open for a long time). | Reload the page and repeat the choice. |
| Select at least one attendee registration form field. | With Named all the fields are set to Inactive. | Set at least one field to Optional or Required (first name and last name are already required). |
| First and last name are required to identify the attendee on named tickets. | First name or last name are not set to Required on a named title. | Reload the page: the two fields are locked on Required. |
| Please complete this field to continue. | The choice between Named and Transferable is missing. | Select one of the two cards. |
Special cases
- Lists and accreditations. A free named title collects first name and last name of every person: it is the typical configuration for the lists where you want to know who comes in.
- Large events. From 5,000 seats up the mode is forced to Named for all the titles; even titles created before raising the capacity are treated as named.
- Change of holder after the purchase. There is no “name change” setting on the title or the event: the possibility of changing the holder depends on the SIAE resale enabled by the Nightify administration, not on this section.
Rules and limits
- First name and last name cannot be made optional on a named title.
- The available fields are those of the catalogue of the attendee registration form: you cannot add custom fields from this page.
- Ask only for the details you need: every extra required field makes the checkout longer.
Related articles
- Create an access title
- Set up ticketing: SIAE, access titles, capacity and seat map
- Advanced settings: quantity per reservation, waiting list and pre-sale rights