Glossary of CPQ terms
A
Term | Description |
|---|---|
Administrators | Individuals who are responsible for maintaining and mapping product catalogs and pricing. |
Attribute-Based Pricing | The price is determined by factoring in attributes of a product. |
Attribute Groups | Attributes associated to products |
Attributes | Are used to associate certain features to a product. Examples of common attributes are color, size, weight, and more. |
B
Term | Desscription |
|---|---|
Base Extended Price | This is derived by Base Price X Quantity X Term. |
Batch Job (CPQ) | Represents an individual batch job. |
Bundle within a Bundle | CPQ allows you to create multi-layered products or “bundles within bundles.” |
Bundled Products | Represent a combination of standalone products that offer added value to the customer while increasing overall sales. |
Bundled Services | Services sold together, as a package, rather than separately. |
C
Term | Description |
|---|---|
Categories | Categories are high-level logical groupings of products. Their grouping affects the way the end user sees them for selection in a product catalog. A category is created for browsing products in the selection pages or they can be created for creating options groups for a bundled product. Products are associated to a category through a category hierarchy. Category hierarchies are maintained using the Hierarchy Manager. They are also used to total the product prices into logical groupings. |
Category Hierarchy | Expresses the collection of subordinate categories into a superordinate category. |
Clone | To replicate a field, record, template, etc. |
Configuration Rules | Ensures an error-free build or customization, even for inexperienced sales reps. |
Configure Products | Button on Quote/Proposal record that allows end users to start configuring a quote. |
Constraint Rule Action | Captures information about rule actions, which are only applied when the rule conditions are satisfied. |
Constraint Rules | Drive automatic inclusion, exclusion, recommendation or replacement of products selected on the catalog page. Each Constraint Rule is composed of three parts; the Rule Detail, the Rule Condition and the Rule Actions. |
Contractual Pricing | Customer specific contractual prices are agreed and used for a defined period. |
CPQ Console | The CPQ Console allows you to manage most product and pricing functions. |
Customer Priority | Field on Account record that defines customer's priority or rating. |
D
Term | Description |
Discrete | The system only considers specific matrix values. |
L
Term | Description |
|---|---|
Line Item | Represents a product or service line item. |
N
Term | Description |
|---|---|
New UI | Revamped user interface of CPQ, which is designed with AngularJS framework (client side JavaScript framework that adds interactivity to HTML). The New UI is intuitive which leads to a better user experience. |
O
Term | Description |
|---|---|
Objects | A definition of a specific type of information you can store in Salesforce. Some objects are native to Salesforce (such as Contacts or Accounts) while others are specific to Conga functionality (such as Proposals or Agreements). |
Opportunity | Salesforce Standard object that allows you to create opportunity records. |
Option Group | To combine product options and then associate that group to a bundled product. |
Organization | A deployment of Salesforce that has a defined set of licensed users. Your organization includes all of your data and applications, and is separate from all other organizations. |
P
Term | Description |
|---|---|
Price Adjustments | Price rules that can be made in CPQ (example: Price Matrix and Price Ruleset). |
Price Dimensions | Represents a price criteria dimension. |
Price List Items | Each price list item includes the list price for the product including details of cost such as per unit, flat price, one time, recurring, and more. Each price list item also represents the different ways that a customer is charged for a product; for example: license fees, implementation fees, etc. Price list items are categorized into Price Lists. |
Price Lists | Containers of items that are grouped in a price list. A price list controls which products are visible to the end user. A price list contains several price list items; each linked to a product. A product can be set up with one or more price list items. |
Price Matrix (Matrices) | These are an advanced pricing concept used to define tiered pricing paradigms, or complex pricing structures with multiple criteria. Common examples are pricing tiers for a product based on user count or particular customer or transactional dimensions. |
Price Ramps and Price Tiers | Pricing mechanisms that establish pricing that varies by time (ramp) or quantity (tiers). |
Price Rule | Represents a single rule in a price ruleset. |
Price Rule Sets | Price Rulesets are a mechanism to allow particular families, categories or groupings of products to have either line item pricing adjustments applied or summary pricing adjustments applied. Typical examples of these are volume discounting rules or promotional pricing rules. |
Product Attribute Group | Represents a product attribute group that contains attributes shared by products. |
Product Attribute Value | Represents the attribute values for a product class. |
Product Console | The product console helps administer product properties and associate products with other CPQ artifacts. |
Product Family | Is a Salesforce standard field on the product record with configurable values. This construct allows you to create combinations of products with similar characteristics/qualities for use in a Price Rule. |
Product Group | Is a Conga custom object that creates a logical grouping of one or more product records. This construct allows you to create combinations of products with similar characteristics/qualities for use in a Price Rule. |
Product Hierarchy | Defines the structure of the product catalog. |
Product Option Group | Represents a product option group which is a member of the list of option groups associated with a product. |
Products | A product or service that can be sold on its own as a standalone item, an option of other products, or as part of a bundled product. Conga utilizes the standard Salesforce Products2 table to store product records and Conga-specific fields on those records that manage the behavior of products. |
Proposal | The Conga custom object used to record information about a specific quote for a specific Opportunity and Account. The tab for the object is presented as Proposals and the record is stored as a Quote/Proposal. |
Q
Term | Description |
|---|---|
Quote | The Conga custom object used to record information about a specific quote for a specific Opportunity and Account. The tab for the object is presented as Proposals: and the record is stored as a Quote/Proposal. |
R
Term | Description |
Records | A collection of fields that store information about a specific item of a specific type (represented by an object), such as a contact, an account, or an opportunity. |
S
Term | Description |
|---|---|
Selling Term | Field on line item object (column in cart) that defines length of time the seller will allow the buyer to pay for a product. |
Standalone Products | Refers to a device or software that is self-contained, one that does not require any other devices or software to function. |
Standalone Services | Refers to a service that is self-contained, one that does not require any other service to function. |
T
Term | Description |
|---|---|
Tiered Pricing Model | The longer a subscription term on a quote, the lower the monthly rate will be. |
V
Term | Description |
|---|---|
Validating | To check or prove the validity or accuracy of a value or instance. |