# Which Detail Should Lead a Product Card? A/B Test

Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/which-detail-should-lead-a-product-card-ab-test

## Hypothesis

If shoppers in this category narrow products down by budget first, price-first cards may make the choice easier; if they want reassurance about quality, cards that lead with rating and review count may. Whichever order fits that decision pattern better could show the higher purchase conversion rate (CR).

## When to run this test

Plan this test when shoppers seem unable to find the detail they decide on right on the card: heavy use of sorting by price or of the rating filter, session recordings of product pages opened just to see the price or rating and closed again, or survey answers about how shoppers choose. Expect one of the two orders to make the choice easier and turn more selections into purchases. If many products lack a rating or reviews, limit the test to products that have both details and handle the empty space on incomplete cards the same way in both versions.

## Primary metric

**Purchase conversion rate (CR)**: Compare purchases among all eligible visitors assigned to each product-card hierarchy.

## Other metrics

- **Listing-to-product click-through rate**: Compare transitions from the listing to product pages.
- **Product-page return rate**: Review return visits alongside the next action; a return alone does not prove the card was misleading.
- **Add-to-cart rate**: Compare successful add-to-cart actions among all eligible assigned visitors.
- **Unintended click rate**: Use predefined interaction events or usability observations to identify unintended taps.

## What to check before and during the test

- **Hierarchy**: Compare price-first cards with cards that place rating and review count first. Include products that have both kinds of information.
- **Keep constant**: Keep the number of details, price, image and CTA unchanged.
- **Discovery**: Review listing clicks and product selection together.
- **Interactions**: Check unintended taps and returns from product pages; do not treat every return as negative.
- **Separate tests**: Test the number or type of details separately.

## What to watch when reading the result

- A gap in listing-to-product click-through rate does not pick a winner unless it shows up in purchase conversion rate (CR). Do not ship an order that lowers add-to-cart rate or raises the unintended click rate, even if conversion is close, and read product-page returns alongside what shoppers do next.
- Treat the result as belonging to the category you tested and to products that show both details. Rating may carry more weight in one category than in another, so measure again in other categories before applying the winning order across the catalog.
- If the two orders end up close, this sample may simply not separate them. Use the [A/B test significance calculator](https://alidemirbas.com.tr/en/calculators/ab-test) to see whether the conversion gap could be chance; if it could, do not declare a winner and choose on secondary grounds such as consistency with your card design.
- Confirm that the price and rating on the card are calculated the same way as on the product page, because a mismatch measures inconsistency rather than hierarchy. If a card highlights a promotion, state its actual terms clearly and the same way in both versions, or the result reflects missing information instead of the real offer.

## Frequently Asked Questions

### How should products without ratings or reviews be handled?

Use the predefined eligibility rule. Handle missing information consistently in both arms so empty states do not introduce another unintended difference.

### Do more returns from product pages prove unmet expectations?

No. Examine subsequent behavior and direct usability evidence. A quick return alone does not explain its cause. Use purchase conversion as the primary outcome.

### Can the winning information hierarchy be used across the catalog?

Validate other relevant categories first. Keep information calculations consistent with product pages. Different information types or quantities require their own comparison.