I have talked myself into circles and maybe someone jump in and get me out.
These are message only rules.
I have 3 products, each with a distinct price type. No constituent rules are in play.
Primary product is X
Secondary product is Y
Third product is Z
Rule # 1: Product only -> 1 of 1 -> You can buy either Y or Z, but not without X in the cart, so I will offer you both when X goes into the cart.
Rule # 2: If you buy X & Y, I want to offer you Z, but only if Z is not already in the cart.
Rule # 2.1: If you buy X & Z, I want to offer you Y, but only if Y is not already in the cart.
Rule # 3: Product Only -> 3 of 3 -> When you buy X, Y & Z, fireworks go off & the choir sings
As you may have guessed, I have multiple rules firing when I only want one of these to fire at any given moment. The conflict is consistently with Rules 2 & 2.1. I feel like I do not have something setup correctly,and believe me, I have looked, deleted, looked, tried different rule types, looked, pulled out the bottle of bourbon, deleted & looked again.
It seems I need the rules to evaluate the entire cart contents to determine if there are only 2 or 3 products in the cart. If only 2, then fire either rule 2 or 2.1 based upon the contents. If 3 products are in the cart, only fire rule # 3.
Special note: we could either add either product Y or product Z first, you know, just to make it fun.
Can I do this or is it too complex?
Winner, winner, chicken dinner. It’s all about the ability to rank.
Note heeded about the SLI disqualification. Not a problem now as we are just trying to get our feet wet with pricing rules, this is a good place to start.
Thanks Kevin!
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Kevin Sheehan Sent: Wednesday, February 08, 2017 11:03 AM To: Dot Krebs <dkrebs@actorstheatre.org> Subject: RE: [Tessitura Ticketing Forum] Pricing Rules - If, then, else
Hi Dot,
You can’t do what you want with Message Only rules, because they don’t disqualify SLIs from the application of other rules (which is why you can’t rank them in rule sets).
However, you can accomplish what you want with Price Change rules, as you can rank those kinds of rules, and if you don’t want them to actually apply a discount, you just set the discount to respect the minimum price.
Once you set them all as Price Change Rules, rank Rule 1 lowest, then Rule 2.1 and 2.2 (the order of 2.1 and 2.2 relative to each other doesn’t matter), and then Rule 3 as the highest ranking rule. This also means that it doesn’t matter the order in which you add X, Y, or Z; the rules should fire correctly regardless.
Keep in mind that setting these up as Price Change rules means that these SLIs would be disqualified from any other unrelated, lower ranked Price Change or Price Type Change rules, which may not be a problem if there aren’t any such rules, but I wanted to bring up just in case.
Let us know if this solution works out for you,
Kevin Sheehan
Senior Technical Writer & Consultant
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com
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!