Comprehensive and Detailed Explanation From Exact Extract:
Revenue Management Intelligence (RMI) is Salesforce's analytics and insights layer for Revenue Cloud.
Documentation describes it as providing:
* End-to-end Quote-to-Cash analytics, including quoting, orders, billing, and payments.
* Dashboards for sales performance, revenue forecasts, and customer behavior.
* Pre-built and customizable KPIs across the revenue lifecycle.
Pricing Operations Console (A) focuses on pricing operations, not full Q2C analytics.
Revenue Lifecycle Management (C) is the product suite itself, not a reporting feature.
References:
Revenue Management Intelligence Guide - Overview and Use Cases
Revenue Cloud Product Documentation - Analytics for Quote-to-Cash

Salesforce Revenue Cloud introduces the Product Selling Model and Product Selling Model Option framework to help companies offer multiple purchase or subscription options for the same base product, reducing catalog sprawl. This approach is ideal for businesses that previously created multiple product records (e.g., separate SKUs for lease vs. buy) just to accommodate different pricing or selling logic.
With selling models, you define whether a product is sold as a one-time purchase, subscription (e.g., monthly, annual), lease, or usage-based. You can then attach multiple Selling Model Options to a single product, each reflecting a specific commercial approach (e.g., Lease Monthly, Term Annual, One-Time).
This allows the business to maintain a streamlined catalog while supporting diverse sales motions.
Option B refers to the decomposition process and is more relevant for fulfillment than pricing.
Option C (Multiple Price Books) enables regional or segmented pricing but doesn't solve the core problem of catalog sprawl due to multiple sales models.
Exact Extracts from Salesforce Revenue Cloud Documents:
* Subscription Management Implementation Guide - "Product Selling Models":"Selling Models reduce catalog complexity by allowing a single product to support multiple commercial options such as one- time, lease, or subscription."
* CPQ Implementation Guide - "Product Configuration Best Practices":"Use selling model options to attach different billing or pricing terms to a single product record rather than duplicating products." References:
Subscription Management Implementation Guide
Salesforce CPQ Implementation Guide
Revenue Cloud Product Catalog Strategy Notes

The recommended approach uses technical products with decomposition rules. According to Revenue Cloud fulfillment documentation, technical products are purpose-built for fulfillment and operational processes rather than commercial sale. User manuals in this scenario should be configured as technical products that accompany the commercial unassembled furniture product but are not visible as separate quote lines to customers.
Decomposition rules govern how commercial products (the unassembled furniture) break down into fulfillment components when an order is activated. By creating a technical product called "User Manual Inclusion" and establishing decomposition rules that link it to the furniture product, the system ensures that when an unassembled furniture order is created and activated, the decomposition process automatically includes the user manual technical product in the fulfillment decomposition.
This approach provides several advantages: customers see only the furniture product in their quote (not the manual as a separate line item), but during order fulfillment, the decomposition rules ensure that user manuals are included in the shipping package. Technical products do not appear in quoting interfaces, so they remain hidden from customer-facing documentation and proposals while still participating in fulfillment operations.
Option A (hiding quote lines) is not recommended because it adds unnecessary complexity to quotes and can cause confusion. Option B (attributes) doesn't support the fulfillment requirement; attributes describe product features, not orchestrate separate fulfillment items. Technical products with decomposition rules is the purpose-built Revenue Cloud mechanism for handling fulfillment-only items that shouldn't appear as commercial line items.
References: Revenue Cloud Fulfillment Documentation - Technical Products and Decomposition Rules, Dynamic Revenue Orchestrator decomposition configuration

Explanation (150-250 words)
* VPN License (quantity 5, non-editable): When a bundle quantity increases, the option must scale so total licenses multiply accordingly (e.g., bundle qty 2 × option qty 5 = 10 licenses). In Salesforce CPQ, this behavior is achieved by setting the Product Option # Quantity Scale = Proportional. Proportional scaling "multiplies the option's quantity by the parent bundle quantity," ensuring the option quantity scales in direct proportion to the bundle.
* Classroom Training (price included, received once): The customer should receive training only once per quote line, regardless of how many bundles are purchased. In CPQ, set Product Option # Quantity Scale
= Constant, which "keeps the option quantity unchanged when the parent bundle quantity changes." Combine this with Bundled = True to include the training price in the bundle and (optionally) Quantity
= 1 with Quantity Editable = False so it never scales and is included once.
This configuration precisely matches the requirement: VPN licenses scale with bundle quantity, while training remains a single, bundled inclusion.
Exact Extracts from Salesforce Revenue Cloud documents (field behavior, paraphrased):
* Quantity Scale - Proportional: option quantity scales with parent bundle quantity (multiplies).
* Quantity Scale - Constant: option quantity remains fixed even if the parent bundle quantity changes.
* Bundled = True: option price is included in bundle price.
Key Steps (concise)
* Option (VPN): Quantity = 5, Quantity Editable = False, Quantity Scale = Proportional
* Option (Training): Quantity = 1, Quantity Editable = False, Quantity Scale = Constant, Bundled = True References (document/source names only; no links)
* Salesforce CPQ Implementation Guide - Product Bundles and Options
* Salesforce CPQ Implementation Guide - Product Option Fields (Quantity, Quantity Editable, Bundled, Quantity Scale)
* Salesforce CPQ Implementation Guide - Bundle Quantity and Option Quantity Scaling

According to Salesforce Help documentation on "Product Catalog Management Personas for Revenue Cloud," the correct role segregation for effective governance uses specialized personas with distinct responsibilities.
The Catalog Administrator role manages classifications, attributes, and the broader catalog governance structure, while the Product Designer role focuses specifically on defining product structures and bundle configurations.
The Catalog Administrator persona administers Product Catalog Management, integrates Product Catalog Management features with other systems, maintains data integrity, and assigns permission set groups to other admins who handle specific areas of catalog management. This role ensures consistent governance across business units and markets. They control attribute definitions, product classifications, and reusable components that span the organization.
The Product Designer persona works within the governance framework established by the Catalog Administrator, focusing on designing specific product structures, configuring bundled products, and defining component relationships. Product Designers inherit standardized attributes and classifications from the Catalog Administrator and apply them consistently when building product offerings.
Option A (Product Managers owning all activities) creates bottlenecks and violates segregation of duties principles. Option C (Sales Operations managing attributes and Salesforce Admin managing bundles) splits responsibilities in a way that leads to inconsistency. The separation in Option B ensures that governance controls (classifications, attributes, reusability) are managed centrally by the Catalog Administrator while Product Designers execute within those controls, supporting scalability and preventing inconsistent updates across business units.
References: Salesforce Help - Product Catalog Management Personas for Revenue Cloud, Product Catalog Management Editions and Permission Sets documentation