Every Salesforce release brings a long list of updates. Most of them are incremental. A few reshape how teams actually work.
The Spring ’26 release for Revenue Cloud – now officially branded as Agentforce Revenue Management – falls somewhere in between: it does not reinvent the platform, but it introduces several capabilities that fill gaps teams have been working around for months.
This article walks through the updates we consider most relevant for ARM implementation teams. We will not cover every line item in the release notes – instead, we focus on what these changes mean in practice and where to watch for surprises.
Promotions have been in beta since the previous release, but Spring ’26 marks their general availability. For the first time, Revenue Cloud has a built-in tool for creating, managing, and applying discounts as part of the standard pricing flow – without custom Apex or external integrations.
The centerpiece is the Promotions Console – a workspace where pricing designers and marketing managers set up promotions, see what is scheduled on a calendar, and manage the full lifecycle from draft to active to expired.
.png)
You can make a promotion manual (a sales rep applies it during quoting) or automatic (the system applies it when eligibility conditions are met). Targeting works at the product level or across an entire category. Key capabilities include:
Of the three capabilities above, price waterfall visibility is what makes Promotions more than a simple discount mechanism – it brings the transparency that governance-heavy implementations need, especially where manual overrides have historically been hard to audit.
Promotions are applied in the configurator or the line editor, and once active, a dedicated Promotions tab in the product side panel shows the applied discount, its type, and history.
.png)
Promotions require specific permission set licenses: Revenue Management Promotions Runtime and Global Promotions Management Basic PSL.
Users also need the Apply Promotions on Sales Transactions and Promotion Designer permission sets assigned. The licensing model is separate from the base Revenue Cloud license – confirm entitlements before planning your rollout.
Promotions in their current form handle straightforward discount scenarios well. For complex promotional logic – stacking rules across multiple tiers, conditional discounts based on transaction-level aggregations – evaluate the boundaries carefully.
This is a first production-ready release, and the functionality will mature. It is worth testing the exact scenarios your business needs in a sandbox before going live.
For a detailed setup walkthrough, see the Salesforce Promotions Console documentation.
The previous limit of 20 products during product discovery has been lifted. Teams that frequently add multiple products to a transaction can now select beyond 20 in a single operation, thanks to an updated Bulk Product Details API. This benefits implementations with large catalogs where users routinely build multi-product quotes.
Note! To increase the limit, contact Salesforce Customer Support. This is not a self-service admin setting.
The configurator receives several usability updates that improve the day-to-day experience for users working with complex bundles.
A persistent error component now stays visible as users scroll through configuration options, so validation errors and warnings are no longer hidden at the top of the page. The new compact layout reduces whitespace and fixes the position of key fields – Product Name, Quantity, Product Selling Model, and Net Price – while additional custom fields appear when expanding the option card.
These are not architectural changes, but for teams whose users spend significant time in the configurator, the effect on efficiency is noticeable.
Instant Pricing is not a new feature – it was introduced earlier to allow prices to recalculate in real time during line edits. The problem was that it had to be toggled on manually in every session, which meant that most sales reps either forgot about it or never used it at all.
Spring ’26 adds a single admin toggle: Instant Pricing Active by Default in Revenue Settings. Once enabled, every new quoting session starts with real-time price recalculation active. Quantity changes, attribute updates, and product additions are immediately reflected in pricing without saving.
Before Spring '26, Instant Pricing was off by default – users had to enable it manually each session, and prices updated only when they hit Save.
After Spring '26, admins can set Instant Pricing to active by default through Revenue Settings. Prices now recalculate in real time as users edit line items – no need to save first.
This is a small change on paper, but it eliminates the save-and-wait cycle that slowed down every pricing scenario. Sales reps exploring different configurations see results immediately. For implementations where quoting speed is a KPI, enabling this toggle is an easy win.
.png)
Configuration details are available in the Instant Pricing documentation.
Debugging pricing procedures has historically meant parsing Apex debug logs for relevant fragments. Spring '26 adds four log types to the Revenue Cloud Operations Console (formerly Pricing Operations Console) through the new Advanced Price Log Settings:
All four capture inputs, execution flow, and full exception details. You can turn them on in Setup under Salesforce Pricing – go to the Advanced Price Log Settings.
Note! These logs add processing overhead. Use them when you are actively investigating an issue, then switch them off. In production especially – leaving all four on "just in case" will cost you performance.
For setup details, see the Revenue Cloud Operations Console documentation.
You can now write conditional logic with nested IF statements directly inside a Formula-Based Pricing element. Before this, the same result required splitting the logic across multiple procedure steps or handling it externally – which made pricing procedures harder to read and slower to debug.
Procedure plans can now be included in deployment packages. If you manage separate dev, staging, and production orgs, this means you can promote your pricing workflow as a single unit instead of rebuilding it manually in each environment.
The previous limit was 10 conditions per approval step. For teams with complex approval matrices – different thresholds by region, product line, discount level, and deal size – 10 was not enough.
As a result, workarounds typically involved splitting logic across multiple steps or pushing conditions into custom flows. Spring ’26 raises the limit to 30, which should cover the majority of enterprise scenarios without architectural compromises.
When a record is resubmitted after rejection, the default smart-approval logic re-evaluates all conditions. In some cases – a minor price adjustment on an otherwise approved deal – this creates unnecessary delays.
Designers can now define custom auto-approval flows for resubmissions, using the new Get Previous Related Record Details invocable action to compare the current submission against the previous one and decide whether full re-approval is needed.
Approval notification emails can now use Lightning or Visualforce templates attached to individual steps or the overall workflow, covering up to eight notification types for submitters and reviewers.
Approvers receive structured emails with tables, record data, and formatting – enough context to act directly from their inbox rather than navigating back to Salesforce.
Before Spring ’26, billing frequency was tied to the product selling model. If a product was priced monthly, billing had to be monthly as well. This was a frequent source of friction for teams that needed to price granularly but bill on a different cadence.
Spring ’26 decouples these two settings. Sales reps can now select a billing frequency on the transaction that does not have to match the pricing frequency. Monthly pricing can be billed quarterly, semi-annually, or annually. The conversion only works from shorter to longer intervals – annual pricing cannot be billed monthly.
The configuration is controlled through a new field on the Billing Treatment object (CanChangeBillingFrequency), and requires the Billing Admin or Billing Operations User permission set.
Teams can now bill at the individual line level, giving each order item its own billing schedule. This means invoicing for delivered goods or services without waiting for the entire order to be ready. For organizations that combine physical products with services in a single order, this aligns billing with actual delivery and can improve cash flow.
The maximum output size for generated documents has been raised to 200 MB for PDF, DOCX, and PPTX files. This targets high-volume, media-rich use cases – detailed proposals with embedded images, technical specifications, or compliance documents – where teams previously had to split content across multiple files or assemble documents outside Salesforce.
This applies to Lightning Experience in Enterprise, Performance, Unlimited, and Developer editions with the Revenue Cloud Advanced or Revenue Cloud Billing license.
New features are only useful if they work in the context of your specific implementation. From our experience with Revenue Cloud projects, a few principles consistently apply when adopting release updates.
This is standard advice, but it matters more for features like Promotions, which interact with pricing procedures, approval workflows, and billing in ways that are difficult to predict without end-to-end testing.
When rolling out new capabilities to business users, create a complete scenario that exercises the feature from setup through quoting to billing. Demonstrating features in isolation leads to disconnected adoption and slower time-to-value.
Feature availability varies by edition, license, and entitlements. Promotions require a separate add-on license. Bulk product selection requires a Salesforce Support request. Verify availability for each customer before committing to a project plan.
Spring ’26 is not a revolutionary release, but it is a substantial one. The overall direction is clear: Salesforce is steadily filling the functional gaps that separated Revenue Cloud from its CPQ predecessor, while adding new capabilities – like promotions – that go beyond what the managed package offered.
For teams already on Revenue Cloud, the question is not whether these features are useful but which ones matter for your next sprint. Start with those that cut the biggest workarounds. That is exactly what the Veloce team helps clients figure out.
Are promotions available in all Revenue Cloud editions?
Not out of the box. You need the Global Promotions Management Basic Add On license on top of Revenue Cloud Advanced. Check your entitlements with Salesforce or your AE before building promotions into your project plan.
Does the Instant Pricing default toggle affect quotes that already exist?
No, it only applies to new quoting sessions. Any quote created before you flip the toggle keeps its previous pricing state until someone re-opens it.
Can I convert annual pricing to monthly billing with the new flexible billing feature?
Only the other way around. You can take a shorter pricing interval (monthly, quarterly) and bill on a longer cycle (semi-annual, annual). Going from annual pricing to monthly billing is not supported.
Is Revenue Cloud now called Agentforce Revenue Management?
Yes, officially. Salesforce rebranded it in Spring '26. The new name brings Revenue Cloud in line with Salesforce's Agentforce branding across all clouds.
How do I increase the product selection limit beyond 20?
You cannot do it yourself – this requires a Salesforce Support case. This is not a configuration setting available to admins.
Should I enable all four new pricing log types in production?
Only when you are actively debugging. Each log type adds overhead, so turn on what you need, get your data, and switch it off. In sandbox environments you can be less careful, but in production treat these as temporary.
.svg)
.png)
