PTA and nonprofit event ticketing with no monthly fee

Parent groups and small nonprofits do not have a ticketing department. They have a treasurer, a volunteer night-of team, and a board that will ask why software was billed in March when the gala is in October. Monthly ticketing subscriptions punish that calendar. Usage-based, pay-per-ticket pricing does not. You publish when you have a date. You pay when someone buys. You turn it off when the yearbook committee is done.

This is the operating reality behind Tixoola’s default rates: a per-ticket platform fee plus a percentage of the transaction, no monthly software subscription. Read pricing and the fee comparison before the next board meeting. Then set up the event the way families already buy—on a phone, in the car, after the reminder email.

What to sell besides “a ticket”

Galas need tables, not just seats. Auctions need a way to collect payment that is not a clipboard. School nights need adult vs student prices. Some events want a donation add-on in the same cart. Keep the first event simple: ticket types, capacity, one public link. You can add complexity when the volunteer team has survived a door. Playbooks for nonprofits and galas and school events match those jobs.

Connect Stripe, Square, or Authorize.Net—the processor the 501(c)(3) or school already uses. Do not invent a new merchant account unless you have to. Settlement to the organization’s account is what the audit letter wants. Apple Pay and Google Pay reduce the “I left my wallet in the minivan” problem.

Night-of without heroics

Print a one-page run-of-show for the door: who scans, who does will-call, who sells walk-ups. Use QR scanning on personal phones. Use box office for remaining tickets so you do not oversell the fire code. Do not run a side Venmo. Side Venmo is how nonprofits lose both the count and the thank-you list. More on the combined flow: online ticketing and box office.

Afterward, export the list. Boards want attendance and net. Sponsors want to know whether their table showed up. You want to know whether to raise the student price next year. If the platform cannot give you that without a developer, it is the wrong platform. The buying checklist is written for that conversation.

A year of events on one site

One Tixoola site can host the fall carnival, the winter concert, and the spring gala. You are not buying a new product for each theme. Branding stays yours. Fees stay usage-based. Volunteers learn one door process. That is the whole pitch for groups that cannot afford a full-time box office manager.

• No monthly software bill in dark months.
• Processor you already have; settlement you can audit.
• One public link for families; QR check-in for volunteers.
• Door sales in the same inventory as online sales.
• Exports a treasurer can attach to minutes.

What to tell the board in one paragraph

We will publish a public event page, take cards through the processor we already have, and scan QR codes at the door. We will not pay a monthly software bill in months we have no events. Door sales will come out of the same inventory as online sales so we cannot oversell. Afterward we will export who paid and who scanned. That paragraph is the whole motion. If a vendor cannot support it without a custom statement of work, they are not built for volunteer organizations.

Sponsors and table captains need a different message: here is the link, here is the deadline, here is how guest names get on the list. Do not promise assigned seats if you are running general admission. Do not promise a printed program insert if the list is still moving the afternoon of the event. Software cannot fix a communications plan you did not write. It can stop you from running three incompatible lists.

When the year turns over, transfer the Tixoola login with the treasurer binder. Keep the same site. Archive last year’s events. Publish the new carnival. Volunteers should recognize the door. That continuity is worth more than a new logo on a new platform every September. If you want the school-night version of this story, read how to sell tickets online for a school or community event.

If you are still collecting cash in an envelope, start there, then create your site.

Grant writers and finance chairs often ask whether ticketing software is an allowed expense. Usage-based fees tied to a specific event are easier to explain than a year-long seat for a tool you used twice. Keep the settlement PDF with the event folder. If a donor asks how many people came, you have a scanned count, not a guess. That is governance, not marketing.

You can still be warm at the door. A QR scan does not replace a greeting. It replaces the clipboard argument. Volunteers who hate “technology” usually hate last year’s broken scanner, not a phone that works. Give them a 60-second practice on a dummy ticket. Most of them will prefer it to deciphering handwriting under a gym light.

Give the next PTA night a real event page and a door that scans. Create your Tixoola site or review current pricing.