Hi all,
We are in the final stages of implementing Dynamic Pricing and we're wondering what way is easiest to 1. understand 2. implement.
For the last several months we have just been adding an additonal price type but would prefer to edit the maps now (so its accessible to online bookers)
let me know your thoughts :)
thanks,
Robert
We layer on additional price maps when we raise prices. So the original price map does not change but a small price map is added on with the start date of the day of the price increase. So far we have only raised prices on shows. When a show needs to go down we offer more discounts instead of lowering the base price.
If you would like more information feel free to contact me.
Thanks,
Boann
Hi Robert,
We build a new price type as we find this is the easiest way reporting-wise to see how many tickets are sold at the changed price level.
Regarding our website and online patrons - We use TNEW and there is a system table called Price Type Alias. With our main productions the patron will always see a price type called ADULT. However in Tessitura we can end date the regular ADULT price type and change the active price type to something like ADULT1 but the Alias table will display this price type on our website still as ADULT.
Duane
Thanks guys, all feedback is welcome!
We are going to have a few trials on a test system next week sometime so hopefully we should be able to decide which method is beneficial to us.
Quick question - do any of your establishments use the RMA software to analise sales patterns & dynamic pricing monitoring?
R
We do not use the RMA software. At this point we have raised all adult prices for all performances of a production when the overall sales have reached a certain point, instead of raising one performance at a time.