Ticket Types and Add-Ons
Set up the tiers buyers choose from, the optional extras sold with them, and the rules that protect tickets already sold.
An event sells ticket types (the tiers a buyer picks between, such as General Admission or VIP) and optionally add-ons (extras like parking, merchandise, or a drink package). Both live on the Tickets & Add-ons tab of the event, and the tab badge counts them together.
An event needs at least one active ticket type with capacity before it can be published.
Ticket Types
Add Ticket Type opens a form; clicking an existing row opens the same form to edit it.
| Field | Notes |
|---|---|
| Name | Required, up to 80 characters. Shown to buyers. |
| Description | Optional, shown under the tier on the public page. |
| Price | Required. Enter 0 for a free ticket (see below). |
| Quantity available | Required. The tier's capacity. The sum of every active tier's capacity is the event's capacity. |
| Min per order | The fewest of this tier a buyer may take in one order. Defaults to 1. |
| Max per order | The most of this tier per order. Blank means no limit, and it cannot be lower than the minimum. |
| On sale from / On sale until | Optional per-tier sales window. Leave empty to sell whenever the event itself is on sale. |
| Display order | Lower numbers show first on the public page. |
| Active | Inactive tiers are not sold and do not appear publicly. Only shown when editing an existing tier. |
The list shows each tier's price, its sold-of-total count, its sales window, and an Inactive chip where relevant. The section header totals sold against capacity across every type.
Per-Tier Sales Windows
A tier is on sale only when the current time falls inside both the event's sales window and the tier's own window. An empty bound on either side means "open" in that direction. That is what makes early-bird tiers work: give the early tier an "on sale until" date and the regular tier an "on sale from" date, and the handover happens on its own.
Min and max per order are enforced at checkout, per ticket type, per order. The event-wide ticket limit per person is separate and counts across all of a buyer's orders.
Free ($0) Tiers
A price of 0 is a legitimate tier and produces a free ticket. Because a $0 order never touches a card, free inventory is the easiest thing on the storefront to farm with a script, so Resytech adds two brakes:
- Any event with an active free tier shows a bot check at checkout before the order is created. This applies to the whole event, so buyers of paid tiers on a mixed event see it too. See The Storefront.
- Setting a ticket limit per person on the event caps how many tickets one email address can hold in total. It is worth setting on any free event.
The bot check is evaluated live. If you activate a free tier while buyers already have the page open, they will be challenged on their next attempt rather than slipping through.
Add-Ons
Add Add-on works the same way, with a shorter form:
| Field | Notes |
|---|---|
| Name | Required, up to 80 characters. |
| Description | Optional, shown to buyers. |
| Price | Required. |
| Quantity available | Optional. Leave it empty for unlimited, or set a number to cap it. |
| Active | Inactive add-ons are not sold. Only shown when editing an existing add-on. |
Add-ons are extras sold alongside tickets, not a product line of their own: they appear on the event's own page underneath the ticket tiers and are bought as part of a ticket order. They have no sales window and no per-order limits. A capped add-on shows its sold-of-total count in the list; an uncapped one just shows how many have sold.
The Capacity Floor
You can raise a ticket type's or add-on's capacity at any time, but you can never drop it below what is already committed. The floor is:
tickets already sold + tickets currently held by buyers in checkout
Try to save a lower number and the save is refused with "Capacity can't be lower than tickets already sold or held." Holds are short-lived, so if a hold is what is blocking you, waiting a few minutes and retrying usually clears it.
Uncapped add-ons have no floor to check. Giving a previously uncapped add-on a limit does apply the floor, so the number you set must still cover what has sold.
Capacity matters beyond inventory on the flat-listing-fee model, where the listing fee is priced by capacity. Raising capacity after paying can require topping the fee up before you can publish. See Fees and Payouts.
Deactivating vs Deleting
Deactivate by switching Active off. The tier or add-on stops being offered on the public page immediately, but every ticket already sold from it stays valid and every existing order is untouched. An inactive tier also stops counting toward the capacity used for listing-fee pricing at publish.
Delete is only available once something has sold nothing at all. The delete button asks for a second click to confirm, and then:
- A ticket type with sales is refused: "This ticket type has sales and can't be deleted, deactivate it instead."
- An add-on with sales is refused the same way.
That is deliberate. Existing orders and issued tickets point back at the tier they were bought from, so deleting it would strand the paperwork behind real sales. Deactivating is the correct move for a tier you are done selling.