Subscription Term and List Price:
Subscription Product A has a Subscription Term of 6 months with a List Price of $100. When added to a Quote with a Term of 12 months, the List Price is prorated to account for the longer term.
Proration and Ranged Discount Schedule:
A Ranged Discount Schedule applies discounts based on quantity, volume, or term thresholds.
For the 12-month term, the price is prorated to $200 (2 times the List Price for 6 months). The Discount Schedule applies a 25% discount to the prorated price, reducing it to $150.
Regular Price Calculation:
The Regular Price reflects the discounted value after applying the Discount Schedule:RegularPrice=200x(1-0.25)=150x0.5=75\text{Regular Price} = 200 \times (1 - 0.25) =
150 \times 0.5 = 75RegularPrice=200x(1-0.25)=150x0.5=75.

Requirement:
Migrate existing contracts to a new Product version upon renewal.
Solution:
Update the Renewal Product field to specify the new version of the Product. Enable the Renewal Forecast checkbox on the Contract to ensure renewal Quotes reference the new Product version.

Scenario:
Original subscription: $600 Net Unit Price x Quantity 10 x 24 months = $14,400. Refund: Ten months into the contract, 14 months remain unused.
Calculation:
Refund amount = ($600 x 10 x 14)/24 = -$3,500.
Amended subscription refund (Quantity = 0): 14 months refund prorated = -$2,500.

Requirement Overview:
* Product A must always be included in the bundle.
* Product B should be included by default but can be removed by the user.
Key Configurations:
* Required = FALSE: This ensures that Product B is not mandatory and can be removed by the user.
* Selected = TRUE: This includes Product B by default when the bundle is added to the Quote.
Steps to Configure:
* Navigate to the Product Option record for Product B.
* Set Required to FALSE.
* Set Selected to TRUE.
* Save and test the behavior by adding the bundle to a Quote.
Validation:
* Product B should be pre-selected in the Quote Line Editor but can be deselected by the user.
* This setup ensures flexibility for Product B while ensuring Product A remains mandatory.

Issue Analysis:
Products not syncing to Opportunity Products is usually caused by specific CPQ conditions or rules.
Reasons for Failure:
B: Products with an Effective Quantity of zero are excluded from syncing.
C: Validation Rules on the Opportunity Product object may silently block the sync process if they are not met.
D: Products with a price of zero do not sync by default.