01Salesforce CPQ was renamed Revenue Cloud Advanced (RCA) — what changes?+
Yes. The product formerly known as "Salesforce CPQ" (internally SteelBrick CPQ, acquired 2015 and shipped as a managed package) is superseded by **Revenue Cloud Advanced** — not just a rename, but a full rebuild on Core Platform / OmniStudio, with performance, scalability, and native Manufacturing Cloud integration a generation better than legacy CPQ. RCA also consolidates **Configure-Price-Quote + Contract Lifecycle Management (CLM) + Billing + Subscription** into one product line. **For new implementations (2024+):** Salesforce no longer sells legacy CPQ to net-new customers; new programs go straight to RCA. **For existing CPQ tenants:** legacy CPQ remains supported, but RCA migration is the long-term direction — typically planned over a 24–36 month migration window. For manufacturers on legacy CPQ, the first conversation is usually about the RCA migration path.
02Where does Manufacturing Cloud’s product surface actually end?+
Manufacturing Cloud is a complete product family, not just "the Sales Agreements object." It includes at minimum: (1) **Sales Agreements** — long-cycle committed volume vs actual shipments vs remaining; (2) **Account Manager Targets** — account-level sales quotas, roll-up to region / product line; (3) **Account-Based Forecasting (ABF) + Advanced Account Forecasting (AAF)** — AAF is the newer version, Data Cloud-native, blending actuals + forecast + predictive models; (4) **Manufacturing Cloud for Service** — Service Console + Asset Service Management built for manufacturers; (5) **Program-Based Business** — milestone schedules for multi-year OEM / aerospace / defence programs; (6) **Rebate Management** — channel rebates, sales incentives, MDF calculation + reconciliation; (7) **Partner Performance Management** — dealer scorecards and partner portal. Choosing which to deploy first is the real consulting work — not "install everything."
03How to control Revenue Cloud Advanced complexity?+
Runaway RCA remains the most common manufacturing-Salesforce incident — product managers want "every spec combination configurable," leading to thousands of product rules, hundreds of price rules, performance collapse, sales abandonment, exploding maintenance cost. RCA’s engine is generationally better than legacy CPQ, but the "business complexity" problem is the same. Practical rules: (1) Day-1 "total rule budget" — exceed it and cut specs, not add rules; (2) 90%-volume SKUs go through RCA guided selling, long tail goes quote-on-request; (3) rule ownership belongs to the product PM, not the Salesforce consultant; (4) pricing exceptions live in a separate approval flow, not in RCA; (5) use RCA’s CLM module to template contracts so each agreement does not start from zero.
04Account-Based Forecasting vs Advanced Account Forecasting (AAF) — what differs?+
Both are Manufacturing Cloud’s "account-level forecasting" (not SKU-level demand planning — that stays in ERP / APS). Difference is the technical foundation: (1) **ABF** is Manufacturing Cloud’s built-in feature, running on Salesforce Core Platform, integrating Sales Agreements and Account Manager Targets — sufficient for mid-sized / mid-complexity manufacturers; (2) **Advanced Account Forecasting (AAF)** is the newer version, **Data Cloud**-native, capable of joining large ERP fact tables and ingesting external signals (market sentiment, raw-material pricing, seasonality) for hybrid forecasts. If you have >10K customer accounts, >5K SKUs, or need ML forecast models in the loop, AAF is right. AAF requires Data Cloud licensing and lakehouse buildout — both cost and timeline higher than ABF. Most clients launch ABF for 12–18 months then evaluate AAF upgrade once the business is mature.
05Asset Service Management + run-rate business — what is it, and who fits?+
For many manufacturers the "post-sale run-rate business" (warranty service, preventive maintenance, parts replenishment, technical support) is the actual cash cow — yet long-managed in Excel + email + custom apps. **Manufacturing Cloud for Service + Asset Service Management** is designed for it: every installed unit (Asset) carries its own lifecycle, warranty window, maintenance schedule, parts BOM, and case history; Service Console for Manufacturing wires case routing, parts lookup, field dispatch (Field Service), and warranty rulings into one flow. Fits: (1) industrial / medical / capital-equipment OEMs with large installed bases; (2) clients with heavy parts-replenishment + preventive-maintenance contracts; (3) clients moving service from cost-centre to profit-centre. Overkill for SaaS / pure-B2C manufacturers.
06Rebate Management + Partner Performance Management — what do they solve?+
Two long-running pain points for channel-driven manufacturers (appliances, auto parts, consumer-electronics OEMs, industrial consumables): rebates miscounted / late, and dealer performance not comparable. **Rebate Management** turns rebate rules (tiered incentives, target bonuses, special contract incentives, MDF) into computed objects — every sale flowing in instantly accrues against each partner, so month-end reconciliation moves from "redo the Excel" to "approve the amount." **Partner Performance Management** gives each dealer a scorecard (attainment rate, complaint rate, return rate, replenishment lead time) surfaced in the Experience Cloud Partner Portal — dealers see their own performance and the gap to target. Combined sweet spot: "within 3 months, channel relationships move from opaque to governable" — often a faster ROI than RCA itself.
07How do ERP (SAP / Oracle) and Manufacturing Cloud divide responsibilities?+
ERP always owns orders, inventory, production scheduling, finance — Manufacturing Cloud should not duplicate. Manufacturing Cloud sits at: pre-sales (RCA quoting, Sales Agreements) + relationship (Account 360, AMT, ABF / AAF) + channel (Rebate, PPM, partner portal) + service (Asset Service Management, Field Service). Integrate event-driven (MuleSoft / Platform Events) on ERP order-create, shipment-confirm, invoice events — nightly batch leaves sales seeing yesterday’s inventory. Bi-directional sync needs idempotency keys — RCA pushing orders back to ERP is the highest-incident path. Data Cloud can serve as the fact-table alignment layer between the two systems, especially for ERP historicals that AAF needs.
08You have no published manufacturing case — is that a risk?+
Honest answer: we have no publicly referenceable manufacturing case. But our work in financial services (FSC + compliance + core system integration), retail / consumer goods (Taiwan’s first CGC Enhanced + Service Cloud consolidation), government / public sector (PSS + cross-agency case routing + strict sharing rules), and transport / logistics (B2B carriage agreements + tracking-event integration) built the discipline for long-cycle B2B, complex data models, strict sharing, and ERP / core integration — the same problems that appear in Manufacturing Cloud + Revenue Cloud Advanced + ERP integration. We are also familiar with the entire Manufacturing Cloud product family by design intent (Sales Agreements / AMT / ABF / AAF / Asset Service Management / Program-Based Business / Rebate / PPM). Manufacturing-specific domain (production-planning vocabulary, industry standards, specific OEM ecosystems) we will learn alongside your team from week one.