Most nopCommerce stores run a related products block that was configured once and has not been revisited since. It still renders on every product page, and it still reflects a merchandiser's assumptions from whenever it was set up rather than what customers have done in the months since.

That block is not the problem. It performs a narrow function and performs it adequately. The limitation is scale: manual cross-sells cannot track a catalog that changes weekly, and they carry no information about recent purchase behaviour.

AI-powered product recommendations in nopCommerce address that limitation by ranking on observed behaviour rather than on fixed rules. This article covers what the change delivers, which placements to implement first, the data required before any model becomes useful, and how to integrate one without replatforming.

What changes when a model ranks the recommendations

The shift is from merchandiser judgement to observed behaviour, and the two diverge more often than most store owners anticipate.

Consider a camera listing. A merchandiser assigns the matching tripod, because a tripod is the accessory that belongs with a camera. A model reading the previous month's cart data may find that camera buyers predominantly added a spare battery, and that tripod sales come from a different segment several weeks later.

AI-powered product recommendations are product suggestions ranked by a model trained on shopper behaviour such as views, cart adds and purchases, rather than by static rules a merchandiser sets by hand.

Where related products still earns its place

The manual block retains a clear role. It handles pairings that exist for commercial reasons: the accessory carrying the better margin, the bundle a supplier wants promoted, the replacement part compatible with only one model. A behavioural model will not surface those reliably, because margin structure and supplier agreements leave no trace in click data.

The constraint is volume. Maintaining accurate cross-sells across 8,000 SKUs is not realistic, and assignments made two years ago now recommend discontinued stock to customers who abandon the session.

The commercial case for improving on this is well documented, if broad. McKinsey found that 71% of consumers expect personalized interactions and 76% report frustration when they do not receive them, with the companies that execute well drawing 40% more revenue from those activities than average performers. Their explainer places the typical revenue lift between 5% and 15%.

Those figures average across industries and traffic volumes, so treat them as direction rather than forecast. A 200-SKU catalog with modest session numbers will not see what a 20,000-SKU catalog sees.

How machine learning eCommerce recommenders decide

Buying one of these sensibly does not require building one, but it does require understanding why the system selects what it selects. Without that, a poor model and poor data are difficult to tell apart, because they fail in similar ways.

Collaborative filtering, content-based filtering, and cold start

Collaborative filtering works purely from patterns across users. If customers who bought A also bought B far more often than chance would explain, B gets surfaced. The method knows nothing about what A and B are, which cuts both ways. It identifies pairings no merchandiser would have considered, and it will also recommend a size 6 shoe to a customer who wears an 11.

Content-based filtering reads product attributes instead: category, brand, price band, specification values. Less surprising, more predictable, and the only approach that produces anything at all for a product nobody has interacted with yet.

One failure mode deserves direct scrutiny during vendor evaluation. Cold start describes what happens when a new product, or a first-time anonymous visitor, gives the model nothing to work from. Every machine learning eCommerce system has a fallback for this, usually category popularity or bestsellers. On a store with high catalog churn, that fallback is what most shoppers will see most of the time, which makes it more consequential than the headline algorithm.

Session-based models sit between the two approaches. They rank on what a visitor is doing in the current session rather than on who that visitor is, which matters because the majority of eCommerce traffic never logs in.

The five placements, and which one to implement first

Rolling out AI-powered product recommendations across every surface simultaneously is the most reliable way to stall a project of this kind. Select the placements where the shopper has already demonstrated intent, ship those, measure, then expand.

nopStation's Amazon Personalize plugin arrives with five use cases already configured:

• Recommended for you
• Most viewed
• Best sellers
• Customers who viewed this also viewed
• Frequently bought together

Homepage blocks versus product page blocks

The first three render on the homepage and answer a question the returning visitor has not yet articulated. Recommended for you depends on identified users to perform well, so on a store with few registered customers, most viewed and best sellers will carry that block for some time.

The last two render on the product details page, and in our experience that is where the measurable revenue sits. A visitor on a product page has already narrowed to a single item. Customers who viewed this also viewed captures those still comparing options. Frequently bought together captures those who have decided and are about to check out without a necessary accessory.

One recommendation carries more weight than the rest: do not enable all five placements in week one and then attempt to read a revenue change. Attribution becomes impossible. Enable frequently bought together, run it against the existing related products block for a full purchase cycle, and review the difference before changing anything else.

How to add AI to a nopCommerce store without replatforming

This is the question we field most often, and the answer is less dramatic than most teams expect. The store does not get rebuilt. It gets connected to a service that already holds the model.

Amazon Personalize is AWS's managed recommendation service, and it represents the shortest route into machine learning eCommerce for a team without data scientists. It runs Amazon's own pipelines against your store data, which removes training and hosting from your scope. Our plugin handles the nopCommerce side: recommenders start and stop from the admin panel, each one toggles independently, status is readable without leaving the store, and multi-store configurations are supported.

Published results indicate the ceiling rather than the average. Skillshare A/B tested the service against their own in-house recommender and reported click-through rate up 63% on the website, 15% on mobile apps and 14% on email. Discovery Education reported a 229% increase in homepage click-through rate on the same service.

The data requirement that comes first

A recommender is worth precisely as much as the interaction history behind it, and this is where nopCommerce artificial intelligence projects most often stall.

Three datasets matter: a clean item catalog, a user dataset if identified personalization is the goal, and an interaction stream covering views, cart adds and purchases. Thin or inconsistent data produces recommendations that appear random, at which point customers stop trusting the block. That reaction happens quickly and is difficult to reverse.

Before any model is budgeted for, export what exists and count the months of usable interaction history. Under three months, phase one should be spent correcting tracking rather than selecting algorithms. The work is unglamorous, and it determines everything downstream.

A strong recommendation can still land on a weak product page

Delivering a visitor to a product page is where the recommender's responsibility ends. What happens after that is a separate problem, and it is the one most stores skip.

If the page carries a two-line description pulled from a supplier feed, no specification summary, and nothing that addresses whether the product suits the buyer, the recommendation was wasted. AI personalization in eCommerce in 2026 sharpens this, because more traffic now arrives directly on product pages rather than filtering down through the category pages where context used to sit.

Where generated summaries help, and where they fail

AI Product Summary writes product descriptions from attributes already held in the catalog, using Gemini, OpenAI, Grok or DeepSeek depending on configuration. Prompt templates fix a brand voice, and generation reads specification attributes rather than improvising from a product name.

Two operational details matter more than writing quality. Smart caching keeps the storefront fast, because calling a model on every page load adds seconds to render time. Per-minute rate limiting protects the provider quota, which is what otherwise produces unexpected costs.

One caveat belongs here, even in a product section. Generated copy inherits whatever is wrong with your attribute data, and it inherits it fluently. Incorrect specifications produce confident, well-written, inaccurate descriptions, which are worse than no description because customers believe them. Review the first batch manually before publishing.

For the search side of the same problem, see our deep dive on Generative AI for eCommerce SEO. The wider stack is documented on our nopStation AI solutions page.

Conclusion

The distance between a stale related products block and a working machine learning eCommerce recommender is shorter than most nopCommerce merchants assume. The model is not the difficult part. The interaction data underneath it is, along with the discipline to change one placement at a time rather than enabling five at once and hoping for a measurable result.

Begin with frequently bought together on the product details page. The intent signal is clearest there, and it offers the shortest path to a measurable change in average order value. AI-powered product recommendations also improve as history accumulates, so the sooner tracking is correct, the stronger the second year looks.

Export three months of interaction data and assess what you actually hold. Then book a call with our team, or review the Amazon Personalize and AI Product Summary plugins to see how they fit your store.

Frequently Asked Questions