Setting Up Pricing Matrices Using the PricingRulesImplementation

Attribute-based pricing requires a matrix. Within the matrix, the calculation can be simple or attribute-based. A charge matrix is also a Vlocity calculations matrix. You define the pricing action in the product specification. A pricing specification is the definition of the physical product.

A pricing matrix requires Omnistudio Data Mapper input and output bundles, a calculation matrix, and a calculation procedure. You associate rules, entity filters, and flows with the pricing matrix.

You create a Data Mapper of the type Extract(JSON). The extract object must be a line item, such as OpportunityLineItem, OrderItem, or QuoteLineItem. You must transform the Data Mapper data to match the pricing matrix column headers.

Next, you create a Data Mapper of the type Load(JSON). This Data Mapper uses generated values from the calculation procedure to input into the line item. For example, you could create a field named OneTimeTotal that appears as a nonrecurring charge on the line item. In Data Mapper, use the picklist to select the destination for the uploaded JSON values.

The following is a sample JSON input structure in which the ID equals the extracting object ID and the UnitPrice (also called the calculated price) is equal to the result output.

Example: JSON Input Structure

{
   "ID": null,
   "UnitPrice": null
}

A pricing matrix uses a calculation matrix. The headers in the calculation matrix correspond to product attribute values, for example, Speed and Brand. For more information about calculation matrices, see Calculation Matrices.

Attaching a product to a price or price matrix binds the columns.

Create the pricing matrix before creating the pricing component. Connect the pricing matrix to the pricing component and the pricing component to the product.

To set up a pricing matrix, you complete the following steps: