I'm trying to create a couple of pricing rules that fire based on quantity items purchased.
The Rules I've created are below in order of how I have them listed in the Rule Set:
Rule #1 -Switch to 3 week price type if purchasing 3 or more weeks of classes (any mix of classes - could be 3 weeks of one class, 2 weeks of one class and 1 week of another, or 1 week of 3 classes)
Rule #2 - Switch to 2 week price type if you purchase 2 weeks of classes (again, any mix of classes qualifies - could be 2 weeks of one class or 1 week of 2 different classes)
I tried using seat volume rules as suggested by the Pricing Rules Recipe Book, but they're not working. I think the problem is that the patron can cart 2 seats of one class (firing the 2 seat discount rule) or 1 seat in each of two classes (again firing the 2 seat discount rule) before they ever get to the third week/class. My understanding is that SLIs stopped being evaluated once they've triggered a rule.
Have you solved this problem? If yes, can you please share your genius with me? Thank you in advance!
I'm not sure how your performances are set up. But you might be running afoul of this:
I have Perf A, Perf B and Perf C. I want to trigger a discount if someone buys three tickets to any of them. That is, if you buy one ticket to Perf A and one ticket to Perf B and one ticket to Perf C it should trigger. Also, if I buy one ticket to Perf A and two tickets to Perf B. Or three tickets to Perf C.
This can't be done: there isn't a "seat per cart" rule, only a "seat per product" rule.
Now, if that's not your issue, then you can set the order by which pricing rules are evaluated, via the ranking in the Pricing Rule Set.
This is exactly the same problem I am having but based on performances. I too, followed the Price Rule Recipe and no luck. I actually have ticket in on it since, according to the book, it should work the way we think. If I get any help, I will let you know!
Again,if you are looking for a rule that will trigger on a sum of seats taken across multiple performances, there is not one.
Thanks Gawain. It's similar to what you describe. However, I think we've complicated the problem more by having a rule that triggers if they have 2 of any of the perfs in the cart. That rule is firing before they even have a chance to add the third perf. It could also be thought of as Build-Your-Own Flex packages, where there's one discount level for 2 perfs or seats and a better discount for 3+ perfs or seats.
Thanks Michelle!
I'm doing a product volume - similar to what Sara is doing but it is meant to trigger when the second performance is added to the cart. Built exactly like the recipe book says. However, it's triggering when the 1st production is added.
Interesting. And there are no possible competing rules? What version of Tessitura are you on?
There aren't any competing rules. We're pretty basic with what we do . We're on 14.1.7. It's so weird since it's something I have done TONS of times before.
Unknown said:Thanks Gawain. It's similar to what you describe. However, I think we've complicated the problem more by having a rule that triggers if they have 2 of any of the perfs in the cart. That rule is firing before they even have a chance to add the third perf.
Did you try changing the rank in the Pricing Rule Set?
Unknown said:It could also be thought of as Build-Your-Own Flex packages, where there's one discount level for 2 perfs or seats and a better discount for 3+ perfs or seats.
Incidentally, having a pricing rule that did product volume within a package was also something we hoped to do (we have different discounts for 4, 6 and 8+ performances in our "choose your own" flex packages), but again, pricing rules cannot do that currently.
We're in the middle of setting up a sale that has two rules, one product volume, one seat volume. Basically we give the discount to anyone who has either bought 2+ tickets to one show, or one ticket to 2+ shows. We do this every year, and it works fine, but we were doing a test yesterday and things looked odd. I'm going to find out how testing is going today. I hope a bug wasn't introduced in 14.1.
I was just looking at the Double Feature Deal recipe in the documentation and found a mistake in it. The qualifying number of products should be 2 to 999, not 1 to 999 as it currently says. If you haven't already, check that low end of your product range starts at 2, not 1.
And that was EXACTLY my issue. That's what I get for following directions and not thinking through the logic. Too many things happening at once. Thank you Kevin!
Hi Sara,
When you have sliding scale pricing rules you need to make sure that the Qualifying numbers don't overlap. So for two Product Volume rules, you would set up one as 2 to 2 products and the next as 3 to 3 products. Doing it this way assures that you can never qualify for the 2 product rule when you have 3 products in the cart. For a Seat Volume rule it would be similar, 2 to 2 seats for the first rule and 3 to 3 seats for the second rule.
Hopefully that helps you sort it out. If not, and you haven't already, I suggest opening a help ticket.