Create Variant slicing rules
This guide covers how to configure Variant slicing rules.
Prerequisites
Before creating Variant slicing rules, you must:
Feature access
Contact your Bloomreach representative to enable Variant slicing for your account.
Required Pixel implementation
Send product IDs for all events (view, add-to-cart, conversion) and ensure SKU IDs are sent for conversion events. SKU parameters are essential for optimal feature function.
Required Feed implementation
Send the variants in the correct feed format. Products without variants won't be sliced.
Configure Variant slicing attributes
Configure at least one variant attribute to use for slicing.
Permissions
Ensure that you have access to the Categories merchandising editor, Search merchandising editor, or the Global merchandising editor role.
Create global Variant slicing rules
1. Access global Variant slicing settings
-
Go to Merchandising > Global merchandising > Ranking rules.
-
Click + New ranking rule. Choose the global rule, global search rule, or global category rule option.
-
Enter a term. On the global level, "*" queries aren’t supported.
2. Apply Variant slicing
-
In the left panel, locate the Variants section under the Products tab. Click the downward arrow to expand the slicing options.
-
Select an attribute for slicing. Each ranking rule can only use 1 slicing attribute at a time.

- Optionally, apply attribute operations site-wide, such as boosting or burying an attribute value. Item-level operations (block, boost, bury, and lock) are unavailable.
3. Save sliced variants
-
Click Preview to see how Variant slicing affects your site results. Preview the changes by entering a query term or category. "*" queries aren’t supported.
-
If results look good, click Save. Review the change and the number of affected local rules, then choose how to handle your local rules:
-
Overwrite and save: Choosing this applies the global slicing attribute to every local rule and discards existing product-level and listing operations. Reverting to Do not slice variants later does not restore the item-level operations removed by a previous overwrite. A rollback is not supported.
-
Save: Saves the global rule without changing any local rules. Global slicing then applies only to queries and categories that don't have their own slicing configured.
TipIf you're enabling global variant slicing for the first time, clone your production rules to staging first, then activate the feature in staging. This helps you preview the impact of the Overwrite and save option on your existing local rules before you roll it out to production.
-
Wait for the rule sync to finish before editing local rules. Saving a global rule for the first time, or overwriting local rules, starts this sync, and you can't save local rules for a few minutes while it runs.
Global versus local rules
Local rules always take precedence over global rules. If a query or category has its own slicing configuration, that local setting overrides the global slicing behavior. You get the flexibility to slice specific queries or categories differently.
Example:
- You slice globally by
colorand click Overwrite and save. - You create a local rule for “rings” and slice by
size. - The “rings” local rule overrides the global rule, so “rings” are sliced by
size, not bycolor.
Override global slicing for query or category
-
To slice a specific query or category differently from the global setting, configure Variant slicing on that query's or category's rule. The local rule applies.
-
To keep a specific query or category unsliced while global slicing is on, set its slicing to Do not slice variants or create an exception to the global rule.
Modify global slicing rule
To modify Variant slicing for the global rule:
-
Go to the Variants section under the Products tab and click to expand the options.
-
Select Do not slice variants or select a different attribute. Disabling variant slicing or changing the slicing attribute on a global rule discards listing‑ID operations such as block, boost, bury, or lock from the rule.
-
Click Overwrite and save or Save based on how you want to apply changes to the local rules.
Create local Variant slicing rules
1. Access Variant slicing settings
- Go to the category or query ranking rules.
- Merchandising → Site search → Ranking rules, or
- Merchandising → Categories → Ranking rules
- You can apply Variant slicing either to:
- An existing rule: Choose a rule from the Ranking rules listing page.
- A new rule: Click +New ranking rule.
- The Product grid opens. Enter the query/category.
2. Apply Variant slicing
-
In the left panel, locate the Variants section under the Products tab. Click the downward arrow to expand the slicing options.

-
Select an attribute for slicing. Each ranking rule can only use one slicing attribute at a time. If an attribute shows an error warning, it may have been removed via the Catalogs application.
-
Applying slicing with already existing operations
Applying Variant slicing to a rule removes all existing product-level operations like locks, boosts, and blocks. Check the detailed impact guide. -
Products without slicing attributes or variants: If a product lacks slicing attributes or variants, it still displays as an individual listing. However, there’s no "slicing" due to the absence of available attributes or variants.
3. Merchandise sliced variants
After choosing the slicing attribute, variants appear as separate listings with individual ranking scores. Merchandise these listings using Boost, Bury, Block, Sequential lock, and Attribute operations. Optionally add a duration and audience for the rule.

NoteThe interface shows an Add to recall toggle, but the operation doesn't apply. We will remove this in an upcoming release.
4. Save sliced variants
Click Preview to see how Variant slicing affects your search results. If results look good, click Save to apply changes.
Conflict resolution at local level
- Impact on existing rules: If a local rule with slicing already exists, it will not affect another multi-query rule with the same query. This means that changes from the existing rule will not appear in the External changes tab, and the recall will still display products as expected.
- Rule duplication: You can't save two rules with the exact same scope, including the same query, time, and audience.
NoteYou may decide to switch attributes by clicking on a different attribute option. When you switch from one slicing attribute to another (for example, from size to color), the grid listings change. The impact is similar to what is mentioned under removing a Variant slicing rule below.
A/B testing slicing rules
To assess the most effective attribute for your rules, run A/B tests. This involves comparing existing rules against the same rule with a different slicing attribute, or against the same ranking rule without slicing.
For A/B testing rules with identical scope
You cannot create two rules with an identical scope. Therefore, you must edit an existing rule and save it as a test variant. Follow these steps:
- Go to an existing ranking rule (with or without slicing applied).
- Modify the rule by selecting a different slicing attribute or applying merchandising operations.
- Click Preview to visualize the impact of these changes on your search results.
- If the results are satisfactory, click Save new test variant to start an A/B test.
For A/B testing rules with different scope
Create two distinct rules and start the test using the A/B test application.
Remove Variant slicing for a local rule
To remove Variant slicing for a specific category or query rule:
-
Go to the Variant slicing settings section and click to expand the options.
-
Select Do not slice variants.

-
Click Save to apply the changes.
Impact of removing Variant slicing
When you remove Variant slicing for a rule, all variants merge under their respective parent products.
Preserved operations
- Attribute-based operations: Exclude, Include only, Boost, and Bury, with their defined strengths, remain active and apply to listings.
- Algo weights operations: Algo weight operations remain active and still apply.
Removed operations
Listing operations: All listing-level operations (Boost, Bury, Sequential lock, and Block) are removed.
Related articles
Updated 11 days ago

