Critical 'As Low As' Price Bug: Magento 2 REST API Stock Updates Fail to Trigger Correct Price Indexing

Understanding the Magento 2 'As Low As' Price Discrepancy with REST API Stock Updates

At Shopping Mover, we constantly monitor the Magento ecosystem for critical issues that can impact merchants and developers. A recent GitHub issue (#41119) has brought to light a significant bug affecting how Magento 2 handles 'As low as' pricing for configurable products when stock statuses are updated via its REST API. This issue, confirmed on the dev-2.4-develop branch, highlights a potential pitfall for any store relying on external systems (like ERPs or PIMs) for inventory management.

The Problem: Stale Pricing After API Stock Changes

The core of the issue revolves around configurable products with multiple simple product variants, each having different prices. Magento's 'As low as' price feature is designed to dynamically display the lowest price among its currently in-stock variants. The bug manifests when a lower-priced variant's stock status is updated from 'Out of Stock' to 'In Stock' specifically through the REST API endpoint: PUT rest/V1/products/{sku}/stockItems/{id}.

Here's the breakdown of the observed behavior:

• Initially, if a lower-priced variant (e.g., Variant B at $100) is 'Out of Stock' and a higher-priced variant (e.g., Variant A at $500) is 'In Stock', the configurable product correctly shows 'As low as $500'.
• When Variant B is brought back 'In Stock' via the Magento admin panel, the system correctly updates the configurable product's 'As low as' price to $100 after partial reindexing.
• However, if Variant B is brought back 'In Stock' via the REST API, even after partial indexing completes, the configurable product *continues* to display the incorrect 'As low as $500' price, failing to reflect the now-available lower-priced variant.

The Root Cause: Indexing Backlog Discrepancy

The issue's author, Vatsal-Patel1, provided an excellent analysis of the underlying problem. It stems from a difference in how product updates are handled by the admin panel versus the REST API in relation to Magento's price indexer backlog. Specifically:

• When a product is saved via the admin panel, it is correctly added to the catalog_product_price_indexer backlog (changelog table). This ensures that during partial (scheduled) indexing, the product's price data is refreshed. This behavior is linked to changes introduced in

  https://github.com/magento/magento2/commit/1984c61cfce3d303956d3405f2bcc3bd50154741

• Conversely, when only the stock status is updated via the REST API endpoint, the product is *not* added to this crucial indexing backlog. Consequently, the price index for that product is never refreshed during scheduled indexing.

This means that while the stock status itself is updated, the associated price index (which determines the 'As low as' price) remains stale, leading to the incorrect display on the storefront.

Impact and Confirmation

This bug can have significant implications for merchants, leading to customer confusion, lost sales, or even legal issues if advertised prices don't match actual availability. The issue has been confirmed as reproducible by the Magento engineering team (engcom-Bravo), indicating a verified flaw in the platform's core functionality.

While no immediate workarounds or solutions are provided within the GitHub thread itself, the detailed bug report and root cause analysis are invaluable for developers and system integrators. It highlights a critical area where custom development or monitoring might be necessary until an official fix is released. Merchants relying on robust API integrations for inventory should be aware of this behavior and plan accordingly to ensure pricing accuracy.