- or
No existing idea results
- ~ No ideas found ~
1297 results found
-
Fallback for Variant Pre-Selection
The storefront presentation can be used to define a specific variant preselection for the listing as well as for the detail page.
If the main article is now selected for display in the listing, but no variant is defined for the preselection on the detail page, any variant is preselected seemingly at random, even if it is no longer available in terms of stock.
Here it would be desirable if we could simply select the next available variant option as a fallback.
16 votes -
Add translations for order statuses
Currently, it is not possible to add translations for order, payment and delivery status as the entries appear to be hardcoded.
There is an issue ticket already which was closed (despite having 18 votes, which seems like nothing to sneeze at), which can be found here:
https://issues.shopware.com/issues/NEXT-15282
Contrary to what is written in that ticket, translations ARE used IF present and that is the issue really. They can't be added in the admin anywhere.
We CAN circumvent this by adding them manually in the database, but we can't expect shop owners to do this because that way is rather technical and comes with certain risks.
An elegant way would be to have them register as snippets so they can be translated like most other content.
Currently, it is not possible to add translations for order, payment and delivery status as the entries appear to be hardcoded.
There is an issue ticket already which was closed (despite having 18 votes, which seems like nothing to sneeze at), which can be found here:
https://issues.shopware.com/issues/NEXT-15282
Contrary to what is written in that ticket, translations ARE used IF present and that is the issue really. They can't be added in the admin anywhere.
We CAN circumvent this by adding them manually in the database, but we can't expect shop owners to do this because that way is rather technical…
4 votes -
simplify import of new Products
The import of new products should be significantly simplified. As in SW5, it should be possible to edit profiles more easily and make ALL nodes/extensions for advanced prices, media, properties, cross-selling, etc. available to provide ALL relevant data for new products in one upload.
In its current form, the import and export process is extremely cumbersome and very inconvenient.3 votes -
Demotivating update strategy
I don't understand why new versions are constantly being released. Shopify releases an update twice a year. Can't you do the same with Shopware? Collect everything or once a quarter and you know in advance what will be optimised. And the release date is fixed, so you can prepare for it. It would simply be structured. Security updates run separately.
We pay a lot of money for updates because many functionalities are no longer available in the Shopware core and we always have to test all plugins to see if they are compatible again. I'm not even going to mention external systems such as ERP or the like. Developers even complain to us that Shopware's version updates are random and that they then have to catch up quickly and features can't be developed because they have to guarantee compatibility. Is Shopware aware of this?
And I suspect that this situation is annoying - for the developers of the plugins and also for the retailers.
We are currently trying to upgrade to Shopware 6.6.7.1 and I already know that a new version is coming.
It's demotivating.
I don't understand why new versions are constantly being released. Shopify releases an update twice a year. Can't you do the same with Shopware? Collect everything or once a quarter and you know in advance what will be optimised. And the release date is fixed, so you can prepare for it. It would simply be structured. Security updates run separately.
We pay a lot of money for updates because many functionalities are no longer available in the Shopware core and we always have to test all plugins to see if they are compatible again. I'm not even going to mention…
1 vote -
The active product should not be displayed in cross-selling
If the opened item is part of the product group selected for crosselling, it should not be displayed in crosselling.
6 votes -
New document type in orders: order confirmation
EN:
There should be a new document type: order confirmation. The order confirmations generated via ERP can contain more information (e.g. contact person based on zip code) and can therefore be important for the customer.DE:
Es sollte einen neuen Dokumententyp: Bestellbestätigung geben. In den per ERP generierten Auftragsbestätigungen können mehr Informationen (z.B. Ansprechpartner basierend anhand er Postleitzahl) enthalten sein und damit wichtig für den Kunden sein.3 votes -
Permissions for extension settings
I like to set up permission for the admin user only for configuration/managment of one specific extension.
1 vote -
Direct links in the account
Shopware provides a lot of website with a lot of interesting data, like feedback.shopware.com, brand.shopware.com and others. As a partner it would be helpful to have links to these site directly in the account. SSO makes it possible to log me in directly.
2 votes -
Import Custom Product Options and Prices
Add profile and mappings to import custom product options and prices
2 votes -
Display creation date of customer account
The creation date of the customer account should also be displayed within the customer and the customer overview.
It should also be possible to filter according to the date or, for example, the condition "older than {number} years/months/days" using the Rule Builder in order to control discount campaigns.
8 votes -
Order and customer overview: compact view
Order overview: the table is 170 pixel line height
Customer overview: the table is 278 pixel line heightBoth should be equal with max. 100 pixel line height to see more entries per page with less scrolling.
14 votes -
Authorisation to display statistics
At present, the display of authorisations is still linked to the right to display and edit orders.
As employees often also process orders but should not be able to view the statistics, a special right is required in the configuration of the authorisations in order to be able to show and hide this display individually for users.
1 vote -
Promotions should be combined with discounts in subscriptions
Discounts are not enabled for subscriptions by default.
A discount should be also available for subscriptions in addition to the discount that is already set in the subscription.
E.G. a subscription has a 10% discount set. A regular discount is defined via promotion and is used for a reqular cart. When the same produdct is used in a subscription the discount from the promotion is not applied.
If a merchant want´s to apply both discounts within a subscription an option is needed in the promotion to use it also within subscritions.
2 votes -
Add User Permission for Notifications in Administration
Certain roles don't need to get notifications about licence violations and updates. Therefore, we need to bind those notifications to dedicated user permissions.
2 votes -
Include dashboard in the user rights
It would be good if you could select the dashboard as an individual right in the user rights in the admin. There are users who are allowed to see orders but should not have access to the dashboard.
2 votes -
Product feed templates for price comparison platforms
Customers ask for additional templates for product feeds for pricing comparison platforms like Idealo once in a while. Maybe we could add some of the most common.
DE
Kunden fragen ab und zu nach weiteren Vorlagen für Produkt Feeds für Anbieter von Produkt- und Preisvergleichen wie Idealo. Vielleicht können wir weitere für die bekanntesten Anbieter ergänzen.2 votes -
It should also be possible to process discount promotions if orders with this discount have already been placed.
It should also be possible to process discount promotions if orders with this discount have already been placed.
Some discounts are intended to be used permanently, except that the discount itself changes from time to time. However, this is currently not possible.
1 vote -
Show CMS element label (same for blocks)
It would be nice to see the used elements (and blocks) in admin to identify them. Especially with custom elements.
Similar elements are sometimes hard to distinguish or retrievable.
3 votes -
Property sorting should be regulated as in shopware 5
The sorting (including the characteristic properties) should be structured in the same way as in shopware 5.
If i have a shop that is mainly based on products with many properties, editing in shopware 6 is very tedious. This should be made easier.2 votes -
Improvement in the cms sidebar
There is a small issue that I want to override a cms block, but this will not make it possible anymore for vendor plugins to override the child block. In the screenshot you can see that I want to make changes to the :disabled property, but I want to keep the child block as-is. So vendors can use this child block to override.
I understand that the {% parent %} only renders the main block and not the nested blocks.
I suggest to improve the value of this :disabled property to make a new computed function. So we can override this function without breaking the nested block.It would be something like:
:disabled="!isDisabledSettingsTypeField(page)"The computed would look like:
isDisabledSettingsTypeField() {
return !this.isSystemDefaultLanguage || page.type === 'product_detail';
}There is a small issue that I want to override a cms block, but this will not make it possible anymore for vendor plugins to override the child block. In the screenshot you can see that I want to make changes to the :disabled property, but I want to keep the child block as-is. So vendors can use this child block to override.
I understand that the {% parent %} only renders the main block and not the nested blocks.
I suggest to improve the value of this :disabled property to make a new computed function. So we can override…1 vote
- Don't see your idea?