Tier Validation in Pricing Matrices

Starting in Oracle CPQ 26B, contiguous range validation is now enforced for pricing matrices, just as in price models. This ensures that:

  • Tier ranges in pricing matrices are contiguous and nonoverlapping for a given effective date and pricing key (e.g., product, charge type, price type, periodicity).
  • This validation guarantees pricing completeness and consistency, supporting advanced tier and volume pricing.
  • It aligns tiering rules, validations, and outcomes across both price models and matrices, simplifying pricing administration and ensuring consistency.

Business benefits of this feature:

  • Reduces Pricing Errors: Prevents gaps, overlaps, or invalid tier definitions in pricing matrices, ensuring accurate price calculations for volume-based and tiered deals.

  • Expands Pricing Flexibility Without Customization: Enables pricing teams to use standard, supported capabilities for complex tiered pricing scenarios, such as attribute-driven volume breaks, reducing the need for custom development.

Steps to enable and configure

Add Quantity Above & Quantity To fields an Attribute-based Charge Template

Complete the following steps to add quantity above and quantity fields to an Attribute-based Charge type Pricing Matrix Template:

  1. Navigate to CPQ Admin > Prices > Pricing Matrix Templates.
  2. Click on the applicable Attribute-based Charge type Pricing Matrix Template.
  3. Select Add Quantity Above/To from the Input Columns Actions menu.

Add Quantity Above/To Columns

Tips and considerations

  • Oracle CPQ 26B renames the tier and volume "Quantity From" pricing field to "Quantity Above". The change is to make it clear that the lower bound value only applies when the quantity is greater than this value. The change is only applicable to the UI. It does not apply to existing  REST APIs and CSV files for upload and download.
  • Beginning in Oracle CPQ 26B, matrix grid .csv files will support Quantity Above and Quantity To fields for tier pricing. During uploads, the  Quantity To (_matrix_quantityTo) field is ignored and the Quantity Above (_matrix_quantityAbove) field is used to populate the next sequential Quantity To  (_matrix_quantityTo) field.