Product Catalog Management has its own Data Translation feature (separate from Translation Workbench) that must be enabled at the org level, with supported languages added, before translated Product Name, Description, and Help Text values can be entered and surfaced through the Product List and Product Details APIs based on the caller's locale. Translation Workbench handles UI/metadata labels, not the catalog data itself, so it would not affect what the API returns.

Salesforce Revenue Cloud recommends centralizing product, pricing, and configuration data within the Salesforce Product Catalog to act as the commercial system of record. This approach ensures that sales teams are quoting from a single, consistent catalog that reflects accurate SKUs, pricing, and configurations. According to the Revenue Cloud Implementation Guides, this centralized model supports seamless quoting, bundling, discounting, and automated order and contract generation -- all critical for streamlining the quote-to-cash process.
The ideal architectural approach is to establish Salesforce CPQ as the source of truth for all sellable items, with upstream data (e.g., from PIM and ERP systems) being normalized and integrated into the Salesforce Product Catalog, rather than allowing disparate systems to overwrite Salesforce data. This enables Salesforce to drive clean, validated quote generation, which can then be integrated downstream to ERP for fulfillment and invoicing.

Revenue Cloud's asset model:
Creates one Asset record per quote line (per product instance).
Creates multiple Asset State Periods when the product uses time-based ramp segments.
For a product ramped into 3 consecutive segments (6 months, 12 months, 6 months) starting 1 Jan 2025, the Asset State Periods align exactly with each segment:
Jan 1, 2025 - Jun 30, 2025
Jul 1, 2025 - Jun 30, 2026
Jul 1, 2026 - Dec 31, 2026

In Salesforce Revenue Cloud, when configurable products are ordered (e.g., internet service with upload/download speeds), the configured values are stored at the Order Product Attribute level.
These are linked to the corresponding Order Product, which represents the actual product ordered.
To generate a report that includes both:
The ordered item (Order Product)
Its specific configurations (upload/download speeds)
You need to use a custom report type that includes:
Order Products
Order Product Attributes
While Product Attribute Definition (mentioned in Option B and C) defines the possible attributes at the product catalog level, it does not store the selected values made during quoting or ordering.
The actual values chosen are stored in the Order Product Attribute object.
This approach ensures that your report includes actual selections made by customers, not just the available options.

"A Term Selling Model defines a fixed duration for a product or service, such as 12 months, and specifies how the customer is billed--monthly, quarterly, or annually."
"Evergreen Selling Models are used for ongoing, indefinite subscriptions without a predefined end date."
"To convert a one-time purchase into an installment plan over a fixed period, use a Term-based Selling Model with the appropriate billing frequency." Step-by-Step Reasoning:
Current State: Product is a one-time purchase.
Required Outcome: Convert to 12 equal monthly payments -- this is a fixed duration (12 months) with monthly billing frequency.
Correct Setup: Assign Term Monthly selling model, defining the duration as 12 months with monthly charge intervals.