I'm doing a little research, and what I'm seeing says it's not possible to use pricing rules with packages? Is this correct?
We currently have our classes set up to only be purchased as packages, but our Members aren't receiving their discount on the web. For non package tickets, that discount is applied by a pricing rule that fires based on their constituency. Is there a setting that we've missed that would make this fire for packages as well?
Hi Brandi,
Pricing rules don’t change the MOS, but sometimes on the web the package purchase path is set to change to a different MOS than the default web MOS. Also, sometimes a web site is set up to change to a special member MOS when a member logs in. Here’s a link to the topic that explains how all of that works in TNEW. So the first thing to do to troubleshoot your pricing rule is to confirm what MOS members are in when they are buying class packages. The pricing rule you use needs to be in a rule set associated with that MOS.
Getting back to your rule setup, you could use a single rule for member discounts on both performances and packages. You are allowed to have a mix of both chosen in the product picker on the rule setup. And the same rule can be applied to multiple products in the same order (as long as you DON’T check the Apply Rule Once Per Order Only box in the rule header). Sometimes packages use different price types than performances, though, as do classes, so make sure that the default price type on your class packages is included in the set of price types selected in the rule criteria. If you wanted to create a separate rule just for the class packages, that would be o.k. too, as multiple rules can be applied to the same order, you just can’t apply multiple rules to the same product in an order.
To sum up:
1. Make sure that the rule is in a rule set associated with the MOS used by members when purchasing class packages on the web.
2. Make sure that the class packages are selected in the product picker (or that the All Products box is checked) for the rule
3. Make sure that the default price type on the class packages is included in the set of qualifying price types for the rule
If following these suggestions doesn’t help you sort it out, I suggest opening a help ticket for further assistance. Good luck, and let us know how it goes!
Kevin Sheehan
Senior Technical Writer & Consultant
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com