# Offering Product Customization Before Buying A/B Test

Page: https://alidemirbas.com.tr/en/lab/ab-test-library/tests/offering-product-customization-before-buying-ab-test

## Hypothesis

Letting buyers choose a color, engraving or combination on the product page may make the product feel better suited to them and make them readier to add it to the cart. The add-to-cart rate, counting standard product adds too, may rise, although a long configuration step could delay the purchase instead.

## When to run this test

Requests for a personal touch tend to surface in support tickets about colors or engraving, on-site searches for personalized versions, or surveys where that kind of request keeps coming up; those are the cue for this test. If the idea holds, some visitors in the variant complete a customization, while those who want the standard product still add it without getting stuck. If add-to-cart is low because of price or missing product information, look into that first. Make sure before launch that every combination on offer can be produced and fulfilled from stock, and that the preview matches the product that will be made.

## Primary metric

**Add-to-cart rate**: Compare all successful add-to-cart actions per assigned visitor, including standard product additions in the customization arm.

## Other metrics

- **Customization completion rate**: Report completion among visitors who start customizing and the number of completed customizations per assigned visitor.
- **Return rate**: Compare returns over the same follow-up period and note any differences in return policy.
- **Cart abandonment rate**: Use the same definition for abandonment among visitors who add an item to the cart.

## What to check before and during the test

- **Change**: Add one predefined product customization option to the variant.
- **Keep constant**: Keep the price, base product option, CTA and other product information unchanged.
- **Behavior**: Review customization use alongside purchases.
- **Purchase path**: Make sure customization does not block adding or buying the standard product.
- **Separate tests**: Test the number of steps, preview or default selection separately.

## What to watch when reading the result

- Judge the variant by the add-to-cart rate including standard product adds, and report customization completion both among starters and across all assigned visitors. If adds rise while cart abandonment rises too, customization may be losing people along the way, so the rise alone does not justify shipping the variant.
- Explain the actual return terms before purchase, and do not assume every customized item is non-returnable. Give both arms the same time for returns to come in before comparing them, and note any policy difference in the result. The finding applies only to the customization option you tested.
- A slow-loading customization flow can cause some variant visitors to drop out of tracking, so check that the traffic split matches the plan (sample ratio mismatch). If the add-to-cart gap is small or unclear, use the [sample size calculator](https://alidemirbas.com.tr/en/calculators/sample-size-calculator) to see how many visitors per arm the effect you care about requires, and if your sample falls short, do not treat the result as settled. Try step count or the preview in separate experiments.

## Frequently Asked Questions

### How should additions to cart be counted?

Include all successful additions per assigned visitor, including standard products in the customization group. Report customization completion among starters and across all assigned visitors. Use a common cart-abandonment definition.

### Which customization options should be excluded?

Do not offer combinations that exceed production or stock constraints. Ensure previews match what can be produced. Keep step count and the default combination fixed.

### How should returns for customized products be handled?

Explain the actual policy before purchase rather than assuming all customized products are nonreturnable. Compare returns over equal follow-up periods and document policy differences.