Magento 2 Multi-Website Alert: Deleting Stores Can Break Your Sales Grids!

Magento 2's Hidden Hazard: Deleting Websites Can Crash Your Sales Grids

Managing multiple websites, store groups, and store views is a core strength of Magento 2, enabling businesses to cater to diverse markets from a single backend. However, a recently reported bug highlights a critical vulnerability in how Magento handles the deletion of these multi-store entities, specifically impacting the backend sales grids.

A GitHub issue (#41750) has brought to light a significant problem where deleting a website in Magento Open Source 2.4.9 (and potentially other versions) can lead to the Credit Memos grid, and likely other sales-related grids, failing with the error message: "The store that was requested wasn't found. Verify the store and try again." This error, originating from

Magento\Store\Model\StoreRepository::getById
, severely disrupts backend administrative tasks.

The Problem: Stale Store IDs in Grid Tables

The issue arises after a seemingly straightforward administrative action: deleting a website that previously had orders and credit memos associated with its store views. While the main sales entity tables like

sales_creditmemo
,
sales_order
,
sales_invoice
, and
sales_shipment
correctly handle the deletion by setting their
store_id
columns to
NULL
(due to
foreign key constraints defined in
db_schema.xml
), their corresponding grid tables do not.

Specifically, the problem is observed in

sales_creditmemo_grid
, which retains the
store_id
of the now-deleted store view. The author of the issue astutely points out that none of the grid tables (
sales_order_grid
,
sales_invoice_grid
,
sales_shipment_grid
, and
sales_creditmemo_grid
) declare an
foreign key for their
store_id
column. This discrepancy means that when the system attempts to load these grids, it encounters references to non-existent store IDs, leading to the fatal "store not found" error.

Impact and Broader Implications

This bug isn't limited to just the Credit Memos grid; it's a systemic issue affecting all sales-related grids that rely on a

store_id
column in their respective grid tables. For merchants operating multi-website Magento stores, this represents a significant operational risk. Deleting an old or unused website, a common cleanup task, could inadvertently cripple essential backend functionality, making it impossible to view or manage past orders, invoices, shipments, or credit memos.

From a Magento migration perspective, this highlights the critical importance of meticulous data integrity checks, especially when consolidating or restructuring store views and websites. While the issue specifically mentions Magento Open Source 2.4.9, it's a fundamental database schema oversight that could affect various Adobe Commerce and Open Source versions.

Community Engagement and Next Steps

As of the provided comments, the issue has been reported, acknowledged by the Magento bot, and a Jira ticket has been created. However, there are no immediate solutions or workarounds provided within the comments. The community is encouraged to reproduce the issue on vanilla Magento instances to speed up its processing.

This bug underscores the need for continuous vigilance in Magento development and administration. Until an official fix is released, developers and merchants should exercise extreme caution when deleting websites in a multi-store setup and be prepared for potential backend disruptions. This issue serves as a stark reminder that even seemingly minor database schema discrepancies can lead to major operational headaches in complex e-commerce platforms like Magento 2.

Start with the tools

Explore migration tools

See options, compare methods, and pick the path that fits your store.

Explore migration tools