Salesforce Industries CPQ Explained: How It Works and What Changes in 2026

What Is Salesforce Industries CPQ, and Which Clouds Include It?

It is the quoting and order-capture engine of Salesforce's subscription-heavy industry clouds: Communications Cloud, Media Cloud and Energy & Utilities Cloud. Salesforce describes it as part of each cloud's solution rather than a standalone product. It sits between the catalog that defines what you can sell and the order management that delivers it, and works across web shops, apps and agent consoles.

Salesforce agreed to acquire Vlocity, a provider of industry software built on the Salesforce platform, and after the deal closed announced that Vlocity is now known as Salesforce Industries. That is why many orgs still show vlocity_cmt objects and a "Vlocity" console, as in the screenshots below.

Salesforce's Communications cloud overview lists the pieces that work together:

Not every Communications Cloud feature needs Industries CPQ. Salesforce's setup guide says CPQ and EPC are required for some features but not all, so check each application you plan to deploy before you scope the catalog work.

How Is Industries CPQ Different from Salesforce CPQ and Revenue Management?

They are three separate products built for different sales models. Salesforce CPQ (the former SteelBrick) quotes SKU bundles for seller-led deals and is now end of sale for new customers. Revenue Management, formerly Revenue Cloud, is Salesforce's native revenue platform. Industries CPQ is the catalog-driven engine of the CME clouds, built for subscriptions, existing assets and network fulfilment.

Salesforce's own Salesforce CPQ end-of-sale page is precise about what changed: no new Salesforce CPQ licences for new customers, while existing customers can add users, renew and keep receiving support, with no forced migration. That page names Revenue Cloud Advanced as the successor; Salesforce Help now calls the platform Revenue Management (formerly Revenue Cloud). Its comparison with Salesforce CPQ advises treating any move as a redesign, not a copy of old configuration.

The overlap with Industries CPQ is growing. Help describes Revenue Cloud for Communications, part of Agentforce Communications, as extending the Revenue Management platform for communications service providers, and the Communications Cloud Advanced edition on Salesforce's pricing page includes Revenue Cloud Advanced for Communications. Section 11 covers what that means for an existing org. If your question is general quote-to-cash rather than telecom or utilities, our Salesforce Revenue Cloud guide and Salesforce CPQ guide cover those products.

How Does the Enterprise Product Catalog Shape Every Quote?

The catalog decides what a rep can sell, to whom, and in which combinations, before a price is calculated. Every Industries CPQ licence includes a shared catalog: one source of truth for commercial and technical product data, built from reusable product, service and resource components. The Enterprise Product Catalog (EPC) extends it with product lifecycle management, including versioning.

Three catalog capabilities do most of the work in a quote:

• Reusable building blocks. Product managers assemble offers from shared components instead of copying products. A broadband speed, a device and an installation service are defined once and reused across bundles, which keeps the catalog small as offers multiply.
• Commercial and technical layers. The catalog holds what the customer buys and the technical services and resources needed to deliver it. Order management later uses the technical layer to decompose orders (Section 08).
• Rules. Industries CPQ has two rules frameworks that work together, context rules and advanced rules. Between them they enforce availability and eligibility (what this customer may buy, for example at this address) and compatibility (which products can be combined). Salesforce's Industries CPQ Trailhead module notes that these rules show customers only offers they qualify for, reducing quoting errors and order fallout.

Product versioning matters once offers change over time. With versioning enabled, Industries CPQ builds product structures from each product's lifecycle status and version dates, and the reference date on the opportunity, quote or order decides which version a customer gets.

How Does Industries CPQ Handle Pricing, Discounts and Promotions?

Prices are assembled from reusable pricing components and resolved from the customer's context and the configuration they choose. Charges, discounts, adjustments, costs and penalties are defined once in the catalog. The pricing engine applies them per line, one-time and recurring, and a rep can still adjust a price on the quote when policy allows.

Salesforce's Industries CPQ documentation defines a discount as a price reduction that is negotiated, approved, activated and then applied, so approval design belongs in the pricing work, not after it. A 2026 release added applying promotions directly to a quote or order in Revenue Cloud for Communications, according to the Agentforce Communications release notes.

Which Industries CPQ Cart Should You Use: Angular, LWC or Enhanced LWC?

New implementations should use the Enhanced LWC CPQ, and orgs on the Angular cart should plan a move. Industries CPQ has three cart interfaces. Salesforce recommends Enhanced LWC CPQ for new customers because it uses native components and performs better with large bundles, and it states it is no longer investing in the Angular cart UI.

The trade-off is customisation against speed. The Flexcard-based LWC cart is highly customisable, but Salesforce notes performance limits with complex product bundles. Before choosing, compare the features you rely on in Salesforce's Industries CPQ feature comparison matrix (linked from the Industries CPQ overview), because a heavily customised Flexcard cart is the part that takes longest to move.

How Does Industries CPQ Quote Changes to Services Customers Already Have?

Through asset-based ordering: completed orders become assets, and every later change starts from those assets. When a customer wants faster broadband, a new location or a cancelled line, the rep opens the account's assets, changes them in the cart, and Industries CPQ creates a quote or order that records only what changes. This is the Move, Add, Change, Delete (MACD) pattern telecom and utility billing depends on.

Salesforce's asset-based ordering guide describes the cycle: opportunity, quote, order, then asset; to change an asset, it goes back to order status. The Change of Plans feature, also called Replace Offers, moves a customer from one plan or bundle to another without interrupting service. Service identifiers such as the mobile number and email address stay the same, common products are retained, and offer migration plans control which moves are allowed. Since Spring '22 it can replace plans in bulk, for example moving every customer on an old broadband plan to a new one in one order.

One detail causes rework if it is missed: the Replace Offers API copies attribute values only when the attribute names match between the old and new offers. Naming attributes consistently in the catalog is what makes plan migrations clean later.

How Does Multi-Site Quoting Work for Business Customers?

A master quote groups a customer's sites, a rep configures each group once, and Industries CPQ creates a child quote or order for every site. Groups can be built from service points, premises, service accounts or subscribers. Products, promotions and discounts added to a group are applied to all its members, so a 300-branch retailer gets one configuration instead of 300.

Steps follow Salesforce's multi-site quote and order guide. Two set-up points are easy to miss: usage pricing must be enabled before Multi-Site Quote and Order Capture is used, and developers processing many sites should use the MultiServiceAppHandler class, which Salesforce provides to scale cart processing to thousands of sites and orders. For large B2B telecom deals, Salesforce's Enterprise Sales Management application builds on this; 2026 releases added handling for larger orders and linking cloned quotes to opportunities.

What Happens After the Quote Becomes an Order?

Industries Order Management decomposes the commercial order into technical fulfilment requests and runs them through an orchestration plan. The order Industries CPQ creates is a commercial bill of materials. Order management adds the technical detail from the catalog, sequences the work across billing, provisioning and field systems, and reports status back to the quote and order in Salesforce.

• Point of no return. Before an order passes its point of no return, Industries CPQ can revise it in flight. After it, for example once equipment has shipped, a change order is needed. Defining that point per product is a design decision.
• Assetization. An order is assetized when its items become assets (commercial products) or inventory items (technical products). In Industries Order Management this happens through an Assetize auto task in the orchestration plan, as Salesforce's assetization article explains. Leave that task out and no inventory items are created.
• Your own order system. If you already run order management elsewhere, Industries CPQ includes integration tools to hand orders to it instead.

Salesforce is also extending Dynamic Revenue Orchestrator with a Decomposition Workspace, a Fallout Library and a Fulfillment Workspace. Our Communications Cloud order management service covers decomposition, orchestration, MACD and fallout design in more depth.

How Do APIs and OmniStudio Extend Industries CPQ?

APIs let web shops, apps and partner channels use the same catalog and pricing as reps, and OmniStudio builds the guided screens around the cart. Cart-based APIs expose browsing, configuring, pricing and ordering. Digital Commerce APIs handle high-volume anonymous browsing. TM Forum APIs connect the catalog to other BSS and OSS systems.

Sources: Salesforce's cart-based API guide and TMF620 API guide. If you integrate through the MuleSoft gateway today, plan the switch before Winter '27. All of these calls count against your org's API limits, so size channel traffic before launch.

OmniStudio supplies the guided experiences: OmniScripts for step-by-step selling and call scripts, Flexcards for the UI, and Integration Procedures for data calls. A typical example is a new-customer flow that captures details and checks serviceability before the cart opens.

For more on the toolset, see our OmniStudio guide, and for system connections, our Communications Cloud API and systems integration service.

What Does Industries CPQ Do for Energy and Utilities Companies?

It gives a customer a calculated price estimate before they sign up, even though their final bill depends on usage. Retail energy suppliers and regulated utilities use it to price commodity and non-commodity products for households and multi-site businesses. Salesforce notes that without it, quoting is either limited or needs a third-party pricing application.

Salesforce's Energy & Utilities Cloud CPQ article lists the utility-specific pieces: service points mapped in asset-based ordering, commodity unit-rate pricing in bundles, qualification rules that allow or block price adjustments, and multi-site orders. In a regulated market, the price also depends partly on the customer's location.

Our Energy & Utilities Cloud services cover the wider platform, from enrolment to field operations.

What Is Changing for Industries CPQ in 2026?

Three things: the names, the runtime and the platform underneath. Communications Cloud is now Agentforce Communications, Salesforce is moving every OmniStudio customer off managed-package runtimes, and new communications revenue features are being built on Revenue Management. None of this switches off Industries CPQ, but it changes what a sensible roadmap looks like.

For an org on the Vlocity-era stack, the practical question is sequence: cart upgrade, runtime migration, then any move to Revenue Management capabilities. Our Communications Cloud migration service runs both legacy-to-Salesforce moves and Vlocity-era runtime upgrades, with reconciliation as the deliverable.

Where Do Industries CPQ Implementations Usually Go Wrong?

Almost never in configuration, and almost always in early design decisions that are expensive to change later. The catalog model, rule structure and integration behaviour set the cost of everything built after them. These are the patterns we look for first when we review or rescue an Industries CPQ programme.

Our Communications Cloud implementation approach sets out the phases, deliverables and measurable go-live criteria we use to avoid these, such as order flow-through and changes your own team can make unaided.

Is Industries CPQ the Right Fit for Your Business?

It fits when you sell configurable services against an install base and fulfil them through downstream systems. It is more than you need when your catalog is small and orders end at a signed quote. The deciding factor is rarely company size; it is how often customers change what they already have and how much fulfilment the order must drive.

Our US telecom case study shows the second path. A mid-market digital services provider launching 5G SIM services needed SIM and subscriber records, reliable provisioning calls to Mavenir and automatic billing records in Alepo. We built ICCID and MSISDN custom objects in Sales Cloud, put MuleSoft between Salesforce and Mavenir with retry logic, and automated billing account creation. The case study reports activation time cut from 48 hours to 12 and 30% fewer provisioning failures in that engagement. Choosing the right tool for the catalog and order volume is part of the job.

1. 1

   Treat the catalog as architecture: design it, sign it off, and rationalise offers before you build.

2. 2

   Use Enhanced LWC CPQ for new work, and plan Angular cart replacement now.

3. 3

   Model MACD, Change of Plans and point of no return from day one.

4. 4

   Map your OmniStudio runtime migration, knowing the assistant does not move the standard CPQ app.

5. 5

   Check TM Forum integrations against the Winter '27 MuleSoft gateway deprecation.

Frequently Asked Questions