Skip to content
Last updated

Introduction

Search & Recommendations extension enhances selected Sales Channels by optimizing Product Listing Pages (PLPs), refining search word predictions, and improving filters. The data flow involves transferring information from the platform to Algolia, where it is stored and powers storefront listing pages. While the data can be obtained through a catalog data loader, the Algolia extension elevates accuracy in results and search predictions, optimizing search-to-result time.

Key functionalities include indexing, sorting, and mapping for effective data organization. The Auto Complete Menu provides quick, intuitive suggestions, and Search Analytics offers insights into user behaviour. The Data Loader ensures seamless data transfer, while the File Uploader simplifies file uploads. In summary, the Algolia extension comprehensively enhance the search experience, optimizing the functionality and efficiency of Sales Channels in e-commerce.


Steps to use Search & Recommendations Extension

  1. Go to Extensions in Fynd Commerce.

QG1

Figure 1: Extension

  1. Open Search & Recommendations.

QG1

Figure 2: Opening Search & Recommendations

  1. Choose from the available integrations:

    QG1

    Figure 3: Extension home page

    • Common – Manage global settings.
    • Algolia – Optimise search using Algolia APIs.
    • Google Retail Search – Sync and manage search with Google.

Using Algolia in Search & Recommendations

The Algolia integration provides advanced tools to configure search ranking, sort orders, rules, relevance, analytics, and more. Open Algolia to get started.

QG1

Figure 4: Opening Algolia

Set up Algolia Credentials

To activate the integration, first set up your credentials:

  1. Open Credentials.

QG1

Figure 5: Opening Credentials

  1. Enter the Algolia's API Keys in this section to complete the setup for the Algolia extension.

QG1

Figure 6: Setup

  1. Go to algolia.com.
  2. Select Dashboard > Overview.

QG1

Figure 7: Overview

  1. Select the company from the drop-down. Here, we have selected Fynd company.

QG1

Figure 8: Fynd Application

  1. Go to API Keys.

    QG1

    Figure 9: API Keys

    1. Copy the Application ID and paste it into the Application ID field on the Fynd Commerce.

    QG1

    Figure 10: Application ID

    1. Copy the Search API Key and paste it into the Search-Only API Key field on the Fynd Commerce.

    QG1

    Figure 11: Search API Key

    1. Copy the Write API Key and paste it into the Admin API Key (or Write Key) field on the Fynd Commerce.

    QG1

    Figure 12: Write API Key

  2. Select the Search module from the left side panel and go to Index under Configure.

QG1

Figure 13: Index

  1. Go to the Index drop-down in the header and select the relevant index from the drop-down menu, and copy the Index Name.

QG1

Figure 14: Index Name

After entering the details in the aforementioned fields, other modules of the Algolia extension will be enabled for you to configure.

After setting credentials for an extension, only the index_name can be modified.

  1. Add Global Context. This refers to universal settings that impact the overall behaviour of search functionalities across the entire application. This field is non-mandatory.

  2. Add Target Mart. It is specific to Jio. Target Mart can be either Jio or Smart. This field is non-mandatory.

Fill in the following fields with the copied details:

FieldDescriptionExample
Application IDUnique ID to identify your Algolia project.3kb42k3v42u42jkjb32k4
Search-Only API KeyPublic key used on the frontend for search queries and analytics.23brkbjb23jb4j234j12n3b4l
Admin API KeyAdmin or Write API key. Keep this confidential.*********** (masked)
Index NameThe name of the index to store and retrieve data.Enter Index Name
Global ContextDefault search context.Global Context
Target MartThe mart type to target (choose either JIO or SMART).SMART

Click Save to store the credentials.

For more information on price internationalisation, click the info link above the form.

Configure Sort & Replica Mapping

Control how your products are sorted and displayed in search results.

Steps to Configure Sort Options

  1. Select Sort & Replica Mapping from the Algolia dashboard.

QG1

Figure 15: Opening Sort & Replica Mapping

  1. Review available sort options such as:

    QG1

    Figure 16: Sorting Options

    • Price Low to High
    • Popularity
    • Discount High to Low
    • Latest
    • Discount Low to High
    • Price High to Low
    • Rating
    • Size Depth (High to Low)
  2. Select the sorting option and then in the Settings section:

    QG1

    Figure 17: Index Name

    • Update its Index Name (e.g. "AK_INDEX_PRICE_L_H").
  3. Click Save.

QG1

Figure 18: Clicking Save

Clicking “click over here” in the info banner will take you directly to this settings screen.

Enable Search Analytics

Use Search Analytics to track user behaviour and improve search performance.

  1. Go to Search Analytics from the Algolia dashboard.

QG1

Figure 19: Opening Search Analytics

  1. Enable Click Analytics to start sending query_id from Algolia to the front end, enabling click and conversion tracking.

QG1

Figure 20: Enabling Analytics

  1. It enable Search Analytics to view:

    • Total searches
    • No result rate
    • Daily search activity
  2. Click Visit Algolia Dashboard to access these insights directly on Algolia.

QG1

Figure 21: Clicking Visit Algolia Dashboard

This link opens the official Algolia dashboard in a new tab.

Upload Rules Using File Uploader

Create and sync bulk rules in Algolia using a structured Excel upload.

Steps to Upload Rules

  1. Go to File Uploader under Algolia.

QG1

Figure 22: Opening File Uploader

  1. Download the Algolia Rules Demo Excel file.

QG1

Figure 23: Downloading Algolia Rules Demo Excel

  1. Fill in the spreadsheet using the format below:
ColumnDescriptionExample
rule_idIdentifier for the rulemy_rule_1
condition_typeType of condition (query, context, filter)query
query_typeQuery operator (e.g. is)is
query_valueTerm to matchjuice
context_nameContext groupingtesting
context_scopeScope of the context (e.g. all)all
filter_nameFilter to apply (e.g. color)color
filter_valueFilter value (e.g. red)red
from_dateStart date of rule validity (MM/DD/YYYY or DD/MM/YYYY format)6/9/2023
to_dateEnd date of rule validity6/15/2023
  1. Click Upload File and select the completed .xls or .xlsx file.

QG1

Figure 24: Clicking Upload File

  1. Monitor the upload status under Uploaded Rules:

    • Success
    • Failed
    • In Progress

QG1

Figure 25: Uploaded Rules

Example - A file named sample_algolia_rule (4).xlsx with status SUCCESS confirms that rules were synced.

Configure Relevance Settings

Relevance settings allow you to fine-tune the way search results appear to customers. These settings define how queries are interpreted, how results are ordered, and which terms are treated as equivalent.

Go to Relevance under Algolia.

QG1

Figure 26: Opening Relevance

To configure relevance settings, you will be redirected to the Algolia Dashboard by clicking the Set up in Algolia Dashboard button.

Searchable Attributes

QG1

Figure 27: Searchable Attributes

Defines which fields of your data are searchable, and in what order.

Purpose
You want to control how users find products (e.g., search by brand, category, or product name)
You want to prioritise certain fields over others in the search results

Example Configuration:

[
  "product_name",
  "category",
  "brand",
  "description"
]

Put the most relevant field (e.g. product_name) first. This ensures better matches appear at the top.

Custom Ranking

QG1

Figure 28: Custom Ranking

Controls how matched results are ordered after applying the search logic.

Use caseExample
Show bestsellers firstbestseller
Prioritise highest rated itemsrating DESC
Highlight most-viewed itemsviews_count DESC

Example Configuration:

[
  "desc(bestseller)",
  "desc(rating)",
  "desc(views_count)"
]

Custom ranking helps display more business-relevant results, such as top-sellers, first.

Synonyms

QG1

Figure 29: Synonyms

Synonyms expand or unify search intent by telling Algolia which words are considered equivalent.

Use caseExample
Search for "pants" should also return results for "trousers"pants ⇄ trousers
"jacket" includes "blazer"jacket ⇄ blazer

All of these settings are configured directly within the Algolia Dashboard after redirection.

Manage PromoRules Context

This section allows you to assign context to rules, so they can be triggered conditionally based on customer behaviour, device type, or other metadata.

Steps to Use PromoRules Context

  1. Go to PromoRules Context from the Algolia dashboard.

QG1

Figure 30: Opening PromoRules Context

  1. View previously synced rules, including their:

    QG1

    Figure 4: Uploaded Rules

    • Rule ID
    • Context (e.g. testing)
    • Type (e.g. all)
  2. Use the search bar to find specific rule contexts.

QG1

Figure 31: Search Bar

  1. Click the Bin Icon to delete a context.

QG1

Figure 32: Bin Icon

Example - Rule ID my_rule_1 with context testing and type all ensures this rule only applies during testing campaigns across all scopes.

  • Promote a rule only during a sale period.
  • Apply different rules for desktop vs mobile experiences.

Enable and Track User Events

User Events: help track and measure key customer actions on your storefront. These events can be used to optimise search relevance and enable personalisation.

Steps to use User Events

  1. Go to User Events in the Algolia section.

QG1

Figure 33: Opening User Events

  1. Toggle the switch at the top right to enable.

QG1

Figure 34: User Events

  1. You'll now see a list of predefined events:

QG1

Figure 35: Toggling Events

Event NameDescriptionMapped Algolia Event
Add to cartCaptures when a user adds a product to the cartaddedToCartObjectIDs
Product viewCaptures when a user clicks on a productclickedObjectIDs
Order completeCaptures when a user places an orderpurchasedObjectIDs
  1. Toggle each event to enable it based on your tracking requirements.

QG1

Figure 36: Toggling User Events

  1. Click Save.

QG1

Figure 37: Clicking Save

Why use this? These events improve search performance by feeding real-time behavioural data into Algolia, enabling better analytics and personalised ranking.

Google Retail Search enables enhanced product discovery by leveraging Google’s search intelligence. With this integration, merchants can optimise cataloguing, indexing, and personalisation, improving customer experience and search conversion rates.

Go to Google Retail Search section.

QG1

Figure 38: Opening Google Retail Search

Set Up Google Retail Search Credentials

To connect your Google Retail Search account with Fynd, you must provide key credentials.

  1. Go to Credentials in the Google Retail Search section.

QG1

Figure 39: Opening Credentials

  1. Enter the following information:
FieldDescriptionExample
Project IDGoogle Cloud project ID used for Retail Searchretail-store-123
Dataset ID (Optional)Identifier for a specific dataset (optional)product_dataset_v1
Service Account KeyJSON key for service account with access to Retail Search{...}.json
GCS Error PathPath to your Google Cloud Storage bucket for error logginggs://fynd-retail-errors/

Use case - These settings allow Fynd to sync your product data and fetch search-related insights from Google’s platform.

  1. Click Save to complete the integration setup.

QG1

Figure 40: Opening Save

Clicking the info link will guide you to more details about price internationalisation and its impact on Google Retail configurations.

Track User Events for Google Retail

User Events: help you capture behavioural data such as searches, views, cart actions, and purchases. These insights are sent to Google Retail to improve search relevance and product recommendations.

  1. Go to User Events in the Google Retail Search section.

QG1

Figure 41: Opening User Events

  1. Toggle the switch in the top-right corner to enable.

QG1

Figure 42: Enabling User Events

  1. A list of available events will appear:
Event NameDescriptionMapped Event
Add to cartWhen a user adds a product to the cartadd-to-cart
Remove from cartWhen a user removes an item from the cartremove-from-cart
Product viewWhen a user views a product detail pagedetail-page-view
Product listingWhen a user views the homepage or a PLPhome-page-view
Order completeWhen a purchase is madepurchase-complete
Product searchWhen a user searches for a productsearch
Order checkoutWhen a user visits the shopping cartshopping-cart-page-view
  1. Use the toggle next to each event to enable tracking.

QG1

Figure 43: Toggling User Events

  1. Click Save once configuration is complete.

QG1

Figure 44: Clicking Save

Use Case - Enabling these events allows Google to understand how users engage with your site, enhancing the personalisation and ranking of search results.

Common Settings

The Common section allows you to configure and manage universal settings for search services across your store. These include pricing, catalogue sync, attributes, autocomplete, and more. This centralises configuration across both Algolia and Google Retail search engines.

Open Common.

QG1

Figure 45: Opening Common

Config – Price Internationalisation

Manage API-based currency conversion for product listings.

How to configure:

  1. Go to Config in Common Settings.

QG1

Figure 46: Opening Config

  1. Select the Exchange Partner from the dropdown & enter Open Exchange API Key.

    QG1

    Figure 47: Config Settings

    • Exchange Partner Example: Open Exchange

    • Open Exchange API Key Example: fynd-openex-12345678

  2. Click Save to apply the settings.

Use case - Display accurate prices for international customers by converting your base price using real-time exchange rates.

Catalogue Sync

Synchronise products, collections, and currency data between Fynd Commerce and external search providers (Algolia or Google Retail).

Steps to Sync:

  1. Go to Catalogue Sync in Common Settings.

QG1

Figure 48: Opening Catalogue Sync

  1. Click Sync.

QG1

Figure 49: Clicking Sync

  1. Choose options from the modal:

    • Sync Type: Select Incremental or Full.
    • Select Provider: Choose from Algolia, Google Retail, or Both.
  2. Click Sync.

Sync History:

You’ll see a job list with the following details:

QG1

Figure 50: Sync History

  • Job Type: Products, Collections, Currency
  • Status: SUCCESS / IN_PROGRESS
  • Items Synced: Auto-filled after completion

Use case - Ensures your search providers have up-to-date product and collection data from the Fynd backend.

Auto Complete Menu

Customise autocomplete suggestions shown in the search bar.

Go to Auto Complete Menu in Common Settings.

QG1

Figure 51: Opening Auto Complete Menu

Available Auto Complete Menu Options:

Turn on the toggle to enable auto complete menu:

QG1

Figure 52: Auto Complete Menu Options

  • Product Suggestion
  • Brand Suggestion
  • Category Suggestion
  • Query Suggestion
  • Departments Suggestion
  • Fallback to Algolia (used if Vertex data is empty)

QG1

Figure 53: Clicking Save

Example: Enable Query Suggestion and provide a Query Suggestion Index name like fynd_query_suggestions.

Use case - Improves search UX by suggesting products, categories, or brands as users type.

Custom Attributes

Create and manage custom attribute mappings for your product data.

Steps to configure:

  1. Go to Custom Attributes in Common Settings.

QG1

Figure 54: Opening Custom Attributes

  1. Toggle Enable Custom Attributes.

QG1

Figure 55: Enabling Custom Attributes

  1. Click Add New.

QG1

Figure 56: Clicking Add New

  1. Fill in:

    QG1

    Figure 57: Adding Custom Attributes

    • Source: e.g., product_colour
    • Destination: e.g., custom_colour

Optionally, toggle:

  • Remain Original: Retains the original source field in the output.

QG1

Figure 58: Enabling Remain Original

QG1

Figure 59: Clicking Save

Use Case - Re-map fields for clarity or compatibility before syncing to search services.

Attributes

Select which attributes from your product data should be passed to Algolia.

Example:

  • uid
  • multi_size
  • slug
  • is_available
  • algolia_facet
  1. Go to Attributes in Common Settings.

QG1

Figure 60: Opening Attributes

  1. Toggle Enable Attributes.

QG1

Figure 61: Enabling Attributes

  1. Enter or delete fields as needed.

QG1

Figure 62: Attributes List

  1. Click Save.

Use case - Reduce payload size or enhance indexing performance by syncing only required fields.

Data Loader

Switch search-related data services from Fynd default to external providers.

Go to Data Loader in Common Settings.

QG1

Figure 63: Opening Data Loader

Options available for:

QG1

Figure 64: Data Loader Features

  • Product Listing
  • Collection Listing
  • Autocomplete Menu

Each row includes two dropdowns, select as per your preference:

  • Mode:
    • Fynd
    • Ext Search Provider
  • Search Provider:
    • Algolia
    • Google Retail
    • Hybrid

Use case - Enables flexible routing of search APIs to different engines depending on A/B testing or performance.

A/B Testing Config

Split traffic between search providers for testing purposes.

Go to A/B Testing Config in Common Settings..

QG1

Figure 65: Opening A/B Testing

Configuration:

QG1

Figure 66: A/B Testing Configuration

  • Algolia Percentage: Set share of traffic (e.g., 50)
  • Vertex Percentage: Remaining traffic (e.g., 50)
  • Rotation Time: Time (in hours) after which user session switches provider

This applies only when Hybrid mode is selected in the Data Loader section.

Analytics Stats:

QG1

Figure 67: Analytics Stats

Enter Start Time and End Time to filter A/B test metrics by time range.

Search Tool Pinning

The Search Tool Pinning feature allows you to assign a specific search engine to a particular user. This is helpful for internal QA, performance analysis, debugging, and A/B testing use cases.

Steps to Pin a Search Engine to a User ID:

  1. Go to Search Tool Pinning .

QG1

Figure 68: Opening Search Tool Pinning

  1. Fill in the required fields:
FieldDescriptionExample
User IDThe unique identifier of the user to pinuser_123456
Search EngineSelect the engine to assign from the dropdownAlgolia, Google Retail, Hybrid
  1. Click Save to finalise the configuration.

QG1

Figure 69: Clicking Save

Use case - If you're running multiple search engines and need to fix one engine (e.g. Algolia) for a tester or a group of users, this ensures consistent and predictable behaviour for them—bypassing A/B testing or dynamic rotation logic.

This pinning overrides the A/B testing and hybrid settings for the specified user ID.