Tiered pricing sublines

Tiered pricing enables you to assign different prices or discounts based on product volume. Tiered pricing sublines have two predefined columns: Range and Value.

Use tiered pricing when you need to differentiate a value for a single line and any other value. Common use cases include:

• Different price discount based on the total quantity of product on the parent line
• Different price based on the total number of product units on the parent line
• Different price discount based on the total extended revenue on this document
• Different price based on the total extended revenue on this document
• Different annual rebate based on the total number of product units purchased over the next 12 months
• Different annual rebate based on the total revenue of this product purchased over the next 12 months

To fit these use cases, you can add fields to the tiered sublines and change the labels of existing fields.

Prerequisites

Before configuring this feature, make sure that the following fields are visible and editable:

• Product Selector Configuration object
  • Add/Delete Tiered Pricing Sublines checkbox
  • Tiered Pricing Comparator picklist
• Subline Column object
  • Salesforce Field
  • Read-Only Condition Field
  • Column Name Override
  • Label Override
  • Number of Decimals
  • Field Order
  • On Change Action
  • Visibly By Default
  • Line Field to Define Visible Condition

If the fields are not visible or editable, confirm that they are added to the object's page layout and are visible in the user's profile. For detailed instructions on how to add fields and check for visibility, refer to Make fields visible or editable.

Configure tiered pricing functionality

1. From the Lightning App Launcher, go to the appropriate Product Selector Configuration.
2. On the Details tab, select the Add/Delete Tiered Pricing Sublines checkbox if you want to enable adding or deleting tiered sublines from the Edit Lines modal.
3. On the Details tab, in the Tiered Pricing Comparator dropdown list, select the desired combination of lower and upper bound comparators.

   • Select Lower Bound > & <= Upper Bound to include the discrete quantity breakpoint values for volume discounts in the next tier below the pricing tier where the lower bound is specified.

   • Select Lower Bound >= & < Upper Bound to include the discrete quantity breakpoint values in the range of the pricing tier itself.

     Tip

     For example, assume you sell individual units but want to offer progressive tiered pricing discounts if you sell one carton, then again at two cartons, and so on. To accomplish this, choose Lower Bound >= & < Upper Bound.

4. In the Product Selector Configuration, on the Related tab, in the Subline Columns section, select an existing subline column you want to edit, or create a new one.
   Note

   The Tiered Pricing feature has two pre-defined columns: Range and Value.

5. In the Edit Subline Column dialog for the Range and Value columns:
   1. Leave the Salesforce Field empty.
   2. In the Number of Decimals field, specify the desired number of decimals shown. The default value is 2.
   3. In the Label Override field, enter a column label that will be visible on the line items list.
   4. Enter Field Order to define the order of columns.
   5. In the On Change Action dropdown list:
      • Select Salesforce Formula Evaluation to trigger formula recalculation once the changes in the Range or Value columns are made. In this case, if you have created and configured any Formula fields for a subline object, they will be updated before the changes in the subline columns are saved.
      • Select None if you do not want to trigger any actions.
   6. Select Save.

Configure custom tiered pricing subline columns

You can also configure a subline column for a custom field on the Subline object.

1. In the Product Selector Configuration, on the Related tab, in the Subline Columns section, select New.
2. In the Salesforce Field field, specify the API name of a Subline field.
3. In the Label Override field, optionally specify a column label that should be shown instead of the default.
4. In the Column Name Override, optionally specify the Custom Label to use as a column label.
5. Specify Field Order to define the order of columns.
6. In the Read-Only Condition Field, optionally specify the API name of a Boolean field on Subline object, to define when this column should be read-only.
7. In the Line Field to Define Visible Condition, optionally specify the API name of a Boolean field on parent Line object, to define when this column should be visible.
8. Clear the Visible By Default flag if you do not want to show this column.
9. Select Save.