B2B Solution Architect Interview Questions

B2B Commerce Cloud (formerly CloudCraze) enables self-service purchasing portals for business buyers integrated with Salesforce CRM.

Storefronts: A storefront is a distinct buyer-facing commerce experience (URL, theme, catalog, pricing). A single org can host multiple storefronts for different brands, regions, or buyer segments.

Buyer Groups: Logical groupings of accounts that share the same entitlement policies, price books, and catalog visibility. An account is added to a buyer group to determine what it can see and purchase. One account can belong to one buyer group (current limitation).

Entitlement Policies: Define what products are visible and purchasable for a buyer group. They map buyer groups to product catalogs and specific price books. Without an entitlement policy, buyers cannot see products.

Catalog and Category Management: Products are organised into catalogs and categories. Entitlement policies control which catalog a buyer group can see. Categories provide the navigation tree on the storefront.

Order Management: B2B Commerce integrates with Salesforce Order Management (OMS) for order fulfilment, shipping, and returns. Orders created via the storefront become Salesforce Order records.

The CPQ quote-to-cash process covers the full revenue lifecycle:

1. Product Catalog: Products and bundles are configured in the CPQ product catalog with pricing, attributes, and rules.
2. Configuration: The sales rep adds products to a quote. Bundle configurator guides the rep through options. Product rules enforce valid configurations.
3. Pricing: The pricing waterfall applies: List Price → Discount Schedules → Price Rules → Manual Discounts → Net Price.
4. Quoting: A quote document is generated from a Quote Template (PDF or DocuSign). The quote is the formal offer to the customer.
5. Approval: CPQ Approval Processes route the quote for approval based on discount thresholds, deal value, or custom criteria.
6. Order: Once accepted, the quote is ordered (SBQQ__Quote__c → SBQQ__Order__c). Order products are created from quote lines.
7. Contract: An active contract is created from the order, capturing subscription terms and pricing. Contracted Prices lock renewal pricing.
8. Renewal: At contract end, a renewal opportunity and renewal quote are automatically generated (if renewal automation is enabled), pre-populated with contracted products and renewal pricing.

Product Rules automate product selection logic on the quote line editor:
- Validation: Blocks saving if an invalid product combination is selected. Evaluated on Save.
- Alert: Shows a warning but allows saving. Evaluated on Save.
- Selection: Automatically adds, removes, hides, or shows products based on other selections. Evaluated in the configurator as selections change.
- Filter: Dynamically filters the product catalog shown to the rep based on other quote fields. Evaluated when the product catalog is opened.
- Evaluation scope: Product/Quote (for bundle configurator) or Transaction (for the full quote). Conditions reference product fields; actions target product option fields.

Price Rules automate pricing logic — they inject calculated values into quote or quote line fields:
- Evaluated when the quote calculator runs (on quote save, product add/remove, or manual recalculate).
- Conditions: Define when the rule fires (based on quote field, quote line field, or summary variable values).
- Actions: Define what field gets updated and with what value (formula, lookup field, fixed value).
- Sort Order: Controls execution sequence. Lower sort order runs first. Critical when one rule's output feeds another rule's condition.

Revenue Cloud (formerly Salesforce Billing + CPQ + Revenue Lifecycle Management) covers the full quote-to-cash revenue lifecycle beyond quoting:

CPQ (Configure, Price, Quote): Configuration, pricing, and quote generation. The upstream module.

Salesforce Billing: Extends CPQ post-sale. Creates invoices from order products based on billing schedules (monthly, annual, usage-based). Handles payment processing (integration with payment gateways), revenue schedules (ASC 606 compliance), and dunning for overdue accounts.

Revenue Lifecycle Management (RLM): The newer, native revenue platform (not a managed package like CPQ). RLM is built on core Salesforce and supports dynamic revenue contracts, automated billing, revenue recognition, and subscription management — designed to eventually replace the legacy CPQ+Billing managed packages.

Contract Lifecycle Management (CLM): Manages the legal contract from creation through execution — integrated with CPQ output to automate contract generation, negotiation workflows, e-signature, and compliance tracking.

Key differentiator: RLM is native (no managed package namespace), more scalable, and designed for the future. CPQ+Billing remains widely deployed and will be supported for years, but new implementations should evaluate RLM first.

Territory Management 2.0 allows organisations to define sales territories, assign users and accounts to them, and integrate with forecasting.

Territory Model States:
- Planning: The territory hierarchy is being built. No impact on users or forecasting. Territories can be freely modified.
- Active: The territory model is live. Users are assigned to territories, accounts are mapped via filter rules, and territory forecasting is enabled.
- Archived: The model is retired. Historical data is preserved but the model is no longer used for assignments or forecasting. Only one model can be Active at a time.

User Territory Assignments: Users are assigned roles within territories (e.g., Account Executive, Overlay). Multiple users can be assigned to one territory; one user can be in multiple territories.

Opportunity Assignment: Opportunities are associated with territories via filter rules on the Account or via manual assignment. Territory determines which forecasting bucket the opportunity falls into.

Forecast Adjustments by Territory: Territory managers can adjust the forecast for their territory roll-up (adding manager judgment on top of rep-level forecasts), just like collaborative forecasting adjustments by role.

Collaborative Forecasting provides a hierarchical view of pipeline and revenue predictions aggregated up the role hierarchy (or territory hierarchy).

Forecast Categories: Opportunities roll into forecast categories: Pipeline, Best Case, Commit, Closed Won (and Omitted). Each stage maps to a category; sales managers track the hierarchy roll-up per category.

Opportunity Splits: Allow the opportunity revenue to be split among multiple team members. The split percentages must total 100%. Revenue splits affect each team member's individual forecast — their quota attainment is based on their split amount, not the full opportunity value. Useful for co-sold deals.

Overlay Splits: For sales engineers, solution consultants, or overlay reps who contribute to a deal but are not the primary owner. Overlay splits can exceed 100% and do not reduce the primary rep's credit. They feed separate overlay forecast roll-ups. Useful for tracking SE contribution to revenue.

Forecast Adjustments: Managers can adjust the rolled-up forecast for their team (manager adjustment) without changing the underlying opportunities. Adjustments are visible in the forecast grid with audit trail.

Partner Community architecture enables channel managers to manage resellers, distributors, and partners via an Experience Cloud portal:

Licensing: Partner Community licences support full CRM object access (Leads, Opportunities, Contacts) with sharing rules and role hierarchy. Partner users are external users with their own profile and role in the Partner Community role hierarchy (below the internal hierarchy).

Channel Manager: An internal Salesforce user who manages one or more partner accounts. The channel manager is the bridge between internal data and partner visibility.

Partner Score: PRM (Partner Relationship Management) includes a partner scoring model that rates partner performance based on certifications, deal registrations, and revenue attainment. Displayed in the partner portal.

Deal Registration: Partners submit deal registrations (Leads/Opportunities) via the portal. Internal teams review, approve, and assign. Prevents channel conflict (two partners registering the same deal).

MDF (Market Development Funds): Partners request MDF from the portal. Approval workflows route requests to channel managers and finance. Approved funds are tracked against partner budgets.

Data sharing: Use Partner Community role hierarchy + sharing rules to ensure partners only see their own leads and opportunities. Never share cross-partner data.

Account Engagement (Pardot) is Salesforce's B2B marketing automation platform. Integration with Sales Cloud enables aligned marketing and sales processes:

Connector: The Salesforce-Pardot connector syncs data bi-directionally. Prospects in Pardot map to Leads/Contacts in Salesforce. Field mappings are configured in Pardot's Salesforce connector settings.

Synced Fields: Specific Prospect fields sync to corresponding Lead/Contact fields. Field sync behaviour is configurable: Pardot wins, Salesforce wins, or most recently updated wins. Changes trigger sync within minutes.

Campaign Influence: Account Engagement tracks which marketing touches (emails opened, forms submitted, webinars attended) contributed to opportunity creation and progression. Campaign Influence models (First Touch, Last Touch, Even Distribution, or custom) attribute revenue credit to marketing campaigns.

Pardot Activities in Salesforce: Pardot activities (email sends, clicks, form submissions) appear on the Contact/Lead record in Salesforce as Engagement History, providing sales reps full visibility into prospect behaviour before outreach.

Engagement Studio: Marketing journey automation in Pardot (email drip campaigns, conditional branching based on prospect behaviour) feeds scored and nurtured leads into Salesforce when they reach Sales-Qualified Lead status.

Marketing Cloud Connect is the standard connector between Salesforce Marketing Cloud (SFMC) and Sales Cloud. It enables:

- Synchronized Data Extensions: Salesforce CRM data (Contacts, Leads, Campaigns) is pushed to Marketing Cloud as synchronized Data Extensions using the Marketing Cloud Connect connector.
- Journey Builder triggers: Salesforce Campaign membership changes, record field updates, or Platform Events can trigger Marketing Cloud journeys.
- Tracking data back to Salesforce: Email opens, clicks, and unsubscribes in Marketing Cloud flow back to Salesforce Contact/Lead records as Campaign Member activity.

Data Cloud (CDP) as the backbone: For enterprise B2B, Data Cloud ingests data from Marketing Cloud, Sales Cloud, Service Cloud, and external sources, unifies B2B account and contact profiles, and activates segments back to Marketing Cloud for personalised campaign execution. This replaces the point-to-point Marketing Cloud Connect pattern with a centralised data hub.

MCA (Marketing Cloud Account Engagement) connector: Newer connector providing tighter integration between Pardot (Account Engagement) and Marketing Cloud for organisations using both platforms for different market segments.

Einstein Opportunity Scoring: An AI model that scores each open opportunity (0–99) based on historical win/loss patterns, activity signals (email, meetings, calls), competitor mentions, and deal characteristics. Sales reps see a score on each opportunity with key positive and negative factors. Sales managers use the score to identify at-risk deals and prioritise coaching.

Scoring requires a minimum of 200 closed opportunities to build an initial model. The model retrains periodically as new data accumulates. Custom fields can be added to the model (in Einstein Setup) to improve accuracy for the specific business.

Einstein Account Insights: Surfaces AI-generated news and business insights about a B2B account — recent company news (mergers, funding, leadership changes, product launches) relevant to the sales motion. Insights appear on the Account record and in the Einstein Insights panel. Helps reps personalise outreach with timely, relevant context.

Key implementation consideration: Both features require Sales Cloud Einstein licence. Einstein Activity Capture (email/calendar sync) must be configured to feed activity signals into the scoring model. Ensure users understand the model's confidence level and treat scores as guidance, not absolutes.

Tableau CRM (formerly Einstein Analytics) provides embedded analytics within Salesforce, built on a columnar in-memory analytics engine.

Pipeline analytics use cases:
- Pipeline Inspection: Visualise open pipeline by stage, owner, close date, and forecast category. Identify deals with no recent activity.
- Win/Loss analysis: Analyse closed opportunity patterns by product, industry, competitor, and rep to identify winning and losing deal characteristics.
- Forecast vs. Actual: Compare forecasted revenue to actual closed revenue by time period, region, and product line.
- Deal Velocity: Average time opportunities spend in each stage. Identify bottleneck stages where deals stall.

Data sources: Tableau CRM dataflows ingest Salesforce CRM data (Opportunities, Activities, Users, Accounts). External data can be loaded via the External Data API for combined analytics.

Einstein Discovery integration: Augment dashboards with AI-generated story insights — factors driving pipeline changes, predicted outcomes, and recommended next actions embedded directly in dashboard widgets.

Embedded in CRM: Analytics dashboards can be embedded on Opportunity, Account, and Home pages for in-context insights without leaving the CRM.

Slack for Salesforce (via the Slack-Salesforce integration) brings CRM data into team communication:

Sales Cloud for Slack: Sales reps can view and update Salesforce records directly from Slack. Receive deal alerts (opportunity stage change, new lead assignment) in Slack channels. Post CRM updates without switching apps.

Deal Room Automation: When a high-value opportunity reaches a certain stage (e.g., Proposal), a Flow automatically creates a Slack channel (Deal Room) and invites relevant team members (AE, SE, CSM, Legal). The Slack channel has pinned links to the Salesforce opportunity, quote, and related documents. Stage advancement and key events post automated updates to the channel.

Slack Connect for External B2B Collaboration: Slack Connect allows creation of shared channels with external organisations (customers, partners). This enables real-time collaboration on deals — removing email friction for large B2B deals where both sides have Slack.

Agentforce in Slack: Agentforce agents can be invoked from Slack (e.g., @Einstein, ask about account health or generate a deal summary), bringing AI-powered CRM intelligence into the collaboration layer.

Field Service Lightning (FSL) and CPQ integration enables end-to-end service revenue management:

Work Order integration with CPQ: When a field service work order is created for a piece of equipment or service delivered to a B2B customer, billable work order line items can feed back into a CPQ quote for the service engagement, enabling accurate billing. Service products (installation, maintenance) are configured in CPQ and quoted alongside equipment.

Service Contracts from Renewals: When a CPQ-contracted subscription reaches renewal, the renewal quote can include service contract products (maintenance plans, SLAs). Upon ordering, Salesforce generates a Service Contract record linked to the asset. Field Service dispatchers use the Service Contract to determine coverage entitlements when scheduling work orders — e.g., is this customer's equipment covered under an active SLA?

Entitlement Management: Service contracts define entitlements (response time SLAs, number of service incidents). Work orders check entitlements to determine priority and coverage. CPQ drives what's in the entitlement; FSL enforces it operationally.

Unified asset record: The Salesforce Asset object (installed product) is the common link between CPQ contracted products, Field Service work orders, and billing.

A comprehensive B2B distributor portal combines multiple Experience Cloud capabilities:

Reseller Portal: Partners log in to view their assigned leads, opportunities, price lists (custom price books by tier), product documentation, and co-branded marketing materials. Data sharing ensures partners only see their own records.

Deal Registration: Partners submit a Deal Registration (custom object or Lead) to claim a prospect. The channel manager reviews in Salesforce. Duplicate logic prevents two partners registering the same deal. Approval flow notifies the partner of registration status. Accepted registrations convert to Opportunities assigned to the partner.

MDF (Market Development Fund) Requests: Partners submit MDF requests (custom object) via the portal with event details, target audience, and requested funding amount. Multi-level approval (channel manager → regional marketing → finance). Approved funds tracked against partner budget. Post-activity proof of execution submitted for fund disbursement claim.

Training and Certification: Trailhead or third-party LMS embedded in the portal to track partner training completion. Certification status updates the partner score.

Security: Partner Community Plus licences for full sharing model support. OWD Private for Leads and Opportunities. Sharing sets or sharing rules grant partners access only to their own records. Guest user access disabled for sensitive objects.

Data Cloud for B2B ABM enables unified account profiles and targeted segment activation:

Data Ingestion: Data Cloud ingests data from Salesforce CRM (Accounts, Contacts, Opportunities), Marketing Cloud, Account Engagement, website analytics, and third-party intent data providers (Bombora, 6sense) via Data Cloud connectors or Data Stream APIs.

Account Profile Unification: Data Cloud's Identity Resolution maps and merges duplicate account records across sources into a Unified Account Profile. This is the single source of truth for an ABM target account — combining firmographic data, CRM data, and intent signals.

Account-Based Segmentation: Build segments in Data Cloud based on account attributes (industry, revenue, technology stack) AND intent signals (topics researched, competitor consideration). Segments can be at account level (all contacts at target accounts) or contact level within target accounts.

Activation: Activate segments to Marketing Cloud for personalised email/advertising campaigns, to LinkedIn Campaign Manager for matched audience advertising, or to Salesforce Sales Cloud to automatically create Tasks and flag high-priority accounts for reps.

Measurement: Data Cloud tracks which ABM segments convert to opportunities and revenue, enabling closed-loop ABM measurement.

Single-org advantages for B2B: Unified 360-degree account view across regions, no cross-org data synchronisation complexity, shared master data (Products, Price Books, Accounts), centralised reporting and analytics, consistent process enforcement.

Multi-org drivers:
- Data residency / compliance: GDPR, local data sovereignty laws may require European customer data to remain in EU infrastructure. Salesforce Hyperforce enables regional data residency within a single org — evaluate Hyperforce before defaulting to multi-org.
- Business unit autonomy: Acquired companies with distinct CRM processes, separate sales motions, or conflicting data models that would require excessive customisation to reconcile.
- Regulatory separation: Financial services or healthcare organisations where different business units have strict data separation requirements.
- Scale limits: Organisations approaching 800 custom objects, extreme API volumes, or storage limits may need to split workloads.

Multi-org costs: Master data management (Account deduplication across orgs), cross-org reporting requires external data warehouse, double licence costs for shared services, complex release management.

Recommendation: Start with single-org + Hyperforce for data residency. Only introduce multi-org when regulatory, security, or process conflicts are genuinely irreconcilable.

Building an AppExchange-listed B2B vertical solution requires packaging, licensing, and go-to-market architectural decisions:

Managed Package: Use a managed package with a namespace. Source code (Apex classes, triggers, LWC) is obfuscated to protect IP. Supports upgradeable versioning — subscribers receive updates via package upgrades.

Packaging strategy: Separate the base package (core data model, core logic) from feature packages (premium features, vertical add-ons). This allows tiered pricing and modular deployment.

License Management App (LMA): Install LMA in the ISV's Partner Business Org to manage subscriber licences (trial, active, expired). Configure licence enforcement in Apex using UserPackageLicense checks.

Security review: Pass the Salesforce AppExchange security review (SOQL injection, FLS, XSS, CSRF checks). Integrate Salesforce Code Analyzer into CI/CD pipelines early to catch security issues before review.

Subscriber data model: Minimise post-install metadata footprint. Custom objects contribute to the subscriber's 800-object limit. Use Custom Metadata Types for configuration (metadata deploys with the package).

Partner Portal: Use Salesforce Partner Community for deal registration, trial provisioning, and customer onboarding. Environment Hub manages multiple subscriber org connections for support.

CPQ-to-ERP integration covers the handoff from Salesforce's quoting/ordering layer to the ERP's fulfilment and financial layer:

Order fulfilment handoff: When a CPQ Order is activated in Salesforce, a Platform Event or outbound callout notifies the ERP (SAP S/4HANA or Oracle ERP Cloud) to create a Sales Order. The ERP assigns an order number that is written back to the Salesforce Order record.

Invoice and payment: The ERP generates invoices. If using Salesforce Billing, invoices are generated in Salesforce and payment data syncs from ERP/payment gateway. If ERP owns billing, invoice data flows back to Salesforce for 360-degree customer view.

Revenue recognition: ERP typically owns the revenue recognition engine (ASC 606 / IFRS 15 compliance). Salesforce Billing can handle rev rec but for regulated industries, ERP may be the system of record for financial recognition.

Integration patterns: Use MuleSoft for the integration layer — SAP Connector and Salesforce Connector provide pre-built adapters. Alternatively, Salesforce Platform Events + SAP Integration Suite (SAP BTP). Always implement idempotency keys on order messages to prevent duplicate ERP orders from Salesforce retries.

Master data sync: Product master, customer (Account) master, and price lists must remain consistent between Salesforce and ERP. Define the system of record for each data domain before implementation.

An event-driven B2B architecture decouples the order, CPQ, and entitlement systems:

Order Status Events: When an ERP processes an order (packed, shipped, delivered), it publishes a Order_Status__e Platform Event to Salesforce. A Platform Event-triggered Flow or Apex trigger updates the Salesforce Order record status and triggers customer notification automations. Decouples ERP timing from Salesforce UI refresh.

CPQ Calculation Events: For complex pricing scenarios that require external system input (e.g., real-time inventory pricing from ERP), a CPQ Price Rule can invoke an Apex action that publishes a calculation request event. An external system subscribes via CometD, calculates the price, and pushes back the result via a REST callout to Salesforce, which then re-triggers the CPQ calculator.

Entitlement Change Events: When a contract is amended or a subscription is upgraded in CPQ, a Entitlement_Change__e event notifies downstream systems (ERP licence server, Field Service entitlement engine, partner portal) to update the customer's entitlements synchronously. Each subscriber handles their own domain without coupling.

Architecture principle: Define clear event schemas (event name, payload fields) and use a service catalogue approach to document producers and consumers. Prevent event payload bloat — include only the data needed for subscriber decision-making, not full record copies.

Renewal automation in CPQ minimises manual effort for recurring revenue management:

Renewal Opportunity: CPQ automatically creates a renewal Opportunity from an active Contract when the contract's SBQQ__RenewalForecast__c checkbox is enabled (or via scheduled job). The renewal Opportunity has Close Date = Contract End Date and references the parent contract.

Renewal Quote: From the renewal Opportunity, CPQ generates a renewal Quote pre-populated with the contracted products, quantities, and renewal pricing. Renewal Pricing methods: Same (contracted price), List (current list price), Uplift (contracted price + % increase configured on the contract or product).

Renewal Term: The renewal quote term defaults to the original subscription term. Configurable per product or per contract.

Co-termination: When new products are added mid-contract via an Amendment Quote, co-termination aligns the new product's subscription end date with the existing contract end date. CPQ calculates a prorated price for the partial period. On renewal, all products share the same end date — eliminating mismatched renewal dates that create operational complexity.

Evergreen subscriptions: Products with Subscription Type = Evergreen do not create renewal opportunities. They continue indefinitely until explicitly cancelled, triggering an amendment or cancellation quote.

B2B master data management (MDM) for Accounts is a foundational architecture challenge in multi-cloud and multi-org environments:

System of Record: Designate one system as the authoritative source for Account master data — typically Salesforce CRM (Sales Cloud). Other systems (Marketing Cloud, B2B Commerce, ERP) are consumers, not owners, of Account data.

Deduplication: Enable Salesforce Duplicate Rules and Matching Rules on Account to prevent duplicate creation. Use Data Cloud's Identity Resolution for cross-system account deduplication (matching on company name, domain, D-U-N-S number).

Account hierarchy: Model Account hierarchy using the Parent Account lookup. Global accounts (HQ) → Regional subsidiaries → Local entities. This structure drives territory management, forecasting roll-ups, and pricing entitlements.

Data enrichment: Integrate with D&B, ZoomInfo, or Salesforce's Dun & Bradstreet connector to keep firmographic data (company size, industry, revenue) current.

Governance: Define Account ownership rules (who can create, merge, edit global accounts). Implement validation rules and approval processes for account creation to prevent free-form entry. Regular data quality reports (incomplete accounts, potential duplicates) assigned to data stewards.

High-volume CPQ deployments require architectural optimisation across the pricing engine, data model, and integration layers:

Reduce Price Rule complexity: The CPQ Quote Line Calculator runs server-side and evaluates all active Price Rules on every save. Minimise the number of active price rules and use efficient conditions. Deactivate rules not needed for specific product families using filter conditions.

Batch pricing calculations: For programmatic quote generation (B2B Commerce → CPQ quotes), use the CPQ Calculate API (SBQQ.QuoteAPI.calculate()) to trigger pricing calculations server-side without user interaction, and control timing to batch multiple line additions before triggering calculation.

Product filter optimisation: Use Product Filter rules with pre-filtered product lists rather than large dynamic queries. Optimise the SOQL behind product filters with indexed fields.

Governor limits at scale: Each CPQ quote save context consumes Apex CPU time. Monitor Apex CPU limits in the CPQ calculator log. Large bundles with many options + complex pricing rules can approach limits. Consider splitting complex bundles into smaller modular bundles.

Async quote generation: For API-driven mass quoting, generate quotes via Queueable Apex with chaining — queue one quote at a time with result callbacks rather than generating all quotes synchronously in one transaction.

Data Cloud's core value proposition for B2B is building a Unified Individual (contact) and Unified Account profile from fragmented data across touchpoints:

Data Ingestion: Data Streams pull data from Salesforce CRM (Contact, Account, Opportunity, Activity), Marketing Cloud (email engagement, journey data), Account Engagement (Pardot prospects, form fills), external sources (website analytics, intent data, event attendance) via API or file upload.

Identity Resolution: Matching rules identify records that likely represent the same real-world person or company across data sources. Match on: email address, phone number, company domain, name + company combination. Resolution Rules define how to merge matched records into a Unified Individual (contact) and Unified Account. Reconciliation Rules determine which source wins for each field (most recent, most frequent, preferred source).

Calculated Insights: Run aggregate computations over the unified data (e.g., total email engagement score, total opportunity value, days since last activity) as stored metrics on the Unified Profile.

Activation: Activate unified profiles and segments to Marketing Cloud (personalised campaigns), Sales Cloud (update Account scores), and Agentforce (ground agent responses with unified account context).

Vector Database: Store unstructured account data (call transcripts, email text) as vector embeddings in Data Cloud Vector Database for semantic search and RAG in Agentforce.

A Configure-to-Order (CTO) process for B2B manufacturing requires orchestrating configuration, quoting, and production across systems:

B2B Commerce configurator: The buyer self-configures a product on the B2B Commerce storefront (colour, dimensions, material, accessories). Configuration selections map to CPQ product options via the Commerce-CPQ bridge.

CPQ Quote generation: When the buyer adds a configured product to the cart and requests a formal quote, B2B Commerce triggers CPQ via API to generate an SBQQ__Quote__c with the configuration translated to CPQ product options and pricing. The quote is surfaced back to the buyer for review and approval.

Order to Manufacturing: When the quote is accepted and ordered, a Platform Event (ConfiguredOrder__e) notifies the manufacturing execution system (MES) or ERP. The event payload includes the product configuration specifications (BOM — Bill of Materials). The MES creates a work order for production.

Production status back to Salesforce: Manufacturing status updates (In Production, QA, Ready to Ship) are pushed back to Salesforce via the Salesforce REST API, updating the Order record and triggering customer notifications via Flow (email, SMS, portal notification).

Asset creation: Upon shipment, a Salesforce Asset record is created, linking the manufactured product to the Account for warranty tracking, field service entitlement, and future renewal quoting.

RevOps architecture aligns Marketing, Sales, and Customer Success on a unified data and process platform:

Unified funnel: Marketing (Account Engagement/Marketing Cloud) → MQL → Sales (Sales Cloud + CPQ) → Closed Won → Customer Success (Service Cloud + CPQ Renewals). Every handoff is automated via Flow, with full audit trail.

Single source of truth for revenue: Salesforce Opportunity + CPQ Order + Contract as the authoritative revenue record. All downstream systems (Finance, ERP) derive from this. Eliminates "two versions of the number" between Sales and Finance.

Forecasting: Collaborative Forecasting (with territory adjustments) + Einstein Forecasting (AI-predicted close probability) combined into a single forecasting view. Sales managers adjust; Finance snapshots via Report runs for period-close submissions.

Analytics: Data Cloud aggregates all touchpoint data; Tableau CRM (Einstein Analytics) provides RevOps dashboards: pipeline health, forecast accuracy, conversion rates by stage, CAC (customer acquisition cost), LTV (lifetime value), NRR (net revenue retention).

Process governance: Revenue playbooks built as Flows (onboarding, escalation, renewal) ensure consistent execution regardless of rep. Slack Deal Rooms for cross-functional collaboration. Einstein Conversation Insights surfaces call coaching data for RevOps to identify process gaps.

Key success factor: RevOps architecture succeeds only when Marketing, Sales, and CS agree on definitions (MQL, SQL, ARR, Churn) before building. Governance over data hygiene and process adherence is as important as the technical implementation.