Recently Viewed Products vs Related Products: When To Use Each

Recently Viewed Products A product page or site module showing items a shopper viewed earlier. It differs from recommendation systems that surface similar or complementary items; the distinction guides placement and goals.

Merchants commonly use both recently viewed lists and algorithmic related-product widgets. Choosing between them (or using both) depends on intent: recently viewed supports recall and task resumption, while related-product modules drive discovery and cross-sell strategies.

Functional Differences

Understand the user problem each tool solves so design and measurement align with outcomes.

• Recently Viewed: Surfaces products the specific visitor has already seen; short-term memory aid for re-finding items.
• Related Products: Algorithmically selected items (similar, complementary, or trending) intended to broaden choices or suggest add-ons.

When To Favor Recently Viewed

Implement recently viewed when your primary goal is to reduce friction or recover shoppers who left product pages without buying. Typical scenarios:

• High-Consideration Products: Categories where shoppers compare specs — electronics, furniture, specialty apparel.
• Large Catalogs: When navigation has many facets and shoppers can easily lose track of an item.
• Returning Visitors: Help repeat shoppers pick up where they left off between sessions.

When To Favor Related Products

Use related-product widgets when you want to increase basket size, encourage discovery, or push inventory that needs demand generation. Scenarios include:

• Cross-Sell Opportunities: Suggest complements (case with phone, batteries with camera).
• Inventory Management: Promote overstocked SKUs via recommendation algorithms.
• New Customer Discovery: When shoppers haven’t yet built a browsed history, related items provide immediate alternatives.

Placement Strategies

Both features can coexist with complementary placement to avoid competing for attention:

• Recently Viewed: Place near the top of product pages, in site header drawers, or on the cart page for easy access to previously inspected SKUs.
• Related Products: Place lower on the product page or in a separate recommendations rail where discovery is expected.

Performance Tracking And A/B Ideas

Measure each widget by the specific outcome you want — recall versus discovery. Suggested tests:

• Recall Test: A/B test recently viewed presence on cart pages and measure conversion lift for returning sessions.
• Discovery Test: Swap related-product algorithm variants (similar vs. complementary) and track AOV and click-throughs to promoted SKUs.
• Combined Approach: Run a three-way test: recently viewed only, related only, and both together to see interaction effects.

Impact On Fulfillment And Inventory

Both features influence order composition differently and warehouse workflows should anticipate the effects:

• Recently Viewed Effects: More single-SKU returning conversions; less sudden SKU diversity in small orders.
• Related Products Effects: Increased multi-SKU orders and mixed pallet picks; may increase packing complexity and require sharper inventory allocation.

Decision Checklist

Use this quick checklist when deciding which to prioritize first:

• Primary Goal: Reduce friction (recently viewed) or drive discovery/cross-sell (related products)?
• Catalog Size: Large, complex catalogs favor recently viewed for navigation assistance.
• Supply Constraints: If inventory is tight, prefer recently viewed to avoid promoting unavailable alternatives.

In short, the Recently Viewed Products module is best when the objective is re-finding and conversion recovery; use it alongside related-product systems when you need both recall and discovery in your merchandising mix.