Setting up an event
Sell parking, camping and merchandise with your tickets
Add parking, camping, meals, merchandise and upgrades to the ticket checkout, with stock, options and limits for each.
- For
- Selling extras with event admission
- Takes
- 8 minutes
Before you start
- You're an owner or an admin on this event. Open Tickets from your event menu. If it isn't there, ask another owner or admin to do this part. If Tickets opens but there is no Add-Ons section, add-ons are switched off for your account, so ask us to turn them on.
- You know what you're selling alongside the ticket, what each item costs, and how many of each you have.
-
Open Add-Ons and select Create Add-On
Open your event and go to Tickets, then scroll to Add-Ons and select Create Add-On.
Tickets, Add-Ons, Create Add-On. -
Enter the name and price
Enter what the buyer gets in Name and what it costs in Price.
Note: The name is what a buyer sees in the checkout beside your tickets, so enter one they will understand: Return shuttle from the city centre, rather than Shuttle A. Where your event takes payments in more than one currency, give the add-on a price in each of them: it will not save until every one has a figure.
-
Enter the stock
Enter the number you can still supply in Stock, or turn on Unlimited for something with no limit, such as a digital programme.
Note: Stock is how many are left, not how many there ever were: once 50 of your 250 shuttle seats have sold, the field shows 200, and entering 60 makes 60 more available. When the last one goes the add-on is no longer available and the tickets remain on sale.
-
Enter the description
Use Description for the details a buyer needs before adding it: where the shuttle leaves from, what time the car park opens, which sizes a t-shirt comes in.
Note: If you are posting something out, turn on the add-on's shipping-details option as well, or checkout never asks the buyer for an address.
-
Limit it to certain ticket types
Optional: Turn on Limit to Certain Ticket Types Only, then pick the ticket types this add-on goes with, such as a weekend ticket for a camping pitch.
Note: Leave it off to offer the add-on with every ticket type. Limit to ticket quantity is a separate setting that allows one add-on per ticket in the order, so four friends on one order get four shuttle seats and not forty.
Tickets, Add-Ons, ticket restrictions. -
Leave Enabled on and select Create Add-On
Leave Enabled on and select Create Add-On. It appears in the list and becomes available during checkout.
Note: The add-on remains on existing orders if you take it off sale later, so previous buyers keep what they bought.
-
Check your event page
Once a release is on sale, open your event page in a private browser window and put a ticket and an add-on in the basket. Your add-ons appear under the tickets, with the description you entered.
Note: The price shows what the buyer pays, so where your event passes fees on it shows your price plus those fees. An add-on limited to certain ticket types appears once one of those tickets is in the basket, so pick that ticket first.
Or have it done for you
Fai and MCP can list or create add-ons. Fai asks before creating one. MCP creates it after you provide the event, price in that event's currency, stock and ticket limit. For a multi-currency event, provide a price in every currency. You can also use the command line.
In your dashboard, with Fai
Add a return shuttle at 12.50 to this event, limited to 250, one per ticket
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.
Pick the brand I run events under and find the event called <EVENT NAME>, then list the add-ons on it and add a car park space at 15 with 400 available, one per ticket
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.
Sign in with the same owner or admin account you use in the dashboard. Point ticketfairy brand use at the brand first. The event id is in the address bar when you have the event open, and addon list prints the id of every add-on on it, which is where the id for addon update comes from. For addon create --from-file, create a JSON file containing the form fields. Add a picture from your machine with --upload imageUrl=<PICTURE_FILE>. Include a price in that file, or in a --body, in the smallest unit of your event's currency, so 1500 is 15.00. The --price flag takes the amount the way you say it. For a multi-currency event, include a price for every currency in the currencies list.
Everything already on sale beside the tickets
ticketfairy addon list <EVENT_ID>
A new one, priced and limited
ticketfairy addon create <EVENT_ID> --name "Return shuttle" --price 12.50 --quantity 250
A whole add-on from a file you created, picture and all
ticketfairy addon create <EVENT_ID> --from-file <ADDON_FILE> --upload imageUrl=<PICTURE_FILE>
A change to one that already exists
ticketfairy addon update <ADD_ON_ID> --body '{"price":1500}'
The same change, on an event taking payments in more than one currency
ticketfairy addon update <ADD_ON_ID> --body '{"price":1500,"currencies":[{"currency":"EUR","faceValue":1400}]}'
Take an add-on off sale
Select the add-on, turn Enabled off and save it. The add-on disappears from checkout without being deleted.
Note: Existing orders keep the add-on the buyer already bought.
Fai can turn the add-on off after showing you its current price, stock and restrictions. MCP creates add-ons but does not update them. Use the dashboard or Fai for the Enabled setting; the CLI update command accepts event data fields but has no dedicated on-sale flag.
In your dashboard, with Fai
Find the add-on <ADD-ON NAME> on <EVENT NAME>. Show me its current price, stock and ticket restrictions, then ask before turning it off
Change an add-on that is on sale
Select the add-on in the list, change its stock, price, description or ticket restrictions, then save it.
Note: Open your event page after saving to check the updated description and availability. The stock field is the quantity still available, and existing orders keep the add-on the buyer already bought.
Fai can show the existing add-on and update the fields you choose. MCP creates add-ons but does not update them. The CLI can apply exact field changes by ID.
In your dashboard, with Fai
Find the add-on <ADD-ON NAME> on <EVENT NAME>, show me its price, remaining stock, description and ticket restrictions, then ask what I want to change
From your terminal
Use the add-on ID and pass only the fields you want to change.
Change an add-on price and stock
ticketfairy addon update <ADDON_ID> --body '{"price": <PRICE>, "stock": <REMAINING_STOCK>}'
Questions you might have
- When can a buyer take more than one add-on per ticket?
- Two event settings lift the one-per-ticket limit when they are on: a table ticket allows one add-on per guest, and a named add-on can count as a ticket of its own. Ask support to turn either on for the event.
- What number should I enter for something with a hard limit, such as a car park?
- Enter the number you can fulfil, and update it whenever more capacity becomes available. Stock is how many are left, so once 50 of your 250 shuttle seats have sold the field shows 200, and entering 60 makes 60 more available.
- Can a buyer purchase an add-on without a ticket?
- Not on your event page. Buyers purchase an add-on with a ticket in the same order, with one checkout and one confirmation. A quick buy link can point straight at an add-on and sell it with no ticket chosen; Ticket Fairy support sets those up, so ask us if you want one.
- How do I sell one thing in several sizes?
- If variants are available for your account, create one T-shirt add-on and let buyers choose a size. Give each size its own stock. Without variants, make one add-on per size and give each its own stock. Ask us to turn variants on if you sell a lot of merch.
- Is an add-on scanned at the gate?
- Scanning the ticket checks in both the ticket and its attached add-ons. At a collection point, scan the add-on's own code so the ticket remains ready for entry.
- What happens when an add-on sells out?
- Your buyers still see it in the checkout, marked sold out, and they cannot add it. Your tickets remain on sale without it. Raise the Stock number and it goes straight back on sale, so a second run of t-shirts needs no new add-on.
- Can I stop add-ons being resold?
- Yes, on an add-on you set up on its own. Withhold from Resale keeps it with the person who bought it when their ticket is resold, which is what you want when the add-on belongs to a named attendee or registered vehicle, such as a campervan permit. An add-on you built as a set of variants, such as t-shirt sizes, has no such setting, so it is resold with the ticket.
- Should camping be an add-on or a ticket type?
- Use an add-on when camping is optional alongside admission. Use a ticket type when the camping product grants admission or needs its own entry entitlement.
Related guides
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.