Skip to main content
inconclusive

Product: Less Or More Visible Prices on Product Page

Hypothesis

If we change the visibility and display of prices in the floating product CTA area, then conversion rates will improve because appropriate price presentation influences purchase intent at the decision moment

PricingProduct PageCross-Industrymobile-uxprice-visibilitypricing-display

Test Results

22,957
Sample size

Key Learning

Context: Key actions on the product disappear as users scroll, creating a gap between intent and the ability to act.

What was tested: Price display format and prominence in conversion UI (especially on mobile) significantly impacts purchase intent; price must be visible but not so dominant it triggers sticker shock

Result: No statistically significant difference was detected. Pricing tests that are inconclusive may indicate the price itself isn't the issue — the perceived value or the framing might matter more.

How to Apply This to Your Site

This experiment tested product: less or more visible prices on product page but produced no statistically significant change. The test was run on a product page page in the cross-industry industry. Inconclusive results suggest this particular change may not be a priority — focus testing effort on higher-impact areas.

Before you test: Consider that pricing tests typically require large sample sizes to detect small effects. Run your test for at least 2 full business cycles to account for weekly traffic patterns.

What Was Tested

In this mobile product page experiment, the variation changed the look of the floating button area once a product was chosen. The variation showed a button with 1) pricing totals along with 2) a link back to the edit area and 3) a button that allowed to add to cart directly. Whereas the control only linked back to the top of the page where the product selction was possible. Impact on adds-to-cart and sales was measured.

Methodology

Confidence Level
70%

Build On These Learnings

Save your own experiments, spot winning patterns across your test history, and stop repeating what's already been tried.

Related Experiments

Explore More Experiments