Explanation:

In SAP Commerce Cloud's Order Management Services (OMS), the Sourcing Logic determines the optimal location (e.g., warehouse, store) to fulfill an order. This is done by calculating a Sourcing Score for each eligible location. You can configure weight factors to define the importance of different criteria in this calculation. The configurable weight factors out of the box are:

B. Allocation:
This factor prioritizes locations based on their ability to reserve or allocate the required inventory. A location with sufficient confirmed, allocatable stock will score higher.

C. Delivery Time:
This factor prioritizes locations that can promise the shortest delivery time to the customer's shipping address, optimizing for speed.

Why the other options are not configurable weight factors:

A. Distance:
While proximity (geographic distance between the location and the delivery address) is a critical input to the sourcing algorithm, it is not exposed as a separate, configurable weight factor. Its influence is primarily embedded within the Delivery Time calculation, as distance directly impacts transit time. You cannot independently adjust a "Distance" weight.

D. Status:
The operational status of a location (e.g., active/inactive) is a prerequisite filter for sourcing eligibility, not a weighted scoring criterion. A location must be active and available for sourcing to be considered at all.

Reference:
This is detailed in the official "Configuring Sourcing Logic" section of the SAP Commerce Cloud Order Management documentation. It specifies that the sourcing score is calculated based on a weighted sum of configurable factors, explicitly listing Allocation and Delivery Time as the primary configurable components.

Explanation:

The SAP Commerce Cloud promotion engine provides a robust set of out-of-the-box (OOTB) rule templates that allow business users to create common promotion types in the Backoffice Promotion Rule Editor without developer intervention. These templates combine conditions and actions using predefined building blocks.

A. Buy over 500 dollars, get any product in category A at 20% off:
This is a standard Product Percentage Discount promotion. It uses:
Condition: Cart total (order over $500).
Action: Apply a percentage discount to products belonging to Category A.

B. If a user buys 100 dollars worth of category A products, then they get a free gift of a specified product: This is a standard "Gift" Promotion.
Condition: Qualifying products from Category A with a total of $100.
Action: Add a specific product (the gift) to the cart with a 100% discount. The gift product is managed in the catalog.

C. Redeem coupon A, get product B for free:
This is a classic Coupon-Based Free Product promotion.
Condition: Requires a specific coupon code to be entered.
Action: Adds a specified product (Product B) to the cart for free (100% discount). This uses the OOTB "Fixed Price Product" action.

Why D is NOT supported OOTB without customization:

D. When a user buys 100 dollars worth of category X products AND 100 dollars worth of category Y products, then they get 50% off category Z products:
This promotion requires a compound condition where two separate qualifying thresholds must be met (Category X and Category Y). The OOTB rule editor does not provide a template for combining multiple "order entry" or "product in category" conditions with "AND" logic at this level of complexity. Creating this would require a custom rule condition, which is a technical development task.

Reference:
This distinction is covered in SAP's "Promotions" documentation and training materials for the Business User role (C_C4H32_2411). The documentation lists the available condition and action types in the promotion rule builder and clarifies that while many combinations are possible, complex compound conditions (especially those requiring "AND" between distinct product category groups) fall outside the standard template set and require custom extensions.