A Recently-Viewed Module

A recently-viewed module is a merchandising widget on an e-commerce site or app that shows a shopper the products they looked at earlier in their visit or in previous visits. As a person browses, the site quietly records which product pages they opened, and the module surfaces those items — usually as a small row or carousel of product cards — somewhere the shopper will see them again, such as the homepage, a category page, the cart, or a persistent strip. It is a form of lightweight personalization: rather than recommending what the shopper might like based on other people's behavior, it simply reflects the shopper's own recent behavior back to them. The value is practical and immediate. Shopping often involves looking at several products, wandering off, and wanting to get back to one — and without a recently-viewed module, finding that item again can mean retracing search terms or hunting through categories.

A recently-viewed module matters because reconsideration is a real and common part of buying, especially for considered purchases. Few people buy the first product they see; they browse, compare, leave, and come back, sometimes across several sessions and devices. Every time a shopper has to work to relocate a product they were interested in, some of them give up, and a potential sale leaks away. The module removes that friction by keeping the shopper's own shortlist one glance away, which supports comparison — putting the items they are weighing side by side — and gentle re-engagement, reminding a returning visitor of what drew them in last time. Because it reflects genuine, first-party interest rather than a guess, it tends to feel helpful rather than pushy, which is part of why it is a near-standard fixture of e-commerce interfaces.

It helps to distinguish a recently-viewed module from a recommendations module, because they look similar but do different jobs. A recommendations module suggests products the shopper has not necessarily seen — items chosen by an algorithm from what similar shoppers bought, what pairs well with the current product, or what is trending. It aims to expand consideration toward new items. A recently-viewed module does the opposite: it deepens consideration of items the shopper already chose to look at, by making them easy to return to. One introduces; the other reminds. The two are complementary and often sit near each other, but conflating them weakens both. A shopper glancing at a recently-viewed row expects to see exactly what they browsed, in a sensible recent-first order — not fresh suggestions, which belong in the recommendations slot.

Using a recently-viewed module well comes down to accuracy, placement, and restraint. It must show what the shopper actually viewed, most recent first, and update as they browse, or it undermines the trust that makes it useful. It should appear where reconsideration naturally happens — near the cart, on return visits, on the homepage of a coming-back shopper — without crowding out the current task. Sensible limits matter: showing a handful of the latest items is helpful, while an endless, cluttered history is noise, and it should respect privacy expectations, especially on shared devices, and offer a way to clear the list. Filtering out already-purchased or out-of-stock items keeps it relevant. Treated this way, the module is a quiet, high-trust aid that reduces friction; treated carelessly, it becomes stale clutter that shoppers learn to ignore.

Using a recently-viewed module well comes down to accuracy, placement, and restraint. It must show what the shopper actually viewed, most recent first, and update as they browse, because a list that misremembers or misorders their history undermines the very trust that makes it useful. Place it where reconsideration naturally happens — near the cart, on the homepage of a returning visitor, on category pages — without crowding out the shopper's current task. Keep it to a sensible handful of the latest items rather than an endless scroll of everything ever seen, since a cluttered history is noise, not help. Filter out items already purchased or now out of stock so the module stays relevant, and respect privacy expectations, especially on shared devices, by offering a clear way to clear the list.

Keep its job distinct from the recommendations that often sit nearby. A recently-viewed module reminds a shopper of items they already chose to look at, so it should contain exactly those and nothing else, while a recommendations module introduces new items an algorithm suggests. Conflating them weakens both, because a shopper glancing at a recently-viewed row expects their own shortlist, not fresh guesses. Used with that clarity, the module quietly supports the reconsideration that considered purchases depend on — letting a returning visitor pick up where they left off and weigh a few finalists side by side — and it does so with high trust because it reflects genuine first-party interest rather than inference. Treated carelessly, though, it becomes stale, cluttered, or eerily off, and shoppers learn to ignore it, so the restraint is what preserves its value.

A recently-viewed module is a common e-commerce personalization pattern that resurfaces a shopper's own browsing history.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where a recently-viewed module is a core concern: