Anytime you have products that come in variations - for example, in different colors - knowing how to structure your data to best represent your inventory without duplicates can become tricky. Good examples are t-shirts of different colors or smartphones with different storage capacity (and consequently different prices).
Let’s take the example of an e-commerce website selling t-shirts and sweatshirts in a variety of models and colors. The simplest solution would be to have one record per model and only have a list of possible color variants. The issue with this approach is that whenever someone searches for “red t-shirt”, the engine returns all the t-shirt models that have at least one variant in red. However, the thumbnail would not necessarily be red, which would be confusing.
Instead, we want to make sure that whenever someone types “red t-shirt”, the page only displays products with a red thumbnail. Also, we want to make sure we only get single item per model, and find a clever way to display all variants.
In our inventory, we have two t-shirt models (A and B) and two models of sweatshirts (C and D). Each model comes in several colors.
In our dataset, we can represent them by creating one record for each color variant of each item. Each record specifies the type, the model, the color and the associated thumbnail. Here’s what our records look like:
Going a step further, we could also add all the possible color variations for each record. This way, we could display all the variants for a single product in our front end (e.g., color swatches under the thumbnail), allowing the end user to discover them.
With this approach, every record represents a single variation, which ensures we always display consistent data. Having one record per variation also lets you add granular custom ranking attributes, like number_of_sales. Besides, you can leverage Algolia’s distinct feature to de-duplicate models. This way, when someone searches for “t-shirt”, they only get one of each model.
Using the API
At indexing time
Before de-duplicating items, we want to restrict what attributes are searchable. We don’t want to search into thumbnail_url, which may be irrelevant and add noise, nor into color_variants, because it could lead to false positives. Therefore, we can set model, type and color as searchableAttributes.
To use distinct you first need to set model as attributeForDistinct during indexing time. Only then can you set distinct to true to de-duplicate your results.
Note that setting distinct at indexing time is optional. If you want to, you can set it at query time instead.
You can also set your attribute for distinct and enable distinct in your Algolia dashboard.
Go to your dashboard and select your index.
Click the Ranking tab.
In the Searchable Attributes section, click the Add a searchable attribute button.
Click on attributes “model”, “type” and “color” in the dropdown one after the other.
Click the Display tab.
In the Display & Pagination section, go and select attribute “model” in the Attribute for Distinct dropdown.
Set the Distinct dropdown to true.
Don’t forget to save your changes.
When distinct is set to true, we get one color for each model. To control which one, you can set a new attribute with business metrics (e.g., number_of_sales) and set it up for custom ranking.
Additionally, we can display all available colors for each item thanks to the color_variants attribute. This way, the end user can access all possible variants from the search results without the page being crowded with too many items.