Skip to main content

Indexable Fields

Indexable Fields allow you to extend the search schema by adding custom product attributes to the search index. By default, the search index includes standard product fields like name, description, SKU, and categories. Indexable Fields let you configure which additional fields are indexed, enabling searching, filtering, faceting, and sorting on custom attributes.

When to Use Indexable Fields​

Use Indexable Fields when you want to:

  • Search custom attributes: Enable full-text search on custom product fields like brand, material, or specifications
  • Filter by custom attributes: Allow shoppers to filter products by custom fields like color, size, or rating
  • Facet on custom attributes: Display aggregated counts for custom field values in your navigation
  • Sort by custom attributes: Order search results by custom numeric fields like rating or popularity

How Indexable Fields Work​

  1. Create indexable fields: Define which fields should be indexed, specifying field name and options (facetable, sortable, locale)
  2. Reindex catalogs: After creating or modifying indexable fields, reindex your catalog releases to include the new fields
  3. Use in searches: Once reindexed, you can reference the indexed fields in your search queries for filtering, faceting, and sorting

Field Configuration​

Each indexable field has the following configuration options:

OptionDescription
nameThe field path — see Field Types below for supported formats
facetableWhen true, the field can be used for faceting to show aggregated value counts
sortableWhen true, the field can be used for sorting results
localeLanguage code for text tokenization, defaults to en for English

Field Types​

Two categories of fields can be indexed:

Extension Fields​

Fields from your product extension templates, following the pattern extensions.products(<template_slug>).<field_name>:

  • <template_slug> is the slug of your product extension template
  • <field_name> is the name of the field within that template
  • The field must exist and be enabled in the flows service
  • Only enumerated string fields, numeric fields, and boolean fields can be faceted

Example: For a product extension template with slug Details containing a field brand, the indexable field name would be extensions.products(Details).brand.

Custom Attribute Fields​

Merchant-defined key/value attributes stored directly on products:

  • shopper_attributes.<attribute_name> — visible in shopper and admin catalog API responses and available for filtering, sorting, and faceting in both shopper and admin search
  • admin_attributes.<attribute_name> — available for filtering and sorting in both shopper and admin search; not returned in search response payloads
  • <attribute_name> must be no longer than 64 characters and can only contain alphanumeric characters, underscores (_), and hyphens (-).
  • Attribute fields are always typed as string
  • Faceting and sorting can be enabled

Examples: shopper_attributes.fabric, admin_attributes.internal_grade

Reindexing Requirement​

Changes to indexable fields require reindexing your catalog releases. The system detects when indexes are out of sync and you can use the reindex endpoint to update them. See Jobs for reindexing operations.

Ask External AI