Best practices for Club Events Management

Set the item's stock before you start selling

The number of tickets available for an event is the stock of the linked Item, not a field on the event itself. Set it before announcing the event, and keep in mind that both paid orders and free tickets reduce it.

Split permissions by role, not by person

Club Events has separate permissions for viewing events, creating events, editing events, viewing tickets, editing tickets, scanning tickets, and issuing free tickets. Give door staff only Scan tickets — it lets them mark a ticket as used without exposing any guest's email, phone or company. Reserve Edit tickets and Issue free tickets for the people who actually manage the guest list.

Use "Choice" options for anything guests need to pick

If guests need to choose a meal, a table or a package, add the options on the linked Item (up to four) instead of tracking it separately outside NIZU. It will then show up consistently on every ticket and on the printed sheets.

Issue free tickets one at a time when guest details matter

Issuing several free tickets in one go creates them empty, to be filled in later. If you already know who each guest is, issue them one ticket at a time so the name goes straight onto the ticket and the printed materials.

Print tickets and labels only once the guest list is final

Both printable sheets (tickets with QR codes, and name labels) are generated from the guest list at the moment you print them. Reprint after any late change — a new free ticket, a corrected name, a cancellation — so the door staff and the badges are working from the same list.

Link the event to a Project when you need to track its budget or tasks

The event's optional Project link is the natural place to plan the tasks and expenses around an event (venue booking, catering, promotion) while Club Events Management stays focused on tickets and the guest list.

Keep the event's country and dates accurate

The event's city, country and dates appear on every printed ticket and label. Set them when the event is created rather than leaving them for later, since tickets may already have been printed by the time a change would be noticed.