Issue
Updated ranking rules in Commerce Studio are not being reflected in the production or staging environments. Products that are supposed to be boosted remain in their original positions on the search results page.
Diagnosis
This issue can occur if:
The category condition specified in the rule is not being triggered by the current query.
The query profile in use on the page does not match the query profile specified in the ranking rule.
The rule was not successfully published or deployed.
Environment
Fusion Managed (SaaS-hosted), Commerce Studio
Applicable across both staging and production environments
Cause
The ranking rule was scoped to a specific category facet path and query profile, but the rule was not triggering because:
The site was executing a keyword search (e.g., "keyboards") without a corresponding category facet selection, so the category condition did not evaluate to true.
The query profile specified in the rule configuration did not match the query profile used by the site when rendering the search results.
Resolution
Confirm the rule’s category condition is triggered by user interaction
Ensure that the user journey on the site results in a category facet being selected in the query string. For example, this condition:
categoryName_hier_ss = 3//Products//Accessories//Mice & Keyboards//Keyboardswill only be met if the query string includes:
fq=categoryName_hier_ss:3//Products//Accessories//Mice & Keyboards//KeyboardsIf a user simply searches for “keyboards” without selecting the facet, the rule will not trigger.
Confirm query profile alignment
In the ranking rule configuration, check that the Query Profiles field matches the query profile used on the site when the rule should fire.
To check the active query profile on the frontend, open the Visual Editor or examine browser network tools for the request’s profile.
If necessary, create a duplicate rule that includes the correct query profile or update the existing rule to include all applicable profiles.
Validate rule actions
Verify that the Boost items action is correctly defined using the ProdID_s field and valid product IDs. For example:
Field Name: ProdID_s
Field Values: 107903313, 113982644, 107794044These product IDs must correspond to live products that appear in the relevant category.
Confirm rule precedence
If multiple rules exist for the same query profile and category, ensure the intended rule has the highest precedence. If multiple rules share the same precedence, the most recently created rule takes effect.
Publish and test
After making changes:
Save and publish the rule.
Test in staging before pushing to production.
Use exact category facet URLs when testing to validate rule behavior.
Example test URL (staging):
https://test.zones.com/site/locate/refine.html?txt_search=&fq=categoryName_hier_ss:3//Products//Accessories//Mice & Keyboards//KeyboardsThe boosted products should appear at the top of the results.
Additional context
If using the Visual Editor in Commerce Studio and not seeing the expected facet paths, be aware that there may be internal display limits (e.g., 100 options). This may prevent full visibility into available values. Use the type-ahead input or search directly using partial values.