Skip to content

Get a recommendation system built

We build a recommendation system using your customer, product and behavioural data, test it in practice and refine it based on real results, as we did for See Tickets.

See Tickets gives fans personalised recommendations, even long after an event

On a scalable Azure platform, we brought together See Tickets’ ticketing and behavioural data and developed recommendation models that keep learning. We tested them in practice.

Read the case study

Why do all our customers see the same products?

Every product page shows the same bestsellers, and the newsletter sends everyone the same offer. A recommendation system selects products from your range for each customer at each moment, within the rules you set.

Book a conversation
Twee vrouwen op een bank bekijken samen producten in een webshop op een smartphone.

A recommendation system is only complete when it runs in your own channels

Discuss your recommendations

Purchases and behaviour in one place

Orders, click behaviour and product attributes on one platform. At Vivara, data from SAP, Magento and other sources comes together daily in Azure Databricks.

A model that fits what you offer

Collaborative filtering, content-based recommendations or a combination, depending on your data. For Olympia, we developed a classification model to match candidates with job openings.

Rules you set

You decide what is out of stock, what must never be shown and what takes priority. The model makes its choices within those limits.

Measured against what you currently offer

A comparison group continues to see the old list. For See Tickets, we tested the recommendations in practice and adjusted them based on real results.

Start with one decision point; add channels only if the test supports it

  1. Decision point and objective

    Product page, basket, newsletter or app: where does the customer make a choice, and are we aiming to increase clicks, purchases or margin?

  2. Testing against historical data

    We train the model on earlier purchases and check whether it predicts later purchases better than a bestseller list.

  3. Live testing and expansion

    We start with one channel and a comparison group. If it works, we add more channels, with monitoring and a designated owner.

Do we have enough customers and products for personalised recommendations?

Discuss whether it’s a good fit

A good fit if

You have a broad product range or lots of content, customers return or click frequently, and purchases or views can be linked to a customer or session. Think online shops, ticketing, media and job openings.

Not a good fit if

You sell a handful of products, customers rarely buy again, or you know every customer personally. In that case, a fixed list of bestsellers or products often bought together does almost the same job.

What determines the scope

How many channels show the recommendations, whether they’re calculated per visit or in batches, how complete the product data is, which business rules apply and who manages the system.

Is an off-the-shelf solution not enough?

Sometimes it is. If you want product recommendations based on customer, product and transaction data, take a look at our Recommend.ai solution. A bespoke solution is worthwhile if your product range, channels or rules don’t fit within it.

Frequently bought together, an off-the-shelf recommender or your own model?

Market basket analysis

Choose this if purchases cannot be linked to a customer. You can see which products often appear together on the same receipt. See our blog post about AI in retail.

Recommend.ai

Choose this if you want product recommendations based on customer, product and transaction data, with rules you set yourself. Read more about Recommend.ai.

A bespoke recommendation system

Choose this if your offering, channels or rules differ, as they might for events, job openings or content. Our advice: start with one decision point and a comparison group.

We've already matched fans with events and candidates with vacancies

Data Science Lab has worked with data and AI since 2016. Based in Amsterdam, we are a Databricks and Microsoft partner. For See Tickets, we predict which events suit each visitor; for Olympia, we worked on matching candidates with job openings.

Book an introductory meeting

The first conversation is about where your customers make their choices, not algorithms yet

Stef Stoelwinder

Stef Stoelwinder

Business Development

Stef is your first point of contact. In our first conversation, we’ll discuss where your customers make their choices, what data you have and how you measure success.

Where should our customers see a better recommendation in future?

Describe when customers make their choice and what data you have. You’ll receive a reply by email, or we’ll arrange an initial conversation.

Enter a valid email address.

Let us know how we can help you.

Frequently asked questions

A recommendation system, also known as a recommendation engine or recommender system, selects what is likely to be relevant to each user from a large range of options: a product, an article, an event or a job opening. It learns from past behaviour, such as purchases, clicks and viewing time, as well as from the characteristics of the available items.

Product recommendations in an online shop are the best-known example. Personalised recommendations in a newsletter or app work in the same way. This is one of the AI applications we build.

Collaborative filtering finds customers with similar purchasing behaviour and recommends things they bought that you have not. It does not need a customer profile. Content-based filtering looks at the characteristics of things someone has chosen before, such as category, brand or genre.

A hybrid recommendation system combines both approaches, as our Recommend.ai does. Large systems often work in three steps: selecting candidates from the full range, scoring them and then reordering the list, for example to add variety or include new items.

This is called the cold-start problem: a new customer or product has no history yet, so collaborative filtering has nothing to learn from. In such cases, the ALS model in Apache Spark, the processing engine behind Databricks, deliberately makes no prediction, leaving you to choose a fallback.

A common approach is to combine methods: new visitors see popular or seasonal products, while new products are recommended based on characteristics such as category and price range. Once clicks and purchases come in, the model takes over.

You need interactions you can link to a customer or session, such as orders, clicks, views or ticket purchases, plus a product catalogue with characteristics and availability. This is usually implicit feedback: a click or purchase, rather than a star rating. Models such as ALS have a variant designed for this.

In a shop without a loyalty card, you cannot link a purchase to an individual, but you can still run a market basket analysis on receipts. If your data is spread across systems, start with the data foundation.

Start offline: train on older data and check whether the model predicts later purchases better than a simple baseline, such as a bestseller list. Common metrics include precision at k, the proportion of the first k recommendations that are relevant, and NDCG, which also takes their order into account.

Then test live, using a comparison group that continues to see the old selection. Agree in advance whether you are optimising for clicks, purchases or margin. Lots of clicks on cheap products are not always what you want.

A model that relies only on past behaviour reinforces what is already popular and overlooks new or less familiar items. That is why you reorder the list: limit the number of products from any one category, give new items a chance and exclude things someone has already bought.

Business rules belong in the same step, such as not showing out-of-stock products. After launch, you retrain the model so it takes new products and seasons into account. You can read about the technical side under MLOps.

Making recommendations based on someone’s behaviour is profiling. The European Data Protection Board describes this as the automated analysis of personal data to assess personal aspects, such as behaviour, preferences and interests. You need a purpose and a legal basis under the GDPR, and customers can object to direct marketing.

The Digital Services Act requires online platforms to be transparent about how their recommendation systems work. The largest platforms must also offer a feed that is not personalised. Your legal adviser or privacy officer can assess whether this applies to your organisation. Together, we determine which data is genuinely necessary.

When your product range is small, customers rarely return or purchases cannot be linked to a customer or session. In those cases, a fixed bestseller list does much the same job with less maintenance. If you first want to understand who your customers are and what value they bring, start with customer analysis.

If your product data is messy, with missing categories or duplicate items, address that first. If an off-the-shelf approach fits, we will point you towards Recommend.ai. If you are unsure where the problem lies, start with a maturity assessment.