Product-to-Cash Lifecycle and Revenue Cloud Fundamentals
Revenue Cloud exists to move a commercial idea from catalog to cash. Trace one order of events: a product is defined, priced in a price book, assembled on a quote, converted to an order and a contract, fulfilled as an asset or subscription, billed as an invoice, settled as a payment, and finally recognized as revenue. Candidates should be able to name the object at each hop and the event that triggers the hop.
Objects you must be able to place
Product2 (the sellable definition, not the price), Pricebook2 and PricebookEntry (price is a separate object), Quote and QuoteLineItem, Order and OrderItem, Contract and ContractLineItem, Asset, Subscription, Invoice and InvoiceLine, Payment.
Traps
- Product versus price. Product2 carries no price. A product can appear in many price books, each with its own entry. A question that says "change the price" expects a PricebookEntry, not Product2.
- Order is not always mandatory. Some flows quote straight to contract and subscription; do not assume every path passes through Order.
- Asset is a fulfilled instance. An asset is what the customer has; a subscription is the term-and-revenue view of the same thing. Related, not interchangeable.
- Revenue Cloud comes in generations. Classic CPQ plus Billing uses the objects above; newer offerings bundle catalog, pricing, configurator, transaction management, billing, invoicing, payments, and recognition. Answer using the terminology the stem uses.
Rule of thumb
One product, many price book entries, many quote lines. When asked where a value lives, walk one hop toward the price and ask whether the value is intrinsic (product) or contextual (book, quote, order).
Worked example
A product sells at $100 list in the standard price book and $90 in a partner book. The correct answer names two PricebookEntry records; the product itself holds no price at all.