Part 1: The house, drawn once
Stalls, circle and balcony as sections you generate rather than place seat by seat. The twentieth night takes as long to set up as the first, which is to say no time at all.
For theatres
Ticketing for theatres and performing arts
The same auditorium, twenty performances, and a box office that has to agree with the website.
Verimly is built for assigned seating, which is what a theatre needs: draw your auditorium once, save it as a template, and apply it to every performance in the run. Each performance prices its own zones, buyers choose a specific seat, and the box office sells from the same availability so the two can never disagree.
What you are looking at
The numbers on the screen above mark the parts that do the work. Here is what each one is.
Part 2: Zones that match your price bands
Band A, band B, restricted view. A zone is a part of the room; what each band costs is set per ticket type, so concessions do not need a workaround.
Part 3: A curved circle, rotated into place
Select a block and rotate it around its own centre. Real auditoriums curve, and a map that pretends otherwise confuses the people using it.
Part 4: House seats and access seats held back
Press, production, a wheelchair space and its companion. Blocked seats stay on the map so the room reads correctly, and nobody can buy them.
Part 5: One template, every performance
Save the auditorium to the workspace and apply it to the whole run. Pricing stays per performance, so a matinee and a Saturday night can differ.
In practice
Draw the house once
The seat-map editor generates sections as rows by seats, rotates a curved circle into place, and puts the stage where it really is. Save the finished auditorium as a workspace template. Every performance in the run starts from it, so setting up a twenty-night run is twenty pricing decisions rather than twenty drawings.
Concessions are a ticket type, not a discount hack
Student, Senior, Member and Full Price are ticket types. Each one gets its own price in each zone, so a student in the stalls and a student in the balcony are different numbers, and any combination you do not offer is simply switched off.
- "Not for sale" and "priced at zero" are different statements, and the grid keeps them apart.
- A concession that only applies to one band is a single switch, not a separate event.
Holding seats back
Block seats to keep them out of sale — house seats, press, a wheelchair space and its companion seat, or a row behind a pillar. Blocked seats stay on the map so the room still reads correctly to a buyer, but nobody can buy them, online or at the box office.
One availability, two counters
The website and the box office draw from the same seats. Somebody buying G12 on the phone removes G12 from the website that instant, which is the whole point of having one system rather than two that sync overnight.
The desk keeps the run in view
Orders, customers and their history are in the same workspace, so a subscriber ringing about last month has an answer without a search through email. Refunds and exchanges are handled from the order and the reporting follows.
Getting it running
What you actually do, in order, the first time.
- 01
Draw the auditorium
Once, properly. Sections, zones, stage, blocked seats.
- 02
Save it as a template
The layout becomes reusable for every future production in the house.
- 03
Create a performance per date
Apply the template, set the prices for that night, publish.
- 04
Sell from both counters
The website and the box office share one availability, all run long.
At a glance
| Auditorium | Drawn once, saved as a reusable workspace template |
|---|---|
| Zones | Stalls, circle, balcony — each priced per ticket type |
| Concessions | Student, Senior, Member as ticket types, priced per zone |
| Runs | One event per performance, the same layout applied |
| Box office | Desktop POS app on the same availability |
| Access | Seats can be blocked and held out of sale |
| Price changes | Editable after sales begin; the layout locks |
| Branding | Your own domain, your identity, your emails |
Questions, answered
Can I sell a whole run as one purchase?
Each performance is its own event with its own seats, so a buyer picks a performance and a seat within it. A season pass across performances is not modelled as a single ticket today.
Can I reuse my auditorium layout?
Yes. Save any layout as a workspace template and apply it to every future event. Pricing stays per event.
Can I change a price once the run has started?
Yes. Prices and the not-for-sale switch stay editable after sales begin. The layout locks once seats are sold so existing tickets always point at a real seat.
How do I handle wheelchair spaces?
Draw them as seats in the appropriate zone and block them, then release them through the box office, or price them as their own zone if you want them bookable online.
Can the box office and the website ever disagree?
No. There is one availability. A seat sold at the desk is gone from the site in the same moment, because there is nothing to synchronise.
Can I run different prices for a matinee?
Yes. The layout is shared through the template; the prices belong to the individual performance.
Keep reading
- Ticketing for concerts and live musicOn-sale day, the seated balcony, the standing floor, and a queue at the door that has to move.
- Ticketing and registration for conferencesEarly bird, standard, student, and a registration desk that has to move a queue of three hundred.
- Timed-entry ticketing for museums and attractionsA capacity per hour, an exhibition with its own price, and an entrance that should not need a printer.
See it for a specific kind of event
Get started
Free to set up. You pay when a ticket sells.
No subscription, no setup fee, nothing to cancel. Build the whole thing, and decide at the end whether to publish it.