An event theme with ticket sales built on your own domain changes one number that nothing else on your marketing plan can touch: the share of every ticket you actually keep. A marketplace takes a cut of each sale, owns the checkout, owns the buyer’s email address and pays you out on its own schedule. Running ticketing on your own site means you keep the margin, you keep the list, and the page the buyer lands on is the page you designed. It also means the refunds, the tax and the door scanning become yours. This guide works through what the marketplace fee is really costing you, what the self-hosted options are, how to put the structure together in a WordPress event theme, and the cases where handing it back to a marketplace is still the right call.

What Eventbrite’s cut actually costs you

Marketplace pricing has the same shape almost everywhere: a percentage of the ticket price, plus a fixed amount per ticket, plus card processing on top of both. Rates differ by country, by plan and by whether the event is free, and they change — so get the current figures from your platform’s own fee page rather than from an article. What does not change is the arithmetic, and the arithmetic is where the surprise lives.

Work it out like this. Take the service fee percentage, apply it to the ticket face value, add the fixed per-ticket amount, then add the payment processing percentage applied to the total the buyer pays — processing is charged on the amount that moves, which includes the service fee if the buyer is absorbing it. Multiply by the number of tickets you expect to sell this year, not this event.

A fully hypothetical example, so you can see the shape: on a 50.00 ticket, a 5% + 0.50 service fee and 2.5% processing comes to roughly 4.31 per ticket. Sell 600 tickets a year and that is about 2,590. Those are made-up rates used only to show the method — substitute your own. The point is that the figure is an annual operating cost in the low thousands for a small event programme, and it is recurring. Self-hosted ticketing costs a plugin licence and a payment gateway percentage, so the comparison is not “free versus paid”; it is a fixed annual cost against a cost that grows with every ticket you sell.

There are two costs that never appear on the invoice and usually matter more. The first is the buyer relationship: on a marketplace, the platform is the merchant of record and the primary holder of the attendee list, which is the asset you need to sell next year’s edition. The second is the drop-off at handover — every click that leaves your site for a third-party checkout is a click where someone reconsiders. If you have spent weeks on the programme and the speakers page, sending the buyer somewhere else at the moment of purchase is the one avoidable leak in the funnel.

Self-hosted ticketing options compared

There are three honest routes to wordpress event ticketing on your own domain, and they suit different events. Pick on the basis of whether your tickets are really products, really registrations, or really both.

RouteBest forWhat you getWhat it costs you
A dedicated event ticketing pluginConferences and one-off events with tiers, capacity caps and attendee dataTicket types, per-ticket attendee fields, capacity limits, QR tickets, check-in toolingAnnual licence for the paid tier; a second admin surface to learn
WooCommerce with tickets as productsClubs, festivals and venues already selling merchandise, bar tabs or membershipsOne cart, one order history, one tax engine, every WooCommerce payment gatewayTickets behave like stock, so capacity is inventory and attendee fields need extending
A simple form plus a payment linkWorkshops and seminars under roughly fifty seatsMinimal setup, no new subsystem, full control of the copyNo capacity enforcement, no scannable ticket, manual reconciliation

The dedicated-plugin route is the default for conferences, because a conference ticket is not a product — it is a named seat attached to a person who has dietary requirements, a job title and a session preference. Event Tickets on the WordPress plugin directory is the most widely installed free starting point, with paid tiers for commerce; whichever you choose, check it is actively maintained against the current WordPress release before you build a season around it.

The WooCommerce route wins when ticketing is not the only thing you sell. A nightclub or a festival selling entry alongside table bookings, merchandise and drinks packages does not want two checkouts and two tax configurations. In our own catalog that difference is visible in the product pages: the Miami nightclub and festival theme states WooCommerce support on its page, which is the honest signal that the commerce path is the one its design anticipates, whereas a conference build is better served by the event data model described below.

Setting up an event theme with ticket sales in YOY

Be clear about the division of labour before you start, because getting this wrong is the main reason self-hosted ticketing projects stall. A theme supplies the structure — the event pages, the schedule, the speakers, the sponsors and the layouts that hold them. Taking money requires a payment gateway and a ticketing or commerce plugin, and you add those yourself. The YOY event and conference theme states on its product page that it includes tickets, event venues, speakers, sessions and sponsors, and ships eight home pages, Schedule templates, Venue, Clients and Speakers pages, the Event Scheduler plugin, WPBakery Page Builder, Contact Form 7 and Google Maps. It does not name a payment gateway, so plan for that as a separate decision rather than expecting checkout to arrive with the theme.

  1. Install the theme and import the demo, then treat it as scaffolding. One-click demo import gives you a working structure and placeholder content, not a finished site. Note that the demo images are licensed for the demo only, so your own photography has to be ready before launch, not after it.
  2. Decide your ticket tiers on paper first. Early bird, standard, student, group of five, speaker and sponsor comps. Write the capacity and the cut-off date for each one before you touch an admin screen; retro-fitting a tier after sales open means reissuing tickets.
  3. Install the ticketing or commerce plugin and connect the gateway. Put it in test mode and complete a full purchase as a stranger would, on a phone, on mobile data. This is the step teams skip and it is the only one that proves the chain works end to end.
  4. Build one ticket page, not a shop. Tiers in a single table, the price the buyer actually pays shown before checkout, what is included per tier, and the refund policy visible on the same screen. Nothing between the table and the button.
  5. Collect the attendee fields you will genuinely use. Name, email, organisation, access requirements, dietary requirements. Every extra field costs you conversions, so if nobody will read the answer, delete the field.
  6. Wire the ticket page into the pages that do the selling. The schedule, the speakers page and the venue page each need a route to purchase in context, not only in the main navigation. The programme is what persuades; the ticket page only closes.
  7. Mark the page up as an event. Use schema.org Offer inside your event markup so price, currency and availability are machine-readable, and keep it accurate when a tier sells out.

Sequence matters more than speed here. Build the programme first, the ticket page second. Our guide to conference session ideas that delegates remember is the input to this step, and the speakers page build is the asset that makes the price defensible — people buy the line-up, then the ticket.

Payments, tax and refunds

When you sell tickets on your own website you become the merchant of record, and three obligations transfer with that status.

Payments. Pick a gateway on settlement time and dispute handling, not on the headline percentage. For European cards you need strong customer authentication to work properly on mobile, which means testing the 3-D Secure step rather than assuming it; Stripe’s 3-D Secure documentation explains the flow and the failure modes. Run at least one real card through the live gateway before you announce sales, and check that the confirmation email arrives in a mailbox you do not control.

Tax. Admission to an event is generally taxed where the event physically takes place, not where your company is registered — that is the rule in the EU VAT Directive for admission to cultural, educational and entertainment events, and most jurisdictions treat live admission similarly. For an online event the place-of-supply rules differ again. So a hybrid event can have two tax treatments in one checkout, and your in-person tickets and your stream tickets may need separate tax classes. Configure this before sales open, take advice for your own jurisdiction, and read your platform’s own tax setup documentation — WooCommerce’s tax documentation is a reasonable orientation if you are on that route.

Refunds. Write the policy before you need it and publish it on the ticket page. Decide four things: the cut-off date after which refunds stop, whether the service fee is returned, whether a ticket can be transferred to another person instead of refunded, and what happens if the event is cancelled or moved. Name transfer explicitly — it is cheaper for you than a refund and better for the attendee, and a transfer link in the confirmation email removes most support email before it is sent.

Check-in on the day

This is the part self-hosted ticketing gets accused of failing at, and it fails for one reason: the venue’s wi-fi. Plan for check-in to work without a connection.

  • Export the attendee list to a device before you arrive and carry it as a printed or offline copy. A scanner that needs your site to respond is a scanner that stops when the venue’s guest network does.
  • Use unique codes, not names. A QR code or short reference per ticket, checked once and marked used, stops the duplicate-entry argument at the door.
  • Run two desks for anything over about 150 people — one for pre-booked, one for problems. Mixing them is what creates the queue photographed and posted.
  • Decide the on-the-door policy in advance. Whether you sell at the door at all, at what price, and who is authorised to wave someone through. Write it down for the volunteers.
  • Reconcile the same evening. Tickets sold against people scanned in tells you your real no-show rate, which is the number you need to set capacity for the next edition.

After the event, the attendee list is the thing you fought the marketplace for. Use it: a post-event page with the slides and recordings, an early-bird window for the next edition offered to last year’s attendees first, and a schedule archive that stays online. The events and conference themes in our catalog are all built around the assumption that the site outlives the event.

When a marketplace is still worth it

Self-hosting is not the right answer in every case, and pretending otherwise would cost you money. An event ticket plugin wordpress setup is the wrong call in four situations.

You need discovery, not just a checkout. For a first public event with no list and no audience, a marketplace’s own search and recommendation traffic can be the difference between a sold room and an empty one. The fee is then a customer acquisition cost, which is a different thing from a payment fee.

Volume is tiny. Forty seats once a year does not repay the setup, the licence and the testing. Take the fee and spend the time on the programme.

Nobody owns the stack. Self-hosted ticketing needs a named person who will answer a payment-failure email during the sales window. If that person does not exist, the marketplace’s support desk is genuinely worth its percentage.

The risk is concentrated. One event a year carrying your whole revenue is a bad place to debut an untested checkout. Run the next edition in parallel — marketplace for the public tier, your own site for members and returning attendees — and compare conversion before you move everything.

For everyone else, the maths is straightforward: a recurring per-ticket fee against a fixed annual cost, plus ownership of the attendee list. If you run more than one event a year, you are already past the crossover. Build the programme first — our creative conference formats guide is a good place to start — then put the ticket page at the end of it, where it belongs.