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

Parents
  • 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.

  • Thanks Kevin! 

    Is there any downside to having the Ticket Price 1 layer be used for Subscription pricing (and all pricetypes on that layer set to the subscription GL) and then using the Ticket Price 2 layer be single ticket pricing using the single ticket GL? I realize that is not really the intended behavior for the price layers, but I want to make sure that there isn't anything "inherently wrong" (to quote Ron Wilson) if we do that.

    Thanks again! 

Reply
  • Thanks Kevin! 

    Is there any downside to having the Ticket Price 1 layer be used for Subscription pricing (and all pricetypes on that layer set to the subscription GL) and then using the Ticket Price 2 layer be single ticket pricing using the single ticket GL? I realize that is not really the intended behavior for the price layers, but I want to make sure that there isn't anything "inherently wrong" (to quote Ron Wilson) if we do that.

    Thanks again! 

Children
No Data