Product Detail Page
Out of Stock: Remove the Button or Notify Me A/B Test
An out-of-stock label explains why a product cannot be bought. Replacing the purchase control with a stock-alert option also gives interested visitors a way to hear back. Sign-ups describe use of this new path; assess its value through later purchases and notification complaints.
A/B test scenario. This page is a test plan, not the result of a real experiment.
- Product page
- Purchase rate after restock
Variant A vs Variant B
Two alternatives; neither is the incumbent.
- Changed
- Options
- Page
- Product page
- Difference
- changed
Hypothesis
If the purchase button gives way to a "notify me when it's back" option, interested visitors may follow the product instead of leaving it; a plain "out of stock" label explains the situation and leaves the next step to them. The notify arm could build up back-in-stock notification signups, but that demand only pays off if it turns into purchases after restock.
Test plan
When to run this test
Steady traffic to sold-out items, support requests asking when a product will be back, or quick exits from out-of-stock pages mean interest in those products may be going to waste. If the notify path works, visitors in that arm leave a signup, and it brings more purchases once stock returns. If visitors want a similar product rather than this one, look at the alternative-product recommendations first. Before launch, check that any restock date is labeled as an estimate when it is one, and that the flow carries no urgency message unsupported by live inventory.
How to measure success
Purchase rate after restock
After the product returns to stock, compare purchases among all eligible assigned visitors over the same follow-up window.
Also track
- Back-in-stock notification signup rateSignups exist only in the notify arm, so they do not compare the two arms; they show how much the added path is used.
- Alternative product page visit rateMeasure visits to alternative product pages among assigned visitors who see an alternative-product link.
- Notification complaints and unsubscribesAmong users who consent to notifications, track complaints and unsubscribes over the same follow-up period.
How to set it up
- ComparisonCompare an out-of-stock status label with one defined back-in-stock notification option.
- ChannelChoose one notification channel and consent flow before launch.
- AlternativesKeep alternative-product recommendations the same.
- Stock timingIf shown, use the same accurate availability estimate in both arms.
- DeviceCheck notification signup completion on mobile and desktop.
What to watch when reading the result
- 1Signups exist only in the notify arm, so they cannot compare the two arms on their own. Make the main comparison on purchase rate after restock, across all eligible visitors assigned to each arm; a flow that collects many signups but brings notification complaints and unsubscribes is not a winner.
- 2If price, images, product details and alternative-product recommendations stay the same in both arms, the difference comes from the notify mechanism alone. Report alternative product page visits as a diagnostic, and do not narrow the main comparison afterward by who saw the link.
- 3Ask only for what is needed to send the stock notification; extra fields can lower signups for reasons that have nothing to do with the mechanism. Read form completion on mobile and desktop separately.
- 4Purchases after restock may be rare and can only be measured once the product is back. Find the sample each arm needs for that rate with the sample size calculator up front, and plan the follow-up period around it. Should the gap still be small, leave the question open rather than naming a winning arm.
Frequently Asked Questions
Is the back-in-stock signup rate enough to compare groups?
No. The status-only control has no signup mechanism. Compare purchases after restocking across all eligible assigned visitors. Monitor notification complaints and unsubscribes too.
What information should the notification form request?
Collect only what is needed. Record the user's request, provide the required privacy notice and send the requested notification. Handle any promotional-message consent and applicable Turkish IYS requirements separately. Do not merge disclosure with consent. Check completion by device and avoid unverified urgency.
Should I show an expected restock date?
Show the same reliable estimate in both groups without presenting it as certain. Alternative-product clicks are diagnostic. Keep the common eligible entry population for the main purchase comparison rather than selecting people by later exposure.
More tests in Product Detail Page
All testsOffering Product Customization Before Buying A/B Test
Product pageAdd-to-cart rate
An experiment example on offering colour, engraving or combination choices before purchase, against a ready-made product. Setup, arms and KPI included.
Showing Country of Origin on Product Pages A/B Test
Product pagePurchase conversion rate (CR)
An A/B test example comparing a page with no origin detail against one stating where the product was made or designed. See both arms and the KPI.
Bundles From Similar or Mixed Price Tiers A/B Test
Product pageRevenue per visitor (RPV)
A CRO experiment on bundle composition: items from one price range against a mix of cheap and expensive products. See the value logic and the KPI.