{"section":"known-issues","requestedLocale":"en","requestedSlug":"visual-merchandising-rules-changing-unexpected-products-due-to-conflicting-ids","locale":"en","slug":"visual-merchandising-rules-changing-unexpected-products-due-to-conflicting-ids","path":"docs/en/known-issues/Intelligent Search/visual-merchandising-rules-changing-unexpected-products-due-to-conflicting-ids.md","branch":"main","content":"## Summary\n\n\nThe visual editor for merchandising rules uses the product ID to register the rules, but they are processed on top of a more generic field, which includes more than just the _ProductID_ but also the _ProductRefID_, _SKUID_, _SKURefID_, and _EAN_, as per our documentation.\n\nIf the value from a product ID is also part of a different ID field in another product, the rule will be applied to both of them.\n\n\nThe same issue also happens for merchandising rules created with the manual editor while creating rules by the ID attribute if the value exists in more than one product, but in this case, it's possible to workaround using different ID values such as _SKURefID_ or _EAN_, which are more likely to be unique.\n\n\n##\n\n## Simulation\n\n\nConsider product A with \"productId=444\" and product B with \"productId=555\", where the SKU from product A is \"skuId=555\".\n\nA rule to pin or hide product B (productId=555) will also be applied to product A (due to skuId=555).\n\n\n##\n\n## Workaround\n\n\nN/A"}