Multiple Ticket Types: How to Structure Tiers That Sell (and Scan)

Multiple ticket types are not a merchandising flourish. They are the rules that decide who can buy, how many seats remain, what the badge prints, and what a volunteer can resolve at the door without calling you. Events fail this in two directions: one undifferentiated price that trains buyers to wait, or a menu so long that checkout becomes homework.

Ticket types on orriven are independent records — capacity, price, and sales window per type — which is the only setup that makes the rest of this article operational.

This is the structure that survives a real Tuesday.

Start with jobs, not names

Before you create anything in the platform, write the job of each type in one line. A type without a job is a support ticket waiting to happen.

Ticket type	Public?	Job	Typical rule
Early-bird	Yes	Convert hesitation	Date or quantity cap that actually ends
Standard	Yes	Carry the budget	The price your math assumes
VIP / plus	Yes	Lift average order value	Includes a perk with its own capacity
Group	Yes	Convert the manager buying five	Minimum quantity or 4-for-3
Student	Optional	Discount with proof	Code-gated, not a self-reported checkbox
Speaker / staff	No	Access without a sale	Invite or redemption code
Comp / press	No	Look like a ticket at the door	Same pass, zero price

Three to four visible types is the ceiling for most events. Everything else belongs behind a code or an invitation. How the public prices get set is a separate problem — how to price event tickets — and ticket tiers that survive contact with attendees covers the edges each type creates at check-in.

Give every type its own capacity, price, and window

The software question is whether multiple ticket types have independent rules, or whether “early-bird ends Friday” means a human remembering to flip a switch at midnight. Manual transitions get missed. A missed transition is either lost revenue or a pricing dispute.

Each type needs:

• Capacity that cannot oversell a nested resource. If VIP includes a workshop seat, the workshop’s 40 seats are the real cap.
• Price that can change on a date or a remaining quantity, without a person in the loop.
• Sales window with a start and an end the page can display. Hidden types have no public window; they unlock with a redemption code.

When a type sells out, the next action should already be configured: open the next public type, or attach a waitlist to the one that filled. A sold-out wall with no next step wastes demand you already paid to attract.

Keep add-ons out of the ticket-type list

Workshops, dinners, and merch are inventory with their own counts. Folding them into extra ticket types multiplies the matrix — “standard + workshop”, “VIP + workshop”, “standard + dinner” — until nobody can tell which combination is left.

The clean model: ticket types establish baseline entry; add-ons sit on top at checkout. Communication then keys off both: people with the workshop add-on get workshop details; VIPs get VIP instructions. If your stack cannot segment that way, you will be exporting CSVs every week, and the export goes stale the moment someone upgrades.

Hide what the public should not choose

Speaker, staff, and complimentary passes belong on the same list the door uses. They do not belong on the public page. Issue them through the same flow with a code rather than a spreadsheet, or you will run two sources of truth and lose a name at 8 a.m.

The test for any type, public or hidden: can a volunteer at the desk resolve a dispute about it without calling you? If the answer depends on a Slack message from last Tuesday, the type is not finished.

When you evaluate platforms, treat independent rules per type as a purchase criterion — it sits in the same column as checkout and offline check-in in our event ticketing system comparison and the ticketing software feature list. The sales page will show you themes. The door will show you whether the types were real.

Frequently asked questions

How many ticket types should an event have?

Three to four public types is enough for most events: early-bird, standard, a plus or VIP, and a group option if you sell to companies. Hidden types for speakers, staff, and comps sit behind codes. Ten visible options is homework, not choice — buyers stall, and volunteers cannot explain the matrix at the desk.

What are examples of multiple ticket types?

Public types include early-bird, standard, VIP or plus, student, and group. Private types include speaker, staff, press, and complimentary. Treat workshops and dinners as add-ons with their own inventory rather than cloning a ticket type for every combination.

Can different ticket types have different prices and capacities?

Yes — and they should. Each type needs its own capacity, price, and sales window. If a VIP pass includes a 40-seat workshop, selling 60 VIP tickets is an oversell the software should have blocked, not a surprise for session operations.

Should free and paid ticket types coexist on one event?

Yes. Free and paid types can share a page as long as the door still sees one pass. Issue comps through the same flow with a code rather than a side list. Out-of-band complimentary tickets are the most common reason a name is missing from the door list.