Ticket platforms often charge on every sale, and the customer list stays with them. A custom system is yours: checkout, barcode and wallet tickets, and scanning at the door, sized for the on-sale rush. For theatres on Tessitura, we're on the TNEW developer list and take TNEW well past its defaults.
What we build
Everything here comes from ticketing systems we have built for real events. Take the parts you need.
Ticket types, quantities and packages, reserved seating, a cart, promo codes, and checkout with or without an account.
Tickets added to the phone's wallet, so there is nothing to print and nothing to lose at the gate.
Barcode e-tickets with the event details, sent the moment each order comes in, with a printable copy for anyone who wants one.
Barcodes scanned with phones or handheld scanners at the door, with offline lists, barcode exports for printed tickets and will-call lists for promoters.
Stripe, PayPal or the payment provider you already use at checkout, custom receipts, and order confirmations by email and SMS.
Events, ticket types, prices and availability in one control panel, usually designEdit, with seats held during checkout, live sales reports and exports for your team.
Member accounts with member pricing, general admission and monthly donations in the same checkout as event tickets.
Event listings with recurring dates, venues and maps, galleries, vendor and promoter portals, and sign-in with email, Google or Apple.
Scaled up for the rush and back down afterwards, behind a firewall, on AWS or wherever you need it.
Two ways in
Most of our ticketing work is custom. If your theatre already sells through Tessitura or Spektrix, we work inside it.
Route 1 · Custom build
For festivals, carnivals, promoters, museums and community events that sell their own tickets. We plan the purchase path around how you sell and build it on AWS or wherever you need it, usually with designEdit as the control panel. The system and its data are yours.
Route 2 · Platform customization
For theatres and arts organizations already selling through Tessitura or Spektrix. We customize TNEW and Spektrix, and build and look after the theatre website around them.
Tessitura TNEW
We build on Tessitura's API to extend TNEW for theatres, and look after the theatre website around it.
A seat map drawn for each venue in place of TNEW's default seat selection, so buyers pick seats on a plan that looks like the room.
Our own tool for drawing a venue's seat map. The map loads into TNEW as a customization, and it can change for each show, season, performance or date.
The performance calendar extended with your own availability labels, so buyers see at a glance which dates are worth booking now.
Extra steps, add-ons and offers added to TNEW's default checkout through Tessitura's API.
Show pages with live dates and availability, and account pages with orders, tickets and memberships, all from Tessitura.
Sales and attendance dashboards built on Tessitura's data, for the people who need the numbers without opening Tessitura.
How a project runs
Ticket sales bunch up at the end. On one event site we built, half the year's ticket sales came in the last two weeks before the event, so the system is sized for that.
Ticket types, prices, capacities, who scans at the door and what reports you need. A blueprint and a working prototype of the purchase path, so you have a price before we start.
The purchase path, the ticket and the wallet pass in your brand, by your designers or a design firm that fits the project.
Checkout, barcodes, wallet passes and scanning, tested end to end: buy a ticket, add it to a wallet, scan it at a door.
Launched behind a firewall and scaled for the rush, with reports through the run. Afterwards the system settles down, and we support it on terms we agree with you.
Start where you are. If you already have a ticketing plan, a platform or designs, we review them with you and pick up from there instead of starting again. Tell us what you have.
Who we have built ticketing for
Client names are used with permission. Tessitura, TNEW, Spektrix, Apple, Apple Wallet, Google, Google Wallet, Stripe and PayPal are trademarks of their respective owners. Design of a Decade is an independent studio and is not affiliated with or endorsed by Tessitura Network or Spektrix.
Questions
Ticket platforms often take a fee on every ticket, and the customer data stays with them. A custom system costs more up front, then you pay for hosting and support, not a cut of each sale, and the customers are yours. If a platform suits you better, we'll tell you.
Yes. It's sized for your biggest on-sale and tested before tickets go live. It scales up for the rush and back down afterwards, so you aren't paying for the peak all year.
Yes. Each ticket arrives as a barcode e-ticket, and buyers can add it to Apple Wallet or Google Wallet, so there is nothing to print.
With phones or handheld scanners. Staff scan the barcode at the gate, and printed tickets and will-call lists work too. Where there is no connection, scanning runs from an offline list loaded onto the devices before the doors open.
Yes. We're on Tessitura's TNEW developer list. We extend TNEW with custom seat maps, checkout steps, show and account pages and dashboards, customize Spektrix, and build and look after the theatre website around them.
It depends on what you sell, how you sell it and what it connects to. The blueprint and prototype work that out, and you have a price for the build before you commit to it.
The system scales back down, and the reports and exports stay available. Support carries on for as long as you want it, on terms we agree with you, ready for the next on-sale.
You keep running what we built, and the customer data is yours. The code is yours to take in-house or to another team. If designEdit is part of the system, we work with you to choose the licence model that fits.
Planning a season or an event?
You don't need everything worked out. Send us a rough idea or a full spec, and we'll reply within one business day.
Burlington, Ontario