How to Create Tickets for an Event (Step by Step)

To create tickets for an event you make four decisions, then prove they work: which ticket types you sell, what each costs, how many exist, and what the buyer gets as proof they paid — then you test one real purchase. Build it on a ticketing platform or your own site. Here's exactly how.

None of this is technical. A "ticket" in 2026 is not a printed stub; it's a priced, countable right to enter your event, plus a confirmation the buyer can show at the door. Creating tickets means defining those rights, setting their prices and limits, and choosing how buyers receive and redeem them. This guide walks the mechanics piece by piece — types, prices, capacity, promo codes, what the ticket contains, and how it gets delivered — so by the end you can build the whole thing without guessing. If you're still deciding whether to sell at all, how to sell tickets online covers the money side first; this one is the build.

What does it actually mean to create a ticket?

Creating a ticket means defining four things: a name buyers understand, a price, a quantity available, and the proof of purchase they get afterward. Everything else — colors, fine print, seating — is optional detail layered on top. Get those four right and you have a working ticket. Get them wrong and you either leave money on the table or oversell a room.

Think of a ticket as a small contract. When someone buys, they hand you money and you hand back two things: a right to enter (counted against your capacity so you never sell the same seat twice) and evidence they hold that right (an emailed confirmation, usually with a scannable code). The buying platform tracks the count for you and generates the proof automatically. Your job is to set the terms — what the ticket is called, what it costs, how many you'll sell — and to make sure the proof actually reaches the buyer and works at the door. That's the whole craft, and the sections below take each part in turn.

What ticket types should you create?

Start with one general-admission ticket, then add types only when each one does a distinct job: early-bird to reward and measure early demand, tiers to sell the same event at different levels, VIP to charge more for genuine extras, and group or comp tickets to handle tables and guests. Most first events need one or two types. Adding six confuses buyers and dilutes every tier.

The rule is that every ticket type should answer a real buyer's real question. General admission answers "how do I get in?" Early-bird answers "why should I commit now instead of waiting?" A VIP tier answers "can I get more than the standard experience?" If a type doesn't map to a question a buyer is actually asking, cut it — a shorter menu sells better than a long one, because a buyer who can't decide often buys nothing. Keep the tiers side by side and easy to compare, and make the price gaps meaningful so the choice is obvious. The table below shows when each type earns its place and how to price it; for the numbers behind those prices, pricing your creator event works through the full method.

Ticket type	When to use it	How to price it
General admission	Every event. The single, simple "get in the door" ticket most buyers will choose	Your baseline price — set it first; every other tier is priced relative to this
Early-bird	You want proof of demand early and momentum on the launch. Cap it by quantity or a cutoff date	Below GA (an illustrative 15–25% off), so committing early is clearly rewarded
Tiered (silver / gold, etc.)	The same event sells at different levels — closer seats, more sessions, a longer day	Each tier priced by what it adds over the one below; keep the jumps meaningful
VIP	You can add real extra value: a meet-and-greet, a small-group session, early entry, swag	Priced on the value of the extras, not a round-up — buyers pay for the add-on, not the label
Group / table	Buyers arrive together — a table of six, a crew, a company outing	Per head slightly below single price, or a flat table price that beats buying seats one by one
Comp / guest	Press, partners, vendors, or your own team who enter free but still take a seat	Free, but still counted against capacity so a full room stays honestly full

You don't need all six. A creator running a first workshop might sell exactly one GA ticket and add a small early-bird batch to test the launch. A multi-day experience might use tiers because the levels genuinely differ. Match the menu to the event, not to a template.

How do you create tickets step by step?

The sequence is the same wherever the tickets live: choose your tool, set up the event, build each ticket type, price it, cap it, add any promo codes, decide what the ticket contains and how it's delivered, then test one real purchase before you share the link. Below is that path in order, with what to actually do at each step.

1. Choose where the tickets live. You have two homes for a ticket: a ticketing platform, or your own website. A platform is faster to stand up and handles the count, the confirmation, and check-in for you; your own site keeps buyers on your brand and, on the right setup, keeps the buyer relationship too. Compare the platforms in the best event ticketing platforms, and if you'd rather host the checkout yourself, how to sell tickets on your website covers the methods. Decide this first, because it shapes every step after it.

2. Set up the event shell. Create the event itself: name, date and time, location (or the note that address is sent after purchase), and a short description. This is the container your tickets attach to. If you're selling from your own page rather than a platform listing, the container is your sales page — a landing page that sells your experience is what buyers read before they reach the ticket.

3. Build each ticket type. Now create the types you chose above. For each one, write a name a stranger understands in a second ("General Admission," "Early-Bird — first 20," "VIP + meet-and-greet"), and a one-line description of what it includes. Resist inventing types on the fly; every type you add is one more choice the buyer has to make.

4. Set the price for each type. Enter the price per ticket. Price the baseline GA first, then set the others relative to it — early-bird below, VIP above, tiers stepping up by what each adds. If cost is a barrier for a higher-priced experience, you can take a deposit now and the balance later instead of the full amount upfront; how to collect deposits for an event shows the Stripe setup. Whatever you charge, know what lands in your account after fees before you commit to a number — event ticketing fees breaks down what each platform takes.

5. Set capacity, per type and overall. Give each type a quantity — how many early-bird seats, how many VIP — and set the event's total capacity so the tool stops selling when the room is full. This is what prevents overselling: the platform decrements the count on each sale and closes the ticket at zero. Real caps also create honest urgency, which sells; event capacity and honest scarcity covers how to use limits without faking them.

6. Add promo and discount codes. If you want to reward a segment — your email list, a partner's audience, the people who came last time — create a code that applies a set amount or percentage off, and cap how many times it can be used. A code does two jobs: it gives a specific group a reason to buy now, and it tags where sales came from so you can see which channel actually worked. Keep the discounts modest and time-boxed; a code that never expires just trains buyers to wait.

7. Decide what the ticket contains and how it's delivered. Set the confirmation up so the buyer's ticket carries everything they need on the day — covered in the two sections below. On most platforms this is automatic; on a self-hosted setup you configure the confirmation email yourself.

8. Test one real purchase, then launch. Buy one ticket yourself, on your phone, and watch the whole chain: does checkout load fast, does the confirmation arrive, does the code scan, does the seat count tick down? Then refund your test and open sales — to your warmest people first, before you go public. The channel-by-channel plan is in how to promote an event.

Step 8 is the one hosts skip and regret. Before you share a single link, run one genuine end-to-end purchase on a phone — use the platform's test mode, or buy a real ticket and refund it — and confirm three things fire: the confirmation email lands (check spam), the ticket's QR code or barcode actually scans with whatever you'll use at the door, and your attendee count goes down by one. A ticket that never arrives or won't scan turns your entrance into a line of frustrated buyers.

What should an event ticket actually contain?

A good ticket carries the event name, date, time, and location; the buyer's name; the ticket type they bought; an order or confirmation number; and a scannable code for check-in. Add your logo and a line of what-to-know, and skip everything else. The test is simple: could someone standing at your door, holding this, get in without calling you?

Walk the fields. The event basics — name, date, start time, and where to go — mean the buyer never has to dig through email to find them; if the address is private until purchase, this is where it appears. The buyer's name ties the ticket to a person so it isn't freely transferable if you don't want it to be. The ticket type tells your door team what this person bought, which matters the moment you have a VIP line and a general line. The order number is the fallback: if a code won't scan, someone can look the order up and wave the guest through. The scannable code — the next section — is the fast path for check-in. Beyond those, a logo makes it feel like yours and one line of practical notes ("doors 7pm, bring ID") heads off day-of questions. Everything past that is clutter on a screen the buyer glances at for two seconds.

A person holding up a phone showing an event ticket with a QR code at an entrance — A modern ticket is a screen with a scannable code — the buyer holds up their phone, you scan, they're in. Test that the code actually scans before the day, not at the door.

How do tickets get delivered to buyers?

Delivery is almost always email plus a scannable code. The buyer completes checkout, an automated confirmation lands in their inbox within seconds, and inside it is a QR code or barcode they show at the door — on their phone or printed. No physical ticket changes hands. Most platforms do this for you; on a self-hosted setup you wire the confirmation yourself.

The email is the delivery vehicle and the record. It should arrive immediately, come from a name the buyer recognizes as you (not a generic no-reply they'll ignore), and contain the ticket details plus the code. The QR code is what makes check-in fast: instead of matching names against a list by hand, someone at the door scans the code with a phone or scanner, the system confirms it's a valid, unused ticket, and the guest walks in — a second per person instead of a search. It also prevents the same ticket being used twice, because a scanned code marks itself redeemed. If you want the full picture of how those codes are generated, scanned, and secured, QR code tickets covers it end to end. Always keep a searchable attendee list as the backup for the one buyer whose phone is dead or whose email vanished — the order number from the last section is what you look them up by.

Is creating tickets on your own website different from using a platform?

The four decisions are identical — types, prices, capacity, delivery — but the setup differs. A platform gives you a ready-made ticketing engine and a listing; your own site means you place a checkout on a page you control and connect your own payment account, which keeps buyers on your brand and, on the right tool, keeps them as your contacts. The mechanics of building a ticket don't change; where the buyer lands and who owns them afterward does.

On a platform, you fill in the event and ticket types inside its dashboard, it hosts the listing, and it handles confirmation and check-in — fast to launch, and some options cost nothing up front, which the best free event ticketing systems rounds up. The trade is that buyers arrive as the platform's customers and a per-ticket fee often stacks on top of card processing. On your own site, you embed a checkout or connect a payment page so the sale runs through your account — the one unavoidable cost there is card processing, which in the US is Stripe's standard 2.9% plus 30¢ (on an illustrative $55 ticket, about $1.90). Other platforms' fees vary and often add a booking fee above processing, so check each tool's current rates rather than assuming. Whichever you pick, the ticket you build is the same object; the choice is about ownership and cost, laid out in how to sell tickets on your website. Once tickets are live, how to host an event and how to host an in-person experience take you through the day itself.

Keep building the ticketing setup end to end:

Frequently asked questions

How many ticket types should I create for a first event?

One or two. A single general-admission ticket is enough to run an event, and a small early-bird batch on top is a low-risk way to test demand and build launch momentum. Adding more types before you know how the event sells just gives buyers more ways to hesitate. Expand the menu once you have real data.

Do I need a QR code on my ticket?

Not strictly, but it makes check-in far faster and harder to fake. A QR code lets someone at the door scan a phone in about a second and confirm the ticket is valid and unused, instead of hunting a name list. Most platforms generate one automatically; if yours doesn't, a searchable attendee list still works for a small event.

How do I set the price for each ticket type?

Price your general-admission ticket first, using what the experience is worth and what lands after fees, then set every other type relative to it — early-bird below, VIP and higher tiers above by the value of what they add. Keep the gaps meaningful so the choice is obvious. Pricing your creator event works through the full method with examples.

Can I limit how many tickets are sold?

Yes, and you should. Set a quantity on each ticket type and a total capacity for the event; the platform decrements the count on every sale and stops selling at zero, so you never oversell the room. Real caps also create honest urgency that helps tickets move. Never fake a limit — buyers notice, and it costs you trust.

You create a code that applies a fixed amount or percentage off, then set how many times it can be redeemed and when it expires. Share it with a specific group — your list, a partner's audience — so they get a reason to buy now and you can see which channel drove sales. Keep discounts modest and time-boxed.

What information does a buyer need on their ticket?

The event name, date, time, and location; the buyer's name; which ticket type they bought; an order or confirmation number; and a scannable code for entry. Add your logo and one line of practical notes, like door time or what to bring. That's enough for someone at the door to admit them without contacting you. Anything more is clutter.

Can I create tickets without paying a platform fee?

You can avoid a platform's per-ticket fee by selling from your own site through your own payment account, where the only unavoidable cost is card processing — in the US, Stripe's 2.9% plus 30¢. Some platforms also offer free tiers that shift fees to the buyer. Event ticketing fees compares what each option costs.

How do I make sure my tickets actually work before the event?

Buy one yourself on a phone and follow the chain: does checkout complete, does the confirmation arrive (check spam), does the QR code scan with what you'll use at the door, and does the seat count drop by one? Then refund the test. This catches the delivery and scanning problems that otherwise surface in front of a live line.

Creating tickets isn't a technical project — it's four clear decisions (types, prices, capacity, delivery) and the discipline to test one real purchase before you go live. Build the types your buyers actually need, cap them honestly, put everything the buyer needs on the ticket, and confirm the QR code scans. Do that and check-in on the day is a scan and a nod. If you want the branded page, the ticket tiers, the live seat count, the QR-coded tickets, and the check-in all in one place — running on your own Stripe at a flat 10% plus processing, so every buyer stays your customer — that's what Meuse is built to do.