An out-of-stock product page can interrupt a customer’s buying journey. The visitor may still be interested in the product category, price range or product type, but the original item is not currently available. Instead of leaving the page without guidance, a WooCommerce store can present carefully selected alternative products that are available to purchase.
This guide explains the documented WooCommerce Product Recommendations workflow for creating such recommendations. It covers how to build a rule-based Product Engine, restrict it to out-of-stock product pages, filter candidates and place the results where visitors can see them. Recommendations are a practical navigation option, not a guarantee of recovered sales. The configuration should be tested against the store’s catalog, theme, stock process and caching setup.
Why show alternatives on an out-of-stock WooCommerce product page?
When a product is unavailable, the most useful recommendation is not necessarily the most popular product in the catalog. It should give the visitor a realistic next choice. That may mean a product in the same category, with a comparable relative price and a current stock status that allows the customer to continue shopping.
The purpose is to keep the product page useful even when its main purchase action is unavailable. A visible alternative can help the visitor compare options without requiring a new search. However, it should be presented as an optional, relevant product choice rather than as an equivalent replacement by default. Category membership alone does not prove that two products have the same attributes, format, compatibility or fulfillment suitability.
Alternative recommendations should also be distinguished from other responses to unavailable stock. A store may use a back-in-stock process or other product-page messaging, but the documented workflow here focuses on showing purchasable alternatives. It does not establish that recommendations are appropriate for every catalog, nor does it guarantee higher conversion, recovered sales or additional revenue.
The documented WooCommerce setup for out-of-stock alternatives
WooCommerce Product Recommendations supports a rule-based Product Engine that can recommend products on an out-of-stock product page. The documented sequence is to create the engine, define which products may be recommended, deploy it to a product-page location and add a visibility condition based on the stock status of the viewed product.
Begin by treating product selection and page visibility as separate configuration tasks. The selection rules determine the candidate products. The visibility condition determines when the engine appears. For this use case, the condition should require the viewed product to have the Out of stock status. That prevents the replacement block from appearing on every product page, including pages where the original product can already be purchased.
The exact menu names and workflow described here apply to WooCommerce Product Recommendations. Other WooCommerce extensions may use different interfaces, terms or configuration steps. The extension is a third-party WooCommerce product; it should not be treated as a WPBetterPlugins product or as a tool developed, owned or supported by WPBetterPlugins.
Separate eligibility rules from display rules
Filters narrow the products that can enter the recommendation pool. Visibility conditions control whether the recommendation engine is displayed at all. Keeping these two checks separate makes the setup easier to review:
- Eligibility: decide which products are available and relevant enough to be considered.
- Visibility: show the engine only when the viewed product has the Out of stock status.
- Deployment: place the engine in a product-page location that remains useful when the unavailable product has no active purchase action.
Test this arrangement with representative products before publishing it on a live store. Confirm that an in-stock source product does not display the replacement engine and that an out-of-stock source product does.
How to choose suitable replacement products
The documented out-of-stock example starts with three practical filters: the current product category, relative pricing and stock status. Together, they create a more focused candidate pool than a general recommendation rule. The stock filter is particularly important because an alternative that cannot be purchased does not solve the original availability problem.
Use an explicit In stock filter when the store’s fulfillment policy requires immediately available products. Then consider the current product category as a relevance signal. This can keep recommendations within a recognizable product group, but it should not be the only review. Two products may share a category while differing substantially in product type, attributes, compatibility or intended use.
A relative-price rule can help when the store’s catalog contains products with clearly different price positions. It may prevent a visitor from being directed to an option that is technically related but unsuitable for the expected budget. The rule is not established as optimal for every catalog or industry, so review the actual results rather than applying it automatically.
Store owners should also consider fulfillment constraints and customer suitability. A candidate may be in stock but still be a weak recommendation if its format, attributes or purchasing conditions do not match the context of the unavailable item. Backordered products require a separate decision: include or exclude them according to the store’s actual fulfillment policy, and verify how the stock filter treats them in the configured workflow.
Filters first, ranking signals second
Filters and amplifiers serve different purposes. Filters narrow eligibility; amplifiers influence the order of products that have already passed those filters. This distinction is useful when configuring a recommendation engine:
- Use category, price and stock-status rules to create a candidate pool.
- Use rating, popularity, freshness or another documented amplifier to influence the order of eligible products.
- Review the live sequence instead of assuming that one ranking signal will always produce the most suitable result.
The documented example can prioritize higher-rated products and can favor newer products through rating and freshness amplifiers. These signals should influence presentation, not replace the basic checks for availability and relevance. Product availability can change after recommendations are generated, so filtering does not eliminate every possible stale-result scenario.
Where to place recommendations on the product page
For out-of-stock alternatives, WooCommerce documentation identifies Product > After Product Meta as a suitable placement. This location allows the recommendation block to appear in the product information area even when the original item cannot be added to the cart.
Placement after the add-to-cart button is less suitable for this specific case. WooCommerce states that recommendations deployed in the After Add-To-Cart Button location are not displayed when the viewed product is out of stock. If the purchase action is unavailable, a recommendation positioned after that action may therefore fail to provide the intended alternative path.
Test the exact position in the active theme. Review the heading, product count, card presentation and mobile layout rather than treating one documented example layout as a universal user-experience requirement. The right display density depends on how the store’s theme presents product information and how easily visitors can compare the suggested items.
Caching, theme compatibility and troubleshooting
Conditional recommendations depend on current product and page behavior. If a cache serves an older version of the product page, the engine may fail to apply the out-of-stock condition correctly. A cached result may also show a product that is no longer available or prevent a dynamic recommendation block from appearing.
When page caching interferes with the display, consider AJAX rendering as a documented option that can bypass the page cache. WooCommerce also notes that AJAX rendering may introduce a visible loading delay. That trade-off should be assessed on the actual storefront, especially on mobile devices and on pages where the recommendation block is important to the visitor’s next action.
Theme compatibility requires similar care. WooCommerce states that Product Recommendations has not been optimized for block themes and that recommendation engines may not work as expected when a block theme is active. Compatibility with a specific theme, hosting stack, caching layer or other plugin must be tested on the individual store. Do not assume that a configuration that works in one environment will behave identically in another.
A focused troubleshooting pass
Use a short, repeatable review when recommendations do not appear correctly:
- Open an out-of-stock product page as a visitor and confirm whether the engine is visible.
- Check that the viewed product meets the Out of stock visibility condition.
- Confirm that suggested products still meet the In stock requirement.
- Compare behavior after cache regeneration and, where applicable, with AJAX rendering enabled.
- Review the active theme and other relevant configuration for rendering conflicts.
- Check the recommendation output after inventory changes instead of relying only on an administration preview.
These checks help distinguish a rule problem from a rendering or cache problem. They do not remove the need to test the final storefront with representative products.
How to validate the recommendation strategy after setup
Validation should cover visibility, availability, relevance and presentation. Open several representative out-of-stock product pages and confirm that the engine appears only where intended. Then inspect every suggested item for current availability, relevant product type, attributes, price positioning and fulfillment suitability. A product should not remain in the recommendation set simply because it matches a category.
Verify the product links, displayed prices, variations and mobile presentation on the live storefront. Repeat the review after inventory updates and cache regeneration, because stock data and rendered pages can become stale. If the store uses a block theme, include that environment in the test before purchase or deployment decisions are finalized.
WooCommerce product documentation describes analytics for recommendation revenue and conversions, with reports that can be filtered by date, converted product and location. Use those reports as measurement tools, not as proof of guaranteed improvement. If recommendations repeatedly produce unavailable, stale or weakly matched products, revise the filters, ranking signals or deployment rules.
In summary, the documented workflow is to create a Product Engine, filter candidates for availability and relevance, use ranking signals carefully, and display the result under the out-of-stock product’s metadata. The Out of stock visibility condition keeps the engine focused, while the In stock filter helps prevent unusable suggestions. Category and relative-price rules can narrow the pool, but catalog-specific review remains necessary. Finally, test placement, caching, AJAX behavior, theme compatibility and live inventory output before relying on the recommendations in production. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.