Manufacturing Cloud and Revenue Cloud: quotes, sales agreements and rebates

3 November 2026
Youssef Elsewefy

Ask a manufacturer in Riyadh or Jebel Ali where a price comes from and you usually get three answers. The quote sits in an Excel file that a sales engineer built, with a freight figure someone typed in last quarter. The price list, orders and invoices sit in the ERP. And the annual volume deal with the biggest customer is a signed PDF in a shared folder. That works while costs are stable. When they move, nobody can tell you which open quotes and which agreements are now losing money.

They are moving now. In October 2026 Saudi purchasing managers reported the fastest rise in purchase prices in six months, driven by freight, insurance, raw materials and energy (our Manufacturing Outlook 2026-27 has the detail). This article is about the two Salesforce products that take over that work, Revenue Cloud and Manufacturing Cloud: which one does what, how a quote turns into a volume agreement, and what should stay in the ERP.

Which product does what

Revenue Cloud handles the deal itself: the product catalogue, prices, configuration, quotes, orders, contracts and billing. You will also see it called Revenue Management or Agentforce Revenue Management in Salesforce documentation, which admits the older name may still appear. The parts you will meet in a project are Product Catalog Management, Salesforce Pricing, Product Configurator, Transaction Management, Dynamic Revenue Orchestrator and Billing.

Manufacturing Cloud looks after the customer over the year. Its sales agreements, account forecasts, partner visits and warranty records answer the questions a sales director gets from the board every month: which accounts are behind plan, what each distributor will buy next quarter, and where margin is slipping.

Work	Where it runs	What it holds
Product catalogue	Revenue Cloud: Product Catalog Management	Products, attributes, classifications, simple and bundled products
Price	Revenue Cloud: Salesforce Pricing	Price books and price adjustment schedules, such as volume tiers
Configuration and quote	Revenue Cloud: Product Configurator and Transaction Management	Valid combinations of options, quote lines, discounts and approvals
Volume deal over time	Manufacturing Cloud: Sales Agreements	Planned quantities and revenue by period, compared with actuals
Account forecast	Manufacturing Cloud: Account Forecasting	A forecast per account built from history, agreements and pipeline
Rebates and channel stock	Channel Revenue Management for Manufacturing	Rebate programmes, claims, payouts and channel inventory
Orders, invoices, stock	The ERP	What was shipped, invoiced and paid

From quote to sales agreement

Most of the value is in the quote. Take a pipe systems maker pricing a tender: the fittings that suit each pipe class, the jointing method, the pressure rating. Those rules usually live with two or three senior engineers, which is why quotes queue up behind them. Product Configurator holds those rules, and in July 2025 Salesforce added a constraint-based engine next to the older rules-based one, with support for quotes of more than a thousand lines.

Once a customer commits to volumes for a year or more, the terms become a sales agreement, which Salesforce describes as a long-term, volume-based agreement tracking planned quantities, actual quantities and revenue. Actual quantities update through orders and contracts, and Manufacturing Cloud can also capture order information and realized pricing from the ERP, so the account manager sees price, cost and margin against plan before the quarter closes.

Getting from one to the other is documented. Manufacturing Cloud has a sales agreement conversion resource that creates an agreement from a quote, an opportunity or a custom object, using a mapping you set up. What Salesforce does not document is an automatic link from Revenue Cloud orders back to agreement actuals. On our projects we settle that early, in writing: which order lines count against which agreement, and whether actuals come from Salesforce orders or from ERP invoices.

Our default: take actuals from the system that ships and invoices the goods. In most of the region that is the ERP, so actual quantities and realized prices come from ERP invoices every night, and a Salesforce order that never reached the ERP does not count.

Orders and the ERP

An accepted quote becomes an order in Revenue Cloud. Dynamic Revenue Orchestrator splits the commercial products into the technical items that fulfilment needs, and a callout step can pass work to another system. For a manufacturer that system is almost always the ERP, and MuleSoft usually makes the call.

If you run SAP S/4HANA, look at the MuleSoft Accelerator for Manufacturing. It has use cases to sync accounts, products and orders into Manufacturing Cloud for account forecasting, and a rebate flow that creates the credit memo in SAP. Be aware that its latest release, 1.4, is from October 2023 and covers S/4HANA only, so we use it as a starting template. With Oracle, Infor or Dynamics you design the APIs yourself. The ownership rules we apply are the same either way. The ERP owns the price list, and Salesforce Pricing adds adjustments on top. Salesforce owns the quote and the agreement, and the ERP sends back deliveries, invoices and the prices actually charged. Freight and insurance go on the quote as their own lines or adjustments, so you can reprice them in one go when rates change.

Rebates, distributors and warranty

Check licences before you design anything for distributors. Rebates, payouts and channel inventory tracking are sold separately as Channel Revenue Management for Manufacturing, which Salesforce lists among the Manufacturing Cloud add-ons. Salesforce describes rebate programmes based on volume, growth or performance, with accruals, claims and settlements, and the settlement still ends in the ERP as a credit note.

After the sale, Warranty Lifecycle Management covers warranty terms, claim submission and adjudication, and dealers can file claims on an Experience Cloud portal. Installation and maintenance visits belong in Field Service; our guide to Salesforce for manufacturers covers that side.

If you are on Salesforce CPQ today

Salesforce CPQ is end of sale: new customers cannot buy it, existing customers keep support, fixes and renewals, and no end-of-life date has been announced. Revenue Cloud is the successor. There is no rush to move a CPQ setup that works, and when you do move, plan it as a rebuild of the product model, price rules and quote templates. We would start sooner in two cases: your products have outgrown what your CPQ rules can express, or you plan to sell service contracts or usage-based charges alongside equipment.

Our work with manufacturers

At Zahid Group, four business units now run leads, quotes, agreements and service cases on one Salesforce platform, with Manufacturing Cloud, Revenue Cloud CPQ, a customer portal and Infor M3 integration. For Johnson Controls we unified twelve line-of-business sales models on one governed platform across the region, and Hepworth, Qatar’s pipe systems maker, moved Sales Cloud into its own org, with Process Builder rebuilt as Flows and quotes generated in Mambo.

Where to start

Write down every input to a price: material, freight, insurance, duty and any local content premium. For each, agree whether it is an ERP price or a Salesforce adjustment, and who is allowed to change it.
Pick your ten hardest configurable products and write their rules out on paper. If those fit the configurator, the rest of the catalogue will.
Choose five run-rate customers with a signed volume deal and set up sales agreements for them, with actuals from ERP invoices.
Agree the order handoff with the ERP team: one accepted order, one ERP sales order, one status back.

Planning for 2026-27? The market numbers are in our Manufacturing Outlook 2026-27, and our manufacturing work shows what we have built. If you already run Salesforce, our Salesforce Health Check scores your org in ten working days. Or talk to our manufacturing team and send your RFP when you are ready.

Frequently asked questions

What is the difference between Manufacturing Cloud and Revenue Cloud?

Revenue Cloud runs the transaction: product catalogue, pricing, configuration, quotes, orders, contracts and billing. Manufacturing Cloud runs the account over time: sales agreements, account forecasts, partner visits and warranty.

Can a Revenue Cloud quote become a sales agreement?

Yes, through design. Manufacturing Cloud provides a conversion resource that builds a sales agreement from a quote, an opportunity or a custom object, using a mapping you define.

Is Salesforce CPQ being retired?

Salesforce CPQ is end of sale. New customers cannot buy it, existing customers keep support and renewals, no end of life has been announced, and Revenue Cloud is the successor.

Does Manufacturing Cloud include rebate management?

Rebates, payouts and channel inventory tracking are sold separately as Channel Revenue Management for Manufacturing, listed among the Manufacturing Cloud add-ons, so confirm your licences first.

Is Revenue Cloud the same as Agentforce Revenue Management?

Yes. Salesforce documentation uses Revenue Cloud, Revenue Management and Agentforce Revenue Management for the same product, and says older names may still appear.

Sources

Youssef Elsewefy

Youssef designs and builds Salesforce solutions with Flows, Apex and Lightning for airlines, manufacturers and healthcare providers. 6x Salesforce certified.