Skip to content

Setting up an event

Set up ticket types

Create clear ticket choices with the right price, allocation, purchase limits, availability and entry rules before your event goes on sale.

This is the ticket setup within creating an event. You can return to the complete event guide when the tickets are ready. Create an event

For
Preparing the tickets buyers will choose for an event
Takes
12 minutes

What you need before you start

  • You're an owner or admin for the event.
  • You have created the event or saved it as a draft.
  • You know what each ticket admits, its price, how many you can sell and when it should be available.
  • You have decided whether buyers pay the booking fee or you absorb it. Choose this before creating the first ticket type because you cannot switch between Added and Absorbed once ticket types exist.

  1. Open the event's ticket inventory

    Open the event, select Tickets, then stay on Inventory. The Ticket Types section lists the tickets buyers can choose and shows whether each one is enabled, hidden or on sale.

    A cancelled event cannot accept new ticket types. Reinstate it before changing the inventory.

    Ticket Fairy Ticket Types inventory with General Admission and the Create action
    Event, Tickets, Inventory, Ticket Types.

  2. Choose how booking fees appear

    In Booking Fees, choose Added when the buyer pays the fee and sees an inclusive price on the event page, or Absorbed when the fee comes out of the ticket price. Added Later shows the fee at checkout and is unavailable for events in Australia, the United Kingdom and the United States.

    Choose between Added and Absorbed before creating the first ticket type. Ticket Fairy prevents that switch later because the existing ticket prices were prepared under the current choice.

  3. Decide whether buyers need another ticket or another release

    Create a separate ticket type when the buyer receives different admission, such as General Admission, VIP, Friday, Full Weekend or an accessible companion ticket. For Early Bird, First Release and Final Release prices that provide the same admission, create one ticket type for each release and group them under one ticket category.

    A ticket category keeps releases for the same admission together. A sale window or a rule that reveals the next release controls when buyers can choose each one.

  4. Create the ticket type and enter its essentials

    Select Create in Ticket Types. Enter a Name that describes what the buyer receives, its Price, and the Max number of sales. Leave Must be bought in multiples of at 1 unless buyers must purchase a fixed bundle, such as two seats together.

    Price can be 0 for a free ticket. Max number of sales is the allocation for this ticket type; 0 leaves it sold out. Do not use the venue capacity blindly when several ticket types share that capacity.

    Ticket Fairy ticket type form with General Admission name, price, allocation and purchase multiple
    Event, Tickets, Create Ticket Type.

  5. Set purchase limits and the buyer-facing description

    Open Advanced settings. Add a badge only when it accurately describes availability. Set a custom maximum per order when this ticket needs a different limit from the event, and a waiting-list maximum when one person should be able to request fewer tickets. Use Description for benefits, entry conditions and anything buyers should understand before choosing this ticket.

    The per-account limit is also available for preventing one account from buying the allocation through several orders. Use Additional text on ticket PDF for information buyers need after purchase, and hide the date on the PDF only when the ticket covers several dates or the date would be misleading.

  6. Choose the controls that match this admission

    Use Scanned multiple times per event only when one ticket can admit the holder more than once, then choose the hourly or daily limit. Keep Enabled on for a ticket you want to offer. Use Hidden for a private or scheduled reveal, Hold tickets to reserve part of its allocation, and Different door times when this ticket has its own entry window.

    The same section can withhold the ticket from resale, send buyers to another ticketing page, use another venue, require NFT ownership or enable sliding-scale pricing. Turn on only the controls that describe what this ticket actually offers. Each enabled control adds fields that must be completed before saving.

    Ticket Fairy ticket options with separate door and last-entry times enabled
    Event, Tickets, ticket type, Advanced settings.

  7. Add tags and a ticket category when they help your team or buyers

    Add tags your team uses to find or organise attendees. Choose a Ticket Category when this ticket belongs with other releases for the same admission, or leave No category selected when it should remain in the main ticket list.

    Tags are internal labels. The ticket name, description and category are the information buyers use to choose.

    Ticket Fairy Ticket Category field set to General Admission
    Event, Tickets, ticket type, Ticket Category.

  8. Set when the ticket is on sale

    Under Ticket availability, keep the ticket always available, make it available after the previous ticket type sells out, or enter its sales start and end. Use exact dates for a scheduled release. Use the previous-ticket option only when the ticket immediately above it is the release that should sell out first.

    Sale dates control when buyers can purchase the ticket. Hidden and enabled are separate controls, so check all three when a ticket does not appear when expected.

    Ticket Fairy ticket availability section with a scheduled sales start and end
    Event, Tickets, ticket type, Ticket availability.

  9. Create the ticket and check the buyer experience

    Select Create Ticket Type. Open the public event page and confirm the ticket name, description, price, fee treatment, category and availability. Add a test ticket to the basket when the event is public so you can check its purchase limits and any entry information.

    Return to the event builder if this ticket completes a new draft. Otherwise continue creating the other ticket types and releases the event needs.

Or have it done for you

Fai can list your existing ticket types, ask for every setting that matters and show the proposed ticket before creating it. MCP and the CLI can also create a ticket type from the details you provide. Every surface asks for approval before making the change.

In your dashboard, with Fai

Set up a ticket type for <EVENT NAME>. Before creating it, ask whether booking fees should be added to the price, absorbed into it or, where available, added at checkout. Ask me what admission it includes, its name, price, allocation, purchase limits, sale window, visibility, entry rules and resale policy. Show me the booking-fee choice and every ticket setting before making either change

From your own assistant, over MCP

Connect your assistant to our MCP server and ask it:

The copied MCP configuration includes --read-only. Remove --read-only only when you want your assistant to make changes. Routine changes run when requested; destructive actions ask you in a compatible client. If your client cannot ask, make the change in your dashboard.

Find the event <EVENT NAME>, list its ticket types, ask me for the name, price, allocation and any other settings needed for a new ticket type, then show me the complete ticket before creating it

From your terminal

Install the CLI from our CLI page, sign in with ticketfairy auth login, and choose the brand you are working on with ticketfairy brand use <BRAND_ID>. ticketfairy brand list and ticketfairy event list show the IDs the other commands use.

Create a standard ticket type with command flags, or use a JSON or YAML file when you need the complete set of advanced fields. Prices use the event currency.

A standard General Admission ticket type

ticketfairy ticket create <EVENT_ID> --name "General Admission" --price 35 --max-inventory 500 --max-per-order 6

A ticket type using every field in a reviewed file

ticketfairy ticket create <EVENT_ID> --from-file ticket-type.yaml

Edit a ticket type

  1. Open the ticket

    In Tickets, select the ticket type you want to change or choose Edit from its row.

  2. Save the change

    Change the required fields, check any sale or visibility controls affected by the edit, then select Update Ticket Type.

    Changing the allocation does not erase tickets already sold. Never reduce it below commitments the event must honour.

Fai, MCP and the CLI can show the current ticket and update the fields you name after approval.

In your dashboard, with Fai

Show me <TICKET TYPE> on <EVENT NAME>, including its price, allocation, limits, availability and entry rules. Ask what I want to change, then show the complete update before saving it

From your own assistant, over MCP

The copied MCP configuration includes --read-only. Remove --read-only only when you want your assistant to make changes. Routine changes run when requested; destructive actions ask you in a compatible client. If your client cannot ask, make the change in your dashboard.

List the tickets for <EVENT NAME>, find <TICKET TYPE>, show its current settings and ask before applying this update: <CHANGE>

From your terminal

List tickets to confirm the ID, then update only the fields you intend to change.

Find every ticket type and its ID

ticketfairy ticket list <EVENT_ID> --all

Change a ticket price and allocation

ticketfairy ticket update <EVENT_ID> <TICKET_ID> --price 42 --max-inventory 650

Duplicate a ticket type

  1. Choose the ticket to copy

    Open the ticket row menu and select Duplicate Ticket Type.

  2. Finish the copy

    Open the new copy directly below the original, change its name, price, allocation, sale window and any settings that should differ, then save it.

    The copy starts with the original capacity and no sales. Custom data-capture fields are not copied.

Fai can duplicate a standard ticket type, then rename or reprice the copy after you approve each change. MCP and the CLI do not duplicate ticket types; create a new ticket from reviewed values instead.

In your dashboard, with Fai

Duplicate <TICKET TYPE> on <EVENT NAME>. Show me the source ticket and what the copy will keep, then ask before creating it. Afterward ask for the new name, price, allocation and sale window

Change the order buyers see

  1. Move the ticket rows

    Drag ticket types into the order buyers should see. Keep sequential releases together and place the current release before any release that waits for it to sell out.

  2. Save the order

    Select Save Order after checking the complete list.

    Reordering changes presentation only. It does not change prices, allocations or whether a ticket is on sale, except that a release configured to follow the previous ticket depends on which row is directly above it.

Fai can list the current order and save the complete new order after approval. MCP and the CLI do not reorder ticket types.

In your dashboard, with Fai

Show me the ticket order for <EVENT NAME>, then arrange it as <ORDER>. Show the complete final order and ask before saving it

Take a ticket type off sale without deleting it

  1. Open the ticket settings

    Edit the ticket type and turn Enabled off.

  2. Save and check the event page

    Select Update Ticket Type, then confirm the ticket is no longer available on the event page. Turn Enabled on again when you want to restore it.

    Disabling preserves the ticket type and its history. It is usually safer than deleting a ticket you may need again.

Fai, MCP and the CLI can change the ticket type between active and inactive after approval.

In your dashboard, with Fai

Show me <TICKET TYPE> on <EVENT NAME> and ask before turning it off. Keep all its other settings unchanged

From your own assistant, over MCP

The copied MCP configuration includes --read-only. Remove --read-only only when you want your assistant to make changes. Routine changes run when requested; destructive actions ask you in a compatible client. If your client cannot ask, make the change in your dashboard.

Find <TICKET TYPE> on <EVENT NAME>, show its current status and ask before setting active to false

From your terminal

Confirm the ticket ID, then deactivate or reactivate it.

Take the ticket off sale

ticketfairy ticket update <EVENT_ID> <TICKET_ID> --deactivate

Restore the ticket

ticketfairy ticket update <EVENT_ID> <TICKET_ID> --activate

Mark a ticket type as sold out

  1. Choose Mark as Sold Out

    Open the ticket row menu and choose Mark as Sold Out.

  2. Decide what happens to live baskets

    Choose whether buyers who already hold this ticket in a live basket may finish checkout, then confirm.

    There is no default for this decision. Allowing checkout honours the temporary basket reservation; clearing baskets makes the sold-out state immediate.

    Ticket Fairy confirmation for a sold-out ticket held in live baskets
    Event, Tickets, Inventory, Mark as Sold Out.

Fai can mark the ticket sold out after showing it and asking whether buyers with live baskets may finish. MCP and the CLI do not expose this action.

In your dashboard, with Fai

Mark <TICKET TYPE> on <EVENT NAME> as sold out. Show me the ticket, then ask whether buyers who already have it in a live basket may finish checkout before making the change

Delete an unused ticket type

  1. Check that the ticket is unused

    Confirm that the ticket type has no orders and is not reserved in a live basket. Disable it instead when you need to preserve it for later.

  2. Delete the ticket type

    Open its row menu, select Delete Ticket Type, check the name and confirm.

    Ticket Fairy refuses deletion when the ticket has orders or is in a buyer's basket. Contact support if you need an accidentally deleted unused ticket restored.

Fai, MCP and the CLI can delete an unused ticket type after showing its identity and asking for approval. Ticket Fairy refuses the deletion when it has orders or live basket reservations.

In your dashboard, with Fai

Show me <TICKET TYPE> on <EVENT NAME>, including its current status and sales, then ask before deleting it

From your own assistant, over MCP

The copied MCP configuration includes --read-only. Remove --read-only only when you want your assistant to make changes. Routine changes run when requested; destructive actions ask you in a compatible client. If your client cannot ask, make the change in your dashboard.

Find <TICKET TYPE> on <EVENT NAME>, show its ID and current status, then ask before deleting it

From your terminal

List tickets to verify the ID. The delete command asks for confirmation unless you deliberately pass --force.

Delete the unused ticket type after confirmation

ticketfairy ticket delete <EVENT_ID> <TICKET_ID>

Questions you might have

What is the difference between a ticket type and a ticket release?
A ticket type describes what the buyer receives, such as General Admission or VIP. A release changes when or at what price the same admission is offered, such as Early Bird and Final Release. In Ticket Fairy, each release is created as a ticket type and the releases can share one ticket category.
What does Max number of sales mean?
It is the allocation for this ticket type. Set it to the largest number you can honour after accounting for other ticket types, holds, venue areas and any stock sold elsewhere. A value of 0 leaves the ticket sold out.
Can I create a free ticket?
Yes. Enter 0 as the price and set an allocation. Purchase limits, approval, hidden access and entry rules can still apply to a free ticket.
Why can't I change who pays the booking fee?
Ticket Fairy prevents switching between Added and Absorbed after ticket types exist because their prices were prepared under the current fee choice. Choose the fee treatment before creating tickets. Added and Added Later can still be changed where Added Later is available.
Why is my ticket not appearing on the event page?
Check that the ticket is enabled, its allocation is above 0, its sales window is open and it is not hidden. A ticket waiting for the previous release also stays unavailable until the ticket directly above it sells out.
Should I hide or disable a ticket?
Hide it when a code, country, date or previous release should reveal it. Disable it when nobody should be able to buy it until you turn it on again. Both settings preserve the ticket type.
Can I lower an allocation after tickets have sold?
You can edit the allocation, but existing tickets remain valid. Keep it high enough to honour every ticket already sold and every place your event has committed elsewhere.
Do tags appear to buyers?
No. Tags help your team organise and find attendees. Use the ticket name, description and category for information buyers need.

Where to go from here

Do this on your own event

Create your account, build your event and follow the steps in your own dashboard. You do not need to book a sales call.

Create a free account Book a demo

Book a demo

See how Ticket Fairy handles your tickets, on-sale and event entry. Pick a time that suits you.

45-Minute Video Call
Pick a Time That Works for You