Product and Revenue Schedules

Why Product and Revenue Schedules Matter
Not every sale is a single, one-time delivery with revenue recognized on one day. A company might sell a 12-month software subscription paid monthly, a training package delivered in six sessions, or 500 units of hardware shipped in five batches. In all of these cases the Opportunity Product (opportunity line item) represents one deal, but the timing of the quantity delivered or the revenue earned is spread across a period. Product and Revenue Schedules are the native Salesforce feature that lets an organization model this timing directly on the opportunity product. For the Advanced Administrator exam, this topic sits inside the Advanced Cloud Applications / Sales Cloud domain and tests whether you understand when schedules are appropriate, how they are enabled, how they behave once created, and how they affect opportunity amounts, forecasting, and reporting.

What Product Schedules Are
A schedule is a set of installments attached to an Opportunity Product. Each installment has a date and either a quantity, a revenue amount, or both. Salesforce supports two schedule types:

1. Quantity Schedules - Used when a product is delivered in increments over time. Example: 120 licenses delivered 10 per month for 12 months.
2. Revenue Schedules - Used when revenue is recognized or billed over time. Example: a $12,000 annual maintenance contract recognized at $1,000 per month.

You can use quantity schedules alone, revenue schedules alone, or both together on the same product. Schedule records are stored in the OpportunityLineItemSchedule object, which has fields such as Schedule Date, Quantity, Revenue, Type (Quantity, Revenue, or Both) and Description.

Prerequisites
Schedules require Products and Price Books to be in use, since schedules live on opportunity products, not on opportunities directly. Schedules are not available on Quote Line Items or Order Products; they are specific to Opportunity Products.

How Schedules Are Enabled (Two Levels)
Level 1 - Organization level: Go to Setup and search for Product Schedules Settings. Here you check Enable Quantity Scheduling and/or Enable Revenue Scheduling. There is also an option to turn on schedules for all existing products at once; otherwise you enable them product by product.

Level 2 - Product level: Once the org-level setting is on, each Product record exposes the checkboxes Quantity Scheduling Enabled and Revenue Scheduling Enabled. Only products with these boxes checked can have schedules established on opportunities. Remember the order: org first, then product. If a question says users cannot see schedule options on a product, the first thing to check is whether the schedule type is enabled at the org level, then whether it is enabled on that specific product.

Default Schedules on the Product
In addition to simply allowing schedules, a product can carry a default schedule. When the product is added to an opportunity, Salesforce automatically creates the schedule using these defaults and the sales rep can then adjust it. Default schedule settings on the product include:

- Schedule Type: Divide or Repeat (explained below)
- Installment Period: Daily, Weekly, Monthly, Quarterly, or Yearly
- Number of Installments: how many dates will be created

If a product has both a default quantity schedule and a default revenue schedule, Salesforce creates the quantity schedule first and then derives the revenue schedule from it, multiplying each installment quantity by the unit sales price. This is a common exam distinction.

Divide vs. Repeat - The Most Tested Concept
Divide splits the total quantity or total revenue evenly across the installments. If an opportunity product has Total Price of $12,000, Divide with 12 monthly installments produces twelve installments of $1,000. The line item total stays $12,000.

Repeat repeats the full quantity or revenue in each installment, so the total is multiplied. If a product has a sales price of $1,000 and you choose Repeat with 12 monthly installments, each installment is $1,000 and the opportunity product Total Price becomes $12,000. Repeat is ideal for recurring subscriptions where the rep enters the per-period price; Divide is ideal when the rep enters the contract total and wants it spread out.

Memory aid: Divide the whole; Repeat the piece.

Establishing a Schedule on the Opportunity Product
On an Opportunity Product that belongs to a schedule-enabled product, the user clicks Establish (or sees the schedule already built if a default exists). They enter the Start Date, the schedule type (Divide/Repeat), the installment period, and the number of installments, and Salesforce generates the installment rows. Each row can then be edited individually, for example to front-load a larger first payment or to push a delivery date. Users can also add or delete individual installment rows.

To replace an existing schedule, the user clicks Re-establish Schedule; this overwrites all existing installments with a new set, so any manual edits are lost. Deleting a schedule removes the installments and returns the opportunity product to its unscheduled state.

Effect on the Opportunity Product and the Opportunity
Once a schedule exists, the scheduled field(s) on the opportunity product become read-only. If a revenue schedule exists, the Total Price (revenue) of the line item equals the sum of the revenue installments and cannot be edited directly - you edit the installments instead. If a quantity schedule exists, the Quantity field is likewise derived from the sum of the installments. Because the opportunity Amount is the roll-up of all opportunity product Total Prices, changing a schedule installment changes the line item total, which changes the opportunity Amount. If a question describes a rep who cannot edit Quantity or Total Price on an opportunity product, the most likely explanation is that a schedule has been established.

Disabling Schedules - Know the Consequences
Turning off a schedule type at the organization level deletes all existing schedules of that type across all opportunity products and removes the related default settings from products. This is destructive and should be called out as a risk in any scenario. Turning off a schedule type on an individual product only prevents new schedules from being created for that product; opportunity products that already have schedules keep them. Exam questions frequently test this contrast.

Reporting on Schedules
Standard opportunity reports show the opportunity Close Date and Amount, not the timing of installments. To report revenue or quantity by schedule date, use the standard report type Opportunities with Products and Schedules (or build a custom report type with Opportunities, Opportunity Products, and Schedules). Grouping by Schedule Date and summing Schedule Revenue produces a month-by-month expected revenue view. This is the answer whenever a scenario asks for revenue by the month it will be recognized rather than by Close Date.

Schedules and Forecasting
Collaborative Forecasts can be configured with a forecast type based on opportunity product schedule dates, so that scheduled revenue appears in the forecast period when the installment is due rather than entirely in the opportunity Close Date period. This is the recommended approach when a company wants forecasts to reflect recurring or staged revenue timing. Without a schedule-based forecast type, the full opportunity Amount lands in the Close Date period.

Other Details Worth Knowing
- Schedules are created in the opportunity currency when multi-currency is enabled.
- Schedule installments are visible on the Opportunity Product record page via the Schedule related list / section; make sure the related list is on the page layout.
- Schedules do not exist on Quotes; if a business process relies heavily on quoting with recurring pricing, a CPQ solution is typically recommended instead.
- Changing the Sales Price on an opportunity product with an established revenue schedule is not possible directly; the schedule drives the total.
- The Product Date field on opportunity products is separate from schedule dates.

Typical Business Scenarios
- Subscription software billed monthly at a fixed price: Revenue schedule, Repeat, Monthly, 12 installments.
- Annual services contract with a known total to spread evenly: Revenue schedule, Divide, Monthly or Quarterly.
- Hardware delivered in phases: Quantity schedule, Divide, with per-delivery adjustments.
- Phased delivery with revenue recognized on delivery: Both quantity and revenue schedules; revenue derived from quantity.
- Finance wants a report of expected revenue by month: Opportunities with Products and Schedules report grouped by Schedule Date.

Exam Tips: Answering Questions on Product and Revenue Schedules

1. Match the keyword to the schedule type. Words like delivered in installments, shipped in batches, units per month point to Quantity Schedules. Words like recognized over time, billed monthly, recurring revenue, payment plan point to Revenue Schedules. If both delivery and revenue timing are described, the answer is both schedule types together.

2. Divide vs. Repeat is almost guaranteed to appear. If the scenario gives a total contract value to be spread out, choose Divide. If it gives a per-period price that recurs, choose Repeat. Check the arithmetic in answer options: Divide keeps the total constant; Repeat multiplies it.

3. Remember the two-level enablement. Org-level setting first (Product Schedules Settings), then the product-level checkboxes. If a question describes a product with no schedule option, the fix is at one of those two levels, not on the opportunity or page layout.

4. Read-only fields signal an established schedule. When Quantity or Total Price cannot be edited on an opportunity product, the schedule controls the value. The correct action is to edit the installments or re-establish the schedule, not to change field-level security.

5. Know what disabling does. Org-level disable deletes all schedules of that type (destructive). Product-level disable only blocks new schedules and leaves existing ones intact. Eliminate answer choices that get this backward.

6. Default schedules save reps time. If a scenario says reps repeatedly build the same schedule manually, the answer is to configure a default schedule (type, period, number of installments) on the Product record so it is created automatically when the product is added to an opportunity.

7. Reporting by recognition date means a schedules report type. Any question about seeing revenue by the month it will be earned rather than by Close Date is answered by the Opportunities with Products and Schedules report type, grouped by Schedule Date.

8. Forecasting by installment timing requires a schedule-based forecast type. If sales leadership wants recurring revenue to show up in the correct forecast months, configure Collaborative Forecasts with an opportunity product schedule date forecast type.

9. Watch for out-of-scope distractors. Schedules do not exist on Quotes or Orders; options that suggest adding schedules to quote line items are wrong. Also, schedules require Products and Price Books to be in use.

10. Remember the quantity-first rule. When both default schedule types exist on a product, Salesforce creates the quantity schedule first and calculates revenue from it. An answer claiming revenue is created first or independently is incorrect.

11. Use elimination on scenario questions. Advanced Administrator questions often present two plausible-sounding configuration answers. Prefer the one that uses native schedule functionality over custom fields, flows, or custom objects when the requirement is simply to spread quantity or revenue over time on opportunity products.

Quick Recap
Product Schedules let you break an opportunity product into dated installments of quantity, revenue, or both. Enable at the org level, then on each product, optionally with a default schedule. Divide spreads a total evenly; Repeat multiplies a per-period value. Once established, scheduled fields become read-only and roll up to the opportunity Amount. Disabling at the org level deletes schedules; disabling on a product does not. Report on timing with the Opportunities with Products and Schedules report type and forecast on timing with a schedule-based Collaborative Forecast type. Master these points and you will handle any schedule question the exam presents.