• Replies 12 replies
  • Subscribers 416 subscribers
  • Views 191 views
  • Users 0 members are here
Related

Let's talk price templates

Lesley Chaney
$organization

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
  • $organization

    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

     

Reply
  • $organization

    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

     

Children