Core Commerce promotions recognize fractional quantities of commerce items and use them when qualifying or targeting items in an order for a specific promotion.
When a fraction-enabled SKU is added to the shopping cart, and the quantity meets the criteria defined in the promotion’s condition and offer, the promotion is applied during the promotion evaluation. For example, if a customer has 1.5 pounds of flour in their cart, and the promotion condition is “Buy 1 pound of flour and get another pound free”, the order qualifies for the promotion.
Promotions can accept fractional values for qualifying and targeting quantities. The quantities can be made up by combinations of fractional or non-fractional items. For example, you could have a promotion “Buy 2.5 from category baking goods and get $5 off the order.” The 2.5 quantity could be comprised of fractional goods, for example 2.5 lbs of flour, or a combination of fractional items, for example 1.5 lbs of flour and 1 baking sheet, or non-fractional items, for example 3 baking sheets.
In forNext type (“BOGO” and “Buy Item X Get Item Y”) promotions, the system can apply the offer discount multiple times. When each condition and offer evaluation occurs, items are filtered out to prevent them from acting as qualifying or target items. Items are filtered using the standard set of qualifier service filter flags, the non-discountable and target filters.
Qualifying and Targeting Non-Fractional Items Rules
For a promotion to qualify during the promotion evaluation, the total number of the commerce item quantities must satisfy the value in the promotion definition (Condition and Offer). When non-fractional items are used to provide fractional quantities for qualification or targeting, the fractional quantity is rounded to the nearest whole number based on the following rules:
Qualifying Items: Non-fractional items cannot be marked as having fractional portions. When a fraction of a non-fractional item is needed to satisfy the condition of the promotion, the quantity of that item is rounded up to the nearest whole number. For example, a promotion requires 3.5 shirts and the order contains 4 shirts. Because shirts cannot be marked as a fractional item, the quantity used for qualification is rounded up from .5 to 1 and the promotion is applied.
Targeting Items: If the promotion qualifies, the cart and commerce items within the cart can be targeted and offered the discount. If the offer quantity is, for example, 3.5, it could be comprised of any combination of fraction and non-fractional item quantities. If the cart contains 4 non-fractional items the system cannot discount a fractional portion of a non-fractional item, for example, discounting half a shirt. In this case, any fractional portion of a non-fractional item will be rounded down to the next whole number, for example 3.5 shirts is rounded down to 3 shirts, and all 3 shirts receive the discount.
For additional information on working with promotions, refer to the Understanding Promotions section.
Hiding Fractional Quantity Properties
You can use the PromotionExpressionContext.properties file to identify the options that appear in the advanced templates expression editor. This component allows you to hide certain properties from displaying within drop-downs for certain dynamic bean information types. The excludedProperties property allows you to identify what should be excluded from the drop-down menus.
For example, the default setting for excludedProperties is:
excludedProperties=\ version, \ type, \ item.quantity, \ item.quantityWithFraction, \ item.returnedQuantity, \ item.returnedQuantityWithFraction, \ order.totalCommerceItemCount
These properties are excluded because the expression editor uses the derived version, ensuring that promotions are computed against either the quanity or quantityWithFraction properties.
Note that the item.quanity and the item.returnedQuantity will return either quantity or quantityWithFraction, based on the value you have provided.
For additional information on working with excluded properties in promotions, refer to the Automatic Property Filtering in Templates section.
