Catalog Price Rules

Catalog price rules allow you to apply discounts to sets of products (or all products) based on conditions, with optional customer group targeting.

Location: Marketing → Catalog Price Rule (admin panel)

Key Features

• Filter products by attributes, categories, SKU, etc.
• Target specific customer groups (e.g., Wholesale, Retail)
• Apply percentage or fixed amount discounts
• Set date ranges for active periods
• Priority and stop further rules processing

Catalog price rules are indexed for performance. The indexed data is stored in the catalogrule_product_price table.

Key Points

• Not indexed by Price Indexer: Catalog rules have their own indexer.
• Catalog Product Rule Indexer: Dedicated indexer for catalog rules.
• Table Structure: Stores rule-based prices per product, customer group, website, and date.

The IndexBuilder class builds the catalog rule indexes.

When a catalog price rule is saved or products change:

1. Indexer evaluates which products match rule conditions.
2. Calculates discounted prices for matching products per customer group.
3. Stores results in catalogrule_product_price table.
4. Frontend reads from this table to display catalog rule prices.

Catalog price rules have a slight performance impact.

Why?

• Rules are pre-calculated and stored in catalogrule_product_price.
• Frontend queries this indexed table rather than evaluating rules on-the-fly.
• Indexing runs during reindex or on schedule (via cron).

Performance Considerations

• Indexing time: Large catalogs with many rules may take longer to index.
• Indexer mode: "Update on Save" impacts admin performance; "Update on Schedule" defers to cron.
• Frontend: Minimal impact—reads from indexed table.

Debugging is easier with access to a production database copy (without sensitive customer data).

Two Places to Check

1. Is the problem the data going INTO the indexed table?
   • Check rule conditions: Are products matching the rule?
   • Verify customer groups are assigned correctly.
   • Ensure rule is active and within date range.
   • Run indexer manually: bin/magento indexer:reindex catalogrule_rule
2. Is the problem the data coming OUT of the indexed table?
   • Query catalogrule_product_price table for affected products.
   • Verify discounted prices exist for the customer group.
   • Check if frontend code reads from the indexed table correctly.
   • Look for price retrieval logic in price models.

Set breakpoints in IndexBuilder to trace rule evaluation and index generation.

1. Verify Rule Configuration:
   • Check rule is active (Status = Active).
   • Verify date range includes current date.
   • Ensure customer groups are selected.
   • Review conditions and actions.
2. Check Indexer Status:

   bin/magento indexer:status catalogrule_rule
   bin/magento indexer:status catalogrule_product

3. Reindex Manually:

   bin/magento indexer:reindex catalogrule_rule catalogrule_product

4. Query Indexed Table:

   SELECT * FROM catalogrule_product_price 
   WHERE product_id = [PRODUCT_ID] 
   AND customer_group_id = [GROUP_ID];

5. Check Product Matches Rule:
   • Manually evaluate rule conditions against product attributes.
   • Use admin Preview > Products Matched to see which products match.
6. Review Logs:
   • Check var/log/system.log and exception.log for errors during indexing.

Two indexers handle catalog price rules:

1. catalogrule_rule: Indexes rule data itself.
2. catalogrule_product: Indexes product-rule associations and calculates prices.

Both must be up-to-date for rules to apply correctly.

• Catalog Price Rules
• Indexing
• Manage Indexers