Product Configurator UX: 4 Changes We A/B Tested on a Custom Product Builder

Product configurator UX: 4 tests

[ FREE CRO TEARDOWN ]

Find the 3 biggest revenue leaks on your store.

Every day a conversion leak goes unfixed, you're paying for traffic that doesn't buy. Get a 5-minute Loom through your PDP, cart, and checkout, with mockups of the fixes. No pitch.

Get My Teardown
or
Book a Call

Most product configurator UX advice says the same thing: fewer steps, faster inputs. We tested exactly that, and it lost.

A home decor brand sells a made-to-measure product. Shoppers build it in a step-by-step product configurator: pick a size, measure, enter width and height, answer a few fit questions, then review. It is the main path to purchase.

We tested four product configurator UX changes against the existing builder. Three lost. The one that held up was not a speed change at all.

Who this is for: Shopify brands with a custom product builder, quiz-style configurator or made-to-measure flow.
The data: one A/B test with control plus four variations, measured on shoppers who opened the builder. Client anonymized.

The Four Changes

The variations were stacked. Each one kept the changes before it and added one more:

Version What it added
Control The existing 7-step builder
Variation 1 Cut the "Are you ready to measure?" step, plus friendlier copy on the measuring step
Variation 2 A new measurement picker: whole inches in a dropdown, fractions on a slider
Variation 3 An exit popup: "Save your frame?" Leave your email and get a link back to the exact build
Variation 4 New images on one of the fit questions

The Result: Only the Save-Your-Progress Version Kept Up

We called the test after 18 days. For shoppers who opened the builder:

  • Variation 3 (with the exit popup) was level with control
  • Variations 1, 2 and 4 were behind
  • Variation 2, the new measurement picker, was the clear loser at -28% revenue per visitor

A note on certainty: this was a directional read on one store, not a 95% result. The -28% gap was big enough to call. The smaller gaps were not.

What We Learned About Product Configurator UX

1. A step that slows people down can be doing a job

"Are you ready to measure?" looks like friction. It is also the moment a shopper goes to find a tape measure. Remove it and people hit the size inputs unprepared. For a made-to-measure product, a pause that gets the measurement right beats a fast flow that ends in a guess.

2. Do not redesign the input people trust

The slider looked cleaner in the design file. In practice, a dropdown of inches is something everyone has used a hundred times. A fraction slider is something to figure out, at the exact step where getting it wrong means the product does not fit. That is the step where you want zero new things to learn.

3. Long builders need a way back

Variation 3 carried the same losing picker as Variation 2, plus the exit popup, and it came back level with control. That points at the popup: people who were about to leave got a link back to their build. A configurator takes effort. Some shoppers need to measure, check with a partner or come back later on another device.

What We Would Do Differently

Stacking changes is fast, but it makes the read harder. When Variation 3 recovered, we could not fully separate the popup from the picker it was sitting on top of.

So the next step is clean: retest the exit popup on its own against control, with the original measurement inputs. If you are planning your own product configurator test, start with one change per variation. For more on test design, see why A/B tests fail.

Product Configurator UX Questions

Do fewer steps improve a product configurator?

Not in this test. Cutting the "are you ready to measure?" step lost to control. On a made-to-measure product, a step that prepares the shopper can protect the purchase.

Should a configurator use sliders or dropdowns for measurements?

In this test the dropdown won clearly. The new picker with a fraction slider lost 28% in revenue per visitor among shoppers who opened the builder. Keep inputs that people already know how to use.

Does a save-your-progress email popup help a long product builder?

It looks promising. The only version that kept up with control was the one with an exit popup offering a link back to the saved build. We are retesting it on its own to confirm.

How long should a product configurator test run?

Long enough to reach a clear gap on revenue per visitor. We called this one after 18 days because one variation was far behind. Smaller gaps need more time and more orders. Our guide on how long to run an A/B test covers the math.

[ SAY HI AND LET'S MAKE YOU SOME MONEY ]