We're in the middle of converting now, and I'm still just a bit muddy about how dynamic pricing changes may work in v12.
Currently (v11), we layer incremental new price maps on top of the original price maps, and the new price maps have a category of "dynamic ticket price", so they are not the same category as the rest of the ticket price. This makes it necessary to tweak some of the out-of-the-box reports, but we've found it useful in tracking pricing changes, and generally, I've got my comfortable habits that fit around this practice.
Has anyone decided to use added price layers in v12 when you increase prices as opposed to using pricing events?
I understand pricing events allow you to see when a price was changed, even if it is changed multiple times, and count the number of changes and even with a little math determine the difference in price paid and the home price. So it sounds like the way to go. I just want to know if anyone is doing anything differently.
Hi Brian -
We moved to pricing events to take advantage of some of the cooked in behavior - in Tessitura and RMA. It definitely is a shift in setup and there is a learning curve, but once it is familiar it is pretty easy for people to set up.
The downside we're still struggling with a bit is lack of reporting - both for reporting sold and set up. As there aren't reports set up in Tessitura to easily calculate dynamic pricing we rely on RMA v4 pretty heavily for our sales piece of it. We haven't made a proofing report yet, but it's in our hopper.
- Heather