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.
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.
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.