Shopify Compatibility Page A/B Test: How a Guided Checker Lifted Desktop Revenue per Visitor by 58.3%

TL;DR

A European car diagnostics brand sells an OBD2 scanner and an app that unlocks features for specific car makes and models. Before buying, shoppers check whether their car is supported on a compatibility checker page.

That page brought in more visitors than any other, but almost none of them went on to buy.

As part of the ongoing Shopify A/B testing programme we run for the store, we redesigned the checker so that every result leads to the product. On desktop, it lifted revenue per visitor by 58.3% and conversion rate by 46.6%.

The challenge: the busiest page was a dead end

For this product, compatibility decides the sale. The features a shopper can unlock depend on their car's make, model and generation.

The checker answered that question, but once shoppers saw their result, the page gave them no clear next step towards buying.

The research: compatibility closed sales, but the checker didn't sell

Our Shopify CRO research for this store combined 90 days of analytics, a store walkthrough and more than 500 post-purchase survey responses and reviews.

• ✓Largest entry page: the compatibility checker was the store's top landing page and converted at 0.04%.
• ✓Deciding factor: 24 survey mentions said support for their exact car closed the sale.
• ✓Compatibility doubt: 19 negative signals came from shoppers who couldn't confirm support before buying.
• ✓Desktop gap: desktop converted at 0.12%, below mobile at 0.19%, although a technical purchase like this would usually convert better on desktop.

The hypothesis: turn the compatibility result into a buying step

If we show shoppers everything the product can do for their car and offer the product right after the result, more desktop visitors will move from checking to buying, increasing revenue per visitor.

The vehicle data behind the checker stayed the same. The test changed how the checker guided shoppers and what came after the result.

The variation: from car selector to product in one flow

The vehicle data and the store's header and footer stayed the same. The variation rebuilt the page in two screens.

The first screen sells the outcome before the shopper picks a car:

1. 1A headline about what the shopper's car can do, a line about fixing it for a fraction of the dealer price, and a rating with the number of drivers using the product.
2. 2A selector card (brand, model, generation) with one button to see the car's features, and a “let us know” link that opens a notify-me form for models not yet listed.
3. 3Four tiles previewing what the shopper can unlock: customisations, diagnostics, service and live data.
4. 4Short videos from drivers using the product.

The results screen answers the compatibility question and moves straight to the product:

1. 1A confirmation that the shopper's car is supported, with the number of features available.
2. 2The customisations most popular with owners of that model.
3. 3A search box and all features grouped into customise, diagnose, service and live data, with a count for each group.
4. 4A reassurance line: not sure a feature will work on your car? Try it risk-free with the 30-day money-back guarantee.
5. 5A product card for the scanner and app bundle, with the price and a buy button.
6. 6An FAQ on safety, warranty and data.

Each part answered a step in the shopper's decision:

• ✓The first screen showed why to check.
• ✓The results screen confirmed fit with a specific list of features, removed the remaining risk with the guarantee, and offered the product at the moment the shopper was most sure.

The test measured the combined effect of these changes and does not isolate any single element.

The results: +58.3% revenue per visitor on desktop

We ran the test in Intelligems on desktop traffic to the compatibility checker.

Conversion drove the result: 46.6% more desktop visitors bought. Average order value fell by 8.0%, but the extra orders more than made up for it, and revenue per visitor rose by 58.3%.

We used revenue per visitor as the primary success metric because it shows whether more conversions are worth a lower order value. After the test, we implemented the winning compatibility checker on the live Shopify store.

What this test taught us about high-traffic tool pages

The store's busiest page already answered the shopper's biggest question. It needed to show what that answer meant for their car and offer the next step.

For this store, shoppers on the checker needed:

• ✓A clear answer: their car is supported.
• ✓Specific proof: the features they can unlock on that model.
• ✓A next step: the product, with a guarantee, right after the result.

What could A/B testing uncover in your store?

We plan, build and run A/B tests for Shopify stores, grounded in customer research rather than guesswork. Get in touch to find out what to test next.