Threshold-based discount approval logic belongs in an Approval Process, with entry criteria referencing the Quote's calculated total discount (or discount percentage) field. When the discount exceeds the defined threshold, the approval process routes the Quote for review before it can be finalized. Pricing Procedures calculate the price itself, not approval routing, and Qualification Rules govern product eligibility, not discount governance.

In Salesforce Revenue Cloud, a unified catalog strategy promotes scalability, governance, and efficient cross-sell and upsell opportunities across business units. For large B2B enterprises with diverse product models, the best approach is to lead discovery with a shared catalog architecture using reusable components, shared attributes, and modular selling models that can be adapted per business line.
This method ensures data consistency and allows governance teams to maintain a single source of truth for pricing, attributes, and approval logic--while still allowing flexibility for each line of business to define unique bundles or rules.

Because Revenue Cloud's amendment and renewal proration logic depends on accurate Asset State Period boundaries, migration must recreate this state history (not just the current snapshot) so that any future in-term change calculates proration correctly. Skipping historical Asset Actions/State Periods risks incorrect proration and inaccurate MRR reporting going forward, even if the "current" data looks correct at go-live. Assets are not generated automatically from Quotes; they come from activated Orders, and historical data should not be loaded into the Quote object.

Salesforce provides the "Create and Update Renewal Opportunities" flow template specifically for this purpose. It listens for platform events fired when Assets are created, amended, or canceled, and keeps the associated renewal Opportunity synchronized in near real time -- without requiring custom Apex or scheduled batch jobs. This keeps forecasting accurate as the underlying install base changes.

Revenue Cloud Product Catalog Management encourages grouping similar products using Product Classification:
Products sharing the same classification can share common behaviors, such as pricing rules or orchestration/decomposition rules.
DRO rules can be built to apply at the Product Classification level, reducing duplication.