How to handle out-of-stock products in WooCommerce with alternatives, back-in-stock alerts and honest backorders

How To Implement

• 1 Split stock-outs into three states before you change the page

  Use one rule for “temporarily out of stock but replenishable”, one for “uncertain restock date”, and one for “discontinued”. Baymard’s guidance is clear: temporary stock-outs should still offer a buying path where possible, while discontinued products should push alternatives hard and be labelled clearly.

• 2 Set stock at variation level where the shopper decision is variant-specific

  In Products → Edit product → Product data → Variations, open each variation, tick Manage stock?, set Stock quantity, Allow backorders? and Low stock threshold, then Save changes and Update. WooCommerce supports product-level, variation-level, or mixed stock management, but OOS handling is usually cleaner when the real constraint is the selected size/colour/option rather than the parent product.

• 3 Hide only the dead-end variations, not every out-of-stock path

  WooCommerce can hide out-of-stock variations from dropdowns when WooCommerce → Settings → Products → Inventory → Hide out of stock items from the catalog is enabled, and the variation is managed at variation level, has quantity 0 or status Out of stock, and has backorders disabled. This is useful where an impossible option genuinely wastes clicks. Measurement note: do not switch this on globally until you have checked what it does to your alert capture, because the official Woo back-in-stock extension cannot collect signups for products or variations that are hidden from the catalogue.

• 4 For temporary stock-outs, prefer an honest backorder or pre-order over “notify me” as the only option

  In core WooCommerce, set Allow Backorders? at product or variation level and make the lead time explicit in the buy box copy. If you want lightweight preorder messaging with a visible date, Easy Pre-Orders uses WooCommerce → Settings → Easy Pre Orders for global defaults and Product Data → Easy Pre-Orders per product for the enable flag, label, button text, availability date and extra information. If you need formal preorder release handling, fees or “pay later”, WooCommerce Pre-Orders adds Product Data → Pre-Orders with Availability Date/Time and When to charge options, but that extension applies pre-orders at product level, not per variation; Woo’s own docs point you back to core backorders for variation-specific temporary stock-outs.

• 5 Add comparable alternatives on the out-of-stock PDP

  With WooCommerce Product Recommendations, go to WooCommerce → Recommendations → Engines → Create new, choose a Product engine, then add filters so the alternatives stay genuinely similar, for example category, stock status and price range. Woo’s docs specifically call out a Relative Price filter for Product engines, which is useful for keeping substitutes within a believable range instead of sending the shopper to unrelated accessories or much more expensive items. Then deploy the engine to a product-page location such as After Add-To-Cart Button, After Product Meta, Before Tabs or After Tabs.

• 6 Handle classic themes and block themes differently

  On classic themes/templates, you can place custom OOS messaging or alternative modules around the buy box using hooks such as woocommerce_after_add_to_cart_button, woocommerce_after_single_product_summary, or woocommerce_after_single_variation. On block themes / Site Editor, edit Appearance → Editor → Templates → Single Product and move or add blocks there. Important caveat: WooCommerce’s own Product Recommendations documentation says the extension is not yet optimised for block themes, so test on staging before using it as the main alternative module on a Site Editor build.

• 7 If you want native WooCommerce back-in-stock capture, use Back In Stock Notifications carefully

  After installing, go to WooCommerce → Settings → Stock Notifications and configure: – Require double opt-in – Minimum stock quantity – Display opt-in checkbox – Catalog sign-up prompt – email templates under WooCommerce → Settings → Emails The plugin supports Simple, Variable, Product Bundles, and Woo Subscriptions product types; it stores selected variation attributes; and it only shows the signup form when the product or variation is Out of stock, not On Backorder. Per product, you can disable it in Products → Edit product → Inventory → Stock Notifications.

• 8 Only notify once inventory is stable enough to fulfil

  In the Woo extension, use Minimum stock quantity so alerts do not fire the moment one or two units land. That matters most for scarce or batch-restocked products where an early blast just recreates frustration. The extension also uses Action Scheduler and loopback requests, so check Tools → Site Health → Status if notifications do not send.

• 9 If the store runs Omnisend, you can build the alert and follow-up there

  Omnisend documents a WooCommerce back-in-stock flow: create the form in Forms → Create Form → “Gather interest in out-of-stock”, set targeting to Show on out-of-stock product pages, add a Legal Consent block if you want contacts to become subscribers rather than non-subscribers, and then create the workflow in Automation → Create Workflow → Back in Stock. For embedded forms on WooCommerce, Omnisend says to paste the embed code into the product short description or description. If you add SMS, Omnisend notes that its back-in-stock SMS cannot use dynamic event data such as specific product names, so keep SMS copy general and use it only where speed matters enough to justify the channel.

• 10 If the store runs Klaviyo, treat WooCommerce BIS as a custom integration unless the current app stack documents a native

  Klaviyo documents back-in-stock for some native integrations and provides guides for custom platform integrations, custom events and custom catalog feeds. I did not find a current official turn-key WooCommerce back-in-stock setup guide equivalent to Omnisend’s Woo guide during this research, so the safe assumption for planning is: capture on-site with your Woo/plugin layer, then sync subscribers, events and catalogue entities into Klaviyo via documented integration or API routes.

• 11 Keep availability truthful everywhere the shopper and Google can see it

  Your PDP copy, structured data and Merchant Center feed should agree on stock state. Google’s merchant documentation says out-of-stock products may show clear text such as “sold out” or a disabled/greyed-out buy button; if there are variants, you may disable only the unavailable options in the selection grid; and for preorder or backorder items, the page must display the expected shipping date. That dovetails with CMA and ASA guidance against misleading scarcity or urgency claims.

• 12 Before launch, baseline the out-of-stock journey and test it on staging

  Record what happens today when a shopper lands on an OOS PDP, selects an OOS variation, joins an alert, returns from a restock email, or buys a backordered item. If you use order-related extensions, confirm HPOS compatibility in WooCommerce → Settings → Advanced → Features, because Woo will block switching if incompatible extensions are active.

How To Measure

Pitfalls

• Mistake: hiding all OOS variations and then wondering why waitlists fall. WooCommerce’s own rules for hiding OOS variations depend on variation-level stock and no backorders, but the Woo Back In Stock Notifications extension explicitly says customers cannot sign up if out-of-stock products or variations are hidden from the catalogue. Use hiding selectively, not reflexively.
• Mistake: “alternatives” that are really accessories, complements or much pricier products. Baymard’s recommendation is to show alternatives, not supplementary suggestions, and Woo Product Recommendations gives you the filtering tools to enforce that. If the substitute would feel like a bait-and-switch to a reasonable buyer, it is the wrong substitute.
• Mistake: alerting on the first unit back in. Official Woo BIS includes a minimum stock quantity trigger for a reason. If you notify faster than you can fulfil, you convert interest into frustration and train subscribers not to trust the alert.
• Mistake: using urgency or scarcity copy that is not inventory-backed. CMA guidance says scarcity or “act fast” claims can be misleading where stock is actually available, where replenishment is imminent, or where the claim creates a false need to rush. ASA guidance says advertisers must make a reasonable estimate of demand, make limitations clear, and must not falsely claim limited availability.
• Myth: “Email me when back in stock” is enough on its own. Baymard’s research does not support using email alerts as the primary answer for temporary stock-outs; where you have a credible replenishment date, the stronger primary move is often to let the customer commit to the order with an honest delay.
• Myth: SMS is automatically better than email for restocks. SMS can be worth testing for scarce, fast-moving restocks, but the published evidence base here is thin and platform-heavy. Omnisend also notes that its BIS SMS cannot use dynamic product event data, which limits how specific the message can be.

Examples

FAQs

Sources & Further Reading

• Baymard Institute — Allow Users to Purchase Temporarily ‘Out of Stock’ Products by Increasing the Delivery Time (68% Don’t) – Independent UX research on why temporary stock-outs should not become dead ends, including the 68% and 30% findings. Date: Published 18 July 2017; updated with new data in 2025.
• Baymard Institute — 15 Common UX Pitfalls Luxury Retail E-Commerce Sites Suffer From – Reinforces the “out of stock” dead-end problem and the abandonment risk when only alerts are offered. Date: 8 June 2021.
• WooCommerce — Variable Products Documentation – Primary source for variation-level stock, hiding OOS variations, dynamic dropdown behaviour, and the >30 variation performance caveat. Date: date not stated on page.
• WooCommerce — Back In Stock Notifications: Store Owner’s Guide – Primary source for native Woo BIS setup, supported product types, minimum stock quantity, double opt-in, variation handling, insights dashboard and export. Date: date not stated on page; requirements section reflects current Woo 8.2+ compatibility.
• WooCommerce — Product Recommendations: Store Owner’s Guide – Primary source for engines, filters, Relative Price filter, product-page locations and deployment logic. Date: date not stated on page.
• WooCommerce — Product Recommendations Documentation – Important caveat that Product Recommendations is not yet optimised for block themes / Site Editor. Date: date not stated on page.
• WooCommerce — Customizing Your Product Pages – Primary source for block-theme Single Product template editing and related product block behaviour. Date: published 2024-era documentation page; exact date not shown in opened lines.
• WooCommerce Developer Docs — Theming for Woo Blocks – Primary source for Single Product template files and Site Editor / block-theme structure. Date: last updated 16 June 2026.
• WooCommerce Code Reference — Action and Filter Hook Reference – Hook reference for classic-theme placements such as woocommerce_after_add_to_cart_button and woocommerce_after_single_product_summary. Date: 28 May 2026.
• WooCommerce — Easy Pre-Orders Documentation – Primary source for lightweight preorder messaging, availability date and per-product enablement. Date: date not stated on page.
• WooCommerce — Pre-Orders Documentation – Primary source for availability dates, charge timing, preorder fee, and the limitation that variation-specific temporary stock-outs should use core backorders. Date: date not stated on page.
• WooCommerce — High-Performance Order Storage Documentation – Primary source for HPOS defaults, migration path, and incompatible-extension handling. Date: page current as accessed June 2026.

About This Page

• Written By: Eliot Webb – Founder & WooCommerce CRO Consultant
• Last Reviewed: 17 Jun 2026
• Last Updated: 17 Jun 2026