Pricing Rule at Constituent Level

We are just starting to investigate Pricing Rules, and I have (I think) a basic question:

In regards to Pricing Rules are they only applied at the order level?

For example during web sales, if we want to limit a buy one; get one free ticket offer to one transaction per patron, can you use pricing rules for that? Can Tess somehow "mark" that this patron has already "redeemed" a buy one; get one promotion and not allow another transaction with that rule to go thru?

Or if they re-login and start a new transaction on the web, will the pricing rule be applied again to their 2nd transaction?

Thank you in advance,

Jessica

Parents
  • While rules are order-based, they do allow for constituent criteria, and one method of applying something like this is to use an exclusion list. That is, create a list of all the constituents who have already received the results of the pricing rule, then add a Constituent Criteria to the rule with the type of “Exclusion List” and apply the list of purchasers.

    Since pricing rules don’t dynamically regenerate lists, you’d need to schedule the Generate List utility to refresh the constituents on it every so often, but that would prevent people from double (or triple)-dipping.

     

Reply
  • While rules are order-based, they do allow for constituent criteria, and one method of applying something like this is to use an exclusion list. That is, create a list of all the constituents who have already received the results of the pricing rule, then add a Constituent Criteria to the rule with the type of “Exclusion List” and apply the list of purchasers.

    Since pricing rules don’t dynamically regenerate lists, you’d need to schedule the Generate List utility to refresh the constituents on it every so often, but that would prevent people from double (or triple)-dipping.

     

Children
No Data