# Variant Selector on Product Cards A/B Test Example

Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/variant-selector-on-product-cards-ab-test-example

## Hypothesis

If shoppers can pick a color or size right on the product card, they may not need to open each detail page just to find a version that suits them. Removing a step where some shoppers drop off while choosing could lift purchase conversion rate.

## When to run this test

Put this test on your list when listing data shows shoppers moving back and forth between products to find the right color or size: quick returns from product pages, session recordings of detail pages opened one after another, or support tickets about sizes and colors. If the selector works, shoppers choose on the card, land on the product page with that variant already selected and reach a purchase in fewer steps. If you cannot show stock status reliably for each variant on the card, fix the stock data first; an out-of-stock option should never look selectable.

## Primary metric

**Purchase conversion rate**: Compare purchases among eligible visitors assigned to the variant-selector experience.

## Other metrics

- **Listing-to-product click-through rate**: Check whether visits to product pages change.
- **Return-to-product-page rate**: Review rapid returns as a possible selection issue; the return alone does not explain why it happened.
- **Return rate**: Track whether selecting the wrong variant increases returns.
- **Page load time**: Make sure additional images do not slow the page.

## What to check before and during the test

- **Selector**: Add a predefined variant selector to eligible product cards.
- **Behavior**: Predefine the available options and image-preview behavior, then keep them fixed.
- **Keep constant**: Keep card size, product order and other card details unchanged.
- **Selection carryover**: Carry the selected variant through to the product page.
- **Mobile**: Check touch targets; test option count or preview behavior separately.

## What to watch when reading the result

- If listing-to-product click-through rate rises while purchase conversion rate stays flat, the selector may be drawing interest without making the decision easier. A purchase lift is not enough to ship if return rate climbs or page load time gets worse. Check returns again once the test orders are past their return window.
- Do not generalize a result from one category to categories without variants; if you plan to use the same selector in another category that has variants, validate it there. Review mobile on its own and confirm touch targets stay above the accessibility minimum, since cramped controls can show up later as wrong selections and returns.
- Purchases are rarer than clicks, so before reading a small or unclear gap, enter the current purchase rate and the lift you care about into the [sample size calculator](https://alidemirbas.com.tr/en/calculators/sample-size-calculator) to see the sample each variant needs. If the test did not reach that sample, record the result as unresolved by this test rather than as no effect. Do not change the displayed options or the preview behavior while the test runs.

## Frequently Asked Questions

### Should a card’s selected variant carry into the product page?

Yes. Losing it forces another selection. Define the displayed options and preview behavior beforehand and preserve the selected variant when opening the detail page.

### How should unavailable variants be displayed?

Do not present them as purchasable choices. Show availability accurately and monitor returns or corrections that may indicate unsuitable selections.

### Which products are suitable for variant selection on cards?

Products with meaningful size or color choices may be suitable. Define the eligible group and use purchase conversion as the primary outcome. Do not generalize to products without variants.