Skip to main content
FilterIQRequest access
Menu
Type to search across all documentation
NavigateEnterOpenEscClose
4 min read

Custom Merchandising Rules

Create dashboard rules to pin, boost, bury, or hide products in browse or query-specific results.

Custom Merchandising Rules

Custom merchandising rules control how matched products are grouped in storefront results. The current dashboard lets each rule target one product, or products matching one tag, vendor, or product type. A rule can use global scope or match a specific search query, and it can have an optional schedule.

The dashboard labels global scope All searches, but the current storefront runtime applies global rules to collection and browse results and deliberately skips them during text searches so relevance stays primary. Use Specific search query when a rule must affect a text search.

Rule Actions

Each merchandising rule applies one of four actions:

Pin

Moves matched products into the pinned group before other results. The position field controls the order among pinned products; it is not an absolute result-list slot.

Use case: Put a flagship product ahead of other pinned products for a branded search term.

Boost

Moves matched products into the boosted group before normal results. When no explicit shopper sort is active, higher strength sorts earlier within that group and ties preserve incoming order. An explicit sort preserves incoming order within the group.

Use case: Boost high-margin products to increase average order value.

Bury

Moves matched products into the buried group after normal results. When no explicit shopper sort is active, stronger bury actions sort later within that group and ties preserve incoming order. An explicit sort preserves incoming order within the group.

Use case: Push discontinued products or low-rated items to the bottom of results.

Hide

Removes a matched product from the applicable result set.

Use case: Hide products that are not relevant to a specific search term.

Creating a Rule

  1. Go to Merchandising > Rules in the app dashboard.
  2. Select Create Rule.
  3. Choose Pin, Boost, Bury, or Hide.
  4. Choose one target: a specific product, tag, vendor, or product type.
  5. Choose global or specific-query scope and, if needed, add a schedule.
  6. Select Create Rule.

Rule Settings

SettingOptionsDescription
ActionPin, Boost, Bury, HideWhat to do with the target products
Which products?Product, tag, vendor, product typeOne dashboard target for the rule
Apply toAll searches, Specific search queryGlobal browse/collection scope, or a specific text query
Search queryText stringRequired when Specific search query is selected
Position1-100Priority among pinned products, not an absolute result slot
StrengthLight, Medium, StrongRelative order within the boost or bury group
ScheduleOptional start and end datesLeave blank to start immediately or run without an end date

Dashboard Targeting

  • A specific product: search for and select one product.
  • Products with a tag: select one tag; the dashboard creates an equality match.
  • Products from a vendor: select one vendor; the dashboard creates an equality match.
  • Products of a type: select one product type; the dashboard creates an equality match.

The backend rule model supports additional conditions, collection IDs, and multiple targets, but those controls are not exposed in the current rule modal. The dashboard does not let you build arbitrary operator combinations or collection-scoped rules.

Rule Priority and Ordering

The dashboard assigns priority by action: Hide 250, Pin 200, Boost 150, and Bury 100. Matching rules are evaluated from highest priority to lowest.

Conflict Resolution

  1. A matching Hide action always removes the product, regardless of priority or another action.
  2. For pin, boost, and bury actions targeting the same product, the first matching rule in priority order wins.
  3. Later pin, boost, or bury actions do not replace or add to the winning action.
  4. After conflicts are resolved, remaining products are grouped as pinned, boosted, normal, then buried. Pin position orders only the pinned group.

Limits

LimitValue
Maximum rules per store500
Dashboard targets per ruleOne product or one tag/vendor/product-type equality match
Pin position1-100; ordering among pins only

Best Practices

  1. Use tag, vendor, or product-type targeting for changing sets -- Newly matching products are included without selecting them one by one
  2. Avoid unintended overlaps -- For the same product, the first matching non-hide action in priority order wins
  3. Choose scope deliberately -- Use specific-query scope for text searches; global scope currently affects collection and browse results
  4. Review rules regularly -- Seasonal rules should be disabled or deleted when they are no longer relevant
  5. Test with preview -- Use the merchandising preview to inspect the result grouping before relying on a rule
Was this page helpful?