All Posts

AI in Practice

AI recommendations that actually move revenue

AI recommendations that actually move revenue

The Label Versus the Reality

Every recommendation app in the Shopify ecosystem claims to be AI-powered. Most of them run static rules. Bestsellers get shown to everyone. Products frequently bought together appear in a carousel. Items from the same category fill a "You might also like" section. This is a database query with a marketing label.

Real AI-powered recommendations are different in a specific, measurable way. They consider who the individual customer is, what they've browsed, what they've purchased, what time of year it is, what similar customers bought next, and which recommendations have converted in the past 48 hours. The output changes for every visitor on every visit.

We built a recommendation system for a DTC supplement brand that replaced their rules-based app. Average order value increased by 23% in the first 90 days. The difference came from one thing: recommending products the customer hadn't already considered but was statistically likely to buy.

How Rules-Based Recommendations Work

A rules-based system follows predetermined logic. If a customer views Product A, show Products B, C, and D. If a customer adds Product E to their cart, suggest Product F. The rules are set by a merchandiser or auto-generated from purchase correlation data.

This works when the recommendation is obvious. Someone buying dog food probably needs treats. Someone buying a moisturizer might want the matching cleanser. For those scenarios, simple rules perform fine.

Rules fail when the connection between products isn't obvious. A customer who buys a glucosamine supplement for their dog might benefit from a probiotic, but a rules engine won't surface that recommendation unless enough previous customers bought both products in the same order. If the probiotic is new, or if most customers buy them months apart, the rule never triggers.

Rules also fail at personalization. Every customer viewing the glucosamine page sees the same recommendations. A first-time visitor, a returning customer with three previous orders, and a customer who just abandoned a cart full of digestive products all get the same carousel. The rules don't know the difference.

What Real AI Recommendations Look Like

Collaborative filtering identifies patterns across your entire customer base. It finds groups of customers with similar purchase and browsing histories and recommends products that others in the group bought but this customer hasn't. If customers who buy glucosamine also tend to buy fish oil supplements eight weeks later, the system learns that pattern and surfaces fish oil to glucosamine buyers around that timeline.

Content-based filtering looks at the attributes of products a customer has engaged with and finds other products with similar attributes. If a customer consistently browses grain-free, chicken-flavor products for senior dogs, the system identifies that preference profile and surfaces matching products across categories.

Contextual signals add a time dimension. Recommendation quality changes based on day of week, season, device type, referral source, and what the customer did in the previous session. A customer returning to the site 20 days after purchasing a 30-day supply is likely ready to reorder. A customer browsing at 11 PM on a phone has different intent than the same customer on a laptop at 2 PM.

These three approaches work together. Collaborative filtering provides the candidate set. Content-based filtering refines it for the individual. Contextual signals determine timing and ranking.

The Shopify-Specific Challenge

Shopify's native recommendation API, powered by product relationship data, provides basic "related products" functionality. It draws from purchase correlation and collection membership. For many stores, this is adequate.

For stores where recommendation quality directly affects average order value, the native API has limits. It doesn't incorporate individual customer browsing history in real time. It doesn't learn from which recommendations convert and adjust accordingly. It doesn't support complex multi-signal ranking.

Building genuine AI recommendations on Shopify requires pulling customer and product data through the Storefront API and Admin API, processing it through your own model, and serving results back through a custom storefront component. On a standard Shopify theme, this means a custom section that calls your recommendation service via JavaScript. On a headless frontend, you have full control over where and how recommendations appear.

The headless approach has a significant advantage here. You can experiment with recommendation placement, test different algorithms for different page types, and measure the revenue impact of each change without being constrained by the theme's template structure.

The Revenue Impact

The supplement brand we built this for was running a popular Shopify recommendation app that showed "frequently bought together" and "customers also viewed" carousels. Those recommendations generated about $4,200 in attributed monthly revenue.

After switching to the custom recommendation system, attributed revenue from recommendations reached $11,400 per month within 90 days. The increase came from two sources: higher conversion on recommendations because they were more relevant, and higher AOV because the system surfaced products customers hadn't considered rather than products they'd already seen.

The most effective placement was the post-purchase page. After checkout, the system recommended products based on what the customer just bought, their full purchase history, and what similar customers bought next. Post-purchase recommendation conversion was 4x higher than product page recommendations, because the customer had already committed to buying and the payment information was already on file.

The system cost more to build than a Shopify app subscription. For a brand doing over $50K monthly with a catalog of 100+ products, the revenue difference paid for the build within two months.

Your system is the bottleneck. Let's fix it.

30 minutes. No slides. We pull up your site live and show you what's possible.

Start a ConversationBack to Blog

More from the blog