Chapter 9: Quote Templates, Documents, and E-Sign – Automating Output

 Creating a deal-winning quote isn’t just about pricing—it’s about presenting a professional, personalized, and accurate document to the customer. Salesforce CPQ helps you do just that using Quote Templates, Document Generation, and E-Signature integration.

In this chapter, we’ll explore how to build and automate sales documents from quote to signed contract.

---

9.1 What Is a Quote Template?

A Quote Template in Salesforce CPQ is a predefined format for generating customer-facing PDF quotes. It controls how the quote looks, what data is displayed, and how terms and conditions are appended.

---

9.2 Why It Matters

A well-designed quote document:

• Increases customer confidence

• Reduces turnaround time

• Ensures compliance and branding

• Supports multi-currency and language localization

---

9.3 Quote Template Components

Section	Purpose
Header/Footer	Company logo, address, date, page number
Line Items Table	Products, pricing, quantities, discounts
Terms & Notes	Commercial terms, billing details, legal disclaimers
Custom Fields	Payment methods, contract terms, approval status, etc.

You can include:

• Dynamic fields (e.g., quote name, expiration date)

• Conditional sections (e.g., show discount only if applied)

---

9.4 Creating a Quote Template – Step-by-Step

Step 1: Create a Template Record

Go to:
App Launcher → Quote Templates → New

Set:

• Name: "Standard Quote"

• Default Template: Yes (if applicable)

• Page Size: A4/Letter

• Top & Bottom Margin: 0.5 in (recommended)

Step 2: Add Sections

Under the Template Content related list:

• Add Line Items table

• Add Terms & Conditions

• Add optional section for Quote Summary

You can choose which columns to display, sort order, and headers.

Step 3: Attach Dynamic Content

Use Merge Fields like:

• {{SBQQ__Quote__r.SBQQ__StartDate__c}}

• {{SBQQ__PrimaryContact__r.Email}}

---

9.5 Customizing the Look and Feel

You can style the template using:

• Fonts, colors, and borders

• Conditional formatting (e.g., highlight discounts)

• Logos and images (uploaded to Salesforce Files)

To make advanced customizations:

• Use HTML Templates or Visualforce (for branding-heavy use cases)

---

9.6 Multi-Template Support

You can create multiple templates for:

• Product-based templates (e.g., software vs hardware)

• Country/language-specific quotes

• Partner-specific formats

Use Template Content Conditions to dynamically include/exclude sections.

---

9.7 Document Generation

Once a template is assigned:

• Open the Quote record

• Click “Generate Document”

• Choose template → Preview → Download as PDF

You can enable:

• Auto-naming (e.g., Quote_{{Account}}_{{Date}})

• Version control with Salesforce Files

• Automated document generation using Flows or Apex triggers

---

9.8 Integration with E-Sign

Salesforce CPQ supports integration with:

a. DocuSign for Salesforce

• Automatically send generated quotes for e-signature

• Pre-fill signer name, email, and signature blocks

• Track signature status inside Salesforce

b. Adobe Sign

• Similar functionality with full audit trail

• Can be launched from Quote or Opportunity

c. Native E-Sign (Industries CPQ/OmniStudio)

• Offers simplified signature flows in Industry-specific contexts

---

9.9 Automating Quote to Contract Flow

A fully automated Quote-to-Signature process might look like:

1. Sales rep configures quote → clicks “Generate Document”

2. Document auto-generates from quote template

3. Email with PDF sent to customer via DocuSign

4. Customer signs → Signature status auto-updates in Salesforce

5. Contract record is created automatically

This improves deal velocity and eliminates manual follow-ups.

---

9.10 Best Practices

• Use versioned templates to avoid accidental changes

• Include branding and T&Cs to reflect legal compliance

• Automate where possible using Flow + Approval Process

• Enable file tracking via Salesforce Files Connect

• Test templates with various quote sizes (small vs complex)

---

9.11 Chapter Summary

• Quote Templates help generate clean, professional PDFs with rich, dynamic content

• Sections like product tables, summary fields, and terms are fully configurable

• E-Sign integrations like DocuSign and Adobe Sign bring speed and legal confidence

• Automating document workflows improves the entire quote-to-cash lifecycle

Chapter 8: Guided Selling and Configuration Rules – Making Sales Reps Faster and Smarter

 One of the biggest challenges in B2B selling is product complexity. Sales reps may not always know which product combination fits the customer need. That’s where Guided Selling and Configuration Rules in Salesforce CPQ come into play.

They help:

• Reduce errors and misquotes

• Speed up the quoting process

• Improve upselling and bundling

• Ensure consistent sales behavior

---

8.1 What is Guided Selling?

Guided Selling is a feature in Salesforce CPQ that provides a step-by-step product selection wizard to help sales reps choose the right products based on customer needs.

Benefits:

• Simplifies product search

• Enforces sales best practices

• Reduces time to quote

• Increases average deal size with smarter suggestions

---

8.2 How Guided Selling Works

You define:

1. Prompt Rules – The questions asked to sales reps

2. Filter Rules – Logic that translates answers into product suggestions

3. Product Filters – Automatically applied search filters

Example:

Prompt:
"What type of solution is the customer looking for?"
Options: CRM, Billing, Support

Based on the response:

• Filter CRM products from the catalog

• Show only subscription-type services

• Pre-check product bundles if required

---

8.3 Setting Up Guided Selling

Step 1: Create a Prompt

• Object: Guided Selling Prompt

• Define question text, picklist or text input

Step 2: Link to Product Filter

• Define logic (e.g., Product Family = value from prompt)

Step 3: Configure in Quote Process

• Ensure “Use Guided Selling” checkbox is enabled

• Trigger upon “Add Products” in the quote

---

8.4 What Are Configuration Rules?

Configuration Rules enforce logic inside product bundles.

They ensure:

• The right products are selected (automatically or by suggestion)

• Invalid combinations are blocked

• Dependencies are respected (e.g., if you choose Product A, you must include B)

---

8.5 Types of Configuration Rules

Rule Type	Description
Selection Rule	Automatically include, exclude, or recommend a product
Alert Rule	Show a message or warning based on a condition
Validation Rule	Block user from saving invalid configuration

---

1. Selection Rules

Used to auto-select or exclude products based on user input or logic.

Example:

• If “Premium Plan” is selected → include “Priority Support”

• If “Wi-Fi Router” is selected → auto-add “Installation Service”

---

2. Alert Rules

Used to show helpful tips or warnings during configuration.

Example:
"If the total quantity exceeds 100, ensure customer signs a volume agreement."

---

3. Validation Rules

Used to prevent invalid configurations.

Example:

• Prevent choosing "Solar Inverter" without selecting a "Solar Panel"

• If user selects both "Basic Support" and "24/7 Support" → throw error

---

8.6 How to Set Up Configuration Rules

1. Create Configuration Rule

2. Define Rule Type (Selection, Alert, Validation)

3. Set up Conditions (using Product Fields or Attributes)

4. Define Product Actions (Include, Exclude, Disable, etc.)

5. Assign rule to your Product Bundle

---

8.7 Real-World Scenarios

Scenario	Solution
Recommend accessories with laptops	Selection Rule
Prevent multiple support tiers	Validation Rule
Warn if order value is too low	Alert Rule
Automatically include installation fee	Selection Rule

---

8.8 Best Practices

• Start small: Begin with 1–2 key rules before scaling

• Use shared Product Features to avoid duplication

• Test edge cases to ensure rules don’t conflict

• Document rule logic for future admins or updates

• Use dynamic bundles for complex selling models (industries CPQ)

---

8.9 Guided Selling vs. Configuration Rules

Feature	Guided Selling	Configuration Rules
Purpose	Help reps choose products	Ensure valid product combinations
Triggered On	Adding products to quote	During product configuration
Ideal For	Discovery, filtering, suggestions	Enforcing logic, auto-selections

---

8.10 Chapter Summary

• Guided Selling simplifies product selection with a question-based wizard.

• Configuration Rules ensure sales reps can’t make invalid or non-compliant product selections.

• Together, they increase accuracy, reduce sales cycle time, and enable scalable quoting across complex offerings.

Chapter 7: Price Rules, Lookup Queries, and Summary Variables – Making Pricing Smart

 

 Salesforce CPQ doesn’t just offer static pricing—it gives you the power to make dynamic, responsive pricing decisions using logic. This is made possible through three powerful tools: Price Rules, Lookup Queries, and Summary Variables.

Used correctly, they turn your CPQ solution from a pricing calculator into an intelligent revenue engine.

---

7.1 What Are Price Rules?

A Price Rule in Salesforce CPQ allows you to automatically update quote line fields, quote fields, or configuration fields based on predefined conditions.

You can:

• Inject values into a field

• Calculate conditional pricing

• Apply logic based on region, customer, or quantity

---

7.2 Key Components of a Price Rule

Component	Description
Price Rule	The rule itself; defines where and when the rule fires
Price Conditions	Optional logic to check before applying the rule
Price Actions	Field updates that occur when the rule conditions are met
Lookup Queries	Pull data from other objects to use in calculations

---

7.3 When Do Price Rules Run?

You can configure when the rule should execute:

• Calculator Initialization – before quote calculations start

• Before Calculation – to influence pricing inputs

• After Calculation – to override final outputs

• On Configuration – within the product configurator

This control allows you to inject logic at exactly the right moment in the quoting process.

---

7.4 Example: Region-Based Pricing

Use Case: If the customer is from “India”, offer 20% discount; otherwise, offer 10%.

• Condition: Billing Country = India

• Action: Set Additional Discount (%) = 20

Otherwise, set to 10%. This can be done with:

• 2 Price Rules (one for India, one default)

• Or 1 rule with dynamic calculation

---

7.5 What Are Lookup Queries?

Lookup Queries allow Price Rules to pull data from another object (e.g., a custom pricing matrix, discount table, or volume break).

You can use them to:

• Fetch pricing tiers from a custom table

• Match values from product-specific discount plans

• Support customer-specific contracted rates

---

Lookup Query Example:

Use Case: A discount is stored in a custom object Discount_Master__c.

Fields:

• Product_Code__c

• Customer_Type__c

• Discount_Percent__c

A Lookup Query matches the Product Code and Customer Type from the quote line and returns the discount.

The returned value is then mapped to the Additional Discount (%) field via a Price Action.

---

7.6 What Are Summary Variables?

Summary Variables are used to calculate totals, counts, or averages across quote lines. You can use them in Price Rules and Quote Terms.

Type	Use Case
Sum	Total quantity of a specific product
Average	Average list price of selected quote lines
Count	Number of lines with a specific attribute
Min/Max	Highest or lowest price in quote lines

---

Summary Variable Example:

Use Case: Apply a bulk discount if the total quantity of licenses exceeds 100.

1. Create a Summary Variable:

   • Target Field: Quantity

   • Aggregation: Sum

   • Filter: Product Family = “Software License”

2. Create a Price Rule:

   • Condition: Summary Variable > 100

   • Action: Additional Discount (%) = 15

This enables smart volume-based pricing across multiple lines.

---

7.7 Real-World Scenarios

Scenario	Solution
Region-based pricing	Price Rule + Condition
Product tiered pricing	Lookup Query + Custom Object
Subscription term discounts	Price Rule + Configuration Attribute
Volume-based discount across lines	Summary Variable + Price Rule
Customer-specific pricing (contracted)	Lookup Query + Account Lookup

---

7.8 Best Practices

• Name clearly: Use naming conventions like PR_Region_Discount_India

• Reusability: Design Lookup Queries to be scalable

• Test combinations: Use debug logs to test multiple conditions

• Avoid complexity early: Use standard discounts unless business logic requires rules

• Combine logically: You can stack multiple Price Rules in a single quote process

---

7.9 Common Mistakes to Avoid

• Forgetting to enable Calculator Plugin if rules don’t fire

• Writing conflicting Price Rules without understanding sequence

• Overcomplicating logic where Discount Schedules might suffice

• Not defining correct target object (Quote vs. Quote Line vs. Configurator)

---

7.10 Chapter Summary

• Price Rules automate field updates and smart pricing decisions.

• Lookup Queries let you pull external pricing logic into quotes.

• Summary Variables help you aggregate quote line data and apply logic.

• These tools power advanced CPQ configurations and bridge static and dynamic pricing.

Chapter 6: Pricing Methods – List, Cost Plus, Percent of Total, and More

 

Pricing in Salesforce CPQ and Revenue Cloud is both flexible and powerful. From basic List Pricing to complex logic like Cost Plus or Percent of Total, understanding how and when to use each method is critical for delivering accurate, scalable, and strategic revenue models.

---

6.1 Overview of Salesforce CPQ Pricing Engine

Salesforce CPQ offers multiple pricing methods, which work in combination with Price Rules, Discount Schedules, and Quote Line fields.

The base price is usually defined in a Pricebook Entry, but pricing can be:

• Modified through standard pricing methods

• Overridden via logic in Price Rules

• Adjusted using discounts or markups

---

6.2 Core Pricing Methods

Let’s explore each of the main pricing types you can configure:

---

1. List Pricing (Standard)

Definition: The product’s price is pulled directly from the Price Book.

• Use Case: Flat-fee product or service (e.g., ₹10,000 for Setup Fee)

• How it works:

  • Pricebook Entry = ₹10,000

  • Quote Line Unit Price = ₹10,000

Advantages: Simple, easy to manage
Limitations: No flexibility based on quantity or cost

---

2. Cost Plus Markup

Definition: Price is calculated by taking the product cost and adding a markup percentage or amount.

• Use Case: When you sell services or items based on your internal cost.

• How it works:

  • Cost Field = ₹8,000

  • Markup = 25%

  • Selling Price = ₹10,000

Setup:

• Enable "Cost Editable" and populate the Cost field

• Use a Price Rule to calculate markup

Advantages: Reflects profitability clearly
Limitations: Requires cost field population and custom logic

---

3. Percent of Total (PoT)

Definition: The product’s price is a percentage of the total price of other quote lines.

• Use Case: Add-on services like Support (10% of total quote)

• How it works:

  • Total of other products = ₹50,000

  • Support (PoT at 10%) = ₹5,000

Setup:

• Enable Percent of Total checkbox on the product

• Define which products are included/excluded in the calculation

Advantages: Great for optional services
Limitations: Not ideal for standalone products

---

4. Block Pricing

Definition: Price is defined in blocks or quantity ranges.

• Use Case: Tiered or fixed pricing per volume

• Example:

  • 1–10 units = ₹1,000

  • 11–50 units = ₹4,000

  • 51+ units = ₹10,000

Setup:

• Add Block Price records to the Product

• Leave Pricebook Entry blank

Advantages: Easy to apply volume-based pricing
Limitations: No per-unit breakdown in invoice

---

5. Slab Pricing (Tiered Per Unit)

Definition: Price is calculated per unit within each block.

• Use Case: Usage-based billing (e.g., electricity, SaaS)

• Example:

  • First 10 = ₹100/unit

  • Next 40 = ₹80/unit

  • Beyond = ₹60/unit

Setup: Requires customization (usually via custom logic or external integration)

---

6. Custom Pricing (via Price Rules)

Definition: You use formulas, lookup queries, or dynamic conditions to control the price.

• Use Case: Any scenario not supported by standard pricing

• Example: If region = India and quantity > 100, apply special rate

Tools Used:

• Price Rules

• Lookup Queries

• Summary Variables

Advantages: Maximum flexibility
Limitations: Requires testing and complexity management

---

6.3 Discounting Approaches

Although not pricing methods per se, Salesforce CPQ allows for robust discount control:

Type	Description
Manual Discount	Sales rep manually adjusts discount (%) or amount
Automatic Discount	Triggered by quantity, tier, or product bundles
Contracted Pricing	Account-specific negotiated pricing
Partner Pricing	Adjusted pricing for partner or channel sales

Use Discount Schedules for quantity-based automatic discounting.

---

6.4 Multi-Currency & Localization

Salesforce CPQ supports:

• Multiple currencies via Advanced Currency Management

• Localized pricing via multiple price books

• Currency conversion based on exchange rates

You must plan pricing to align with local billing regulations and taxes.

---

6.5 Choosing the Right Pricing Method

Pricing Method	Best For
List Pricing	Fixed-fee products
Cost Plus	Service-based pricing with known cost
Percent of Total	Add-on services (support, warranty)
Block Pricing	Tiered packages or bundles
Custom Pricing	Region-based or dynamic logic

---

6.6 Best Practices

• Start simple; scale pricing complexity gradually

• Document pricing logic for easy handover

• Use Lookup Price Rules to reduce hardcoded values

• Align pricing methods with product types and billing terms

• Always test with multiple use cases and contracts

---

6.7 Chapter Summary

• Salesforce CPQ supports flexible pricing strategies for modern sales models

• Choosing the right pricing method impacts scalability and maintainability

• Price Rules and Lookup Queries unlock dynamic, intelligent pricing

• Pricing connects deeply to billing, renewal, and revenue recognition — design with the full lifecycle in mind