Hi all,
I am in the midst of planning my first full season build since converting to version 12, and have some questions about price templates. My initial thought was that I would create separate templates for Subscription tickets and Single tickets, since those pricetypes have separate GL numbers, and GLs are required when creating a template. But then I wondered if the point of a template was to be more all-inclusive, so now I'm not sure what the best plan is. The one thing I really want to avoid is adding new single ticket pricetypes in the midst of a season and adding them to the subscription GL.
Any thoughts?
Thanks as always, and Happy New Year to all!
Lesley
The price layer types you currently have were created as part of the migration for all your pre-v12 pricing. Renaming Ticket Price 1 and Price 2 won’t hurt anything, but it might make looking at the setup on past performances a little confusing as the price types on the layers probably won’t entirely conform to the business practice reflected in the new layer type descriptions. Based on that, I think it’s cleanest to create new layer types with the new descriptions and then inactivate the old layer types that you won’t be using anymore.
Kevin Sheehan
Senior Technical Writer & Consultant
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
I have a question regarding Price templates - I have my templates set up for my season and i find that I need to add a new price to the template - but I wasn't sure if that would apply if the template is already applied to the performance.
Thanks!