Magento 2 Catalog Price Rule Bug: When Same Priority and Different Customer Groups Collide

Unraveling Magento 2 Catalog Rule Conflicts: Same Priority, Different Customer Groups

As an e-commerce platform, Magento 2 offers robust catalog price rules to empower merchants with flexible promotional strategies. However, even the most sophisticated systems can encounter unexpected behavior. A critical issue identified within the Magento 2 ecosystem highlights a significant flaw in how catalog price rules are applied when they share the same priority but are targeted at different customer groups, particularly affecting configurable products.

The Core Issue: Priority Collisions in Catalog Rules

The GitHub issue #41258, reported on Magento 2.4.9 (and confirmed for 2.4.x versions), details a scenario where two catalog price rules, designed for separate customer groups but assigned identical priorities, do not apply as expected. This bug primarily surfaces when dealing with a mix of standalone simple products and simple products associated with configurable products.

The problem can be systematically reproduced with the following conditions:

• Environment: Magento 2.4.x (e.g., 2.4.9-sep-2026).
• Products: A configurable product, its associated simple product, and a standalone simple product.
• Rules Setup: Two distinct Catalog Price Rules configured in the Admin panel:
  • Different discount percentages.
  • Identical Priority values.
  • Assigned to different customer groups.

After creating these rules and reindexing the catalog price rules, the `catalogrule_product` database table reveals the core of the problem.

Expected vs. Actual Application

Expected Result: Catalog rules with the same priority but different customer groups should apply correctly to all matching products for their respective customer groups.

Actual Result: The system exhibits a selective application. Only the catalog price rule with the highest ID is applied to configurable variant simple products. Conversely, the rule with the lowest ID is only assigned to standalone simple products. This creates a significant discrepancy in pricing and promotions, potentially leading to incorrect discounts for specific customer segments or product types.

Community Insights and Workaround

The community's investigation into this issue quickly identified a practical, albeit temporary, workaround. By simply changing the priority values of the conflicting rules to be different, the system behaves as expected. Reindexing the catalog price rules after this adjustment shows that both rules are then correctly applied to all simple products for their respective customer groups.

While this workaround offers immediate relief, it's crucial to acknowledge its limitations. In complex production environments with numerous catalog rules and diverse customer groups, manually adjusting priorities can become an unmanageable task. It might disrupt existing promotional logic or require a complete re-evaluation of the priority hierarchy across all rules.

Why This Matters for Merchants and Developers

This bug carries significant implications for both Magento merchants and developers:

• For Merchants: Inaccurate promotional pricing can lead to customer dissatisfaction, loss of trust, and potential revenue loss. It undermines carefully crafted marketing strategies based on customer segmentation and targeted discounts. Ensuring price integrity is paramount for any e-commerce business.
• For Developers: Understanding this behavior is key for debugging pricing discrepancies and implementing robust solutions. It highlights the need for thorough testing of promotional rules, especially in environments with complex product structures (like configurable products) and customer group-specific pricing. Developers might need to implement custom logic or carefully manage rule priorities during migrations or new feature rollouts to avoid this pitfall.

This issue underscores the importance of continuous monitoring of GitHub issues and community discussions for Magento users. Staying informed about such bugs allows for proactive measures, whether through workarounds or by advocating for official patches.