Ticketing fees: subscriptions vs pay-per-ticket

Ticketing software is priced in two common ways. You pay a monthly or annual subscription (sometimes plus a cut of each ticket). Or you pay only when you sell—a per-ticket platform fee plus a percentage of the transaction. The second model is usage-based, or pay-per-ticket. Neither is automatically cheaper. The right choice depends on how many tickets you sell and how many months you are dark.

A high school theatre that sells 1,200 tickets across three productions and is quiet all summer will usually lose money on a twelve-month seat. A venue that is live fifty weekends a year might prefer a subscription if the per-ticket rate is high. Most schools, PTAs, boosters, rec leagues, and community presenters are in the first group. That is why Tixoola default rates have no monthly software subscription. See current public rates.

Build a one-page comparison

Pick a real event: 300 tickets, average price $18, 10% sold at the door. Price that night on your current tool including the monthly fee allocated to that month. Then price it on a usage-based tool. Add payment processing (Stripe, Square, or Authorize.Net) in both columns so you are not comparing apples to software-only numbers. If the subscription tool also charges a “facility fee” to the buyer, write that down—buyers notice.

Ask what happens in a month with zero events. If the answer is “you still pay,” you are funding the vendor’s idle capacity. Volunteer treasurers feel that. Boards feel that. The article on PTA and nonprofit ticketing is written for that conversation.

What “all-in” should include

All-in means platform fee + payment processing + any required subscription + any mandatory add-ons (SMS packs, extra scanner seats, “premium support”). It does not mean you hide fees from the buyer. You can absorb fees or pass them through; just be consistent on the event page. Checkout should not invent new line items after the buyer has committed. Phone wallets should work. Details on payments live at payments and payouts.

Custom agreements exist for high-volume organizations. Public default rates are the honest starting point. If a salesperson will not quote a $15 student ticket in writing, keep shopping. The software checklist includes this as a gate.

When a subscription can still win

If you sell tens of thousands of tickets a month and want a negotiated rate, a subscription or a hybrid can be cheaper. If you need a dedicated success manager in the contract, you will pay for that somehow. Just do not buy an enterprise seat to run four PTA nights. And do not keep a leftover subscription from a previous booster board because “we already paid for the year.”

• Price a real event, not a vendor’s sample 5,000-ticket night.
• Include the months you sell nothing.
• Include processing, not just the platform fee.
• Write down who pays: organizer or buyer.
• Get the $15 student ticket in writing.

A worked example for a seasonal group

Imagine a PTA that sells 900 tickets a year across four events, average price $20. A $99/month tool is $1,188 before any per-ticket cut. If that tool also takes 2% plus a ticket fee, add that on top. A usage-based tool with no monthly seat charges only on those 900 tickets. In the eight dark months the PTA pays the vendor nothing. That is usually the entire board conversation. Plug in your real counts on a napkin. If the subscription still wins, keep it. If it does not, stop paying for idle software.

Do the same math for a 4,000-seat Friday night that happens ten times a year. The monthly fee is a smaller slice. Processing still dominates. The decision then is about door operations and reporting, not the seat license. That is why we tell athletic directors to price a real home game and a real playoff, not a vendor’s 50,000-ticket slide. See school and college athletics if that is your calendar.

Pass-through versus absorb is a policy choice. Absorbing fees keeps the advertised price clean. Passing them through can protect a tight budget. Either way, write the choice on the event page in one sentence. Families forgive a stated fee. They do not forgive a checkout that grows after they thought they were done. Test the flow on a phone before you send the link to the whole school.

Tixoola’s default is usage-based for every industry we publish, from school events to concerts. If you want to see the product around those fees, start at event ticketing.

Refunds change the math. If you cancel a weather-sensitive outdoor night, you need a refund path that does not require a developer. Ask whether refunds reverse the platform fee, how long payouts take, and whether door sales refund the same way as online. Write the policy on the event page before you sell the first ticket. A clean fee model with a messy refund story is still a messy fee model.

If you share the event with a booster club and a school account, decide who is the merchant of record before you connect a processor. Usage-based software will not fix a split bank account. It will make the split visible. That visibility is useful. Have the conversation in April, not at the gate in October.

Run the numbers on your next event, then create a site if the math is obvious. Create your Tixoola site or review current pricing.