Pricing Conditions
Penny Perfect Pricing considers various pricing conditions when calculating prices. The system calculates the penny perfect prices based on flexible rules (set through pricing configuration), and customer and product pricing conditions, such as prices, discounts, and surcharges, to determine the prices in scenarios such as when creating an invoice for an on-demand sales order, calculation of presales order, or calculation of a return.
Required Editions
Available in: Lightning Experience Available in: Enterprise and Unlimited Editions that have Consumer Goods Cloud enabled |
Penny Perfect Pricing supports various condition types and uses search strategies and key types to find relevant pricing conditions. Each condition type is mapped to a pricing condition template. The pricing condition template points to a search strategy which in turn points to a key type and each key type points to one or multiple key attributes. This doesn’t apply for special pricing condition templates such as Max, Min, Sum, or Last Valid Value with no search strategy assigned and is used for calculations and to store intermediate results.
You can define pricing conditions for order items and the order header in these ways:
| DETERMINANT | ITEM CONDITIONS | HEADER CONDITIONS |
|---|---|---|
| Search Strategy | Base price and special price | Contractual and promotional discounts as percentage and amount |
| Exclusive conditions | Contractual, user-related, promotional, scale, and discretionary (manual) discounts | Cash discounts |
| User exits | Logistics discounts and surcharges | Discretionary (manual) discounts |
| Customer partner roles | Cross-products and grouping | Logistics discounts and surcharges |
| Customer and product hierarchy | Free items | Scale discounts by volume, value, and quantity |
| Customer sets | Tax | Tax |
| Promotions | Percentage Discounts, Amount per Unit, and Flat Rate | — |
- Integrate and Prepare Pricing Conditions
Typically, pricing conditions are stored in an Enterprise Resource Planning (ERP) system in different condition tables, such as Product key Customer key Combination of product, customer, and customer classification keys. Dynamically, for each key type or key combination a table is created. These pricing conditions are integrated from an ERP system to provide the same pricing behavior, to reuse condition data, and to handle complete calculated documents in Salesforce. - Pricing Condition Types
You can create different pricing conditions to define various pricing scenarios. - Scale Pricing Conditions
Use scales to define pricing conditions for different quantities or value of products in an order. You can add scale conditions to a calculation schema. Based on the condition, the system determines the scale of an order item or order header (for example, freight surcharges) and applies the corresponding rate. - Grouping
Penny Perfect Pricing supports grouping conditions in calculation. Grouping conditions consider only a subset of order items for a certain condition. For example, a group of beverages and candies with discounts for each. With grouping, you can make sure that the beverage condition is used for order items with the attribute beverage and the candy condition is used for order items with the candy attribute. - Free Items
Penny perfect pricing supports free-item conditions where customer is given free goods based on predefined conditions. Free-item conditions are considered during condition finding and calculation. - Header Conditions
Header conditions apply at the header level of an order. Header conditions are independent of individual line items. To determine a condition, the system considers a base value for all items. The condition can be a percentage or a flat rate. The result is calculated at the header level. - Hierarchies and Sets
Penny perfect pricing is data-intensive. As numerous condition types are defined at the product level or customer level, storing all conditions in a mobile device is impossible. So the condition information is stored in more general levels, specifically Customer Hierarchy, Product Hierarchy, or Customer Sets.
