- or
No existing idea results
- ~ No ideas found ~
1403 results found
-
Default layout for products
Currently, it is only possible to define default layouts for categories. As it is possible to create custom product layouts, it would also be beneficial if one could assign that layout to all existing and newly created products.
This would make it much easier to assign a new layout with several thousand products.
37 votes -
Crossselling: It would be great if you could assign both manual products and dynamic product groups
It should be possible to add both a dynamic product group and individual products when crosselling. You could then use a product group for several products, but also add individual products for each product.
4 votes -
Admin Search: Expand Search results in the quickview
Searching by name, company name or e-mail address is also difficult or the results are difficult to interpret because the e-mail address and company name are missing.
1 vote -
CMS Layouts - change section type
The type of section (default / sidebar) should be changeable at a later stage. If you want to change the type of a section from "sidebar" to "default / full width" (or vice versa), you'd have to set up a new section from scratch.
3 votes -
Automatically transform images into webp / avif format
Make it possible to transform images (especially product images) into into webp or avif. Here, you should select which one to use. Also: if you want to delete the original from the media storage.
Why: For SEO, you get a better rank while the website loading faster. The plugins for doing this are terrible.12 votes -
Manufacturer description in the data mapping
It should be possible to assign the manufacturer description to the stored manufacturer in the experience worlds or at least in the categories in the description and then in the data assignment.
Since there are no global manufacturer layouts, it should at least be possible to build one with the help of the data assignment.
2 votes -
Discount promotions in the listing
Discount promotions should already be marked or displayed in the listing (comparable to Shopware 5) and not only in the shopping cart.
28 votes -
Define basic information for different languages
It is currently possible to change the language under Basic information, but the content, e.g. for the shop's bank details field, is maintained globally for all languages and it is not possible to maintain this for one language. This is not user-friendly, as in a sales channel with several languages it should also be possible to make different entries here.
2 votes -
Define main category for breadcrumb
The products use the category that was added first as the breadcrumb. There is no option to specify which category should be used for the breadcrumb.
A possibility to define this in the administration would be great.
3 votes -
Allow filtering of stock levels = 0 and < 0 in the product filter in the backend
Unfortunately, it is not possible to filter products in the bakend that have a stock level of 0 or less than 0.
It would make work much easier if these options were implemented.
3 votes -
Flowbuilder - form related triggers
Implement triggers that validate on specific fields / entries within a (custom)-form.
For example: If field1 (checkbox) is true / checked, then perform action xy on customers.
4 votes -
It should also be possible to export inactive products via the product comparison.
Currently, inactive products are not exported in a product comparison. Also products with a stock level of 0 with activated clearance sales.
It should also be possible to export inactive products via the product comparison.
5 votes -
Save sorting config in the admin
Sorting in the admin, for example in the customer overview, should be saved automatically when it is applied.
12 votes -
CategoryDefinition: More searchable properties
If I use Criteria::setTerm() I actually just can find categories by name. Only the name have the flag "SearchRanking". If I add the flag to the property "keywords" I also can find categories by the keywords. It would be great if more properties become searchable there!
3 votes -
It should be possible to display all variants in the search results without them also being displayed individually in the listing.
It should be possible to display all variants in the search results without them also being displayed individually in the listing.
Currently, the variants are only displayed in the search results if you activate the expansion of the properties in the product list in the storefront display.
8 votes -
Matrix order
To simplify ordering process when purchasing several variations of one product, such as a USB flash drive in various colors and capacity, you can use a Matrix Form. The matrix form is available only when a product has one or two attributes.
5 votes -
Search Result Layout (header search) with active Commercial Extension
If the Commercial extension is inactive, the search result layout (header search, not the result page) is defined by the class "search-suggest-container". If, on the other hand, the Commercial extension is activated, the styling is generally controlled by the advanced-search-suggest-container class.
However, the latter should only be the case if Advanced Search is actually activated. Until that is the case, use the default search-suggest-container.
1 vote -
Approve reviews in bulk from the grid
We receive a lot of product reviews in our shop. At this point we need to set them to 'Visible' one by one. It is very time consuming and unneeded.
We should be able to approve reviews in bulk by selecting them from the grid and choose for 'Make Visible' now you can only choose for 'Delete' when selecting reviews from the grid.
4 votes -
Quickfix: Link from Support Form to the Extension License
The extension name in the sidebar of the a support thread should link to the extension details, to be able to view more information, such as the changelog - which can come in handy from a customer/partner perspective to check for updates.
1 vote -
Assign tag for newsletter recipients via the Flow Builder
It is not yet possible to automatically assign a tag to a newsletter recipient via the Flow Builder. This function would be desirable, as newsletter recipients can be assigned a tag anyway, just not automatically via the Flow Builder.
1 vote
- Don't see your idea?