How to add a ticket type to a published event without losing track of stock

1. Confirm the new type and available stock

Download the live ticket-type launch card (Markdown, English)

Record the new type’s purpose, admission unit, eligible date or session, and the number of tickets it may issue. Compare that number with approved event capacity, existing sold and available tickets, and any shared pool or reserved seats. If it is only more stock for an existing offer, use that provider’s quantity-change route instead. Do not create capacity by changing a label.

2. Create the type with deliberate settings

Open the published event’s ticket editor and add the new type. Set its name, approved price or free status, quantity, sales window, and visibility where your provider offers those controls. Check any ticket group or section link before saving. Peatix asks for name, paid price if applicable, and quantity; Eventbrite includes availability and section settings; Ticket Tailor offers ticket status and optional groups. These are provider-specific controls, not a shared menu.[1][2][3]

3. Check the live buyer view

Know what Save will do. Peatix says a newly added type becomes available for sale as soon as it is saved on a published event. On other systems, inspect the configured status and start time rather than assuming the same result. Immediately open the public buyer page and verify the new name, date, price display, availability, and relevant checkout description. Check an excluded or not-yet-open type too. Do not place a live test order without an approved test route.[1][2]

4. Reconcile the event record

Compare the ticket list and remaining inventory before and after. Ticket Tailor notes that individual type limits can exceed a separate event capacity, so check the actual overall limit rather than summing type labels as a safety proof. Verify existing sold tickets and buyer options were not unintentionally changed. If the new type is invisible, unexpectedly on sale, or draws from the wrong pool, stop promotion and assign an owner to correct and recheck it.[4]