Assigning a pricing rule or a coupon to customer attributes
You can assign a pricing rule or a coupon to one or more sets of customer attributes, such as vertical, relationship type, customer level, and region.
Vertical indicates the industry that a customer belongs to, such as Education or Government. Relationship type indicates whether a customer is a reseller, distributor, a contract manufacturer, and so on. Customer level indicates tiered values that represent a customer’s status, such as Gold, Platinum, or Silver. Region indicates a defined geographic territory.
For example, you can assign a pricing rule or a coupon as follows:
- If you want to assign a pricing rule or coupon to customers in the Boston area, you can assign it to attribute region=Boston.
- If you want to assign a pricing rule or coupon to customers that serve the educational market, you can assign it to attribute vertical=Education.
- If you want to assign a pricing rule or coupon to gold-level customers, you can assign it to attribute customer level=Gold.
- If you want to assign a pricing rule or coupon to customers who are resellers, you can assign it to attribute relationship type=Reseller.
You can also assign a pricing rule or coupon to several customer attributes, such as all gold-level customers in the Boston area who are serving the educational market. For example, you can assign a pricing rule to attributes region=Boston, vertical=Education, and customer level=Gold.
The behavior of assigning pricing rules and coupons to customer attributes is similar to that of assigning price lists to customer attributes. The best matched region does not make sense in the case of rules; all the rules that are applicable for the US region are also applicable for the East Coast region or West Coast region.
Generally, you assign rules to specific regions rather than hierarchically defining rules that are based on regions. The assignment of customer attributes to a pricing rule or coupon also happens at the Enterprise level.
Given a customer, pricing rules that are assigned explicitly to that customer and the pricing rules assigned based on customer attributes are used. There is no precedence as there is in pricing rule selection.
If multiple pricing rules are applicable because of assignment at different levels and only one of them has to be applied, then the mutual exclusivity feature must be used.