A good teacher rarely says “no” by slamming a door. They guide — a gentle nudge here, a clear boundary there — so the student naturally walks toward the right answer. Salesforce CPQ does the same thing for sales reps, and the feature that makes it possible is the product rule.
Let me show you how these quiet guardrails work.
Why product rules exist
Picture a rep configuring a bundle. They add a premium support plan but forget the base license it requires. Or they select two options that can’t coexist. Or they build something that’s technically possible but not something your company actually sells.
Without guardrails, that broken configuration sails straight into a quote — and the problem surfaces later, when it’s expensive to fix. Product rules catch these issues at configuration time, right there in the Quote Line Editor, while the rep can still correct course.
If you’ve met Salesforce validation rules before, the spirit is familiar: stop bad data before it’s saved. Product rules apply that same protective instinct to the act of configuring a bundle, but they can do more than just block — they can also guide and automate.
A product rule’s job is to make the correct configuration the easy one and the incorrect configuration impossible — so the rep is guided, not just scolded.
The four kinds of product rules
CPQ gives you four rule types. Each plays a different role, and the beginner’s task is simply to learn what each one is for.
Validation rules
A validation rule checks the configuration and, if something is wrong, blocks the rep with a message until they fix it. “Premium Support requires the Enterprise License.” It’s the strict but fair gatekeeper. The rep can’t move forward with an invalid combination, and the message tells them exactly why.
This is the rule type that most directly mirrors classic validation: a clear condition, a clear message, a clear stop.
Selection rules
A selection rule acts on the options themselves — it can automatically add, remove, enable, or disable options based on what the rep has chosen. Select the Enterprise plan, and the rule auto-adds the required base component. Choose Option A, and Option B becomes unavailable because the two conflict.
Selection rules are the most “helpful” of the four. Instead of waiting for the rep to make a mistake and then scolding them, they shape the available choices so the mistake never comes up.
Alert rules
An alert rule shows the rep a message without stopping them. “You’ve added hardware but no warranty — consider adding one.” It’s advisory. The rep stays in control and can ignore it, but they’ve been informed. Think of it as a nudge rather than a wall.
Alerts are perfect for upsell hints and soft reminders that shouldn’t block the deal.
Filter rules
A filter rule narrows what shows up when the rep searches for products to add — limiting the list to what’s relevant for this context. Instead of seeing the entire catalog, the rep sees only the products that make sense here. It reduces noise and steers the rep toward valid choices from the start.
How the pieces fit together
Each product rule is built from a few parts working in concert:
- Conditions — the “when” of the rule. They examine the configuration (which options are selected, what attribute values are set) and decide whether the rule should fire.
- Actions — the “then.” For validation rules, the action is the error message. For selection rules, it’s adding, removing, enabling, or disabling options.
- Error conditions and lookups — for more advanced cases, the logic that determines exactly when and how the rule applies, sometimes referencing data in lookup objects so you don’t hard-code every scenario.
When you’re starting out, don’t worry about mastering every advanced option. Focus on the shape: a rule watches the configuration (conditions) and responds (actions). That’s the whole pattern, repeated.
A beginner’s approach to building them
Start small and specific. Pick one real problem — say, “Support cannot be sold without a license” — and build a single validation rule for it. Test it in the Quote Line Editor. Watch it fire. Watch the message appear. That one working rule teaches you more than reading ten pages of documentation.
Then layer in the friendlier types: a selection rule to auto-add a required component, an alert to suggest a warranty. Step by step, your bundles go from “anything goes” to “guided and safe.”
I think of it the way I think of teaching scales before songs. You don’t hand a beginner a concerto. You give them one clean exercise, let them succeed, then build. Product rules reward exactly that patience.
Where product rules end and pricing begins
Notice that everything here is about configuration — what can be selected and combined. None of it changes the price. Deciding what something costs is a separate job, handled by price rules. They look similar at first glance, which is exactly why beginners confuse them — so that’s where we go next.
Your next step
Continue with the natural follow-on:
- CPQ Price Rules: Dynamic Pricing Without Chaos
- CPQ Products and Bundles
- Validation Rules for Beginners
Or browse the full CPQ series.