Product Recommendations
A practical glossary entry on product recommendations — how "you might also like" surfaces work across PDP, cart, and post-purchase, with conversion-lift benchmarks and design rules.
Product Recommendations
Algorithmic or curated product suggestions placed on PDPs, cart, and post-purchase pages to reduce decision cost and grow basket size.
Product recommendations are the 'you might also like', 'frequently bought together', and 'complete the look' modules that surface relevant SKUs at decision points throughout a store. They blend behavioural data (co-purchase, co-view, similarity embeddings) with merchandising rules (margin, stock, brand fit) to suggest what a shopper is most likely to add next.
Done well, recommendations are a form of choice architecture: they narrow a large catalogue down to two or three high-probability picks, lowering cognitive load rather than adding to it. Done poorly, they crowd the page with noise that delays the click to buy.
Most stores run three recommendation surfaces. The product page shows similar or complementary items, the cart shows add-on accessories or bundles, and the post-purchase confirmation page shows reorder or upsell candidates. Each surface answers a different shopper question, so a single algorithm rarely wins everywhere.
The engines behind these widgets fall into three buckets: collaborative filtering ('shoppers who viewed this also viewed'), content-based similarity (image and attribute embeddings), and rule-based merchandising (curator's picks, new arrivals, margin boosts). Modern systems blend all three and re-rank by business constraints before rendering.
Incremental Revenue = Sessions × Rec CTR × Attach Rate × AOV Lift
Sessions
Sessions exposed
Sessions that load a page containing the recommendation widget.
Rec CTR
Recommendation click-through rate
Share of exposed sessions that click at least one recommended product.
Attach Rate
Attach rate
Share of clickers who add a recommended item to cart and check out.
AOV Lift
Average order value lift
Incremental revenue per attached order versus the same order without the recommended item.
A Shopify apparel store runs a 'complete the look' widget on 120,000 PDP sessions per month.
Sessions exposed: 120,000
Rec CTR: 8%
Attach rate: 12%
AOV lift per attached order: €18
→ ≈ €20,700 incremental monthly revenue
120,000 × 0.08 × 0.12 × €18 ≈ €20,736. A single PDP widget at industry-average rates clears €240k a year on this traffic — enough to justify dedicated A/B testing of layouts and ranking logic.
Lift varies dramatically by placement. Post-purchase recommendations convert highest because the buying decision is already made and friction is low. Cart recommendations sit in the middle. PDP recommendations have the most volume but the lowest click rate, because the shopper is still evaluating the focal product.
Typical performance ranges by recommendation surface
| Surface | Click-through rate | Attach rate | Revenue share |
|---|---|---|---|
| PDP — similar items | 4-9% | 6-10% | 2-4% |
| PDP — complete the look | 6-12% | 10-15% | 3-6% |
| Cart — frequently bought together | 8-14% | 15-25% | 4-8% |
| Post-purchase upsell | 10-18% | 20-35% | 3-7% |
| Homepage — trending / for you | 2-5% | 4-8% | 1-3% |
Read those ranges as starting points, not targets. A beauty brand with strong cross-category affinity (cleanser → moisturiser → SPF) will beat the cart benchmark easily. An electronics store selling single high-ticket items rarely will. Segment performance by category and intent before judging a widget.
Product Recommendations FAQ
Start with the cart page. Cart recommendations have the cleanest measurement — shopper intent is high, the surface is small, and a single 'frequently bought together' widget typically lifts AOV 3-7% within two weeks of launch.
Three to six on most placements. Beyond six, click-through drops because you've re-introduced the catalogue-browsing problem the widget was supposed to solve. On mobile, four is the practical ceiling before horizontal scroll kills engagement.
Yes — product recommendations are a child concept of choice architecture. The whole point is to pre-filter the catalogue down to a tractable set, so the shopper makes a faster, more confident decision rather than abandoning to a category page.
Collaborative filtering wins on catalogues with deep purchase history and broad SKU overlap. Content-based similarity wins on new SKUs, long-tail items, and visual-first categories like apparel or home. Most production systems blend both and let an A/B test pick the weighting.
Sometimes. If your 'similar items' widget always shows cheaper alternatives, you'll trade margin for clicks. Re-rank by margin or revenue contribution, not just similarity, and measure incremental revenue rather than widget CTR alone.
Hold out a control group that sees no widget (or a static merchandised list), then measure revenue per session — not click-through. CTR can rise while revenue per session falls if the widget is pulling clicks away from the primary CTA.
They can. Server-rendered widgets add a database call; client-rendered widgets add a script. On Shopify, aim for under 80ms server response and lazy-load below-the-fold widgets so they don't block Largest Contentful Paint.
Recommendations are one tactic; personalization is the broader practice of varying the experience by visitor. A recommendation widget can be personalised (ranked by this shopper's history) or generic (same for everyone). Start with generic, layer personalization once you have enough data.
For collaborative filtering, roughly 10,000 orders or 100,000 product views to produce stable co-purchase signals. Below that, lean on content-based similarity and curated rules — the algorithm will produce noisy 'frequently bought together' pairs that hurt trust.
No. Filter stock at render time, not just at indexing time, because stock levels change faster than your recommendation cache refreshes. Showing an unavailable item is one of the fastest ways to lose a session you'd otherwise have converted.
Get an AI expert review of your site
Paste your URL — Metricuno's AI runs the same heuristic checks a senior CRO consultant would, scoring your page and prioritising the fixes that'll move conversion fastest.