Hello Tessi folks, I'm wracking my brain trying to create a Pricing Rule that does what I'm trying to achieve. I've tried a few different permutations (from both the documentation and the recipe book) but to no avail. The scenario is:
I can make the rules work if all three tickets are for the same performance.
Is this possible? Can this also work with packages?
Has anyone else done this sort of offer?
Martin
Pro-tip: never come up with a discount idea, to then implement it with Pricing Rules. That way lies only sadness.
I believe we had a similar discount: buy at least four tickets across any selected shows, and all tickets are discounted to $25. Can't be done. What you would need is a "seat per cart" rule, which doesn't exist, but which I should file an enhancement request for some day.
Speaking of enhancements, and maybe this is way too complicated to be practical, but I wondered if it might be possible to have a List Manager style "manual edit" for Pricing Rules. That would still require someone with SQL knowledge, and probably pretty decent knowledge as opposed to the sort of intro/learning knowledge with which you can get away in terms of modifying List Manager pulls to do what you need.
But if the queries and things do not get TOO complicated, it might be useful for all of these promos that the Marketing-types invent and then send out assuming they can be done. I am sure there could be additional Pricing Rule options that would cover some more things, but just like List Manager elements, you are going to end up with weird things specific to each organization.
Just a thought I had; it has not gotten relevant enough to our organization so I have not even really thought about submitting it yet, and I was curious if others had had the same thought.
I'm guessing that the sticking point with pricing rules is performance: they need to execute under the highest stress that the Tessitura database faces. Even a slightly inefficient manual query could take down a significant onsale.
Definitely something that went through my mind, as an inefficient List Manager element is only tied to the ticket history tables and not the active sales tables (or active web sales tables).
Then again, TNEW allows freely for someone to create highly inefficient up-sell customizations for the precart and other such pages, leaving that in the hands of the users. So maybe here, too? Knowing that most would either know what they are doing when they start to mess with it and/or reach out to Tessitura Consulting for their weird and complex ones?
Again, just throwing this stuff out there.