Diagnosing Magento 2 Catalog Price Rules That Do Not Apply Discounts

Recognizable Condition

Products that should receive a discount from a catalog price rule display the regular price on the storefront, even though the rule appears active in Admin → Marketing → Promotions → Catalog Price Rules with a valid date range and customer‑group assignment.

Cause / Diagnostic Table

Possible Cause	What to Look For
Rule status disabled or date range mismatch	Rule shows “Inactive” or From/To dates do not cover today’s UTC time.
Product attribute not usable in promo rules	Attribute used in rule conditions (e.g., color, size) has “Use in Promo Rules” set to No, or the product’s attribute value does not match the condition.
Stale indexers	Indexer status shows “Processing” or “Reindex Required” for catalog_rule_product or catalog_product_price.
Full‑page cache or Varnish serving stale price data	After a change, the storefront still shows old prices until cache is cleared.
Custom extension interfering with price calculation	Observers or plugins that modify sales_rule_validator_period or price rendering are present.

Ordered Verification Steps

1. Check rule status and dates

   Log in to the Magento Admin with a user that has the Magento_Promotions::manage resource. Navigate to Marketing → Promotions → Catalog Price Rules, open the rule, and verify:

   • Status = Active
   • From Date ≤ today’s UTC ≤ To Date
   • Customer Group matches the intended shoppers.

   Where to run: Admin UI. Permissions: Admin role with promotion rights. Risk: None.

2. Validate product attributes used in conditions

   Open the product that should receive the discount. For each attribute referenced in the rule (e.g., color):

   • Edit the attribute via Stores → Attributes → Product.
   • Ensure Used in Promo Rules is set to Yes.
   • Confirm the product’s attribute value matches the rule condition (e.g., color = red).

   Where to run: Admin UI. Permissions: Admin role with catalog rights. Risk: Changing attribute scope may affect other rules; test in staging first.

3. Reset and reindex the relevant indexers

   Access the Magento root directory on the server (typically /var/www/html/magento). Run:

   php bin/magento indexer:reset
   php bin/magento indexer:reindex catalog_rule_product catalog_product_price

   Where to run: Server CLI. Permissions: File system user that owns the Magento files (often www-data or a dedicated deploy user). Risk: Temporary CPU load; reindexing can take several minutes on large catalogs.

   Expected check: After completion, run php bin/magento indexer:status and verify both indexers show Ready.

4. Flush Magento cache and, if used, purge Varnish

   From the CLI:

   php bin/magento cache:flush

   If Varnish is configured, issue a purge (example using varnishadm):

   varnishadm "ban req.url ~ ."
   

   Where to run: Server CLI. Permissions: Same as Magento CLI user; Varnish purge requires access to the Varnish admin port. Risk: Clearing cache removes all stored pages, causing a temporary increase in origin load while the cache warms.

   Expected check: Reload a product page in a private/incognito browser window; the price should reflect the discount if the previous steps resolved the issue.

5. Isolate custom extensions

   Temporarily disable suspect modules (e.g., those that observe sales_rule_validator_period or modify price rendering). From the CLI:

   php bin/magento module:disable Vendor_ModuleName
   php bin/magento cache:flush
   

   Where to run: Server CLI. Permissions: Magento CLI user. Risk: Disabling a module may break functionality; perform this in a staging environment first.

   After disabling, repeat steps 1‑4. If the discount appears, re‑enable the module and examine its observers/plugins for conflicts.

Corrective Actions Tied to Findings

• Rule disabled or dates wrong – Enable the rule or adjust the From/To dates to include today’s UTC time, then save.
• Attribute not usable in promo rules – Edit the attribute, set Used in Promo Rules to Yes, save, and re‑save the affected products (or run php bin/magento catalog:product:attributes:update).
• Stale indexers – Run the reset/reindex commands from step 3.
• Cache serving stale data – Flush Magento cache (step 4) and purge Varnish if applicable.
• Custom module interference – Disable the module (step 5), test, then either fix the observer/plugin or leave the module disabled if it is not required.

Escalation Criteria

If after completing all five verification steps the discounted price still does not appear:

1. Enable developer mode: php bin/magento deploy:mode:set developer.
2. Check var/log/exception.log and var/log/system.log for errors related to price calculation or rule validation.
3. Run the rule via CLI to isolate: php bin/magento dev:tests:run functional --test=Magento/Rule/Test/RuleTest (adjust path as needed).
4. Collect the logs, a reproducible test case (product SKU, rule ID, steps to reproduce), and contact Magento Support or a certified developer.

Practical Verification of Fix

After applying the corrective action:

1. Open a private/incognito browser window.
2. Navigate to a category or search result page that lists a product matching the rule conditions.
3. Confirm the product price shows the discounted value (e.g., original $100 → $90 for a 10% rule).
4. If the price is still incorrect, repeat the verification steps, paying close attention to the indexer status and cache flush logs.