Published at: 2026-09-17

Use aggregation rules in pricing policies

Pricing policies can reference aggregation rules to determine whether an order meets promotion conditions or threshold conditions.

Overview

Aggregation rules calculate document fields into aggregation values. After pricing policies reference them, they can support single product promotions, order-level promotions, and bundle promotions.

Before you begin

[!IMPORTANT] - Role permissions: You need permission to edit pricing policies and pricing rules. - Prerequisite configuration: An administrator has configured pricing policies, pricing rules, and aggregation rules. - Data conditions: Order data must meet the account, product, and aggregation conditions in the pricing rule.

Use in order-level promotions

Order-level promotions use master-object rules. Aggregation rules can be used in these positions:

Position	Purpose
Rule condition	Determines whether an order meets promotion conditions.
Threshold condition in execution result	Determines whether the benefit is applied by multiple.

Order-level promotion rule condition references an aggregation rule

Order-level promotion threshold condition references an aggregation rule

Example: After the amount of products in a category reaches a threshold, the whole order receives a reduction.

Use in product promotions

Product promotions use detail-object rules. Aggregation rules can be used in single product promotions and bundle promotions.

Scenario	Aggregation rule purpose
Single product promotion	Used as a rule condition to determine whether an order meets the promotion condition.
Bundle promotion	Used as a rule condition or bundle rule to determine the bundle scope and matching condition.
Bundle promotion threshold	Used as a threshold condition to determine the benefit multiple.

Single product promotion rule condition references an aggregation rule

Bundle promotion rule condition references an aggregation rule

Bundle promotion threshold condition references a bundle rule

Free bundle promotion example

Scenario: A product bundle reaches 1,000 CNY, and the total bundle amount is reduced by 300 CNY.

Cleaning product bundle aggregation value

The administrator first creates a product combination aggregation value.
The aggregation value calculates the eligible promoted product amount as one value.
The administrator creates a bundle pricing detail-object rule.
The rule condition references the product combination aggregation value.
The execution result reduces the bundle subtotal by a specified amount.
After the user creates an order, the system uses the bundle aggregation result to determine whether to run the promotion.

If a bundle promotion must evaluate both bundle quantity and single product quantity, configure a product combination aggregation value and a standard aggregation value separately.

Single product quantity aggregation value

Expected result and verification

The pricing policy runs when the order meets aggregation conditions.
Bundle promotions can identify the promoted product scope.
Threshold conditions can calculate benefits by multiple based on aggregation results.

Troubleshooting

Issue	Suggested action
The bundle promotion does not match.	First confirm that the aggregation rule result type is Product combination.
The threshold benefit is not multiplied.	First confirm that the threshold condition references the correct aggregation value.