The shade was close. Show them the next four.

The cosmetics problem

Shade, finish, formula — the matrix the visitor never explores.

A visitor lands on a foundation PDP from a TikTok ad or a Google search. The shade is close but not exact, or the finish is matte when they wanted dewy, or the formula is for normal skin and theirs is sensitive. They reach for the back button — and at that moment, the storefront has done one of two things. Either nothing happens and the visit ends, or a popup appears asking for an email in exchange for 10% off, which addresses none of the actual mismatch.

The actual problem is that the store has three other foundations in adjacent shades, two other matte-to-dewy options, and a sensitive-skin range the visitor never reached. Cosmetics catalogs are unusually wide on these dimensions and unusually punishing when visitors don't see the alternatives. The recovery page is the cheapest place to fix that.

Live in production

Running on POP MAKEUP today.

POP MAKEUP — an Italian cosmetics brand selling colour and skin ranges across the EU — runs Before You Go on every product page. In the cosmetics stores we've measured, the recovery page sees a 30-45% click-through rate, the highest CTR of any vertical we've observed. Click through to see the actual recovery experience on a live storefront — same code path their visitors hit.

POP MAKEUP

Cosmetics · Italy

See the recovery page live →

The 30-45% CTR figure is from the cosmetics stores currently running Before You Go in production. Vertical economics will vary; smaller catalogs and earlier-stage stores see lower click-through, larger and more mature catalogs see higher.

Why this matters for cosmetics

Three things cosmetics has that other categories don't.

• A multi-dimensional product matrix. Shade, finish, formula, skin type, fragrance, packaging — a single foundation has half a dozen axes of variation, and the catalog has dozens of foundations. The recovery page is built to surface adjacency along whichever axis the visitor was actually exploring.
• Cross-category adjacency that compounds. A visitor on a lipstick PDP often buys an adjacent gloss, lip liner, or matching blush. The behavioural signals (co-views, co-clicks, co-purchases) capture those adjacencies automatically — no manual rule-building required.
• A buyer who's in active discovery mode. Cosmetics shoppers compare more than buyers in almost any category. A visitor leaving a PDP isn't done with the store; they're done with that specific product. A full page of adjacent options is exactly what the moment needs.

• Does the recovery page work for cosmetics SKUs with shade variants?

  Yes. The recommendation engine works on parent products, so a visitor leaving a specific shade of foundation gets matched against alternative foundations and adjacent products by what other shoppers actually bought, not against other shades of the same SKU. Shade swatches and variant pickers on the recovery page inherit your theme's existing display logic.

• Will the recovery page conflict with our existing review widgets or sampling app?

  No. The recovery page only renders when a visitor is about to leave a product page — it doesn't add anything to the PDP itself. Reviews, samples, AR try-on widgets, and bundle builders on the product page are untouched. The recovery page is a separate surface that fires on departure, not during browsing.

• What about cruelty-free, vegan, or fragrance-free certifications — do they surface in recommendations?

  If those attributes are tagged on your products in Shopify or Shopware, the content-similarity model picks them up automatically and a visitor browsing fragrance-free formulas tends to see other fragrance-free formulas in the recovery page. The behavioural signals (co-views, co-clicks, co-purchases) reinforce the same pattern over time as more shoppers reveal their preferences through actual purchases.

• How does it work for international cosmetics stores in different currencies and languages?

  The recovery page renders inside your store's own theme, so it inherits the storefront's currency formatting, locale, and number conventions automatically. The UI strings (button labels, headings) are localized into eight languages, with shop-level overrides if a particular phrase needs a different translation. Multi-storefront setups that route different markets to different theme variations are supported out of the box.

• Will the page slow down my storefront or hurt Core Web Vitals?

  No. The detection script is small (under 10KB gzipped), loads asynchronously, and doesn't block rendering of the product page. The recovery page itself only assembles when a back-navigation actually fires, so the main browsing experience is unaffected. Page-speed tools like PageSpeed Insights and Shopify's Web Performance Report show no measurable impact on LCP or CLS in the stores currently running it.