Create a ticket type when the offer needs it
Use clear names such as regular, early bird or VIP. Explain admission and any differences between types. A VIP label does not automatically allocate a seat, refreshment or separate entrance. Arrange those details for the event and configure scan profiles when needed. Keep the visitor’s choices focused enough to understand quickly.
Describe inclusions alongside the ticket.
Keep combined ticket allocations within capacity
Set event capacity and give each ticket type an allocation. Their combined quantities must not exceed that capacity. The editor shows what happens when regular allocation grows without reducing other types. Its warning does not alter inventory; it explains the relationship between the overall limit and individual allocations. Include complimentary admission in your operational capacity plan.
Account for complimentary and separately reserved admission.
Configure windows and order limits deliberately
Each type supports a price, description, per-order limits and sales window. Check the time zone and alignment with your announcement. Do not assume another price phase opens automatically because an earlier type sells out. Test what visitors can actually order before opening, during sales and after a window closes rather than relying on names alone.
Test availability at sales-window transitions.
Check the order, not only the settings
After configuration, place a test booking containing different ticket types. Inspect the total, confirmation and issued tickets. Brief admission staff on relevant types and instructions. This editor uses fictional cards and quantities; it does not create saved events or ticket types and cannot replace actual checkout inventory checks. Test each admission variant before opening.
Scan a test ticket for every different admission entitlement.