Let's talk price templates

Hi Lesley,

You would have just one template for both your subscription and single tickets, as both sets of price types will be on the same layer, presumably your ticket price layer, and after you use the template to add a layer to a performance you’ll be making changes directly on the layer on the performance (you don’t edit the template to affect a performance and you can’t use a template to add price types to an existing layer)  Additionally, you can set the GL at the individual price type level on Price Templates (just like you can when adding layers directly to a performance). The Default GLs you set when creating a new template (or a new ad hoc layer), are just the defaults that are used as new price types are added to the template (or a layer). Since the template defaults will carry over to the layer defaults when you use the template to add a layer to a performance, I would probably set the defaults to the single ticket GLs, that way if someone adds a price type to a layer after the initial setup and forgets to check the GLs on that price type, they will default to the single ticket GLs.

To sum up:

1.       Set the default GLs on your price template to the single ticket GL.

2.       After you add your subscription price types to the template, go to the Price Type Properties and change the GLs on the subscription price types to the subscription GLs.

Here are some related help links in case you need them: Price Templates and Price Layers

Let me know if any of that doesn’t make sense.

Happy New Year!

Kevin Sheehan

Senior Technical Writer & Consultant

Tessitura Network

+1 888 643 5778 x 329

ksheehan@tessituranetwork.com

From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Lesley Chaney
Sent: Wednesday, December 31, 2014 1:43 PM
To: Kevin Sheehan
Subject: [Tessitura Ticketing Forum] Let's talk price templates

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

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.5577 / Virus Database: 4235/8737 - Release Date: 12/14/14
Internal Virus Database is out of date.

Hmmm… As long as both layers are in the same Price Category (Ticket Price) but use different Price Layer Types, I think you should be o.k. for reporting, which would be my biggest concern.

The biggest downside I can think of is that you are going to still see all the single ticket price types on the subs price layer and all the subs price types on the single ticket layer as ghost rows, which could be little confusing. And on the All tab you are going to see a lot more partial set icons on all the performances. All of this should only affect staff who look at the setup side of things, though.  So I would make sure everyone is really clear on what your business practices are here, name your Price Layer Types clearly (something like Single Ticket PTs and Subscription PTs), and test out setting up a performance or two this way in your Test system before setting up the whole run.

To sum up, I don’t think there’s anything “inherently wrong” doing it that way, but it might make things a little more confusion and/or error prone than the standard way of doing it.

Kevin Sheehan

Senior Technical Writer & Consultant

Tessitura Network

+1 888 643 5778 x 329

ksheehan@tessituranetwork.com

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

Hi Joel,

There is no connection between price templates and performances to which they have been applied, so making changes to a template will not affect performances to which you have previously applied that template.

If you need to add a price type to existing price layers on performances, you can do it in Season Maintenance.

Kevin Sheehan

Senior Technical Writer & Consultant

Tessitura Network

+1 888 643 5778 x 329

ksheehan@tessituranetwork.com