# Sell parking, camping and merch beside your tickets | Ticket Fairy Guides 1. [Ticket Fairy](https://www.ticketfairy.com/) 2. [Guides](https://www.ticketfairy.com/guides) 3. Sell parking, camping and merch beside your tickets Setting up an event # Sell parking, camping and merch beside your tickets How to put everything that is not admission into the same checkout as the ticket, so a buyer picks a car park space, a t-shirt and a meal package in one order. For: Anyone selling something alongside admission Takes: 8 minutes - [Create your first add-on](#step-1) - [Say how many you have](#step-2) - [Write what the buyer gets](#step-3) - [Limit it to the tickets it belongs with](#step-4) - [Turn it on and save it](#step-5) - [Change one that is already selling](#step-6) - [Buy one yourself](#step-7) ## What you need before you start - You're an owner or an admin on this event. Add-ons sit on the **Tickets** screen, and the menu shows that screen to owners and admins. If you can't open it, ask one of them to do this part. If they open **Tickets** and there is no **Add-Ons** section on it at all, add-ons are switched off for your account rather than for you, so ask us to turn them on. - You know what you're selling beside the ticket, what each item costs, and how many of each you have. 1. ## Create your first add-on Open your event and go to **Tickets**. Scroll to **Add-Ons** and select **Create Add-On**. Put what the buyer gets in **Name** and what it costs in **Price**. The name is what a buyer reads in the checkout beside your tickets, so write it the way you would say it out loud: Return shuttle from the city centre, rather than Shuttle A. Where your event sells 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. ![The Create Add-On form in Ticket Fairy, with name, price, stock, a description editor and four toggles](https://www.ticketfairy.com/embeds/posters/marketing-add-ons--new-add-on.png) Tickets, Add-Ons, Create Add-On. 2. ## Say how many you have Put the number you can still supply in **Stock**. Turn on **Unlimited** only where there is no number, such as a digital programme. Stock is how many are left, not how many there ever were: once 50 of your 250 shuttle seats have sold, the field reads 200, and typing 60 there sells 60 more. When the last one goes the add-on stops selling and the ticket keeps going. On something with a hard physical limit, such as a car park, keep a few back rather than typing the exact number: two buyers checking out in the same moment can both take the last one. 3. ## Write what the buyer gets Use **Description** for the detail somebody needs before they add it: where the shuttle leaves from, what time the car park opens, which sizes a t-shirt comes in. Where 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. This is the answer to the question your inbox gets otherwise. 4. ## Limit it to the tickets it belongs with Turn on **Limit to Certain Ticket Types Only** where an add-on only makes sense with some of them, then pick those ticket types. A camping pitch belongs with a weekend ticket rather than a Saturday day ticket. Leave it off and everybody is offered it. **Limit to ticket quantity** is a separate one: it holds a buyer to one add-on per ticket in their order, so four friends on one order get four shuttle seats and not forty. Two event settings lift that cap where somebody has turned them on: a table ticket can carry one per guest, and a named add-on can be set to count as a ticket of its own. 5. ## Turn it on and save it Leave **Enabled** on and select **Create Add-On**. It joins the list on the same screen, and buyers see it in the checkout from then on. Turn **Enabled** off to take something off sale without deleting it. The add-on keeps its orders, so anybody who already bought one still has it. 6. ## Change one that is already selling Select an add-on in the list to open the same form with its values in it. Change the stock or the description and save. Stock is how many are left, so a number you type here is that many more to sell. **Price** greys out on every add-on on the event as soon as one of them no longer matches what your event's current fee settings would work out, so ask us to reprice it. Anyone who already bought keeps the price they paid either way, and on an add-on you are creating the price is always yours to set. ![The Edit Add-On form in Ticket Fairy, with a return shuttle priced at 12.50 and 250 in stock](https://www.ticketfairy.com/embeds/posters/marketing-add-ons--edit-add-on.png) Tickets, Add-Ons, an add-on. 7. ## Buy one yourself 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 should appear under the tickets, with the description you wrote. The price shows what the buyer pays, so where your event passes fees on it reads as the price you set plus those fees rather than your figure on its own. Before anything is on sale the checkout turns your test order away with the buyers, so this is a check for the day the first release opens rather than the night before. An add-on limited to certain ticket types only appears once one of those tickets is in the basket, so pick that ticket first. ## Or have it done for you Fai, the assistant inside your dashboard, can list your add-ons and create one, and so can your own AI assistant through our MCP server. Fai asks you before it writes. Your own assistant asks before anything destructive, and adding an add-on is not that, so read back what it is about to create. The command line does the same work in a script. Name the event you mean rather than asking for your next one, and give the price as a plain number: it lands in that event's own currency, and the card Fai asks you to approve prints the amount without naming a currency, so settle the event before you settle the price. An event that sells in more than one currency wants a price in each of them. Give one and the assistant comes back naming the currencies it still needs, so have those amounts ready. ### 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](https://www.ticketfairy.com/mcp-server) and ask it: The setup on that page starts your assistant in read-only mode, where it can look but change nothing. Take `--read-only` out of it to let the assistant do this for you. It stops to ask you first only for a destructive change, such as a refund, so read back what it is about to do. Pick the brand I run events under and find the event called \, 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](https://www.ticketfairy.com/cli), sign in with `ticketfairy auth login`, and choose the brand you are working on with `ticketfairy brand use `. `ticketfairy brand list` and `ticketfairy event list` print the ids the commands below take. Sign in with an owner or admin login on the event, the same as on the screens. 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. The file **addon create --from-file** reads is a JSON one you write, holding the same fields the form has, and the picture beside it is a file on your own machine. Write 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. An event that sells in more than one currency wants every price at once, so a change to one carries a **currencies** list beside it holding a price for each of the others. ### Everything already on sale beside the tickets ticketfairy addon list \ ### A new one, priced and limited ticketfairy addon create \ --name "Return shuttle" --price 12.50 --quantity 250 ### A whole one from a file you wrote, picture and all ticketfairy addon create \ --from-file \ --upload imageUrl=\ ### A change to one that already exists ticketfairy addon update \ --body '{"price":1500}' ### The same change, on an event selling in more than one currency ticketfairy addon update \ --body '{"price":1500,"currencies":\[{"currency":"EUR","faceValue":1400}\]}' ## Questions you might have Can somebody buy an add-on without a ticket?: Not on your event page. There an add-on rides along with a ticket in the same order, which is the point of it: one checkout and one confirmation. A quick buy link can point straight at an add-on and sell it with no ticket chosen, and we set those up rather than you, so ask us if you want one. How do I sell one thing in several sizes?: Some accounts have variants turned on, and there a t-shirt is one add-on with a size to pick in the checkout, each size carrying its own stock. Where you don't have them, 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?: It travels on the ticket, and it also carries a code of its own. A gate scan of the ticket takes the ticket and everything attached to it in one go. At a collection point, tell your staff to scan the add-on's own code instead: that checks in the add-on and leaves the ticket alone, so the gate still works when the buyer arrives. 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 keep selling 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 where the thing is tied to a name or a 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 travels with the ticket. Should camping be an add-on or a ticket type?: An add-on, in most cases. A ticket type is admission, and a buyer choosing between camping and a weekend ticket in the same list has a decision they should never have been given. Camping as an add-on sits under the ticket, priced on its own, with its own stock. ## Where to go from here - [What else you can do with Ticket Fairy](https://www.ticketfairy.com/event-ticketing/features) - [Set up ticketing for a multi-day festival](https://www.ticketfairy.com/guides/sell-a-multi-day-festival) - [Schedule when your event goes live](https://www.ticketfairy.com/guides/schedule-when-your-event-goes-live) - [Share your event setup as a template](https://www.ticketfairy.com/guides/share-your-event-as-a-template) - [Every Ticket Fairy guide](https://www.ticketfairy.com/guides) ## Do this on your own event Create your account, build your event, and follow these steps in your own dashboard. No sales call first. [Create a free account](https://manage.ticketfairy.com/welcome) [Book a demo](https://www.ticketfairy.com/event-ticketing/book-a-demo) --- This page is on Ticket Fairy, a ticketing, marketing and operations platform for live events and the venues that host them: festivals, club nights, concerts, conferences and tours, and night clubs, beach clubs and concert venues. It grows revenue with fan rewards that turn an audience into a sales channel, and runs the money side with payments and payouts, Vault business banking, and working capital advanced against ticket sales. [How Ticket Fairy ticketing works](https://www.ticketfairy.com/event-ticketing) ยท [Ticket Fairy for AI assistants](https://www.ticketfairy.com/llms.txt)