Purchase Rules
Purchase Rules is a declarative rule within the Salesforce platform that applies business logic to records based on field values and conditions.
Definition
Purchase Rules is a declarative rule within the Salesforce platform that applies business logic to records based on field values and conditions. When criteria are satisfied, the rule performs its configured actions automatically, ensuring consistent enforcement of business policies.
In plain English
“Here's a simple way to think about it: Purchase Rules enforce buying constraints inside B2B Commerce. Account-specific catalogs, contract minimums, approval thresholds - the rules that turn a B2B storefront into something the contract actually permits.”
Worked example
Greenfield Industrial Supply runs a B2B Commerce storefront for 400 contracted distributors, each with negotiated pricing tiers and minimum-order quantities. Purchase Rules enforce the contract terms in the storefront itself: a distributor on the Silver tier can't see Gold-tier SKUs, a 50-unit minimum is checked at cart, and orders over $25k route to an approval workflow before submission. Without Purchase Rules, distributors would have to call sales to confirm "am I allowed to buy this at that price?"; with them, the storefront mirrors what each distributor's contract actually permits, and only valid orders make it through checkout.
Why Purchase Rules enforce buying constraints inside B2B Commerce
B2B commerce isn't like consumer commerce - buyers operate under contracts, account-level pricing, quantity minimums, and approval thresholds that constrain what they can purchase from your storefront. Purchase Rules are the declarative layer that enforces those constraints inside Salesforce B2B Commerce. Define rules tied to product, account, or buyer-type criteria, and the cart, checkout, and approval flows respect them automatically.
The reason this is administrator territory rather than something the storefront's UX handles is that constraints are most reliable when enforced in the data layer. A storefront can hide products from a buyer; only a rule can prevent that buyer from circumventing the hide and adding the product through an API or shared link. Build Purchase Rules during the storefront launch as part of the contract data model, and revisit them whenever the contract terms change for any account segment.
How to set up Purchase Rules
Purchase Rules in Salesforce CPQ enforce buying constraints — "can't sell SKU A without SKU B," "max 5 units of SKU C per quote," "discount cap depends on tier." They prevent invalid quote configurations at quote time. Configured per-rule with Condition + Action; CPQ evaluates rules during quote line edits.
- Confirm Salesforce CPQ is installed
Setup → Installed Packages → look for Salesforce CPQ. Without it, Purchase Rules aren't available.
- Open the CPQ App → Purchase Rules tab (or App Launcher)
App Launcher → Purchase Rules. Purchase Rules are records, not Setup metadata.
- Click New Purchase Rule
Top-right of the list.
- Set Rule Name, Description, and Active
Active rules fire on quote line evaluation; inactive ones are stored but don't fire.
- Set Type (Validation / Selection / Alert)
Validation: blocks save if violated. Selection: auto-adds / auto-removes products. Alert: warns user but allows save.
- Build Conditions (which quote lines trigger the rule)
Field-Operator-Value rows. Multiple conditions combine via AND/OR logic.
- Build Actions (what the rule does when conditions match)
Validation: error message + line. Selection: add / remove products. Alert: warning text.
- Save → Activate
Rule fires on next quote line evaluation.
Validation / Selection / Alert. Locked at creation.
Triggering criteria.
What happens on match.
On/off.
- Purchase Rules fire on every quote line evaluation. Heavy rule chains slow quote configuration — keep rules lean.
- Validation rules block save. A user hitting a Validation rule can't proceed until they fix the violation. Use sparingly; prefer Alert + manager override for soft constraints.
- Selection rules auto-modify the quote. Auto-added products surprise users — pair with clear UI messaging ("Adding required Service product because Hardware was selected").
How organizations use Purchase Rules
Account-specific catalogs prevent cross-region purchasing; partners only see products their contract permits.
Quantity minimums enforced via Purchase Rules; orders below threshold blocked at cart, not at processing.
Approval thresholds for high-value orders; auto-routing to commercial managers preserves human-in-loop where needed.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What best describes the purpose of Purchase Rules in Salesforce?
Q2. What happens when Purchase Rules data is not maintained properly in Salesforce?
Q3. Who would typically configure or interact with Purchase Rules?
Discussion
Loading discussion…