Audience: Salesforce Partners reviewing the finished figures of a customer estimate.
The Totals step is the final step of the Flex Credit Pricing Calculator. It combines every configured Solution into one set of figures and breaks that total down by year and by individual priced product, so you can see what drives the cost.
Read this to understand each figure shown on the Totals step, how the per-year and per-SKU views differ, and what to do when a figure looks wrong. Figures shown here are estimates for planning; final pricing comes from a formal quote.
Four views, from the highest level down:
The headline figures: total credits, total seats, and total price for the intended contract period
The Overview, with a total for each year, the subtotal, and any Overall discount applied.
The SKU Breakdown, showing each priced SKU's share of the total.
The Consumption Over Time chart for Year 1.
The headline figures answer "what is the whole deal worth across all years". The Overview splits the same amount by year, so you can see how the ramp you modeled distributes the cost, and shows the subtotal before and after the Overall discount.
"SKU Breakdown" is the name of the card in the calculator. It shows which individual priced products make up the total and what proportion each one represents. Use it to explain to a customer what they are paying for, rather than presenting a single combined figure.
If the SKU Breakdown is empty, the estimate has no priced products yet. Configure at least one Solution and return to this step.
The Year 1 consumption pattern, month by month, split by Solution and by credit type. Select items in the legend to filter down to specific Solution and credit-type combinations, which is useful when one Solution dominates the chart and hides the others.
Yes, but it invalidates work you have already done. Adding a Solution at this stage means the combined Consumption and Ramping figures must be recalculated, so the calculator warns you and asks you to re-validate those two steps for the whole configuration. Confirm only if you intend to review them again.
Work backwards through the steps that feed it:
Check the Discounts step, since an Overall or SKU Level discount changes the total.
Check the Ramping step, since the number of years and the growth you modeled drive the multi-year total.
Check the Consumption step, since manually edited months override the values derived from the Solution configuration.
Check the Solutions step for a Solution that is added but not fully configured.
A1E stands for Agentforce 1 Edition. That edition already comes with a pool of Flex Credits. When an estimate includes the edition, those credits appear as included rather than as credits to purchase, because the customer has already paid for them as part of it.
This figure is specific to that edition. It is a different subject from the interactions a customer's licences may already cover, which is explained in "Building and Managing an Estimate".
Usage beyond the included pool draws on Flex Credits bought separately. The Overview separates the two so you can see how much of the customer's projected usage the edition already covers, and how much sits on top of it.
Flex Credits to purchase are packaged. The calculator takes the Flex Credit consumption you modeled and rounds it up to the next Flex Credits SKU quantity that covers it. The customer buys that packaged quantity, so the Flex Credits figure on Totals can sit above the burn you entered.
Packaging is applied once for Flex Credits across the whole estimate, across every Solution that uses them.
This is separate from Included A1E Credits, which reduce what still needs to be bought. Building and Managing an Estimate covers licences the customer already holds, which can move the real need the other way.
A Derived Price Product is one whose price is calculated from another product's price rather than set on its own — for example, a line priced as a proportion of a base licence. Because those prices depend on the products they derive from, the Totals step leaves them out of the headline figures and tells you so.
Their absence from the estimate is not an oversight and does not mean the customer will not be charged for them. As with every figure in the calculator, the complete picture comes from the formal quote.
Update the total by navigating to prior pages using the top navigation bar and updating Solution configuration, consumption, ramp, and/or discounts. Use the cart to navigate to different Solutions.
Example of using the breakdown with a customer: A partner finishes a three-year estimate and the customer asks why the total is what it is. The partner opens the Overview to show how the amount splits across the three years. Then the SKU Breakdown, to show which SKUs carry most of the cost. Finally the Consumption Over Time chart, which shows Year 1 usage starting low during the build window and rising after Production launch.
Example of tracing an unexpected total: A partner sees a Year 2 total higher than expected. They return to the Ramping step, find the Year-Over-Year growth set higher than intended, correct it, and the Totals step recalculates.
Example of packaged Flex Credits to purchase: A partner models Flex Credit consumption that does not fill a whole Flex Credits SKU. Totals shows the Flex Credits to purchase rounded up to the next SKU quantity that covers it, which is the quantity the customer would buy.
Trace a figure back through the steps that feed it first. If it still looks wrong, open a support case in Partner Community with the name of the estimate and the figure you expected.
005459666

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.