Should I delete out-of-stock products from my online store?

When replenishment is expected, we generally recommend keeping the informative product page accessible at its existing URL. State clearly that the item is currently unavailable. Only show a delivery date when it is reliable. An honest statement without a confirmed date is more useful than a promise that moves forward every day.

Descriptions, technical specifications, images and suitable alternatives remain useful. The purchase button must reflect whether orders can actually be accepted. If you do not accept backorders, avoid stopping customers only at the last checkout step. If you accept orders without stock, the fulfilment process and information across connected sales channels must support that arrangement.

Check individual variants, too. One unavailable size does not mean that the entire model is unavailable. Review the selected variant and its data rather than displaying one blanket message for every option. This also involves keeping ERP and store inventory aligned.

A discontinued item requires a different decision from a temporary supply gap. A permanent redirect can be appropriate if there is a genuinely suitable successor. The replacement must match the original search intent. A spare part for another device is not an equivalent replacement merely because it belongs to the same category.

When no suitable replacement or useful information remains, a removed page can return a 404 or 410 status. This is not automatically an SEO mistake. Google considers these status codes when processing URLs. An empty error page returning 200, however, sends conflicting signals and may be treated as a soft 404. Google's HTTP status code documentation explains the technical basis.

A third option is an information page clearly marked as no longer available for purchase. This can be useful when customers still need instructions, compatibility information or spare parts. The page should genuinely provide that value. Keeping old product pages indefinitely simply because they once received traffic is not an archive strategy in itself.

Someone searching for a specific model number does not want to browse the entire catalogue again. A blanket homepage redirect rarely addresses that need. We assess which destination actually fulfils the original intent for each product or product group. If no such destination exists, a clear not-found page may be more honest.

For a genuine replacement, we update internal links to point directly to the destination and avoid unnecessary redirect chains. The old product URL should no longer appear as a regular destination in the XML sitemap. For a retained information page, we instead check that it remains accessible and linked where useful. Our relaunch redirect guide covers the same technical task during a complete store migration; this article focuses on ongoing catalogue changes.

PrestaShop provides settings for quantities, combinations and accepting orders when stock is unavailable. The interface and available options depend on your version. Changing a quantity, disabling a product and redirecting a page are different actions. Agree on the intended business behaviour before implementing an automatic rule.

We consider PrestaShop a strong foundation when merchants need to adapt these workflows to their catalogue and ERP. That flexibility still requires coordination. An import may overwrite a manual setting, and a theme may display a notice differently from what was intended. Modules and custom changes therefore need checking as well. The PrestaShop product management documentation describes the main settings areas.

Consider a hypothetical example: a merchant sells pumps and spare parts. One pump returns in two weeks, an older model is permanently discontinued, and a seal kit remains relevant to existing customers. A single rule stating “zero stock means delete the page” would be unsuitable for these three cases. We would assess replenishment, replacement models and information needs separately. This is a planning example, not a claimed customer case study.

The page, product feed and structured data must provide consistent information. For an item that temporarily cannot be ordered, Merchant Center supports the out_of_stock availability value. Preorders and backorders have their own requirements and should not be used to disguise uncertain availability. Google instructs merchants to remove permanently discontinued products from their data source. That does not automatically mean deleting a useful information page from the store. Source: Merchant Center availability guidance.

After a change, check the next feed run and the data actually delivered by the page. A corrected ERP stock figure achieves little if a cached export still reports the item as available. If products have already been rejected, see our guide to Merchant Center product disapprovals. Here, the focus is on establishing catalogue rules before issues occur.

We do not limit testing to one sold-out product. A small, targeted sample should cover the different business rules:

• A temporarily unavailable product with no confirmed delivery date.
• An unavailable variant alongside variants that can still be purchased.
• A discontinued item with a suitable successor.
• A discontinued item without a meaningful redirect destination.
• An old item with useful instructions or spare-part information.
• Restored availability after the next ERP import and feed run.

For each case, we record what the customer sees, whether ordering is possible, which HTTP status the URL returns and which availability the data channels report. This makes it possible to establish whether a later change affects only the display or the entire workflow.

Our PrestaShop services connect technical checks with the rules of your catalogue. We clarify which system determines the status, examine the store output and agree on necessary changes to themes, modules or integrations. For important URLs, we also consider existing search queries and visits when deciding what to retain.

After implementation, we check the agreed scenarios and monitor indexing, feed messages and relevant landing pages. Retaining a URL guarantees neither rankings nor inclusion in AI answers. It can, however, continue to provide a useful answer instead of leaving a customer at a dead end without an explanation. That is the practical basis for the decision.