Growth-stageWorkforce & Education Technology

Moving discount authority out of the quote header: re-architecting bundles and the price waterfall in Salesforce CPQ

Discount accountability moved down a level

SalesforceSalesforce CPQMake
Play leadCamRevOps team · LeanScale

The problem

A single Salesforce CPQ instance carried multiple catalogs and price books, and the pricing model had drifted past what the configuration could express. Discounting was accountable only at the quote header, so nobody could see which part of a deal was actually being given away. Price tiers had proliferated well past what the model could carry.

The play

  1. 1
    Rebuild the bundle model, then decide what a rep is allowed to touch

    Parent bundles were rebuilt per catalog with option groups underneath, and quantity was locked on the bundle parents, one bundle per billing entity means the quantity is always one and letting reps edit it only creates bad quotes. The one line item whose quantity genuinely varies stayed editable, optionally with a floor.

  2. 2
    Push discount accountability down from the header to the bundle

    The core change: pricing accountability moved below the quote header. Reps discount at the bundle level, with the major bundles separately discountable from each other but line items inside a bundle not discountable individually.

  3. 3
    Pull the volume-priced product out of the bundle as a sibling

    One line item priced on a volume schedule rather than a fixed list price kept colliding with bundle-level discounting, changing its quantity moves the regular unit price but not the list unit price, which then interacts unpredictably with a bundle discount applied above it.

  4. 4
    Design the price waterfall in order, and decide what is allowed to be invisible

    Pre-negotiated partner pricing applies as the first step of the waterfall, sourced from a field on the partner account via the opportunity, and was verified by testing rather than assumed.

  5. 5
    Delete system-generated discounts rather than governing them

    Automatic multi-year and pay-upfront discounts were removed in favour of year-over-year price lists, with pre-negotiated partner pricing kept as the only baked-in discount.

  6. 6
    A three-level discount ladder evaluated at two altitudes

    Discount authority was structured as rep → manager → leadership, with thresholds evaluated both at overall quote level and at product-family level, and a single unified threshold set across catalogs at launch for simplicity.

  7. 7
    Make product family the control surface, not product codeMake

    Discount policy was applied via the product family field rather than product codes, and families were cleaned up and bulk-corrected on active products only. The payoff is that every new SKU inherits family-level discount policy automatically instead of requiring a rule change.

What it moved

Discount accountability moved down a level

Discounting shifted from the quote header to bundle and product-family level, evaluated against a three-tier approval ladder, with system-generated discounts eliminated in favour of year-over-year price lists.

From a LeanScale case studyRead the full case study →