Skip to content
CRO

Ecommerce A/B Testing Ideas: 25 Things You Can Test

25 ecommerce A/B test ideas across discovery, category pages, product pages, cart, checkout and offers, each tied to the evidence that justifies it and a metric.

Quick answer

Good ecommerce A/B tests come from evidence, not lists. The 25 ideas below cover discovery, category pages, product pages, cart, checkout and offers. Each is paired with the evidence that would justify running it and the metric to judge it by. Pick ideas that match problems your data already shows, on pages with enough traffic, write a clear hypothesis, set a primary metric and guardrails such as margin and returns before launch, run to the planned sample size in full weeks, and record every result.

How to Use This List

Don't run these in order. Start from your funnel and research: find the stage that loses the most shoppers and the evidence for why, then look for ideas in the matching group. The method behind testing, including sample size and analysis, is covered in ecommerce A/B testing; how to run testing as an ongoing program is in ecommerce experimentation framework. Shopify stores can also use 50 Shopify CRO testing ideas.

Worth noting

These are hypotheses, not proven wins. We don't quote uplift figures because results depend on your store, traffic and implementation.

Discovery: Search, Navigation and Filters (Ideas 1–5)

#TestRun it when evidence showsPrimary metric
1Visible search field in the mobile header instead of an iconSearchers convert well but mobile search use is lowRevenue per session
2Autocomplete with product images and pricesMany searches are refined or abandonedSearch-to-product view rate
3Navigation labels rewritten in shoppers' wordsTree tests or recordings show people opening the wrong menusCategory click-through, product views
4Filter chips above the grid on mobile instead of a hidden drawerFilter use on mobile is far below desktopProduct view rate from listings
5No-results page with corrections, popular categories and alternativesHigh exit rate after zero-result searchesSearch exit rate

Category Pages (Ideas 6–8)

#TestRun it when evidence showsPrimary metric
6Product cards showing a deciding attribute (sizes in stock, key spec, colour count)Shoppers bounce between listing and product pagesAdd-to-cart rate from listing sessions
7Default sort changed from newest to best-selling or relevanceLow click-through from the first rowsList click-through
8Two products per row on mobile instead of oneShoppers scroll deep without clickingList click-through, product views

Product Pages (Ideas 9–14)

#TestRun it when evidence showsPrimary metric
9Estimated delivery date next to the add-to-cart buttonVisits to the shipping page followed by exitsAdd-to-cart rate
10Rating and review count near the product name and priceShoppers scroll to reviews before decidingAdd-to-cart rate
11Gallery leading with the product in use or at scaleLow image engagement; questions about size or lookAdd-to-cart rate
12Fit or sizing guidance shown inline next to the size selectorSize guide opens followed by exits; fit-related returnsAdd-to-cart rate (guardrail: returns)
13Sticky add-to-cart bar on mobileLong mobile pages with low mobile add-to-cartMobile add-to-cart rate
14Short benefit summary above the foldRecordings show scrolling without interactionAdd-to-cart rate

Not sure which tests your evidence supports?

ZSpace builds prioritized test roadmaps from your funnel data, recordings and user research.

Start a Project

Cart (Ideas 15–18)

#TestRun it when evidence showsPrimary metric
15Progress toward a free-delivery thresholdMany orders sit just below the thresholdAverage order value (guardrail: conversion, margin)
16Delivery cost estimate shown in the cartCart visits followed by exits or policy-page viewsCart-to-checkout rate
17Express wallets shown in the cartMobile shoppers start checkout at a low rateCheckout starts, completed orders
18Cross-sells moved below the checkout button or removedRecordings show cart distraction; low cart-to-checkoutCart-to-checkout rate (guardrail: AOV)

Checkout (Ideas 19–22)

What you can test here depends on your platform. Hosted checkouts restrict changes; on Shopify, customizing the information, shipping and payment steps with checkout UI extensions requires Plus. See Shopify checkout optimization.

#TestRun it when evidence showsPrimary metric
19Guest checkout made the most prominent optionDrop-off at the account stepCheckout completion
20Address autocompleteFrequent address errors or long form timesCheckout completion
21Payment methods reordered or local methods added per marketPayment-step exits concentrated in certain marketsPayment step completion
22Returns and security reassurance near the pay buttonExits at payment; survey mentions of trustCheckout completion

Offers and Trust (Ideas 23–25)

#TestRun it when evidence showsPrimary metric
23Returns window and process stated plainly on product pagesReturns questions in support and surveysAdd-to-cart rate (guardrail: returns)
24Bundle or multi-pack offered as the default choiceCustomers often buy several units separatelyRevenue per session (guardrail: margin)
25Risk-reducer such as a guarantee instead of a first-order discountDiscount-acquired customers rarely returnConversion and margin per new customer

Write Each Test as a Hypothesis

Use one template for every test: because we observed [evidence], we believe [change] for [audience] will cause [effect on behavior], which we'll measure with [primary metric], while watching [guardrails]. It forces a link between evidence and change and makes results easier to learn from.

Choose Guardrails Before You Launch

  • Gross margin or discount rate for any pricing or offer test
  • Returns rate for sizing, imagery and expectation-setting tests
  • Average order value for cart and cross-sell tests
  • Page speed for tests that add scripts or media
  • Error and payment failure rates for checkout tests

When Not to A/B Test

Some changes should just be made: broken functionality, accessibility failures, misleading information and obvious usability bugs. On low-traffic stores, tests may take too long to reach a reliable answer; test larger changes on the highest-traffic pages and use user research for the rest.

Record Every Result

Keep a searchable log of hypothesis, evidence, variants, dates, sample, results with uncertainty, decision and screenshots. Losing and flat tests are as valuable as winners because they stop the team retesting the same idea.

Want tests that teach you something?

Talk to ZSpace about a CRO audit and test roadmap and variant design.

Start a Project

Conclusion

The best test ideas are the ones your evidence already points to. Use this list to find a matching idea, write it as a hypothesis, set guardrails, run it properly and record the result. For the full diagnostic starting point, see the ecommerce CRO audit.

FAQ

Common questions

The idea tied to the biggest, best-evidenced problem on a high-traffic page. Look at where the funnel drops most and what recordings, surveys and tests say about why, then pick the test that addresses it.

Get in touch

Have a project in mind?

Whether you're building a new digital product, improving an existing website, or looking to automate part of your business — let's talk.