We are wanting to setup a map that would offer reserved seating in a main floor and loge sections, but then we would want to offer general admission tickets to a balcony section if possible. Our original thought was just to create a third screen on the map with a block section, the same way we would setup a GA house. However, we would only be able to use a single best seating map for said performance,and we wouldn't want to check off the GA Ind. box for it. I'm assuming this would create an issue if we wanted to sell the GA tickets online. Has anyone done this before? Do you know of any problems this might cause? How would TNEW handle it, if was wanted to sell the reserved on an SYOS but GA through the best seating section?
Our other concern is that we use different ticket designs for reserved seating as compared to GA. The reserved, of course, displays all seating info on the side of the ticket. The GA simply says General Admission in the seating section area of the ticket. The only way we could think of to sell 2 different ticket types for one performance is using different price types each associated to a different ticket design. Does anyone know of another way to use a single price type to display one ticket design when sold in a certain section and another design when sold in a different section?
We have an outdoor facility that we use every year with reserved seating and general admission seating in the grass area. We built it as you described - nicely laid out sections for reserved and then a big block for the grass. No G/A indicator checked. Our old web developer built some customizations for us so we can sell shows for that online with SYOS in the reserved only and best available options for all seating sections. We aren't on TNEW so I can't speak to what your options are in that regard.
We also wondered about what to do with the ticket design. In the end we went with one design. It pulls the section description on our tickets (which we simply named Grass for that section) and it also pulls a row/seat number but we didn't particularly care about that. Sometimes we get a customer confused about the number on their ticket but it doesn't come up very often and we simply tell them it's a ticket number and not a reference to a specific spot on the grass.
If you have a skilled enough systems admin on hand they might be able to do some fancy masking on your ticket design so you can get away with one design for everything.