How to sell tickets online for a school or community event

If you run a school play, PTA movie night, booster dinner, or community concert, you already know the hard part is not the show. The hard part is collecting money from families who will not mail a check, standing at a folding table with a cash box, and then guessing who actually paid when the doors open. Selling tickets online is the cleanest way to fix that—if the software does not add a monthly bill for months you are dark.

This guide walks through a complete path: publish a public event page, take card payments, share one link, and scan QR codes at the gym or auditorium. It is written for volunteer treasurers and school staff, not enterprise venue operators. If you also run athletics or youth sports, the same site can host those events later—start with the next date on the calendar.

Start with the event, not the software catalog

Write down the night you are selling: capacity, ticket types (adult, student, family), whether you need a presale for cast families, and whether you will sell anything at the door. Those four facts decide the setup. You do not need reserved seating software for a cafeteria dinner. You do need a page that works on a phone, because that is where parents buy.

Create a Tixoola site from signup, name the organization the way families already know it, and add the event. Use a clear title, a start time in the local timezone, and a short description that says what is included. Upload a poster if you have one. Set capacity so you cannot oversell the fire-code limit. Add ticket types with prices that already include whatever you want the buyer to see—no surprise “service fee” surprises after they tap pay if you prefer an all-in price.

Take payment without opening a new bank product

Connect the processor your organization already uses: Stripe, Square, or Authorize.Net. Ticket money settles to that merchant account. Families can pay with cards and, when the processor supports it, Apple Pay or Google Pay. That matters on a Thursday night when a parent is buying two student tickets from the pickup line. You are not asking them to create a consumer “ticket app” account just to see a QR code.

If your board is sensitive about fees, read Tixoola pricing before you publish. Default rates are usage-based: a per-ticket platform fee plus a percentage of the transaction, with no monthly software subscription. You pay when you sell. That is the difference between a PTA that runs four events a year and a venue that is live every weekend. For a deeper comparison, see subscriptions versus pay-per-ticket.

Share one link everywhere

Once the event is published, you get a public URL. Put it on the school website, the Facebook event, the paper flyer QR, and the email from the principal. Do not invent a second “cash only at the office” list unless you truly need it. Split lists are how you double-sell a seat and then argue at the door. If you must take cash, sell those tickets in the box office on a tablet so they come out of the same inventory.

School and community groups often juggle more than one night. A winter play, a spring gala, and a Friday football gate can live on the same Tixoola site. Industry playbooks for school events and nonprofits are useful if you want copy and examples that match how you actually operate.

Check people in without a clipboard

On the night, staff open scan on a phone and read the QR on the buyer’s screen or a printed confirmation. Look up will-call by last name when someone shows a screenshot that will not scan. Transfers happen when a family gives tickets to grandparents—do that in the order, not on a sticky note. Live redemption counts tell you whether the balcony is actually full. Details live in QR code ticket scanning and the scanning product page.

If you also sell at the door, do not run a separate cash app and a paper list. Use box office so walk-up sales decrement the same remaining capacity. Online and door orders then land in one settlement view, which is what your treasurer wants on Monday. That workflow is covered in online ticketing and box office.

What “done” looks like after the event

You should be able to export who bought, what they paid, what was refunded, and how many tickets scanned. Boards ask for that. Boosters ask for that. A good event ticketing setup makes the Monday report boring. If you cannot answer “how many student tickets scanned?” without opening three spreadsheets, the stack is wrong.

• Publish one event page with capacity and ticket types.
• Connect Stripe, Square, or Authorize.Net—the account you already have.
• Share a single public link; sell door tickets in the same inventory.
• Scan QR codes from any phone; look up will-call by name.
• Export settlement for the treasurer the next morning.

A simple timeline for the first event

Two weeks out: publish the page, connect payments, and send the link to a small test group (cast families or the booster board). One week out: share the link on the school site and social posts. Two days out: print a one-page door script and decide who scans versus who sells walk-ups. Night of: phones on, brightness up, name lookup ready. The next morning: export settlement and email it to the treasurer. That is the whole operating system. You do not need a project manager.

If a parent cannot find their confirmation, search will-call by last name. If the gym Wi-Fi dies, keep selling from the tablet on cellular and look people up by name. If someone wants to pay cash at the door, sell that ticket in box office so it still decrements capacity. None of those exceptions require a second spreadsheet. They require one inventory and one habit: do not invent a side list.

If you are comparing platforms, use the ticketing software checklist and the event ticketing overview. Tixoola is built for live events—schools, venues, sports, and community organizations—not as a consumer concert marketplace.

Ready to stop collecting checks in the school office? Create your Tixoola site or review current pricing.