Skip to main content

Personalized recommendations

Generic “customers also bought” recommendations don’t work for fragrance — two popular perfumes can smell completely different. A customer who loves a woody ambery will not appreciate a fresh citrus, regardless of how many other people bought it. WikiParfum generates recommendations based on olfactive affinity: ingredient composition, family relationships, and structural similarity. The result is suggestions that genuinely smell like something the user would enjoy — driving higher conversion and trust in the recommendation.

The business impact

  • Higher conversion — trust in the recommendation drives purchase
  • Increased average order value — users explore and add complementary products
  • Stronger loyalty — personalized experiences generate return visits (most users return within 30 days)
  • Better cross-sell — suggest products based on what customers actually like, not just what’s popular

What you can build

  • “If you like this” carousels on product pages
  • Cross-sell and upsell modules based on olfactive proximity
  • Scan-to-recommend experiences using EAN barcodes
  • Personalized homepages based on browsing history
  • Catalog-restricted recommendations scoped to a retailer’s assortment

Recommend similar perfumes

Given one or more perfumes the user likes, get similar fragrances ranked by olfactive proximity.

Match score

Each recommendation includes a recoValue field: a similarity score between 0 and 1 representing how closely the recommended perfume matches the user’s profile. Results are sorted by this score in descending order, so the first result is always the best match. The score is computed from multiple olfactive dimensions including ingredient overlap, fragrance family proximity, and intensity similarity. You can convert it to a percentage for display purposes (e.g., 0.87 = 87% match).

Recommend by EAN

Use EAN barcodes as input — ideal for scan-based or POS-integrated experiences where you have barcodes but not WikiParfum IDs.

User-scoped recommendations

Pass a userId to incorporate the user’s interaction history into the ranking. Over time, recommendations become increasingly aligned with each user’s evolving taste profile — without requiring explicit questionnaires or profile setup.

Scoping to a catalog

Custom recommendation rules

Use customRecommendation to control which brands or perfumes appear in results. This is essential for retailers who need recommendations limited to their own assortment, or brands that want to exclude competitors.

Filtering results

Recommendations can be further narrowed using standard filters — for example, limiting to a specific gender or market segment. See Filtering & Pagination for all available filter options.

Price-based filtering and sorting

If your catalog includes product prices via the Product Feed, you can filter recommendations by price range and sort by price.
These options require the price column in your Product Feed. Perfumes without a price in your catalog are excluded when filtering, and placed last when sorting.

Ingredient recommendations

Given a set of ingredients the user enjoys, surface other ingredients they might like. This powers ingredient-based exploration flows where users progressively build an olfactive profile.

Perfumer recommendations

Surface the perfumer whose creative style best matches the user’s taste — based on the perfumes they enjoy.
This enables “meet your perfumer” modules that connect users to the creators behind their favorite fragrances.