Tiered discount should calculate on combined quantity of a product group (not per individual product)

Hello B2BKing team,

I’m trying to configure tiered pricing so that the discount is applied based on the combined quantity of all items in a product group/category, not per individual product.

Goal (expected behavior):
If a customer buys multiple different products from the same group (e.g., Group A), the total quantity across that group should count toward the tier.
Example tiers:

• 3+ units (any mix from Group A) → 5% off all Group A items in the cart

• 6+ units (any mix from Group A) → 10% off all Group A items in the cart

Current behavior (issue):
Tiered discount is calculated per product. So if Group A has 30 products, the rule only triggers when the quantity of a single product reaches the tier, instead of using the sum of quantities of all products in Group A within the cart.

How I configured it:

• Rule Type: Tiered Price (Price by Quantity)

• Applies to: Product Group / Category (not a single product)

• Applies to who: Specific B2B group (hairdressers) and/or All users

• Tiers: e.g., 3→5%, 6→10%, 12→15%

• I need the rule to sum quantities across the selected group/category in the cart.

What I need:

1. Either a built-in option (e.g., “Calculate tiers based on combined quantity of selected group/category in cart”), or

2. A code snippet / filter / hook I can add to make tier thresholds evaluate against the aggregated quantity of all items in the chosen group/category.

Illustrative example:
Cart has:

• Product A (Group A): qty 1

• Product B (Group A): qty 2
  Total for Group A = 3 → Should trigger the 3+ tier and apply 5% to both A and B.
  Currently, discount does not trigger unless a single product reaches qty 3.

If you can provide a code snippet or point me to the correct setting to make tiered rules aggregate quantities by group/category across the cart, that would be perfect. Thank you!

We need Tiered Price (Price by Quantity) rules to calculate tiers based on the combined cart quantity of items inside the selected product group/category, and then apply the discount to all items from that selected group—not per individual product.

Target group (what we want the rule to apply to)

• Product group/category: e.g., “I.C.O.N. Ecotech” (category ID 151)
  (This is just an example. We want this to work for any category or product group we select in the rule.)

• Applies to who: our B2B customer group “Hairdressers” (and optionally All users for testing).

Expected behavior

If a customer buys different products from the selected group/category, the sum of quantities across that group should determine the tier, and the discount should apply to all items from that group in the cart.

Example tiers:

• 3+ (any mix from the selected group) → 5% off all those items

• 6+ (any mix) → 10% off

• 12+ (any mix) → 15% off

Illustration:
Cart = Product A (Group) qty 1 + Product B (Group) qty 2 → total 3 in the selected group → should trigger 3+ tier and apply 5% to both A and B.

Current behavior (issue)

Tiers evaluate per product, so the rule only triggers when a single product reaches the threshold, instead of using the aggregate quantity of all items in the selected group/category.

Our configuration

• Dynamic Rules → Rule Type: Tiered Price (Price by Quantity)

• Applies to: Product Category / Product Group (not single product)

• Applies to who: Hairdressers (B2B group) and/or All users

• Tiers: e.g., 3→5%, 6→10%, 12→15%

What we need

• A built-in option (e.g., “Calculate tiers based on combined quantity of the selected group/category in cart”), or

• An official code snippet / filter / hook to aggregate quantities by the rule’s selected scope (category or product group, including child categories) and apply the resulting tier to all matching items in the cart.

What we tried (for your reference)

We enabled cart-wide tier calculation and tested a custom filter to sum quantities in one category (ID 151) including its children. It worked earlier for a single category, but after further adjustments it stopped applying in cart. We would prefer an official, supported approach that works whenever we choose any category/product group in the rule.

Questions

1. Is there a built-in way for Tiered Price rules to aggregate by the selected group/category across the cart (not per product)?

2. If not, could you share an official snippet that sums quantities by the rule’s scope (selected category/group), including children, and applies the tier to all items in that scope?

3. Do all items need to share the exact same rule for aggregation to work, or can multiple Tiered rules target the same scope and still aggregate?

4. Any known limitations, hook order, or caching considerations we should follow?

Access for faster troubleshooting

We can provide temporary WP admin/staging access if helpful. Please let us know the safest way to share credentials.

Thanks a lot for your guidance!

thank you its working

its not working 

Right now the plugin calculates discounts based on the total cart quantity, regardless of which products are in the cart. In the rule UI we only see options like “Cart quantity” or “Cart value,” but there is no option to count only the quantity of the products targeted by the rule (e.g., selected products/categories/attributes).

What we need:
An option/setting so that the threshold for tiered/quantity discounts is calculated only from the quantity of the products included in that specific rule (not from unrelated items in the cart).

Example:

• Rule targets Product A (or Category X).

• Cart contains 1× Product A and 5× Product B (not targeted by the rule).

• Currently, the rule triggers because total cart quantity = 6.

• Expected: the rule should only count qty of Product A = 1, so the threshold should not be met.

Please advise if there is a built-in setting or recommended filter/action to enable “count matched products only” behavior for tiered/quantity rules. If not available, could you provide the official snippet or guidance to achieve this?

Thank you!

Hi Stefan,

Quick update — the attribute option works on our side, thanks.
However, when we add this filter to expose the attribute in Dynamic Rules:

add_filter('b2bking_dynamic_rules_taxonomy_option', function($taxonomy){    return 'pa_talpa';
}, 10, 1);

the UI switches to the attribute mode and the other rule conditions disappear, e.g.:

• Category / Group quantity

• Product quantity (within the selected scope)

In practice, after enabling the attribute option, we no longer see the choices that let us count only the quantity of the selected group/category (or selected products). The rule falls back to “Cart quantity/value” (whole cart), which is not what we need.

What we need:

1. Keep the attribute (pa_talpa) selection available without losing the conditions to count quantity for selected groups/categories/products only; or

2. Provide an official snippet that counts only the combined quantity of items with a specific attribute value in the cart (e.g., pa_talpa = 1000 ml), applies the rule only when the min qty is reached, and does not include unrelated items.

Important pricing base: the discount should be calculated from the regular (B2C) price, not from any B2B discounted price (to avoid double-discounting).

If option (1) is not currently possible, we’re happy to proceed with option (2). Please share the snippet (preferably hooked in woocommerce_cart_calculate_fees) with:

• Attribute taxonomy: pa_talpa

• Values handled separately (e.g., 1000 ml, 3000 ml, 5000 ml)

• Threshold example: ≥ 3 for a given attribute value

• Discount applied only to matching items; base = regular price; no stacking with other rules

Thanks a lot!
Vladislav

Hi,

Thank you for the information and your assistance. Since it’s currently not possible to achieve the discount logic we need with your plugin, we’ve decided to test an alternative solution. We are now trying the Flycart plugin, and their discount system works exactly the way we require.

I would recommend taking a look at how their system is built — it’s very similar to yours, but certain scenarios are handled more efficiently and we haven’t encountered as many bugs or issues as we did here.

Thank you again for your time.