Cross-Generation Comparison Strip and Live Price Gap for One-Screen Purchase Decisions

Hypothesis: Adding a compact cross-generation comparison strip to both PDPs — with a live price gap that reads from each page's embedded data — will convert more of the shoppers who currently defer while reverse-engineering the difference across tabs.

Brand of the Week

REI is the beloved American outdoor coop — running shoes, camping gear, and everything else for people who spend their weekends outside. Founded in 1938, REI has built a mature ecommerce operation with a fiercely loyal customer base, and their product pages reflect that care: well-photographed, well-specced, well-reviewed.

But when a manufacturer discontinues a product and REI keeps the older generation live on the site alongside the new one — as they currently do with the HOKA Clifton 10 and 11 — the shopper is left to figure out on their own what changed and whether the price gap between the two is worth it.

Which is exactly why what we found on the Clifton PDPs stood out.

The challenge

We took a peek at REI's HOKA Clifton PDPs, and two things caught our attention.

The two generations live side by side, and neither page acknowledges the other.

REI sells the HOKA Clifton 10 (discontinued, $99.83) and the Clifton 11 (full price, $155) side by side on their site. Both are complete, well-designed product pages. Neither one mentions the other exists.

Nothing on either page explains what changed between generations. Nothing frames the $55.17 gap. So a shopper who lands on one page and wants to know whether the extra $55 is worth it ends up doing the site's work themselves — opening tabs, comparing specs, reading reviews. The Clifton 10's review section is full of customers doing exactly that reconciliation in public.

The likely outcome of all that friction isn't the wrong Clifton. It's no Clifton at all. Near-identical alternatives + no decision rule = deferral.

The information for the comparison already exists on each page.

Here's the interesting part. Both product pages already publish, in their content, what changed for that specific generation. And both pages ship live prices in embedded JSON that renders on the page. The data REI would need to build the comparison already exists on their own site.

It's just never on one screen.

So what would we A/B test?

Control: REI's current HOKA Clifton PDPs — both fully designed and well specced, each unaware of the other. Shoppers researching the price gap reverse-engineer it across tabs, or defer entirely.

Variant (built in MidaGX): Three changes to the buy-box area of both PDPs.

Add a compact comparison strip below the buy-box price

The strip lives right below the price on the buy box — the moment the shopper is deciding to add to cart. It shows what changed between generations (pulled from each page's own generation-change content), a one-click swap link to the other Clifton, and the live price gap: "This page saves you $55.17."

Run the strip in reverse on the Clifton 11's page

Deliberately two-sided. Deal-seekers on the 11's page get a nudge to consider the older 10; spec-seekers on the 10's page get a nudge to trade up to the 11. Both are wins compared to a deferred purchase.

Read prices live from each PDP, with graceful degradation

The price gap reads dynamically from each page's embedded product JSON. If REI runs a sale, the strip updates automatically. If the JSON isn't readable — rare, but possible — the strip degrades gracefully to copy-only, never showing a stale number.

Our hypothesis

REI's PDPs already have every piece of information they need to make each Clifton shopper's decision easier. The site just doesn't put both pieces on one screen at the moment the decision is being made.

We'd expect the variant to lift add-to-cart conversion on both PDPs. On the Clifton 10, the strip converts confused deal-seekers who currently defer while comparing tabs. On the Clifton 11, it converts spec-seekers who otherwise leave to research whether the upgrade is worth it.

We'd also expect a drop in cross-version comparison content in the Clifton 10 review section — because the site is finally doing that reconciliation work itself, at the moment it matters.

The CRO principle underneath

Product pages assume the shopper only cares about the product on that page. When there's actually a second product on the same site that the shopper is likely comparing against — a previous generation, an adjacent model, a cheaper alternative — the shopper does the comparison work whether the site helps or not.

The fix isn't to hide the alternative. It's to acknowledge it, explain the trade-off, and let the shopper make a fast, informed decision without leaving the page.

REI's PDPs already have all the data. They just need to put both sides on one screen.

Want to run a test like this on your own site? Get started with Mida for free — now available even if you don't have an account with Mida.