Skip to main content

SF-0154 · Scenario · Medium

Is the default or out of the box functionality sufficient for complex product quotes?

✓ Verified by Vikas Singhal · Last reviewed 5/17/2026 · Updated for Spring '26

No — standard Salesforce Quotes are fine for simple catalogs and flat pricing, but they fall over once you need configurable bundles, tiered or volume pricing, approval matrices, or subscription renewals. That’s the gap CPQ products fill.

Where standard Quotes work fine

  • Flat product list with a single price per Price Book entry
  • Optional discount field on each line, header-level discount on the Quote
  • A small set of branded PDF templates
  • Linear approval (one or two approvers)
  • Up to a few hundred line items per Quote

If that describes your business, save the budget and use what’s built in.

Where standard Quotes break

RequirementWhy it hurts in standard Quotes
Configurable bundles — a “router” includes mandatory power supply plus optional ports, with cross-product dependenciesNo bundle structure. Each item is a flat line; reps have to remember the rules
Volume / tier pricing — $10/unit for 1-99, $8/unit for 100-499, $6/unit for 500+One price per PricebookEntry. No tier table
Ramp deals — Year 1 at 1,000 users, Year 2 at 1,500, Year 3 at 2,000One line, one price. No time-phased quantities
Multi-year subscriptions — auto-prorate, renewal upliftNo subscription pricing engine
Approval matrices — discount over 20% needs VP, over 30% needs CFO, custom by regionStandard approvals are workable but get unwieldy fast
Quote-to-order automation — convert a signed quote into an Order with assets and contractsManual creation; sync is partial
Localised templates — same products, different language/currency/legal text per regionLimited template logic in standard Quote PDFs
Guided selling — rep answers questions, system suggests productsNo native flow for it
Amendments / co-terms / swaps — change one line mid-contract, keep co-terminus end dateNot modeled at all

Symptoms that you’ve outgrown standard Quotes

  • Reps maintain spreadsheets alongside Salesforce
  • Pricing exceptions need a Slack chain to figure out
  • Quote-to-order is a manual rekey
  • Excel files travel in email attachments
  • Renewals are tracked in a shared calendar

What to upgrade to

  • Salesforce Revenue Cloud / CPQ — the official upgrade. Bundles, guided selling, tiers, ramps, renewals, contracts, and out-of-the-box DocuSign-style flows.
  • Conga CPQ (formerly Apttus) — strong AppExchange alternative used by large enterprises.
  • DealHub, PandaDoc CPQ, GetAccept — newer, lighter options for SMB / mid-market.
  • Custom development on standard Quotes — viable for small additions (a custom approval flow, an extra PDF template). Don’t try to rebuild CPQ from scratch on the platform.

How to decide in an interview answer

The simple rubric: if your products are “pick from a catalog at a fixed price”, standard Quotes are sufficient. The moment you need bundles, tiers, time-phased pricing, or contract lifecycle, you need a CPQ.

Common follow-ups

  • Is CPQ free? — No. Salesforce CPQ is licensed separately, per user per month.
  • What’s the migration effort from standard Quotes? — Months. Product modelling and approval matrix work dominate.

Verified against: Salesforce Help — Salesforce CPQ Overview and Quotes documentation. Last reviewed 2026-05-17 for Spring ‘26.