• Replies 2 replies
  • Subscribers 337 subscribers
  • Views 153 views
  • Users 0 members are here
Related

PAHT challenges with shared Modes of Sale on websites

Tiffany Elliott (Past Member)
$organization

Hi everyone,

We are working to try and offer Print at Home Ticketing on our websites and I have a few questions after trying to figure out some challenges in regard to our Modes of Sale.

Right now, we have 2 websites and only want to offer PAHT on one.

One site is dedicated to selling tickets for local theatre companies who rent our space and the other site is for only our shows.   We are not set up like a consortium within Tessitura with different control groups, so our price types and Modes of sale are sometimes shared and sometimes different.  It has caused some confusion for me because now we have over 2K active Modes of Sale with various price types associated with them.  This is mainly because instead of using offers, the box office has set up promo codes in TR_WEB_SOURCE_NO, to trigger new modes of sale, often times with only one price type associated with that new mode of sale in order for the web to not show other prices.

So far, everything is configured for PAHT the way I think its supposed to work, however, I am having a hard time determining how to limit PAHT by price types since the way to activate it as a choice on the web is by mapping the MOS to PAHT in  TX_MOS_SHIP_METHOD.  To make matters worse, both environments also SHARE some modes of sale, so if I turn it off on one site, it turns off on the other as well! 

Does anyone have any guidance about how to NOT offer PAHT to specific price types?

Example:  We don't want to offer students the choice to print tickets at home, but since the student price type is associated with every Mode of Sale, would I need to create an entirely new Mode of Sale to do this or is there an easier way to restrict this? 

Thanks for any help! :)

  • $organization

    Hi Tiffany,

    Although it is not recommended to make changes to standard procedures by the Network, you could probably achieve this by altering WP_GET_SHIPPING_METHODS to look at all of the price types in the cart and then suppress any PAH shipping methods from being returned by the procedure. You could create a local table of price types that would cause this to happen.

    I was able to get this up and running in a slightly different scenario where we wanted to disable PAH for specific performances, and have not observed any performance issues.

    Hope that helps you out, I can't believe you have 2,000 modes of sale!

    Paul

  • $organization

    Thanks Paul!

    I think you’re onto something.

    We are probably going to talk with our web developers to see if they can build some code to do what you’re suggesting.  It already does this with one price type, so I think we may be able to broaden the scope a bit.

     

    Yes, 2000!!!  I almost died. 

     

    From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Paul Kappel
    Sent: Wednesday, December 11, 2013 1:00 PM
    To: Tiffany Evans
    Subject: Re: [Tessitura Technical Forum] PAHT challenges with shared Modes of Sale on websites

     

    Hi Tiffany,

    Although it is not recommended to make changes to standard procedures by the Network, you could probably achieve this by altering WP_GET_SHIPPING_METHODS to look at all of the price types in the cart and then suppress any PAH shipping methods from being returned by the procedure. You could create a local table of price types that would cause this to happen.

    I was able to get this up and running in a slightly different scenario where we wanted to disable PAH for specific performances, and have not observed any performance issues.

    Hope that helps you out, I can't believe you have 2,000 modes of sale!

    Paul

    From: Tiffany Evans <bounce-tiffanyevans7088@tessituranetwork.com>
    Sent: 12/11/2013 11:39:42 AM

    Hi everyone,

    We are working to try and offer Print at Home Ticketing on our websites and I have a few questions after trying to figure out some challenges in regard to our Modes of Sale.

    Right now, we have 2 websites and only want to offer PAHT on one.

    One site is dedicated to selling tickets for local theatre companies who rent our space and the other site is for only our shows.   We are not set up like a consortium within Tessitura with different control groups, so our price types and Modes of sale are sometimes shared and sometimes different.  It has caused some confusion for me because now we have over 2K active Modes of Sale with various price types associated with them.  This is mainly because instead of using offers, the box office has set up promo codes in TR_WEB_SOURCE_NO, to trigger new modes of sale, often times with only one price type associated with that new mode of sale in order for the web to not show other prices.

    So far, everything is configured for PAHT the way I think its supposed to work, however, I am having a hard time determining how to limit PAHT by price types since the way to activate it as a choice on the web is by mapping the MOS to PAHT in  TX_MOS_SHIP_METHOD.  To make matters worse, both environments also SHARE some modes of sale, so if I turn it off on one site, it turns off on the other as well! 

    Does anyone have any guidance about how to NOT offer PAHT to specific price types?

    Example:  We don't want to offer students the choice to print tickets at home, but since the student price type is associated with every Mode of Sale, would I need to create an entirely new Mode of Sale to do this or is there an easier way to restrict this? 

    Thanks for any help! :)




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical 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!