Before anyone can quote anything, the system has to know what’s for sale. That sounds obvious, but it’s where most CPQ projects either find their footing or quietly start to wobble. A quote is only as trustworthy as the catalog behind it.
So let’s build that foundation together, one piece at a time.
Products: the smallest unit of “what you sell”
In CPQ, a product is a single thing you offer — a license, a device, a service, a support tier. Each product is a record, and that record carries the details CPQ needs: a name, a product code, whether it’s a one-time charge or recurring, and how it connects to pricing.
Products live alongside price books, which hold the list prices. A product can appear in more than one price book — for example, a standard price book and a special partner price book — with different list prices in each. Keep that pairing in mind: the product describes what it is, the price book entry describes what it costs in a given context.
Most catalogs have many simple products like this. They’re the building blocks. The interesting part begins when you start combining them.
The product catalog as the foundation
The full collection of your products, price books, and the relationships between them is your product catalog. It’s the single source of truth for what can legitimately appear on a quote.
When the catalog is clean — clear names, correct prices, sensible structure — quoting feels effortless. When it’s messy, every quote inherits that mess. I’ve seen teams spend weeks debugging “pricing problems” that were really catalog problems all along.
If you want the broader, platform-level view of catalog design, I cover it in The Product Catalog Foundation. The principle is the same everywhere: get the catalog right first, and everything downstream gets easier.
A bundle is not a discount or a marketing label — it’s a structured product that tells CPQ which pieces belong together and which choices a rep is allowed to make.
Bundles: a parent with options
Here’s where CPQ earns its keep. A bundle is a product that contains other products. Think of a laptop package: the laptop is the parent, and the warranty, carrying case, and software add-ons are options underneath it.
In CPQ terms, a bundle is built from:
- A parent product — the bundle itself, the thing the rep selects.
- Product options — the child products that can be included.
- Features — groupings that organize options into logical sections, like “Hardware,” “Support,” and “Software,” often with rules like pick exactly one or pick at least one.
When a rep adds the parent to a quote, CPQ opens the bundle so they can choose options. Features keep that choice organized and bounded. Instead of scrolling a flat list of hundreds of items, the rep sees a clean, guided set of decisions.
This is the heart of the “Configure” in Configure, Price, Quote. A well-built bundle quietly walks the rep through a valid selection.
Configuration attributes: choices that shape the bundle
Sometimes a choice isn’t “add this product” but rather “what variation do you want?” — color, size, region, term length. CPQ handles these with configuration attributes.
A configuration attribute is a field shown at the top of the bundle that the rep sets once, and it can flow down to the options. Pick “Region: Europe” once, and every option in the bundle can inherit that value instead of asking again and again. It keeps the rep from repeating themselves and keeps the resulting data consistent.
Attributes are a small feature with an outsized effect on how smooth a bundle feels to use. This is one of those places where a tiny detail changes the whole experience — like the small finger placement on a bağlama that turns a flat note into the right one. The audience may not name what changed, but they feel it.
How to think about structure
When you’re starting out, resist the urge to make one giant bundle that does everything. Good bundle design mirrors how customers actually decide: a clear parent, a few meaningful features, and options grouped where they naturally belong.
A useful test: could a brand-new rep look at the bundle and understand what to pick without being told? If yes, your structure is probably sound. If they freeze, the structure is asking them to think too hard.
If bundles are a topic you want to go deeper on conceptually, the platform-agnostic explanation in Product Bundles Explained is a good companion.
From catalog to quote
Once your products, price books, bundles, features, options, and attributes are in place, you’ve built the stage. Now the rep needs somewhere to actually perform — to add these products to a real deal, set quantities, and watch totals come together.
That place is the Quote Line Editor, and it’s where this all comes to life.
Your next step
Continue building your CPQ foundation:
- The CPQ Quote Line Editor: Where Deals Take Shape
- What Is Salesforce CPQ?
- The Product Catalog Foundation
Or explore the full CPQ series.