(Cross-posted to Administration & IT)
So, here's what we'd like to do. Normally we sell packages to provide discounts for buying multiple performances at a time. We have three packages for this each season: 4+, 6+ and 8+, with increasing discounts. Also, if you buy at least one package, any single tickets you purchase from then on out also have a discount.
We're looking at moving to pricing rules, but we have a problem: by default the pricing rules only look at the number of performances, so someone could buy one ticket to seven shows and six tickets to the eighth, and all the tickets would be at the highest discount. Now, with product volume pricing rules you can select "Apply discount to lowest common number of seats." So far so good. But then there is this snippet:
Note: SLIs that are not repriced but are used as qualifiers in Add On and Buy One Get One rules, SLIs that qualified for a rule but were not repriced because they were past the seat max for the rule, and SLIs that did not qualify for a rule but are for the same product as SLIs that did qualify for the rule are marked as affected by a rule and are not considered when lower ranked rules in the set are evaluated against the order.
Now, this is not an "Add on" or "Buy One Get One" rule, but it appears that slis that were not changed because of the "Apply discount to lowest common number of seats" restriction are still being marked and then ignored by further rules, which is very frustrating. Has anyone figured out a way to work around this?
Hi Gawain,
The behavior you're seeing, which described in the last part of that sentence ("SLIs that did not qualify for a rule but are for the same product as SLIs that did qualify for the rule..."), applies to all rule types. There is not a way to work around it within the same order in v15. Some other workarounds I can think of:
- When someone buys the "pricing rule package," mark their constituent account with a constituency or attribute. Use that marker as a qualifier for a pricing rule on the single tickets, which they would need to purchase in a subsequent order. (Your wording of "any single tickets you purchase from then on out also have a discount" makes me wonder if you are already planning on doing this.)
- Go back to using packages, and use pricing rules to discount the single tickets based on the presence of the package.
I'm pleased to report this is changing in v16. For all rule types, any seats that aren't repriced by the rule and aren't qualifiers can be affected by subsequent rules. When you have the "lowest common number of seats" checkbox checked, the unaffected seats are no longer "qualifiers" and can be affected by other rules.
Okay, thanks: sounds like we will be going back to our old package-based system, but excited to hear that we might be able to revisit this next year.