Quote Line Pricing explains how one Salesforce CPQ quote line's price was calculated. Use it when you want to understand a line's price or the price rules that affected it, using Quote Line Microscope and Elements evidence.
Quote Line Pricing is an Elements MCP playbook. See What is an MCP playbook? to learn how playbooks work.
What it does and when to use it
Ask why a quote line is priced a particular way or which price rules affected it.
The playbook explains the available evidence, identifies gaps, and answers follow-up questions about the line.
Requirements
Salesforce CPQ and Elements Quote Line Microscope (QLM) are installed in the org. See Setting Up the Quote Line Microscope for CPQ.
The user has the 'Salesforce CPQ Admin' and 'Elements Quote Line Microscope Admin' permission sets. Together they grant every CPQ and QLM read the playbook uses. Elements Quote Line Microscope Admin is the only set that grants access to the QLM objects. The playbook reads as that user, subject to object and field access and record sharing.
Access to contracted prices (
SBQQ__ContractedPrice__c) and standard objects (Account,Product2,PricebookEntry,Pricebook2,Organization) comes from the user's profile.Contracted prices also require record sharing on the parent account.
Block overage rates come from
OverageRate__c, a custom field the CPQ administrator creates on Block Price (SBQQ__BlockPrice__c). When the field exists, the user also needs read access to it, which no CPQ permission set grants.
A missing required field stops the analysis and identifies the access gap. An unreadable required object can mean the package is missing or the object is inaccessible; the playbook asks an administrator to check both. Missing optional access limits the answer, which says what could not be read. For example, an unreadable contracted price is reported as unreadable, not as an absent price.
The playbook reads the quote line, its QLM log and related CPQ records from Salesforce, so it needs a way to make those queries. There are two supported routes:
Salesforce CLI (recommended): the Salesforce command-line interface (
sfCLI) is installed and an org alias is authenticated. The plugin's script runs every query and reads the results directly; the AI assistant copies nothing.Salesforce Hosted MCP server
platform/sobject-reads: use this route when the CLI can't be used. The administrator has activatedplatform/sobject-readsunder 'MCP Servers' in Setup, created an External Client App, and authenticated the Salesforce MCP server with the AI assistant. On this route, the AI assistant runs each query and passes each result to the script, copying it when the result is shown in the conversation rather than saved to a file. A copying slip can drop or change a value. The playbook checks result completeness, queried record Ids, quote line names and log-to-line links, but can't detect changes to other values; a field other than a record Id dropped in copying is reported as not readable. Check any surprising figure against the quote line in Salesforce.
The core
elementsplugin is installed and connected to the Elements MCP server, in an authorized Space linked to the Salesforce org with its reference model synced. See Connect your AI assistant to the Elements MCP server for core setup.Optional price rule change history: the Revenue Cloud flag is enabled in Elements, and
SBQQ__PriceRule__c,SBQQ__PriceCondition__candSBQQ__PriceAction__care selected on the org's Industries settings tab in Elements. History starts with the first sync after the flag and objects are set; earlier changes are unavailable. If history is unavailable, the answer says so and the analysis continues. Change history covers price rules, price conditions and price actions only; Elements doesn't sync quote, quote line or QLM records, so the playbook shows no change history for them.
Install
The playbook is tested on Claude Code with the Salesforce CLI and Salesforce Hosted MCP routes, and on Codex with the Salesforce CLI route.
Claude Code
Claude Code
/plugin marketplace add Q9Elements/elements-mcp-server
/plugin install elements-quote-line-pricing@elements
Codex
Codex
codex plugin marketplace add Q9Elements/elements-mcp-server
codex plugin add elements-quote-line-pricing@elements
Start and resume
On the quote line, click QLM 'Create Diagram'. Creating a QLM diagram also creates the Quote Line log record the playbook needs.
Start with one of these prompts:
"Why is this quote line priced this way?"
"Which price rules affected this quote line?"
Provide the line identifier or name, your question, and your chosen data route. For the CLI route, also provide the org alias.
The playbook saves progress and evidence in an engagement directory. To continue, say "Resume my quote line pricing explanation." The playbook uses execution-state.json in the current working directory or a directory you supply, and asks for the engagement directory only when it can't find the state file. An unfinished collection resumes from its saved evidence for the same line; naming a different line gathers fresh evidence. The closing report lists the distinct quote lines with saved answers. Keep the directory and its contents together.
What you get
An explanation of the price waterfall, pricing method and proration, discounts, bundle and option context, calculator price rules and their available history, and Multi-Dimensional Quoting (MDQ) segments and uplift, as relevant to your question and the available evidence. Price rule history shows who changed each rule, condition and action and when. To see before-and-after values, open that component's history in Elements.
Follow-up answers use the line's saved evidence and focus on your question. You can ask for a full re-analysis or to rebuild the data.
The answer identifies missing evidence and warns when the quote line has changed since its log was written.
When a log holds several calculations, the playbook explains the last one, which produced the current price. If it can't separate them, the answer says "Earlier calculation passes may be included in these figures."
A List Price source of Price Rule, Option Unit Price or Price Book requires its recorded value to equal the line's List Price. When those values disagree and no other pricing method or manual edit explains it, the source is reported as "not determined from the recorded data".
What it doesn't do
The playbook reads Salesforce and Elements data and makes no changes in the org. It explains one quote line at a time.
Price rule analysis covers calculator rules captured by Quote Line Microscope. Configurator rules, price actions on quote line groups or custom objects, and repeat firings within one calculation event aren't recorded.
When it stops
Data route unavailable or unauthorized: a Salesforce System Administrator sets up or authorizes the route.
Package missing or required object unreadable: a Salesforce CPQ administrator or System Administrator installs or enables the package, or grants object read access.
Required field unreadable: a Salesforce CPQ administrator or System Administrator grants access to the listed fields.
Pricing log missing: click 'Create Diagram' on the quote line.
Query or calculation failed: a Salesforce CPQ administrator or System Administrator resolves the error.
Once the issue is resolved, tell the playbook and it rechecks the analysis.
Tested with
Claude Code: Salesforce CLI and Salesforce Hosted MCP routes.
Codex: Salesforce CLI route.
