In every Salesforce CPQ implementation, Product Bundles are one of the core configuration capabilities that must be discussed during scoping and discovery—even if the customer does not initially think they need them.
✔ Why the correct answer is BB. Yes, bundle configuration should be introduced and it's up to the customer to decide whether they need it or not.
This aligns fully with Salesforce CPQ implementation best practices, discovery methodology, and the guidance in CPQ documentation and study resources.
Why bundles must be discussed in scopingSalesforce CPQ Bundles are used to solve many common quoting problems:
Grouping products together
Managing optional/required components
Handling feature selections
Automating inclusion, exclusion, or quantity logic
Supporting configuration rules
Ensuring sales reps configure solutions correctly
Improving quote accuracy
Providing guided selling experiences
Because bundles fundamentally shape:
Product catalog architecture
Pricing structure
Rules design
Quote line generation
Amendment/Renewal behavior
Order + Billing outputs
…they must be addressed early during discovery and scoping to avoid major redesign later.
Salesforce implementation playbooks emphasize:
Introduce all CPQ capabilities during discovery.
Allow the customer to confirm whether a capability meets their use cases.
Document decisions in the solution design before build.
Therefore, bundles should always be a topic of discussion, but the customer chooses whether they need them based on business requirements.
⌠Why the other options are incorrectA. “Bundle configuration is necessary and should always be implemented.â€Incorrect because:
Not all customers need bundles.
Some catalogs are simple, flat, or priced per unit with no component logic.
Salesforce CPQ documentation does not state bundles are mandatory.
C. “If they don’t use bundles now, they won’t need them later.â€Incorrect because:
Customers often evolve pricing and product strategies.
Many legacy quoting tools do not support bundles, so current-state ≠future-state.
CPQ discovery must capture future-state needs.
D. “Assume no bundle configuration unless customer brings it up.â€Incorrect because:
Customers often don’t know what CPQ bundles can do.
CPQ consultants are responsible for educating customers on capabilities.
Failing to introduce bundles leads to:
Incorrect product catalog design
Broken pricing logic
Large rework later in the project
This contradicts CPQ best-practice discovery methodology.
