Price Optimization

Hi All

 

Increasingly we are being asked to implement price optimization on our performances here at Sydney Opera House.

 

This is done by adding a price Increment price map to each pricetype  

 

Often the changes occur on all performances in a Season and in these cases we administer the updates by Season Manager. However, more frequently we are being asked to make these price changes on a performance level. In these cases we have been going into each performance and making the changes in Ticketing setup, performance by performance.

 

Does anyone know of a quicker and more time effective way to make these changes

 

Many Thanks

 

Justin Griffiths
Ticketing System Manager

T 02 9250 7731  F 02 9241 6410

 

Sydney Opera House Bennelong Point

GPO Box 4274 Sydney NSW 2001 AUSTRALIA

Parents
  • Clean Clean false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4

    Hi Nicole,

    I’ve done it both ways, but was told by very reliable source, not to change price maps. It would make some situations a lot easier, and reduce the numbers of maps, to change the map for our price increases. As a very reliable source yourself, any problems this will cause with reporting?

    Thanks.

    Ray

    From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Nicole Keating
    Sent: Thursday, March 01, 2012 5:25 PM
    To: rbernard@smm.org
    Subject: RE: [Tessitura Ticketing Forum] Price Optimization

     

    Have you ever considered just changing the prices on the price map from Facility Mgr instead of creating a new Price Map?  It really depends on how you are handling the changes, but that way would work as well.

     

    Nicole

     

    From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Justin Griffiths
    Sent: Thursday, March 01, 2012 6:10 PM
    To: Nicole Keating
    Subject: [Tessitura Ticketing Forum] Price Optimization

     

    Hi All

     

    Increasingly we are being asked to implement price optimization on our performances here at Sydney Opera House.

     

    This is done by adding a price Increment price map to each pricetype  

     

    Often the changes occur on all performances in a Season and in these cases we administer the updates by Season Manager. However, more frequently we are being asked to make these price changes on a performance level. In these cases we have been going into each performance and making the changes in Ticketing setup, performance by performance.

     

    Does anyone know of a quicker and more time effective way to make these changes

     

    Many Thanks

     

    Justin Griffiths
    Ticketing System Manager

    T 02 9250 7731  F 02 9241 6410

     

    Sydney Opera House Bennelong Point

    GPO Box 4274 Sydney NSW 2001 AUSTRALIA




    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!




    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!

  • I wish it was possible to add price maps using Season Manager. As Skypp mentions, if you're layering the new price maps on top of the old, you'll have to add the original as well at the same time you add the new one. We find it useful to always keep the original base price map on each perf. We've got some custom reporting that uses that to report on dynamic pricing. I'm currently working on a script to automatically add price maps based on local rules. 

    A word of warning about layering price maps though - you'll want to check any reports you run to make sure they are still counting seats correctly. Some reports will count each price map as a seat sold, so you could easily end up with some inflated numbers.

  • Former Member
    Former Member $organization in reply to Brian Graham

    True, we make sure to only have one "ticket price" map type and only count "ticket price" when counting number of tickets.  But usually I just change my old "ticket price" price map with the new one so that excanges honor the new price.

Reply Children
No Data