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?
Are your packages sold in a different mode of sale than non package tickets? And if so, is the pricing rule/pricing rule set added to that mode of sale?
Okay, so it sounds like we need to create a different pricing rule specific to packages? Our current rule does not switch the MOS, just the price type, and it is working for everything but packages.
If we set up a package pricing rule and continue using the current pricing rule, what will happen if a guest has a non package ticket and a package ticket in their cart when they log in? Will both rules fire?
Hi Brandi,
You can use pricing rules with packages. For example, you could set up a Product Only rule that’s triggered by the combination of a class package in the cart and a Member constituency on the constituent. The first thing to check for rule that isn’t working is that it has been added to a rule set and that that rule set has been associated with the Web MOS. Also, is it possible your members are shifted into a special member MOS on the web? If so, the pricing rule set would need to be associated with that MOS.
The one thing you can’t do is trigger pricing rules based on the component performances in a package.
Kevin Sheehan
Senior Technical Writer & Consultant
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Brandi Cline Sent: Wednesday, November 9, 2016 9:23 AM To: Kevin Sheehan <ksheehan@tessituranetwork.com> Subject: [Tessitura Ticketing Forum] Pricing Rule for Packages
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
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!