- or
No existing idea results
- ~ No ideas found ~
1297 results found
-
form block element with the possibility to create radio buttons
Introduction of a radio button element for the form tool (Erlebniswelt Block Element) This should be a standard feature
5 votes -
The address settings in the country configuration should have an effect on the registration form.
The address settings in the country configuration should have an effect on the registration form.
The current order is always street, town, zip code. For Germany, for example, the correct order would be: street, zip code, town.1 vote -
Shopping cart display “Delivery time” on oldest date
Partial deliveries within orders are often excluded, which is why only the oldest delivery period within the items is important. There should therefore be an option to display only the oldest delivery period in the shopping cart.
Otherwise, the only alternative would be to completely deactivate the delivery period display.
3 votes -
No mandatory fields for Import
The fact that there are mandatory fields during import means that unnecessary data (e.g. stock in the event of a price change) is transferred, but this only delays the duration of the import and makes no sense.
For example, it is not necessary to change the stock when changing prices. This is not necessary and only delays the duration of the import. For large customers, the import takes many hours.
It would therefore be desirable to be able to deactivate the dependencies.
1 vote -
Split amount of product-listing items for different Devices
Right now, you can force SW to list as many items as you want in a category. Having 96 items on a category page may look good on desktop, but it slows down the mobile view by at least 2 seconds.
So, it would be a great feature to split the product listing view into Devices. For example, there are 24 items on mobile and 96 items on desktop.
User and Pagespeed would appreciate that.
Thanks.1 vote -
Position related discounts in cart / order details
Enable position related discounts in cart and order details. Currently all discounts that have been granted for one cart are beeing summed up and they show as one dedicated position.
6 votes -
Specify what field-values are missing when saving a product having empty mandatory fields
Currently, if mandatory fields are empty while saving, the following message is shown:
"1x "This field must not be empty.""
This often times will lead to uncertainty since the exact field is not mentioned within the error message itself.
Therefore, it would be nice to have some kind of message that looks like:
[fieldname]: "This field must not be empty."
82 votesHello,
Thank you for your feedback and your patience with this topic!
In a first iteration, we already improved the error handling for the product module by highlighting the specific tab in which the error occurred and displaying a list of missing fields at the top of the module. In further iterations, we like to specify these messages.
In general, this topic is relevant not only for the product module but also for all kinds of user situations within the administration. We would like to work on this more generally and would love your feedback on it as well: https://feedback.shopware.com/forums/942607/suggestions/48892556.
We’ll keep you updated as things progress, and we appreciate your understanding and input!
Best,
Marie Reckendrees
-
New event needed: Request for Customer group XY
When the registration for a customer group is received, there is currently no option to send a message for a specific customer group that the customer must be approved for the customer group. As the approval in the customer overview can easily be overlooked, an event with an email to the shop operator or similar would be useful.
Wenn die Registrierung für eine Kundengruppe eingeht, gibt es aktuell keine Möglichkeit für eine bestimmte Kundengruppe eine Nachricht zu verschicken, dass sich der Kunde für die Kundengruppe freigegeben werden muss. Da die Freigabe in der Übersicht Kunden schnell übersehen werden kann, wäre ein Event mit einer Mail an den Shopbetreiber oder ähnlich sinnvoll.
When the registration for a customer group is received, there is currently no option to send a message for a specific customer group that the customer must be approved for the customer group. As the approval in the customer overview can easily be overlooked, an event with an email to the shop operator or similar would be useful.
Wenn die Registrierung für eine Kundengruppe eingeht, gibt es aktuell keine Möglichkeit für eine bestimmte Kundengruppe eine Nachricht zu verschicken, dass sich der Kunde für die Kundengruppe freigegeben werden muss. Da die Freigabe in der Übersicht Kunden schnell übersehen werden kann, wäre…
2 votes -
DHL Extension - DTP (duties & taxes paid)
It should be possible to integrate DTP in DHL.
2 votes -
When you upload a file to a digital product, there should be a process bar
Big files need some time to upload. So a process bar helps to see if the upload works and how long it will take.
1 vote -
Cross selling improvements
Cross sellings are a fairly commonly used feature in many online shops.
Our implementation still seems somewhat basic. It would be great to have the option to treat cross sellings as separate entities (instead of being an "attachment" to every product individually) so we can assign ONE defined cross selling - in bulk - to many products.
Currently, there is no way to realistically do this. Instead, you have to create a cross selling for every single product you want to use it for separately.
The export function for cross sellings suffers from this "individual" logic as well or this would be a practical workaround - allow product_id to contain an array of products, separated by pipe or something. That way, we'd at least allow one cross selling to be attached to many products, even if it's still quite a lot of effort for most shop owners.
While we're at it, for the far future we should also consider using AI here. There must be ways to analyze which customers buying product A also frequently buy product B and C and such.
Cross sellings are a fairly commonly used feature in many online shops.
Our implementation still seems somewhat basic. It would be great to have the option to treat cross sellings as separate entities (instead of being an "attachment" to every product individually) so we can assign ONE defined cross selling - in bulk - to many products.
Currently, there is no way to realistically do this. Instead, you have to create a cross selling for every single product you want to use it for separately.
The export function for cross sellings suffers from this "individual" logic as well or this…
3 votes -
Improved centralized management of variants to reduce maintenance effort
EN
Improved centralized management of variants to reduce maintenance effort
Description:
Currently, variant management in Shopware 6 causes an enormous amount of extra work when it comes to updating variants that are used in many products. This particularly affects store operators who offer many products with identical variants.DE
Verbesserte zentrale Verwaltung von Varianten zur Reduzierung des Pflegeaufwands
Beschreibung:
Derzeit verursacht die Variantenverwaltung in Shopware 6 einen enormen Mehraufwand, wenn es um die Aktualisierung von Varianten geht, die in vielen Produkten verwendet werden. Dies betrifft insbesondere Shopbetreiber, die viele Produkte mit identischen Varianten anbieten. Hier ein Beispiel, das die aktuelle Problematik verdeutlicht und wie diese verbessert werden könnte:Beispiel: Angenommen, ein Shop bietet Paneele in 100 verschiedenen Profilen an (z. B. U-Profil, V-Profil, Null-Fugen-Profil), und jedes Profil ist in 120 Farben erhältlich. Der Ablauf in Shopware sieht derzeit so aus:
Die 100 Profilvarianten werden im Backend einzeln angelegt. Die 120 Farbvarianten werden als Eigenschaften angelegt und jedem Profil als Variante zugewiesen.Sollte nun eine der Farbvarianten – z. B. „Sonderfarbe Blau“ – geändert werden, muss das Bild dieser Variante für jede der 100 Profilvarianten manuell angepasst werden. Das bedeutet, dass man für jedes Profil die betroffene Farbvariante auswählen, das Bild ändern und die Änderung speichern muss. Dies führt zu einem extrem hohen Aufwand, da dieselbe Aktion mehrfach durchgeführt werden muss, obwohl die Variante identisch ist.
Vorgeschlagene Lösung:
Eine zentrale Verwaltung der Varianten, bei der Änderungen an einer "Vatervariante" automatisch auf alle zugehörigen Produkte angewendet werden, würde den Workflow erheblich verbessern. Konkret könnte dies wie folgt aussehen:Zentrale Variantenpflege: Varianten werden einmalig erstellt und dann zentral verwaltet. Änderungen (z. B. an Bildern oder Zusatzfeldern) können an der zentralen Variante vorgenommen werden und werden auf alle zugewiesenen Produkte übertragen. Automatische Vererbung von Änderungen: Änderungen an einer Variante – sei es ein neues Bild oder ein Zusatzfeld – werden automatisch an alle Produkte weitergegeben, die diese Variante verwenden. Performance-Optimierung im Backend: Eine zentrale Verwaltung reduziert nicht nur die Pflegezeit, sondern sorgt auch für eine effizientere Nutzung der Backend-Ressourcen, da redundante Datenbearbeitung entfällt.Durch die Umsetzung dieser Funktionen könnten Shopbetreiber immense Zeit und Arbeit sparen, die Pflege von Varianten effizienter gestalten und die Fehleranfälligkeit durch manuelle, sich wiederholende Eingaben reduzieren.
EN
Improved centralized management of variants to reduce maintenance effort
Description:
Currently, variant management in Shopware 6 causes an enormous amount of extra work when it comes to updating variants that are used in many products. This particularly affects store operators who offer many products with identical variants.DE
Verbesserte zentrale Verwaltung von Varianten zur Reduzierung des Pflegeaufwands
Beschreibung:
Derzeit verursacht die Variantenverwaltung in Shopware 6 einen enormen Mehraufwand, wenn es um die Aktualisierung von Varianten geht, die in vielen Produkten verwendet werden. Dies betrifft insbesondere Shopbetreiber, die viele Produkte mit identischen Varianten anbieten. Hier ein Beispiel, das die aktuelle…1 vote -
Opportunity to change the order of storefront snippet files
There should be a way to customise the order in which the storefront snippet files are loaded.
Currently the snippet files are loaded in a first come first serve principle.
For example like this
vendor/shopware/core
vendor/mycompany/mytheme/
vendor/store.shopware.com/
vendor/mycompany/myplugin/
vendor/store.shopware.com/swaglanguagepackLoading the snippet files should be like this:
vendor/shopware/core
vendor/store.shopware.com/
vendor/mycompany/myplugin/
vendor/mycompany/mytheme/So that you can overwrite all others with the snippet files of your own theme.
1 vote -
admin: menu bar permanent collapsed
Possibility to set the menu bar permanent collapsed or not.
3 votes -
Extend ruling / possibilties for shipping methods
EN
The number of requests to expand the options for shipping methods is increasing. Many customers who come from Shopware 5 miss the option of entering individual calculations or combining standard shipping methods with surcharge or discount shipping methods. I'll take DHL as an example here. When shipping abroad, the EU / non-EU distinction is used, the destination countries are divided into zones, there is a basic price and a surcharge per kilogramme.
This can of course be mapped with Rule Builder and the current shipping methods, but if I send goods weighing up to, say, 100 kg, it means creating a price matrix with at least 100 entries. This also involves manually calculating which basic price with which number of kilograms results in which total price.The price per kilogram remains the same in the scenario, so the whole thing would be relatively easy for our customers to map if it were possible to specify a calculation, for example "total weight * 1.50 EUR", the basic prices are staggered according to kilogram ranges, which could already be easily mapped now. It would only be necessary to add the two together to produce a final shipping price. Percentage surcharges etc. are also missing.
DE
Die Anfragen zu einer Erweiterung der Möglichkeiten für Versandarten nehmen zu. Viele Kunden, die von Shopware 5 kommen, vermissen die Möglichkeit individuelle Berechnungen zu erfassen oder Standardversandarten mit Aufschlags- oder Abschlagsversandarten zu kombinieren. Als ein Beispiel nehme ich hier DHL. Bei dem Versand ins Ausland wird die Unterscheidung EU / Nicht EU angewendet, die Zielländer sind in Zonen aufgeteilt, es gibt eine Grundpreis und einen Aufschlag pro Kilogramm. Das lässt sich mit Rule Builder und den aktuellen Versandmethoden natürlich abbilden, aber allein wenn ich Versandgut bis sagen wird 100 Kg verschicke, bedeutet es eine Preismatrix mit mindestens 100 Einträgen anzulegen. Dabei muss dann auch noch manuell berechnet werden, welcher Grundpreis mit welcher Kilozahl welchen Gesamtpreis ergibt.Der Preis pro Kilogramm bleibt in dem Szenario gleich, somit wäre das Ganze für unsere Kunden relativ leicht abzubilden wenn es die Möglichkeit gäbe eine Berechnung anzugeben, zum Beispiel "Gesamtgewicht * 1,50 EUR", die Grundpreise sind nach Kilogrammbereichen gestaffelt, das ließe bereits jetzt einfach abbilden. Es müsste nur beides zusammen gerechnet einen Versandendpreis ergeben. Vermisst werden außerdem prozentuale Aufschläge usw.
EN
The number of requests to expand the options for shipping methods is increasing. Many customers who come from Shopware 5 miss the option of entering individual calculations or combining standard shipping methods with surcharge or discount shipping methods. I'll take DHL as an example here. When shipping abroad, the EU / non-EU distinction is used, the destination countries are divided into zones, there is a basic price and a surcharge per kilogramme.
This can of course be mapped with Rule Builder and the current shipping methods, but if I send goods weighing up to, say, 100 kg, it means…5 votes -
404 Meta title
The 404 page should get an own Meta Title to better track visits on the 404 via GA4
8 votes -
Warehouses as condition and stocks
A Warehouse should be selectable for the definition of Dynamic Product groups
The stock of the warehouse should be possible to use for condition, example: Stock in Warehouse 1 > 1
The warehouse stocks should change the main stock in the Product listing.
2 votes -
B2B checkout: Order reference and deliverydate
SW6 B2B Component should have same functionality as the previous B2B-suite. In Order process (checkout) merchants should have form-fields for own Order-Reference and wishes for the delivery-date.
(order.customFields.b2bOrderReferenceHolder, order.customFields.b2bDeliveryDateHolder)
4 votes -
Quick orders - CSV format
When a CSV file is created on a standard Windows PC, as most users still do, it is in DOS ANSI encoding (the normal user does not care about this but simply creates a file). This format is not supported by the quick orders (in the upload).
It would be great if more formats were supported, OR if a hint text was added to the upload field for the UTF-8 format.
1 vote -
Define database fields yourself | Datenbankfelder selbst definieren
DE
Datenbankfelder selbst definieren, um die Nachvollziehbarkeit und business-individuelle Zweckhaftigkeit der Auswertungen zu steigern.
–
EN
Define database fields yourself to increase the traceability and business-specific usefulness of the evaluations.1 vote
- Don't see your idea?