The OOB feature shows the categories and subcategories even though no products assorted to it. So, if same channel navigation hierarchy is being used across multiple channels (for different countries), and if the products assorted to the channel across countries are not the same, this will end up with large number of empty category pages with no products in it. This impacts the customer journey and confuses the users.
Example: For a multi-brand site with each node as a brand, a customer logged in to Channel UAE will see all 5-6 brands although the channel only has 2 brands in UAE, as mapped in the assortments. When the customer clicks on the other 4 brands it takes them to an empty category page.
Expectation: The site pages should only show the nodes with respect to the products assorted to it, so the empty nodes won’t be visible to the users. This will reduce a high number of unwanted category pages within the site. This should apply to the Site builder Product section as well, Only the nodes with products assorted will be available for the users to edit/enrich.
Comments
Acknowledging the above. The site pages should only show the nodes with respect to the products assorted to it.
Category: Web front end experiences and framework
Acknowledging the above.this is important requirement .
Category: Web front end experiences and framework
Acknowledging the above.When an end customer browses the web site, he/she sees the entire Navigation category hierarchy as-is. Its not aligned to defined assortments for the online store.Impact: Bad customer experience. Customer sees irrelevant hierarchies and when customer drills down it says "No items found".Expected Solution: The Navigation hierarchy should show in line to assortments which is already mapped and data available in D365. Ideal to have a setup which would allow partners to set it up which would allow to grey out and/or not to show hierarchies that are irrelevant to the store. This would make the solution flexible.
Category: Web front end experiences and framework