Hello,
Short of using an Exclusion List that would need to be updated and input every day, does anyone know of a way to limit a Pricing Rule to be used once per CONSTITUENT and NOT just once per Order?
Thanks!
Hi Jolene,
I don't think so - I had a similar issue where that would have been useful. But I think the exclusion list should work ok if you have a daily (or more frequent) generating of the Generate a List report. That would remove the need to manually update the list?
We are experiencing the same issues, but what would the exclusion list do? Could you please go into more detail of how to actually exclude people from the rule using the list?
Angela:
An exclusion list is just a regular list, generated through List Manager or a report, using criteria to find constituents who have already purchased the qualifying event(s) for the pricing rule. You then add it to the Constituent Criteria using the Exclusion List parameter.
When a transaction that qualifies for the pricing rule is added to the constituent's order, the pricing rule is evaluated, but as part of processing, it checks to see if the constituent in question is on the list; if they are, they're prevented from receiving the benefit of the rule again. (Note that their being on an exclusion list for this specific rule does not prevent them from qualifying for other pricing rules that are in the same rule set, if the exclusion list is not also applied to those.)
The caveat is that lists used in Pricing Rules are not (for performance reasons) dynamically regenerated when invoked by a rule. So you would need to have the Generate List utility scheduled at least daily to recreate the list in order to add the most recent constituents to it.
This is great! THANK YOU!