Skip to main content
Business-to-business (B2B) buyers know what they need to buy and often search using precise product identifiers, such as stock keeping units (SKU). Or, they search for a product that meets strict specifications, which would match several items in your catalog. This guide describes how to set up Algolia to make searching and filtering by numbers easier.

​
Turn off typo tolerance when searching by SKU

Algolia supports searching by SKU and other numbers by default, if you include them as searchable attributes. By default, typo tolerance is turned on for numbers as well. That’s helpful when you don’t want to limit the search results to exactly matching numbers, for example, when searching for product variants or physical sizes. When searching by SKU however, it’s better to turn off typo tolerance to allow for more precise searching. If you add your SKU attribute to disableTypoToleranceOnAttributes, the search results only include products with exactly matching SKU. 
var response = await client.SetSettingsAsync(
  "ALGOLIA_INDEX_NAME",
  new IndexSettings { DisableTypoToleranceOnAttributes = new List { "serial_number" } }
);

​
Search in hyphenated attributes

By default, Algolia regards hyphens as separators, so searching for “123-X-456” and “123 X 456” returns the same results. If you also want to allow searching for the number without spaces, for example, “123X456”, it’s important to consider all variations.

​
Detect searching intent with Rules

You can guide buyers effectively by using Rules to detect keywords in a search query. To learn more, see:

​
Let users search by custom aliases for products

B2B buyers often return to buy the same products. Typing or copying SKUs or other lengthy product identifiers every time can be tedious and error-prone. Some ecommerce platforms allow buyers to save a custom alias, or reference, for an item. With Algolia, you can use Rules to support searching by a custom alias to speed up the search. For example, the buyer can save an alias my_product for the product with the ID “123-456-789”. You can create a rule that detects the alias and replaces it with the product ID. When the buyer searches for my_product, Algolia applies the rule and returns the product matching the SKU.
JavaScript
const rule = {
  objectID: 'user_123_alias_1',
  conditions: [
    {
      pattern: 'my_product',
      anchoring: 'contains',
      context: 'user_123'
    }
  ],
  consequence: {
    params: {
      query: {
        type: 'replace',
        delete: 'my_product',
        insert: '123-456-789',
      }
    },
  },
}
Each buyer defines their own aliases. To apply the rule specific to each buyer, you can use ruleContexts when searching. For example, using an API client: 
namespace Algolia;

using System;
using System.Collections.Generic;
using System.Net.Http;
using System.Text.Json;
using Algolia.Search.Clients;
using Algolia.Search.Http;
using Algolia.Search.Models.Search;

class SearchWithRuleContextBuyer
{
  private static string GetBuyerAccountId()
  {
    return ""; // Implement your logic here
  }

  async Task Main(string[] args)
  {
    var client = new SearchClient(new SearchConfig("ALGOLIA_APPLICATION_ID", "ALGOLIA_API_KEY"));
    // get the buyer account information
    var buyer = GetBuyerAccountId();
    var searchParams = new SearchParams(
      new SearchParamsObject { Query = "", RuleContexts = [buyer] }
    );

    await client.SearchSingleIndexAsync("", searchParams);
  }
}
For more information, see:

​
Guide users by increasing search precision

For example, if a buyer searches for “article ref21”, they might look for an item that starts with the number “21”. If that’s the case, you can create a Rule to increase the precision of the search, by:
  • Removing the keyword “article”
  • Restricting the searchable attributes to the title and ID

​
Define a rule using the API clients

var response = await client.SaveRuleAsync(
  "ALGOLIA_INDEX_NAME",
  "article-rule",
  new Rule
  {
    ObjectID = "article-rule",
    Conditions = new List
    {
      new Condition { Pattern = "article", Anchoring = Enum.Parse("StartsWith") },
    },
    Consequence = new Consequence
    {
      Params = new ConsequenceParams
      {
        Query = new ConsequenceQuery(
          new ConsequenceQueryObject
          {
            Edits = new List
            {
              new Edit { Type = Enum.Parse("Remove"), Delete = "article" },
            },
          }
        ),
        RestrictSearchableAttributes = new List { "title", "book_id" },
      },
    },
  }
);

​
Define a rule using the Algolia dashboard

  1. Go to the Rules page in the Algolia dashboard.
  2. Click the New rule button.
  3. Select Create your first rule or New rule and select Manual Editor.
  4. In the Condition(s) section, keep Query toggled on, select Contains, and enter article in the input.
  5. In the Consequence(s) section:
    1. Click the Add consequence button and select Add Query Parameter.
    2. In the input field that appears, enter the JSON search parameter you want to add. For example, { "restrictSearchableAttributes": ["title","id"] }.
    3. Click the Add consequence button again and select Remove Word.
    4. Enter article in the input field.
  6. Save your changes.
⌘I