Task · Ticket types
Sell several tickets together at one price
Sell one ticket that issues the tickets inside it, at a price worked out from what they cost.
5 steps · About 5 minutes · Needs: Another ticket type to put in the bundle
-
Create a ticket type, or open one you already have and select Edit
A family ticket, a weekend pass, whatever you call it.
Your eventSet upTicket types -
Select Price it another way under the price, then Bundle price
The price box is replaced by the tickets this one is made of.
go.tito.io/acme/summer-fetes-summer-fete/admin/ticket-types/1/edit -
Pick a ticket and set Quantity
Comes to is what that line adds. + Add a line gives you another one, and each line's ✕ takes it out again.
-
Put an item in too, if one comes with the tickets
Every line lists your items under the ticket types, so a t-shirt goes in the same way a ticket does and its price joins the total the same way. A bundle needs at least one ticket in it.
-
Take an amount off on Bundle discount, then save
What buyers pay is the total, and it's what the ticket sells for. Change what one of the tickets inside it costs later, and this price follows on its own.
To sell two tickets at full price with a t-shirt thrown in, put both tickets and the shirt in the bundle and take the shirt's price off here. The buyer pays for the tickets and gets the shirt.
Single price goes back to one price you type.The lines are dropped and the ticket keeps that price.
Lowering a price is refused when it would make a bundle free.If a new price would leave a bundle's discount bigger than the tickets in it come to, the save stops and names the bundle. Reduce that bundle's discount first.
What a bundle sale issues
Selling a bundle issues the tickets inside it. One family ticket of 2 × Adult and 2 × Child issues four tickets, two Adult and two Child. Each one has its own name, its own questions and its own check-in. The bundle itself isn't issued as a separate ticket.
A session connected to a bundle gives each ticket a place in the option chosen for that ticket. A family bundle of two Adult and two Child tickets needs four places, regardless of the connection's Places per ticket setting.
Those tickets are listed under the bundle wherever the order is itemised. The summary beside the payment form, the receipt and the invoice all show them, each one reading Included, because the price is on the bundle's own line. The total on the event page counts them for the number of bundles chosen, so two family tickets read 4 × Adult, 4 × Child.
A bundle sells while every ticket type in it has places left, and comes off sale on its own once one runs out. A ticket type that's off sale can go in a bundle, which is how you sell one only as part of a bundle.
Ticket types in a bundle keep their own settings, such as per-order limits or attached questions and offerings.
A question or an offering connected to a ticket type is asked of that ticket wherever it's sold, on its own or inside a bundle.
An extra included with a ticket type comes with that ticket wherever it's sold, so a bundle issuing two Adults brings two of whatever an Adult includes. The bundle's row on the event page lists them, so buyers see what's coming before they choose. Include the same thing with the bundle as well and it's brought once, at the count set on the bundle.
Every other row counts tickets. Three families reads as three bundles there and as twelve tickets across the Adult and Child rows.
Refund the bundle from the order and all of its tickets stop working together, with their places back on sale.
Only new sales issue the tickets inside them.
Good to know
Each ticket in a bundle says so on its own page too, under Bundles that include this ticket, where you can change how many of it the bundle includes.
Connect an offering to the bundle rather than to the tickets inside it, and it's asked of every ticket the bundle issues. Connect it to both and it's asked once.
The bundle's own page lists what the tickets inside it come with, under What comes with it. Each of those lines says which ticket it belongs to, and you change it on that ticket's own page.
Buyers are asked once for each ticket that owes a choice, and each picker is headed with the ticket it's for. The ticket is named even when only one of them is asked. Each ticket holds what was picked for it, and a place is held for each of them.
Questions work the same way. Buyers answer per ticket the bundle issues, and a question connected to both the bundle and one of its tickets is asked once.
Bundles and price tiers don't work together. A ticket with tiers can't go into a bundle, a ticket already in one can't be given tiers, and a bundle can't go inside another bundle.
It keeps its last worked-out amount. The only change it accepts is taking that missing line out.
Events imported from Tito Pro
A bundle set up in Tito Pro is imported as a bundle of the same tickets, at the price it had on Pro. The difference between that price and the tickets inside it is the Bundle discount. A Pro bundle that cost more than the tickets inside it is imported as a ticket with one price, and a sale issues that one ticket.
Use the API
The API can read, replace, or remove a ticket bundle. Include the tickets, goods, quantities, and discount when replacing it. Removing the bundle keeps its last calculated price as a flat ticket price. Bundled goods count toward prices in other currencies. A missing price keeps the bundle off sale in that currency.