{"section":"known-issues","requestedLocale":"en","requestedSlug":"collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite","locale":"en","slug":"collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite","path":"docs/en/known-issues/B2B/collections-doesnt-work-in-custom-search-results-pages-in-b2b-suite.md","branch":"main","content":"## Summary\n\nCustom search results pages set up with collection id don't work when different product Collections are assigned to an organization.\n\nThe expected behavior when using Collections is to define the assortment of products the organization users will see in the storefront, but since B2B Organizations also use `productClusterId` in the search, when accessing custom search results pages set up with a different `productClusterId`, the search results show products from both collections.\n\nAlso, if the organization has more than one `productClusterId` assigned to it, when using `productClusterId` as a filter in the search, the products from all collections assigned to the organization will be shown.\n\n## Simulation\n\n**Scenario 1:**\n\n- Set up a product Collection to an organization;\n- Create a custom search results page with a different collection Id on the `productClusterId` filter;\n- Log in and access the custom search result page; products from both collections are shown.\n\n**Scenario 2:**\n\n- Set up more than one product Collections to an organization;\n- Create a custom search results page using only one of the`productClusterId` as filter;\n- Log in and access the custom search result page; products from all collections registered to the organization are shown.\n\n## Workaround\n\nUse `productClusterNames` as the filter for these search pages in place of `productClusterIds`."}