SCC FeedbackWe value your input! Tell us what you think about our Sana Commerce Cloud roadmap initiatives and the direction we're taking. If there's something specific you'd like to see, don't hesitate to share it with us below. Vote for ideas on the page to let us know what you find important. You can vote by clicking on an idea and then click thumbs up, down or neutral.
Individually allocable product group page templates and article detail page templates
Since product group pages and item detail pages are fully editable, it would be great if several different product group pages templates or item detail pages templates could be created and assigned to product groups or items individually. In this way, the display can be optimally adapted to the properties of the different product groups or articles.
Today, the layout (for both Desktop and Mobile) of the ProductPage is handled as follows:
If there is a change at the level of a specific ProductPage, this is used. Otherwise, the layout of the SystemPage "Product details" is used
One of our customers had to structure the layout of a group of articles in a different way than all the others. Specifically, these articles were to have 3 columns in the detail line instead of the 2 columns defined as standard:
In the first the images are shown.
In the second, the article detail is shown (Title, Short Description, Price, Variant, Quantity, Unit of Measure, etc...)
In the third, related articles are shown (vertically)
In order to do this, we had to manually update all pages one at a time. This means that if we need to change this layout in the future, we will have to intervene on all pages one at a time.This is why we propose the following idea: add a new layer through which you can define the layout of the ProductPage. In our opinion, the layout selection logic could be as follows:
If there is a change at the level of a specific ProductPage, this is used
Otherwise, if a "Group/Template" layout is associated with the ProductPage, this is used
Otherwise, the SystemPage layout "Product details" is used.
3
Optional identifier for mapping images
Optional identifier for mapping images

If you want to import and map many images at the same time, these must be named according to SKU. If there are several images or variants, there are rules such as SKU_1. In order to ensure the quality of product handling and to have synchronized flows between the supplier, us and customers, we try to use GTIN/EAN. Images retrieved from external sources should be handled according to the GS1 standard in how images are named. Suggestions:That the mapping of image can be optional if it should go to SKU or GTIN (perhaps also the manufacturer's article number). With GTIN mapping, different sales units become unique, and there are ready-made standards for how different sodas are named and displayed. Images that come from the GDSN network follow GS1 naming rules.

3
0
0