The Price Specification is the core data model component designed to handle complex pricing logic. It supports various price types (list, purchase, etc.), can be associated with different contexts (customer, region, channel), and is the foundation for applying discounts, taxes, and promotions, making it the correct choice for flexible pricing scenarios.

For a first-time visitor with no history (a ‘cold start’ problem), the system cannot use collaborative or behavioral filtering. The most common and practical fallback is to display a manually curated or rule-based list of featured or best-selling products until enough user-specific data is collected.

In standard SAP Commerce Cloud checkout pipelines, the typical and logical sequence is to first calculate the base cart totals, then apply promotions (discounts) to those totals, and finally calculate taxes on the promoted/net amount. This ensures promotions are applied to the pre-tax subtotal, aligning with the stated business rule.

The Backoffice provides administrative tools for search configuration, including the ability to set boost values for specific product attributes. Increasing the boost for attributes like ‘waterproof’ will make products possessing those attributes rank higher in relevant searches, providing a direct and manageable way to tune relevance.

For payment providers that require a redirect to an external page, a custom PaymentRequestStrategy is the standard extension point. This strategy is responsible for creating the payment transaction and returning the necessary data (like a URL) to the controller to perform the redirect to the provider’s page.

The point at which inventory is reserved is controlled by the checkout process definition. The ‘Reserve’ step is a specific action in this pipeline. Moving this step later in the process (e.g., just before payment) or configuring its conditions is the correct way to change when stock reservation occurs.

The CMS integrated with Personalization allows business users to create different content variations (like banner layouts), define targeting rules (e.g., 50% of users see Variant A, 50% see Variant B), and track performance. This provides a low-code/no-code environment for running A/B tests directly within the platform.

B2B Units are the core data model concept for representing a company or organizational hierarchy within SAP Commerce Cloud B2B. Users are assigned to units, and permissions, budgets, catalogs, and approval processes can be defined at the unit level, making it the foundation for complex B2B commerce scenarios.

In SAP Commerce Cloud, product search is typically handled by Solr, not direct database queries. Slow search performance is most commonly related to the Solr index (e.g., slow queries, insufficient resources, or a need for optimization). Checking Solr health, query logs, and index configuration should be the first diagnostic step.

The Price Specification is the core data model component designed to handle complex pricing logic. It supports various price types (list, purchase, etc.), can be associated with different contexts (customer, region, channel), and is the foundation for applying discounts, taxes, and promotions, making it the correct choice for flexible pricing scenarios.0