Skip to main content

3 posts tagged with "Catalog Search"

Catalog Search query-triggered boost and bury with search rules

MINOR Catalog Search query-triggered boost and bury with search rules

Catalog Search now supports search rules in rule groups so merchandisers can boost, bury, pin, hide, rewrite, or filter results when a shopper query or browse listing matches a trigger.

What's New?

  • Search rule groups - Named containers for query-time merchandising rules
  • Search rules - Exact, contains, and browse triggers with boost/bury, pin, hide, query rewrite, and rule filter actions
  • Profile rule_groups - Attach ordered rule group IDs to a search profile to activate the rules engine
  • Ordering controls - execution_order within a group and stop_after_match across the profile pipeline
  • matched_rules on search results - See which rule and rule group IDs matched a full search (not autocomplete)

What's Changed?

  • Always-on profile boosts remain available for every search on a profile; search rules apply only when a trigger matches
  • Autocomplete does not evaluate search rules

For details see:

Catalog Search Indexed Fields replaces Searchable Fields for schema discovery

MINOR Catalog Search Indexed Fields replaces Searchable Fields for schema discovery

Use Indexed Fields to list every field in the search index — including numeric, boolean, and date fields — with flags for how each field can be used.

What's New?

  • GET /pcm/catalogs/search/indexed-fields - Returns all exposed indexed fields of every type
  • searchable and filterable flags - See whether a field can be used as a full-text query field and in filter expressions
  • Guide coverage - List Indexed Fields in Setting Up Catalog Search, with links from filtering, faceting, and sorting guides

What's Changed?

  • GET /pcm/catalogs/searchable-fields is deprecated - Prefer Indexed Fields. Searchable Fields returns only text query fields and does not cover fields needed for filtering and sorting
  • Searchable Fields remains available for existing integrations; migrate to Indexed Fields for complete schema discovery

For details see:

Catalog rules can specify a search profile for shopper segments

MINOR Catalog rules can specify a search profile for shopper segments

Catalog rules can optionally include a search profile so shopper search follows the same segment as catalog and pricing — without hard-coding search_profile in your storefront.

What's New?

  • Optional search_profile_slug on catalog rules - Attach a search profile when configuring the rule for an account, customer, channel, or context tag
  • Automatic profile on shopper search - Matching shopper search and multi-search use that profile for filters, ranking, and related search behavior; a valid rule slug takes precedence over the search_profile query parameter
  • EP-Search-Profile response header - See which profile was applied (SYSTEMS_DEFAULT_PROFILE when the built-in default is used)
  • Price and assortment together - Use the same rule for price books and searchable assortment (for example a reseller-only category filter on the profile)

What's Changed?

  • Shopper search profile resolution - Catalog rule slug (when valid) → search_profile query parameter → tenant default → built-in default
  • Admin search unchanged - Explicit catalog/release search does not apply catalog rule profiles
  • Safe fallthrough - An invalid or stale rule slug does not fail the search; Catalog Search falls through to the next resolution source

For details see:

Ask External AI