Data selection criteria for pricing orders
Prices and price adjustments for the lines in an order are determined by the data that is passed to the Pricing Service.
The Pricing Service uses the following types of data to price orders:
- Pricing Date
For confirmed orders and quotes, a rule can be configured to determine whether the Pricing Service uses the current date or the order date for pricing orders. For draft orders, the Pricing Service uses the current date.
Note: If a custom pricing date is specified in an order or a quote, the custom pricing date overrides the pricing date that is applied to the order or the quote by a pricing date rule. - Address
The Pricing Service uses an address in the order to determine the prices for the items in the order. The address that is used is determined by the type of customer in the order.
- For B2B customers, the Sold To address in the order is used. If a Sold To address is not specified, the Bill To address is used.
- For all other customers, the Bill To address in the order is used.
- Customer Attributes
The Pricing Service uses the customer's attributes to determine the prices for the items in the order. Customer attributes include Vertical, Relationship Type, and Customer Level, and are tied to pricing rules and price lists. For example, if a customer in an order has Customer Level=Gold, the Pricing Service uses the price list and pricing rules that are assigned to Customer Level=Gold.
If a customer is not specified in the order, the Pricing Service will not consider customer attributes to determine pricing.
- Order Attributes
The Pricing Service uses the order attributes to determine the prices for the items in the order. You can use both application-provided as well as custom order attributes for filtering. These order attributes are tied to pricing rules and price lists. For example, if an order has an attribute Channel=web, the Pricing Service uses the price list and pricing rules that are assigned to Channel=web.
For additional information about the data selection criteria for pricing orders, see Javadoc.