Learn Salesforce CPQ: Bundles, Product Rules, Pricing and Subscriptions, Hands-On

To learn Salesforce CPQ, start with products, price books and bundles (features and options), then learn the Quote Line Editor, configuration attributes, product rules and option constraints, and finish with subscription, evergreen, MDQ and usage-based products. CPQ in the Wild covers that path on real-world scenarios, built live: I configure each bundle and rule, generate the quote, break it and fix it.

What Salesforce CPQ is and where you use it

Salesforce CPQ (Configure, Price, Quote) is a managed package that sits on top of opportunities and quotes. It answers three questions every sales team has:

• Configure. Which products can be sold together? Which options are required, optional or incompatible?
• Price. What's the price after volume discounts, partner discounts, bundle pricing and term-based subscription pricing?
• Quote. How do you turn that into a quote document, an order and, eventually, a contract that renews?

On real projects, CPQ work includes designing the product catalogue and bundles, writing product and price rules, setting up subscription and renewal behaviour, building quote templates and approvals, and untangling what the last consultant built.

One honest note: Salesforce is also investing in a newer, platform-native Revenue Cloud. Many orgs run Salesforce CPQ today and will for years, which is what this course teaches. Check which product a client is on before scoping work.

Prerequisites

• Strong admin skills. Objects, relationships, page layouts, validation rules and the sharing model. CPQ is configuration on top of those. Start with the admin guide.
• Understanding of the sales process. Opportunities, products, price books and quotes in standard Salesforce.
• Basic Flow. Useful for automation around quotes and orders. See Salesforce Flows.
• No Apex required to start.

What you'll be able to configure afterwards

• Bundles with features, required and optional options, and nested configuration
• Configuration attributes, and knowing when to use configuration, inline or global attributes
• Product rules (validation, alert, selection and filter) and option constraints
• A Quote Line Editor experience that guides reps instead of confusing them
• Subscription products with correct term and proration behaviour
• Evergreen subscriptions, MDQ (segmented) products and usage-based products

A worked scenario: a laptop bundle that sells itself correctly

Requirement: field engineers buy a "Field Laptop" bundle. Every laptop needs exactly one warranty, either standard or three-year. If the rep picks the extended battery, the high-capacity charger must be added automatically.

Here's how I'd configure it.

1. Bundle and features. Create the Field Laptop product and three features: Hardware, Warranty and Accessories. Features group options on the configuration page, and each feature can enforce minimum and maximum option counts.
2. Warranty: exactly one. Set the Warranty feature's minimum and maximum option count to 1. The rep can't save the bundle without a warranty, or with two.
3. Warranties exclude each other. An option constraint of type Exclusion between the standard and three-year warranty options makes the conflict visible on the configuration page. With the feature count above, this is belt and braces. In larger bundles, constraints carry the logic on their own.
4. Battery adds charger. This needs a selection product rule. Its error condition tests whether the extended battery option is selected. Its action adds the high-capacity charger option. Set the evaluation event so the rule runs while the rep configures the bundle, not only on save.
5. Test like a rep. Configure the bundle, deselect the warranty, add the battery, remove the battery and save. Then amend the resulting contract and check that the bundle still behaves.

The lesson I keep repeating in the course: pick the simplest mechanism that works. Feature counts before constraints, constraints before product rules, and product rules before custom code.

Common mistakes beginners make

1. Using product rules for pricing. Product rules control configuration. Prices belong in price rules, discount schedules or the pricing fields on the product.
2. Bundles nested too deeply. Every level makes configuration slower and amendments harder. Flatten where you can.
3. Writing Apex triggers that change price fields on quote lines. The CPQ calculator owns those fields and will overwrite your changes. Use price rules, or the Quote Calculator Plugin when price rules can't express the logic.
4. Ignoring evaluation order. Several price rules touching the same field produce different results depending on order. Set it deliberately.
5. Testing only new quotes. Amendments and renewals are where subscription bugs show up. Test the whole lifecycle.
6. Misunderstanding subscription terms. Know how subscription term, start and end dates and proration interact before you configure renewal pricing.
7. Building rules with no naming convention. Six months later, nobody can tell what "Rule 14" does.

How CPQ connects to the other topics

• CPQ is built on admin skills, so the Salesforce admin guide and the admin roadmap come first.
• Automation around quotes, orders and approvals uses Salesforce Flows.
• Advanced customisation and integrations with ERP and billing systems need Apex and, sometimes, Salesforce integration.
• The full career path, including what to learn before and after this course, is the Salesforce CPQ consultant roadmap.

Who should skip this

• Skip it if you're new to Salesforce. Learn administration first, or CPQ concepts won't have anything to attach to.
• Skip it if your client or employer is implementing the newer Revenue Cloud rather than Salesforce CPQ. The concepts transfer, but the configuration doesn't.
• Skip the bundle basics if you already configure CPQ every day. The subscription, evergreen, MDQ and usage-based modules are likely the most useful part for you.

There are no refunds. The free admin course is taught the same way, so use it to judge the teaching before you subscribe.