Every article explains what a feature does, when to use it and how to proceed step by step.
Tickets and access types
- Set up ticketing: SIAE, access titles, capacity and seat map The Add tickets step gathers in five sections the SIAE configuration, the Free and Paid cards used to create the titles, the Tickets added to the event table, the capacity and the seat map. Every field with its exact labels, the values calculated automatically, the capacity thresholds and all the error messages.
- Create an access title The Create access type page, section by section and field by field: status, basic information (name, price, fees, quantity, sales period, map element), advanced settings, visibility, availability and notices, purchase form. With the real default values, the blocks for SIAE events and the error messages.
- Schedule sales: dates and dependencies between titles A title can open at a precise date or when the preceding title closes or sells out. How to build early bird and later releases, when the second mode appears, what the fan sees before and after the opening, what happens if the preceding one becomes available again and all the validation rules on the dates.
- Limited visibility: access codes, sales channels and quotas With Limited visibility a title is seen only with an access code or by arriving from an enabled channel (direct sales, members of the organization, tracking channels), with sales quotas per channel. Every field of the Visibility section, what the fan sees in the booking screen, the attempts allowed and all the messages.
- Low-stock ticket warning The ONLY 1 LEFT / ONLY N LEFT badge appears in the booking screen when the available tickets of a title drop to the threshold. It is on by default with a threshold of 10: how to change it or turn it off in the Availability and notices section, how it is calculated and when it does not appear.
- Purchase form: named or transferable titles and attendee details For every title you decide whether each attendee has to enter their own details (Named) or whether one single holder is enough (Transferable), and which information to ask for as Inactive, Optional or Required. Default value, forcing above 5,000 seats, what the fan sees in the Who’s attending? screen and the error messages.
- Advanced settings: quantity per reservation, waiting list and pre-sale rights The Advanced settings section limits the tickets per order, turns on the waiting list for the sold out, adds the pre-sale right and the description of the title. What every field does, how the waiting list really works (the fan signs up, everyone on the list is alerted, table in the Reservations report) and the messages the fan sees.
- Status of an access title: Active, Sales ended, Sold out, Hidden The selector in the header of the title controls the sale independently of the dates. What each of the four statuses does, what the fan sees, the effects on the waiting list, badges and dependent titles, the Hide shortcut from the table and how to go back on sale.
- Edit, hide and reorder access titles From the Tickets added to the event table you open a title with View, take it off sale with the Hidden, Sales ended or Sold out statuses (there is no deactivation function) and drag the rows for the display order. Fields locked in SIAE events with reservations, control of the editor and messages.
- Common validation errors for access titles At publication Nightify checks quantity, capacity, map, sales dates, dependencies, visibility and SIAE rules of every title. How the issues are shown (one card each, with the name of the rate and the Edit access type button) and every message with its cause and its fix.
- Glossary of Nightify ticketing The terms you meet in the console and in the Nightify Business app, explained in a few lines and linked to the article that goes deeper: organization and roles, event statuses, access titles, DDP and fees, capacity and BA code, seat map, channels and promoters, reservations, QR and wallet, waiting list, resale and name change.