Cpq Interview Question
Cpq Interview Question
CPQ
INTERVIEW
Q&A
Having a well-configured CPQ tool is essential for sales and operations teams to create
accurate quotes with correctly configured products and pricing.
Products can be sold together as part of a bundle or standalone. Bundles can have
complex logic applied to them through Product and price Rules.
This means they can be used for more than just pricing use cases. Price rules can have
a condition (or multiple conditions) defined to tell the system when to apply the price
action, but conditions are not essential.
Q5. What is a Summary Variable and how is it different from a Roll Up Summary?
A. Summary variables summarize a number of fields (such as quantity or price) and allow
you to define criteria for the summary such as product code or product family. Summary
variables run specifically within the quote line editor and the value is not retained* in the
system once the calculation is performed. This means you are not contributing to the
limit for roll up summary fields on objects (25 in most cases but can be increased to 40).
Roll up summary fields behave in the same way, but the value is not calculated until the
record is saved – whereas Summary Variables are calculated within the quote line editor
and are usually used for the purposes of triggering product or price rules.
A good example would be if you are offering a discount on all quotes over a certain
threshold, let’s say $1,000. You would define a summary variable to add up the gross
amount of all quote line items, and if the value is over $1,000, then a price rule could be
triggered to automatically apply a 50% discount to the entire quote.
Note: You can retain the value by using a price rule to populate the value into a field on
the quote or quote line.
Q6. Explain the difference between a Subscription Product and a One-Time Product?
A. Subscription product: A product that generates recurring revenue – e.g. software
license, ongoing service subscription, a product that is leased or rented, etc.
One-Time Product: A product that generates revenue once – e.g. a physical good
that is sold rather than rented or leased, a perpetual software license, a fee for
implementation services, etc.
Subscription Prorate Precision defines how the system will calculate any non-whole
terms for subscription products e.g. if the term is six months and three days, how
the system will calculate the price for a subscription product with a yearly price.
The options are Day, Calendar Monthly + Daily, Day with Calendar Month Weighted,
Monthly, and Month + Daily. Each produces a slightly different calculation, and this
setting applies to every quote in the system.
This setting is important as it defines if bundles are re-evaluated upon renewal. This
means if you have changed the structure, rules, or price of a bundle between the
time it was first sold to the time of renewal, it clarifies whether the system should
apply the new rules, structure, and/or pricing or have the bundle remain the same as
when the customer first bought it.
Let’s use the entertainment package example from earlier as an example. If a
customer purchased a bundle during promotion and got a great price, plus the movie
and sports package included for free, should the bundle be re-evaluated by the
system when the customer’s package is up for renewal? If yes, this global setting
should be checked. This will apply across all bundle products in the system.
This setting is important as it enables the ability to have multiple orders generated
from a single quote. This is useful if you need to split line items on a quote into more
than one order, such as if you are selling to multiple business units and need to
generate a different invoice for each order.
In March, the customer comes back to you for five more licenses. The user would create
a Contract Amendment to sell the five extra licenses from March to December rather
than starting a new contract from March to February.
Using Contract Amendments ensures all subscription products renew on the same date,
making it easy to handle renewals when the time comes.
Product Options are records related to two Product records, the Configured SKU (the
Parent or Bundle product) and the Product record that holds the Option itself.
The Product Options are items like the solar panels and mounting kits.
Product Option records are related to two Product records, the Configured SKU (Solar
Controller Hub) and Optional SKU (Solar Panel, Mounting Kits, etc.).
Product records which are not to be sold outside a bundle must have the field
“Component” checked. This removes them from the Product Catalog.
Orders are created by Sales Ops or the Finance team and are used to prepare invoices
for the customer based on what they have purchased. Data from the primary quote will
flow downstream to the Order record such as Account Name, Opportunity Name, Quote
Lines > Order Products, etc. but could contain additional financial information such as
billing period, VAT number, etc. In many cases, the Quote and Order will be exactly the
same.
Example: Manufacturing
Manufacturing is a good fit for CPQ because manufacturers often sell complex products
that can be configured in a number of ways. This can make it hard for non-technical
salespeople to create proposals and sell the products, as well as make it difficult for the
team building the product if they do not know exactly what the customer ordered.
Salesforce CPQ empowers non-technical salespeople to sell complex products by
having guardrails in place to prevent incompatible configurations.
Example: High-Tech
Salesforce is the best example of a high-tech company using CPQ. Salesforce sells a
number of licenses which can be sold either in packages or standalone, and as their
product catalog grows through internal product growth and mergers, having a tool like
Salesforce CPQ makes it easy to sell a highly complex catalog of products.
Professional Services companies, such as Accenture, Deloitte, and PwC, offer resources
(people) to staff projects. Resources usually have a fixed cost based on their location,
and every project will require specific resources to achieve the end goal. Having a CPQ
tool in place can make it easy to configure a quote for resources based on the client’s
needs.
Q14. What is the difference between Product Rules and Option Constraints?
A. Option Constraints are a simplistic version of product rules allowing users to exclude or
require an option based on the selection of another option, e.g. a user selects option A
so they must also select option B.
Product rules are far more sophisticated and have four types of rules: validation, alert,
selection, and filter. The selection type will provide the same functionality as Option
Constraints but with more features.
For example, let’s say you want to apply an automatic discount based on information on
the Account record.
Let’s say you have a partner discounting program in place. Partners are given a general
rating based on their size and resource skill set, but the number of delivered projects is
also tracked and influences their discount. The more projects they deliver, the bigger the
discount. You can even configure the Discount field on the object to automatically
update as more projects are delivered, for example.
The lookup data is used by the Price Rule and the discount is applied automatically
based on the matching parameters in the lookup data and what’s on the quote record.
Q16. Give a Use Case for using Price Rules to populate Non-Pricing Fields on the Quote Line
Object?
A. One possible use case is to use a price rule to populate the value derived from a
Summary Variable into a field to hold it permanently. Summary Variable values are
derived dynamically and are not stored by default anywhere in Salesforce. If you need to
store the value, create a price action to populate the value from the variable in a field on
the quote object.
Q17. How can you simplify the look and feel of a customer’s Product Catalog using CPQ?
A. The Product Catalog can be grouped using either Product Family or another custom
field to sort and group products together. This setting can be found in the global
package settings.
Q18. Give some examples of CPQ-specific discovery questions for Requirements Gathering
A. How do you sell your products (i.e. bundles, standalone, etc.)?
Do you have complex rules about what can and can’t be sold together?
What is your pricing method (i.e. subscription, one-time, milestone, etc.)?
What is the process to send a quote to your prospects and customers today?
Do you offer contracted pricing or volume pricing to customers?
How do you record the commercial terms agreed with a customer?
Note: There are many more discovery questions, but these examples show that the
candidate understands the nuances around CPQ development and what information is
needed.
Q20. Explain how to roll out Salesforce CPQ (at a high level)
A. Salesforce CPQ will require a phased deployment and the process should be planned
well in advance. At a high level, the following steps are required:
Install the CPQ package in the Production environment for admins only.
Migrate fields to Production.
Migrate relational data to production.
Update Global Package settings.
Smoke test with admins and a small group of test users who have been given the
required permissions.
Add Permission Set License to all users who require CPQ permissions.
Add relevant permission sets to all users who require CPQ permissions.
Monitor usage and monitor hypercare channels (email, Slack, etc.)