Skip to content
AI & Automation16 min read

AI Product Recommendations vs Rule-Based Recommendations: What Should Your Ecommerce Store Use?

AI vs rule-based product recommendations: how each works, the data, cost and latency they need, when rules are enough, and how to prove either adds revenue.

01

Quick answer

AI product recommendations use models trained on product data and shopper behavior to predict which products are relevant in a given context. Common approaches are co-purchase patterns, collaborative filtering, content similarity, embeddings and sequence models, usually combined and constrained by merchandising rules for stock and margin. Language models are now used to interpret needs and explain recommendations, grounded in the live catalog. Most stores should buy rather than build, evaluate models offline and then against a holdout, and watch for cold start, popularity bias and irrelevant suggestions.

02

Where This Fits

Recommendation types, placements and honest measurement are covered in ecommerce product recommendations; Shopify's tools are in Shopify product recommendations. This guide explains the models and how to judge them.

03

Rule-Based vs AI Recommendations

Rule-based recommendations follow logic a person writes: "show other products from this collection", "suggest the matching cleanser with this serum", "never recommend out-of-stock items". AI recommendations learn relationships from behaviour and product data instead. Rules are predictable, cheap and work with no data; AI finds patterns nobody wrote down but needs volume, evaluation and monitoring. Most stores that do this well use both: rules for business constraints and curated pairings, models for ranking and discovery.

ApproachHow it decidesData it needsEffort and costFits
Manual and rule-basedCurated pairings, collection rules, tags, stock and margin filtersProduct data onlyLow; merchandiser timeSmall catalogues, launches, regulated or bundled products
Co-purchase (bought together)Products frequently ordered togetherOrder historyLow to medium; many platforms include itComplements, accessories, cart add-ons
Collaborative filteringShoppers who behaved like you also viewed or boughtLots of interactions per product and shopperMedium; needs volume and retrainingLarger catalogues and traffic
Content-based similarityProducts with similar attributes, text or imagesClean attributes, descriptions, imagesMedium; depends on data qualityNew products, long tail, "similar items"
Learned ranking and hybridsA model scores candidates from several sources for this shopper and contextBehaviour, product and context dataHigh; data pipeline, evaluation, monitoringLarge stores with a data team or a capable vendor
Real-time session modelsRecent clicks and searches in this visitEvent stream with low latencyHigh; infrastructure and latency budgetBig catalogues where intent shifts within a visit
04

Which Should Your Store Use?

Use rules first if you have fewer than a few hundred products, little traffic, or products that need expert pairing (skincare routines, compatible parts, regulated items). Rules also handle the constraints every system needs: hide out-of-stock items, respect margin floors, exclude products that should not be cross-sold.

Add co-purchase and similarity models when your catalogue and order history are large enough that manual curation misses useful pairings. Consider personalised, learned or real-time models only when you have enough traffic to test them properly, someone to own the data and evaluation, and a clear revenue case. On Shopify, start with built-in recommendations and the Search & Discovery app before paying for more (Shopify product recommendations).

Privacy matters at every step: personalised recommendations rely on behavioural data, so they need consent where the law requires it and should degrade gracefully to non-personalised suggestions when consent is not given.

05

Model Families

In practice, systems combine several: for example, embeddings for similar items, co-purchase for complements and a ranking model on top.

06

Data Requirements

DataUsed for
Product views, adds, purchases with IDsBehavior-based models
OrdersComplements and bought-together
Product attributes and categoriesSimilarity and cold start
Text and imagesEmbeddings
Stock, price, marginFiltering and business rules
Consented user identifiersPersonalization across sessions
07

Cold Start and Long Tail

New products have no interactions, and many catalog items have few. Content-based similarity and embeddings from product text and images help them appear; merchandising rules can seed new launches. Without this, recommendations concentrate on a small set of popular products, which limits discovery.

Are your recommendations actually adding revenue?

ZSpace Labs evaluates recommendation models against holdouts and tunes them with your merchandising rules.

Start a Project
08

LLM-Assisted Recommendations

Language models can turn a request like “a gift for a runner under 80” into constraints, choose candidates from a retrieval system and explain why each fits. The key is grounding: the model should only recommend products retrieved from the live catalog, with real prices and stock, and should not invent specifications.

09

Evaluating Models

StageMethodWatch
OfflineHeld-out interaction data; precision, recall, coverageOptimizing for clicks, not revenue
OnlineA/B test against a holdoutRevenue per session, AOV, conversion
GuardrailsMonitor after launchReturns, margin, stock-outs, diversity
10

Build vs Buy

Platform features and vendors handle most needs, include tooling for rules and reporting, and improve over time. Building makes sense for large catalogs with unusual relationships (compatibility, configuration), strict data requirements or a strong in-house data team, and it means owning pipelines, retraining and monitoring. See AI ecommerce.

Whichever route you choose, the data, retrieval, ranking and monitoring architecture is set out in ecommerce recommendation engine.

11

Placement Strategy by Page

The right recommendation depends on where the shopper is and what they're trying to do.

PageShopper goalRecommendation type
HomepageExplorePersonalized picks, trending, recently viewed
Category pageBrowse a rangePopular in category, personalized ordering
Product page (above add to cart)DecideAlternatives, similar items
Product page (below)Complete the purchaseFrequently bought together, accessories
CartFinishLow-cost add-ons, compatible items
Post-purchase emailUse and returnComplementary items, replenishment
Empty search resultsRecoverPopular or related items
12

Measuring Recommendations Properly

Recommendation widgets often report their own clicks and attributed revenue, which overstate their effect because shoppers might have found those products anyway. Test strategies with random assignment and measure whole-visit outcomes: revenue per visitor, conversion, average order value and returns. Keep placement the same when comparing algorithms. See personalization testing.

13

Merchandiser Controls

Merchandisers need to shape recommendations: exclude out-of-stock, low-margin or sensitive products, prevent recommending items from different gender or age ranges where inappropriate, boost strategic ranges, and set rules for specific products. Good tools combine model output with these controls and show why a product was recommended. See AI merchandising.

14

Recommendations Without Much Data

Small stores and new catalogs often lack the behaviour data that collaborative filtering needs. Content-based approaches work better here: recommend products with similar attributes, from the same collection or complementary categories defined by merchandisers. Rules such as "accessories for this product type" and bestsellers within a category are simple, transparent baselines. Move to learned models as data grows, and test each step against the simpler baseline.

Data availableSuitable approach
Little behaviour dataAttribute similarity, merchandiser rules, category bestsellers
Moderate order historyCo-purchase (frequently bought together)
Rich behaviour dataCollaborative filtering, session-based models
Rich data plus text and imagesHybrid and embedding-based models
15

Personalized recommendations use browsing and purchase data, so they fall under privacy rules and consent settings in many markets. Non-personalized recommendations (similar items, frequently bought together across all customers) can work without individual profiles and are a sensible fallback when consent isn't given. Avoid recommendations that reveal sensitive purchases, for example in shared-device or email contexts. See ecommerce privacy and customer data.

16

Risks

  • Popularity bias narrowing what shoppers see
  • Recommending just-bought or out-of-stock items
  • Irrelevant pairings that reduce trust
  • Measuring clicks instead of incremental revenue
  • Generated explanations that misstate facts
  • Heavy scripts slowing product pages

Planning AI recommendations?

Talk to ZSpace Labs about recommendation systems, data pipelines and testing.

Start a Project
17

Conclusion

AI recommendation models work when they're fed clean data, combined with merchandising rules, grounded in the live catalog and judged on incremental revenue. Start with platform or vendor models, measure honestly, and invest in data before model complexity. For cross-sell and upsell strategy, see cross-selling and upselling.

FAQ

Common questions.

Models learn from product data and shopper behavior, such as what's viewed and bought together, which shoppers behave alike, and which products are similar, then score products for each context.

Co-occurrence (bought or viewed together), collaborative filtering, content-based similarity, embedding models, sequence models that predict the next item, and hybrids. LLMs are increasingly used to explain or assemble recommendations.

New products and new visitors have no behavior history. Content-based similarity, popularity and merchandising rules fill the gap.

Offline, with metrics such as precision or recall on held-out data; online, with A/B tests against a holdout on revenue per session and order value.

Most stores should use platform features or a vendor. Building makes sense with large catalogs, unusual needs and in-house data science.

They can interpret natural-language needs, explain why products fit and assemble sets, but they must be grounded in the live catalog to avoid inventing products or facts.

Interaction events with product IDs, orders, clean product attributes and categories, stock status and, for personalization, consented user identifiers.

Yes, if they're irrelevant, repeat what shoppers just bought, push out-of-stock items, distract from checkout or favour a few popular products too much.

The product recommendations guide covers types, placements and measurement. This one focuses on the models behind them.

Shopify generates product recommendations automatically and lets merchants customize related and complementary products through Search & Discovery. Third-party apps offer additional models.

Get in touch

Have a project in mind?

Whether you're building a new digital product, improving an existing website, or looking to automate part of your business — let's talk.