Scenario SummaryUniversal Containers sells a bundle “Corporate IT Solutions.”
Inside it is a product option: Hardware Firewall.
Requirement:
If the customer previously purchased that Hardware Firewall (historical purchase),
Then hide the product option inside the bundle during configuration.
This is a Configuration Rule
Using Selection/Filter logic to hide options
The rule must trigger as soon as the bundle loads, because the product option must be hidden before the user interacts with the bundle.
What type of Product Rule?Which Evaluation Event is Correct?Salesforce CPQ Product Rule Evaluation Events:
Event
When it Fires
Typical Use
Load
When the configuration page loads the first time
Hide/show options, preselect options, set initial values
Edit
On any user modification
Rerun rules based on changes
Load and Edit
Both events above
When both initial setup and change handling are required
Save
When the quote line editor is saved
Validation rules that block save
We need the product option to be hidden immediately when configuring the bundle.
It is not dependent on user edits.
It uses historical purchase data (Opportunity Product / Asset / Subscriptions).
In this requirementTherefore, the rule should fire at initial load only, not waiting for user interaction.
Always → not a valid Product Rule Event type in CPQ.
Save → too late; user would see the option before it's hidden.
Load and Edit → unnecessary; we do not need edits to trigger this rule.
Edit → would fail because hiding must occur before user interaction.
Why Not the Others?Salesforce CPQ Documentation AlignmentCPQ Product Rules documentation states:
Use Load when you want the rule to evaluate immediately when the configurator opens, typically for hiding, filtering, or preselecting options.
This matches the required behavior perfectly.