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,
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!
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?