Hello,
We have pricing rules set up to discount exhibition tickets when two exhibitions are purchased. The rules are set up to apply to equivalent tickets, i.e. Adult - Adult, Concession - Concession, Member - Member, etc. We have a pricing rule set up for each price type rather than using the discount % as we find it more exact.
We're finding that when multiple price types are added to the cart, the order will only apply one rule and the system indicates that the additional price type qualifies for the price rule already added even though the price type is not applicable in that rule. As a result, the pricing rule for the secondary price type won't fire.
For example
1 adult ticket for Exhibition A and 1 adult ticket for Exhibition B are added to the order. Pricing rule for adult tickets is applied correctly.
1 child ticket for Exhibition A and 1 child ticket for Exhibition B are added to the same order. No pricing rule fires. Subline item identifies child Exhibition ticket A as qualifying for the adult pricing rule.
If I remove one of the adult tickets the adult pricing rule is removed and the child pricing rule fires. If I add the adult ticket back in the child pricing rule is removed and the adult pricing rule reapplies.
I guess this is a long winded way of asking, will orders only accept one pricing rule at a time?
Many Thanks,
Emily
Yes, v14.1 will include a pricing rule enhancement that allows you to map price type changes, so you could have a single rule that changes Adult and Child to Adult Discount and Child Discount.
And to clarify the current limitation you are encountering about multiple rules…only one rule can be applied per product in an order (technically it’s not per line item, as the sub line items are grouped by product across all line items in an order when evaluated for pricing. SLIs that did not qualify for a rule but are for the same product as SLIs that did qualify for the rule are marked with a Q and are not considered by lower ranked rules. So in Emily’s example, only one rule can be applied to Exhibit A SLIs in an order, the Adult rule or the Child rule, and which one is applied depends on which one is ranked higher in the rule set.
Changing this behavior so that the non-qualifying SLIs don’t get marked with a Q is on our radar for potential future enhancements, though such an enhancement is not currently in development. Price type mapping should resolve the most common reason why people are wanting to apply multiple pricing rules to the same product, though, shrinking the range of scenarios when multiple rules per product is needed.
Kevin Sheehan
Senior Technical Writer & Consultant
Tessitura Network
+1 888 643 5778 x 329
ksheehan@tessituranetwork.com