Felix is the Vlocity CPQ administrator, and he manages a very large product catalog with over 5 million SKUs. He needs to write a rule that will…

A Context Rule is the most appropriate and easiest solution for this scenario. Context Rules are designed to evaluate the circumstances of a transaction, such as the type of account placing an order. Felix can create a single Context Rule that checks if the Account.Type is 'Consumer'. This rule can then be referenced by pricing, availability, or other logic across the entire 5-million-SKU catalog. This approach is highly scalable and easy to maintain because the condition is defined in one place rather than being repeated for every product.

1. Salesforce Industries CPQ Developer Guide

"Context Rules": "Context rules determine the context for a transaction

which is then used to drive pricing and product eligibility. For example

a context rule can determine a user's location

a customer's account type

or the current season." This directly validates using a Context Rule to identify a "consumer account".

2. Salesforce Industries CPQ Developer Guide

"Rules in Industries CPQ": This document provides an overview of the different rule types

distinguishing the purpose of Context Rules (evaluating the transaction's situation) from Qualification Rules (product eligibility) and Calculation Procedures/Matrices (pricing).

3. Salesforce Industries CPQ Developer Guide

"Qualification Rules": "Qualification rules determine whether a customer is eligible for a promotion or a product." The documentation illustrates that these are typically tied to specific products or promotions

making them inefficient for a catalog-wide condition based on account type.