- or
1464 results found
-
Properly display error messages for customer-facing formfields
Currenty, Showpare (default skin) does not reliably display error messages on missing or wrong form fields when submitted by the users, e.g.
- When logging in with wrong credentials
- When registering an account (most fields)
- When using the newsletter registration form.
Shopware will highlight the fields in red and there are internal attributes (data-form-validation-required-messag) on the fields that do contain error messages, but these are not displayed reliably to the user. There seems to be something in place that will sometimes client-validate those error messages and display them, but that hardly happens / seems broken. (Not a bug accordinging to Shopware support, redirected here instead)
We would expect any error messages attached to wrongly filled or empty obligatory fields to be displayed at a sensible space (below?) the form field.
See attached Screenshots.
Currenty, Showpare (default skin) does not reliably display error messages on missing or wrong form fields when submitted by the users, e.g.
- When logging in with wrong credentials
- When registering an account (most fields)
- When using the newsletter registration form.
Shopware will highlight the fields in red and there are internal attributes (data-form-validation-required-messag) on the fields that do contain error messages, but these are not displayed reliably to the user. There seems to be something in place that will sometimes client-validate those error messages and display them, but that hardly happens / seems broken. (Not a bug accordinging to Shopware…
4 votes -
Bulk translation editor for CMS element config in Layout tab
Currently, when managing translations for CMS configurations (such as a text block, images, ...) within product or category pages, the process is quite time-consuming. We need to manually switch languages and update the field one-by-one for each language. For stores with multiple languages, this creates a lot of overhead for even small content updates like updating a photo.
I’d like to propose a bulk translation editor that allows us to edit the config of a CMS element across multiple languages in one view, similar to how snippet management already works at this moment. This would greatly improve usability and efficiency for content managers working in multilingual shops.
Ideally, this editor could be opened from the CMS config card in the Layout tab and show a table or structured form where we can input translations for each language side-by-side.
Additionally, bonus points for a way to copy a translated config for a certain element to all other languages would be great. An image for example is often not translated, thus does not need a specific config for each language.
Currently, when managing translations for CMS configurations (such as a text block, images, ...) within product or category pages, the process is quite time-consuming. We need to manually switch languages and update the field one-by-one for each language. For stores with multiple languages, this creates a lot of overhead for even small content updates like updating a photo.
I’d like to propose a bulk translation editor that allows us to edit the config of a CMS element across multiple languages in one view, similar to how snippet management already works at this moment. This would greatly improve usability and efficiency…
1 vote -
gallery slider is not compatible with different sizes
When the pictures are very different in size or ratio, the gallery slider pops out downside or shrinks back upside, which is not very nice
an option to choose a certain height so that the pictures scale to it would be nice
1 vote -
Display of variants in product-sliders and cross sellings if assigned via dynamic product group
The display of variants within product sliders - if assigned via dynamic product groups - is based on the configuration from the storefront presentation. Even if individual variant options are explicitly assigned to the dynamic product group, it is still possible that the main product or a different variant will be displayed, unless it has been specified that the variants should be fanned out.
If I want to ensure that only certain variants are displayed in a product slider, the individual variants must currently be manually assigned to the product slider. This is because changes to the storefront display always have a direct effect on the listing at the same time, even though this may not be desired and the configuration should only relate to the slider.
The display of variants within product sliders - if assigned via dynamic product groups - is based on the configuration from the storefront presentation. Even if individual variant options are explicitly assigned to the dynamic product group, it is still possible that the main product or a different variant will be displayed, unless it has been specified that the variants should be fanned out.
If I want to ensure that only certain variants are displayed in a product slider, the individual variants must currently be manually assigned to the product slider. This is because changes to the storefront display always…
3 votes -
Add search for blocks and elements at cms page editing
Add a search bar to block sidebar and element selection to get blocks and elements quicker.
Important when more elements/blocks are added with plugins/apps.2 votes -
predefined periods for products / add an expiration date
In Shopware 6 it would be very useful if it were possible to activate products for a set period of time.
Since there is already a “release date”, it would be very useful to add an end to it.
In certain sectors, products may only be offered for a period of time x, e.g. for pesticides as these have approvals with an end date.
2 votes -
Different flows for different forms
It is currently not possible to send different actions, for example different e-mail templates, if different forms are sent.
A differentiation through a rule in the Rule Builder or different flow triggers would be helpful here.2 votes -
Automated Birthday Greetings with Discounts
I would like to suggest an enhancement to Shopware 6 that brings back a popular and valuable feature from Shopware 5: automatically sending birthday emails with discount codes or greetings to customers.
The Issue:
Currently, Shopware 6 lacks the functionality to automate birthday-related actions through the Rule Builder and Flow Builder. This prevents shop owners from creating personalized birthday campaigns, which are an effective tool for customer engagement and loyalty.Proposed Solution:
Enhance the Rule Builder and Flow Builder with the ability to:Identify Birthdays:
Add a rule condition that checks the "Date of Birth" field in customer profiles.
Allow dynamic filtering, such as "is today," "is in the next X days," or "has already occurred this year."
Automated Email Trigger:Enable automated email workflows based on the customer's birthday, either on the exact date or as part of a pre-scheduled campaign.
Custom Discount Code Generation:Integrate the ability to generate unique, single-use discount codes as part of the workflow.
Include these codes dynamically in the email template.
Personalized Messaging:Allow email templates to include dynamic fields, such as the customer's name or age (optional), to make the greetings feel personal.
Benefits for Shop Owners:Strengthened Customer Loyalty: Birthday emails are a great way to engage customers on a personal level and show appreciation.
Increased Sales Opportunities: Discounts incentivize customers to make a purchase, driving revenue.
Time Efficiency: Automating this process saves time for shop owners, especially for shops with a large customer base.
Customer Delight: A thoughtful gesture like a birthday greeting can leave a lasting positive impression.I would like to suggest an enhancement to Shopware 6 that brings back a popular and valuable feature from Shopware 5: automatically sending birthday emails with discount codes or greetings to customers.
The Issue:
Currently, Shopware 6 lacks the functionality to automate birthday-related actions through the Rule Builder and Flow Builder. This prevents shop owners from creating personalized birthday campaigns, which are an effective tool for customer engagement and loyalty.Proposed Solution:
Enhance the Rule Builder and Flow Builder with the ability to:Identify Birthdays:
Add a rule condition that checks the "Date of Birth" field in customer profiles.
Allow…3 votes -
Order details - Show customer group, company name etc.
Add information just like "customer group", "company name" and "vat id" to the order details. To get those kind of information you currently need to open the customer record itself.
4 votes -
Offer management & stock management
If you want to place an order from an offer, but one of the items is no longer available (on sale), you can no longer place the entire order. An error message is displayed “The product [...] is no longer available”.
It is also not possible for the customer in the frontend or the admin in the backend to edit the offer afterwards and remove the affected item
This makes the entire offer unusable, which is of course particularly unfavorable for a B2B store, as customers here compile complex offer requests with 50 or more items.
It would actually make sense for the order to be placed anyway and for the relevant item to be removed with a message or for the item to be removed manually. At the very least, the admin should be able to correct it.
If you want to place an order from an offer, but one of the items is no longer available (on sale), you can no longer place the entire order. An error message is displayed “The product [...] is no longer available”.
It is also not possible for the customer in the frontend or the admin in the backend to edit the offer afterwards and remove the affected item
This makes the entire offer unusable, which is of course particularly unfavorable for a B2B store, as customers here compile complex offer requests with 50 or more items.
It would actually make…
1 vote -
Improve credit system
Deutsch:
Das Anlegen einer Gutschrift z.B. bei einer Retoure ist zu kompliziert.
Verbesserungsvorschlag: Beim erstellen einer Gutschrift ein Auswahlmenü der bestellten Artikel anzeigen lassen. Aus diesem können dann die retournierten / reklamierten Artikel für die Gutschrift ausgewählt werden. Optimal wäre noch eine Option, ob die Versandkosten gutgeschrieben werden sollen oder nicht.
English:
Creating a credit note, e.g. for a return, is too complicated.
Suggestion for improvement: When creating a credit note, display a selection menu for the items ordered. From this, the returned / complained articles can then be selected for credit. Another option would be ideal whether the shipping costs should be credited or not.
Deutsch:
Das Anlegen einer Gutschrift z.B. bei einer Retoure ist zu kompliziert.
Verbesserungsvorschlag: Beim erstellen einer Gutschrift ein Auswahlmenü der bestellten Artikel anzeigen lassen. Aus diesem können dann die retournierten / reklamierten Artikel für die Gutschrift ausgewählt werden. Optimal wäre noch eine Option, ob die Versandkosten gutgeschrieben werden sollen oder nicht.
English:
Creating a credit note, e.g. for a return, is too complicated.
Suggestion for improvement: When creating a credit note, display a selection menu for the items ordered. From this, the returned / complained articles can then be selected for credit. Another option would be ideal whether the shipping…
8 votes -
Rule Builder - Additional operators for custom fields
Additional fields can be created with a date field and can also be used in a rule. Unfortunately, there aren't very suitable operators available. Useful ones would be: "Time until," "Time after," "Between," "Greater than," and "Less than."
3 votes -
Support partial quantities and decimals in order quantity & inventory
As a merchant, I want to manage and sell products in partial quantities or decimals, so that I can efficiently handle use cases like selling goods by weight, length, or volume, and better meet the needs of industries requiring fractional units.
This will improve flexibility for different business models and ensure seamless inventory management and customer satisfaction.
2 votes -
Enable non deletable discounts
It is currently possible to delete discounts from your cart and the checkout.
This behaviour could lead to customers accidentally deleting discounts via the "X" that they are obliged to.
Mandatory or non deletable discounts could solve this problem.
Why would a customer want to delete a discount from his/her cart?2 votes -
Add discount as sorting option
There is currently no nice way to create a sorting option based on the discount of products in the Admin under "Settings > Shop > Products > Sorting options".
It is a common use case (especially during times like Black Friday), that consumers sort the products based on the discount. It would be valuable to have that option also for Shopware.
3 votes -
In the mobile version, only the smallest thumbnails should be loaded to save traffic.
It requires unnecessary traffic to load large images. In the mobile version for the SMartphone it should be sufficient to load the small thumbnails instead of the large ones.
1 vote -
Zusätzliche Spalte und Kommentarfeld bei SW6 Backend Bestellungen I Additional column and comment field for SW6 backend orders
Aktuell steht bei SW6 Backend Bestellungen nur ein Feld, mit Dropdown Menü für die Suche nach Artikelnummer oder Artikelname zur Verfügung. Oder die leere Positionszeile.
In SW5 gab es bei Backendbestellungen je eine Spalte für Artikelnummer und eine für Artikelname, Preis, Steuer, etc. Man konnte die Artikelnummer verwenden, den Artikelnamen, Preis, Steuer etc. bearbeiten und die Bestellung mit den überschriebenen Daten anlegen. Damit war alles geregelt und konnte sauber an Kunden, Lager, etc. übergeben werden.
Diese weitere Spalte bei den Backend Bestellungen fehlt in SW6. Damit hat man nicht mehr beide Felder zur Verfügung und kann keine Änderungen mehr vornehmen, da die Datenbank dann scheinbar nach einem nichtvorhandenen Eintrag sucht und die Eingabe nicht abgeschlossen werden kann.
Gibt es dafür eine Lösung?
Ebenfalls fehlt in dieser Ebene der Backend Bestellung noch ein Kommentarfeld, z.B. für Kundeninterne Nummern, Export-Angaben, etc… In SW5 gab es dafür die Freitextfelder.
Das Kommentarfeld steht erst im nächsten Schritt zur Verfügung. Um dahin zu gelangen, muss man die Bestellung speichern, woraufhin jedoch schon die Bestellbestätigung versendet wird. Auf der man eben gern noch ein paar Angaben gemacht hätte, bevor sie zum Kunden gesendet wird.
Gibt es dafür eine Lösung?
There is currently only one field available for SW6 backend orders, with a dropdown menu for searching by article number or article name. Or the empty item line.
In SW5 there was one column for article number and one for article name, price, tax, etc. for backend orders. You could use the article number, edit the article name, price, tax etc. and create the order with the overwritten data. This meant that everything was organised and could be transferred cleanly to customers, warehouses, etc.
This additional column in the backend orders is missing in SW6. This means that you no longer have both fields available and can no longer make any changes, as the database then appears to search for a non-existent entry and the entry cannot be finalised.
Is there a solution for this?
A comment field is also missing at this level of the backend order, e.g. for internal customer numbers, export details, etc... In SW5 there were free text fields for this purpose.
The comment field is only available in the next step. To get there, you have to save the order, after which the order confirmation is sent. You would like to have entered a few more details before it is sent to the customer.
Is there a solution for this?
Aktuell steht bei SW6 Backend Bestellungen nur ein Feld, mit Dropdown Menü für die Suche nach Artikelnummer oder Artikelname zur Verfügung. Oder die leere Positionszeile.
In SW5 gab es bei Backendbestellungen je eine Spalte für Artikelnummer und eine für Artikelname, Preis, Steuer, etc. Man konnte die Artikelnummer verwenden, den Artikelnamen, Preis, Steuer etc. bearbeiten und die Bestellung mit den überschriebenen Daten anlegen. Damit war alles geregelt und konnte sauber an Kunden, Lager, etc. übergeben werden.
Diese weitere Spalte bei den Backend Bestellungen fehlt in SW6. Damit hat man nicht mehr beide Felder zur Verfügung und kann keine Änderungen mehr vornehmen,…
3 votes -
Multi-Change Cover on Variants
(This feedback was formerly created as NEXT-23370)
EN
The multiple changes should definitely make it possible to set the cover image. If an article has many variants that don't differ in appearance, it's a real punishment to go through them all and set the cover images by hand. Not to mention how much time is wasted doing it.
DE
Über die Mehrfachänderungen sollte es unbedingt ermöglicht werden das Coverbild zu setzen. Hat mein ein Artikel mit vielen Varianten, die sich optisch aber nicht weiter unterscheiden ist es eine echte Strafe alle durchzugehen und die Coverbilder von Hand zu setzen. Ganz davon abgesehen wieviel Zeit man dabei verschwendet.
(This feedback was formerly created as NEXT-23370)
EN
The multiple changes should definitely make it possible to set the cover image. If an article has many variants that don't differ in appearance, it's a real punishment to go through them all and set the cover images by hand. Not to mention how much time is wasted doing it.
DE
Über die Mehrfachänderungen sollte es unbedingt ermöglicht werden das Coverbild zu setzen. Hat mein ein Artikel mit vielen Varianten, die sich optisch aber nicht weiter unterscheiden ist es eine echte Strafe alle durchzugehen und die Coverbilder von Hand zu setzen. Ganz…
2 votes -
When I work in the Admin, I don't want to fall back into the overviews again and again, but to the last editing location.
When I'm in the admin and search for something in products, for example, then edit it and go back, I expect to return to the last search result and not end up in the overview.
9 votes -
Selling unit should have more than 3 Decimal places
For example, if you use kilograms as the scale unit and want to enter 21.6 grams, the value is rounded to 0.022, as you can only enter 3 decimal places.
3 votes
- Don't see your idea?