Understand CPQ Data Model

Core objects used in CPQ 

Quote: The main proposal sent to the customer, linked to a sales deal (Opportunity). It holds all items, prices, and customer details.


Quote Line: Each row in the quote, like “5 Laptops at 50,000 each”. Every product, quantity, and price is one quote line.


Product: What you sell. It can be a simple item (one laptop) or part of a bundle (Laptop + Mouse + Warranty).


Price Book: A price list, like “Standard Prices” or “Partner Prices”.


Price Book Entry: Connects one product to one price list with its list price (e.g., Laptop in Standard Price Book at 50,000).


Product Options: The individual choices inside a bundle, like adding a mouse or extra warranty to a laptop.


Product Features: Groups of related options, like “Accessories” or “Support Plans”, to keep options organized.


Configuration Attributes: Extra questions asked during setup, such as color, size, or memory, to fine-tune the product.


Quote Line Group: A way to group lines on a quote, like “Hardware” and “Services” sections, to keep complex proposals clear and easy to read.


Quote Life cycle


Sales reps create quotes for mobile phones in Salesforce CPQ by linking to a sales opportunity and adding products step-by-step.

Mobile Phone Quote Example

  1. Select Opportunity: Pick the customer’s sales deal, like “John’s New Phone Upgrade”.
  2. Add Quote: Create a new quote tied to that opportunity, set expiry date.
  3. Choose Products: Add “iPhone 15 Pro” (standalone) or bundle “Galaxy S24 + Case + Charger”.
  4. Quote Lines Appear: Each item shows as a line—e.g., 1x iPhone at $999, 1x Case at $49 from Standard Price Book.
  5. Review & Share: Final quote with totals, discounts, and details gets emailed as a PDF.



Salesforce CPQ uses smart rules to guide product setups and pricing without mistakes.


Product Rules: These enforce logic when picking products.

  • Validation Rules: Block invalid choices, like “Can’t pick laptop without charger”
  • Selection Rules: Auto-add related items, e.g., select phone and it adds a case.
  • Alert Rules: Warns but lets you continue, like “Add warranty for best coverage?”


Product Rule



Price Rules: Auto-changes prices on quotes. Example: Buy 10 phones, get 10% off automatically.


Constraint Rules: Forces or limits options. Example: High-end phone requires premium screen protector. It is mandatory.

Price Rule


Comments

Post a Comment

Popular posts from this blog

How to Give Permissions to Automated Process Users or System Context Users

Image
What is Automated Process Users Automated Process Users are special users created automatically by Salesforce, are essential to the execution of automated jobs and background processes. These users are essential for executing tasks that require no direct human intervention, such as: Flows: Automated Process Users can run Flow automations that perform actions like updating records, sending emails, or creating tasks. Approval Processes: They can act on behalf of users in approval processes, ensuring that approvals move forward even without direct user interaction. Scheduled Jobs: These users can run scheduled jobs that perform maintenance tasks or batch data processing. 1. How to fetch automated process user using SOQL? SELECT ProfileId, name FROM User WHERE Alias = 'autoproc' 2. How to give permission of apex class to automated process user step 1: visit following link <ORG_BASE_URL>/_ui/system/user/ProfileApexClassPermissionEdit/e?profile_id=<Automated_Process_User...
Read more

Understanding the Salesforce Approval Process: A Step-by-Step Guide

Image
The Approval Process in Salesforce is an automated sequence of steps where a record is reviewed and approved (or rejected) by designated users based on predefined conditions. This ensures compliance, proper authorization, and consistency in business operations. Key Objects of an Approval Process 1. ProcessNode (Approval Step Definition) (04b) Defines the approval steps in a process. SELECT Id, Name, DeveloperName, ProcessDefinitionId, Description FROM ProcessNode 2. ProcessInstance (Approval Request) (04g) Created when a record is submitted for approval. Stores the current status and progress of the approval process for that record. Acts like a snapshot, tracking where the approval stands at any given moment. SELECT Id, ProcessDefinitionId, TargetObjectId, Status, CompletedDate, LastActorId FROM ProcessInstance 3. ProcessInstanceHistory  Keeps a record of all actions (audit trails) taken on a specific approval process instance. Logs approvals, rejections, reassignments, and recall...
Read more

Headless action button using LWC (No Modals)

Image
  A headless quick action executes custom code in a Lightning web component. Unlike a screen action, a headless action doesn’t open a modal window. Expose invoke() as a public method for headless quick actions; the invoke() method executes every time the quick action is triggered. Return type of invoke() is void . Using async will make invoke()  execute asynchronously.  // js file import { LightningElement, api } from 'lwc'; import { ShowToastEvent } from 'lightning/platformShowToastEvent'; export default class DispatchEventHeadlessAction extends LightningElement {     @api recordId;      isExecuting = false;     @api async invoke() {           if (this.isExecuting) {           // This code uses a boolean flag to block a double execution            return;          }           this.isExecuting ...
Read more