- or
1269 results found
-
Migration: Automatic placeholders for missing values
Customer migrations are tedious and involve a lot of work, as data records are often not transferred to Shopware 6 because they are missing from Shopware 5.
For example, if the salutation of a customer is not filled in Shopware 5, but the field has become a mandatory field in Shopware 6. Or the first name.
To make migrations much easier, the migration wizard should store a meaningful placeholder in such cases so that the data is transferred correctly.
Within Shopware 6, you can then search for these placeholders and adjust the entries. This takes away the frustration that many customers experience during a migration.
Customer migrations are tedious and involve a lot of work, as data records are often not transferred to Shopware 6 because they are missing from Shopware 5.
For example, if the salutation of a customer is not filled in Shopware 5, but the field has become a mandatory field in Shopware 6. Or the first name.
To make migrations much easier, the migration wizard should store a meaningful placeholder in such cases so that the data is transferred correctly.
Within Shopware 6, you can then search for these placeholders and adjust the entries. This takes away the frustration that many…
2 votes -
New Trigger for the Flow Builder: Customer Login
Currently, the Flow Builder does not offer a dedicated trigger for logging into a customer account, only in connection with the checkout process. This significantly limits automation possibilities.
Proposed Enhancement:
A new "Login" trigger that activates whenever a customer logs into their account – independently of the checkout process.Possible Use Cases:
Automatic tag assignment based on login frequency.
Customer group changes for logged-in users, e.g., granting access to exclusive content or discounts.
Automated email dispatch, e.g., a welcome back message after a long period of inactivity or targeted marketing campaigns.
2 votes -
Improve UI and Logic for Postal Code Validation and Advanced Validation Rules
he current UI for the Postal Code settings is not intuitive and may confuse users. The "Advanced Validation Rules" option can only be enabled after enabling "Postal Code Validation," but there is no clear indication that these options are linked. Additionally, there is no visibility into which validation rules apply when enabling "Postal Code Validation."
Problems Identified:
Lack of clear dependency between "Postal Code Validation" and "Advanced Validation Rules."
No information on which postal code validation rules are applied by default.
Unclear if "Postal Code Required" influences the validation settings.
2 votes -
Optimierung der Dropdown Menüs (z.b. Verkaufskanal -> Auswahl Länder)
The selection of values within the dropdown menus in Shopware Admin is very error-prone.
For example, if additional countries are to be added or removed within the sales channel, the menu only ever shows 25 entries and each entry has to be clicked individually. This is very error-prone and you should also be able to select/deselect “all” entries.
This would make it easier for large customers to use the Admin, as the problem occurs at various points in the Admin.
2 votes -
Vermeidung von Fehlern bei PayPal-Teilrückerstattungen
Die in Shopware eingebaute PayPal-API ermöglicht Rückerstattungen mit einem Klick. Leider passieren bei Teilrückerstattungen in der Hektik des Kundenservice-Alltags oft Fehler – statt z. B. 20 € Nachlass wird aus Versehen der Gesamtbetrag (z. B.100 €) erstattet. Das passiert jedem MItarbeiter mindestens einmal im Monat, weil im Feld „Betrag“ standardmäßig der gesamte Betrag voreingetragen ist und man leicht vergisst, ihn anzupassen.
Mögliche Lösungen:
1) Das Feld "Betrag" ist leer, und der Betrag muss aktiv eingetragen werden.
2) Der Betrag wird rot markiert.
2) Ein Warnhinweis erscheint: „Möchtest du wirklich den vollen Betrag erstatten?“
4) Neben dem blauen Button "Rückerstattung" wird ein zweiter, farblich weniger gesättigter Button "Teilrückerstattung" platziert
Kann Shopware oder PayPal hier etwas tun oder gibt es dazu bereits eine Lösung?
Die in Shopware eingebaute PayPal-API ermöglicht Rückerstattungen mit einem Klick. Leider passieren bei Teilrückerstattungen in der Hektik des Kundenservice-Alltags oft Fehler – statt z. B. 20 € Nachlass wird aus Versehen der Gesamtbetrag (z. B.100 €) erstattet. Das passiert jedem MItarbeiter mindestens einmal im Monat, weil im Feld „Betrag“ standardmäßig der gesamte Betrag voreingetragen ist und man leicht vergisst, ihn anzupassen.
Mögliche Lösungen:
1) Das Feld "Betrag" ist leer, und der Betrag muss aktiv eingetragen werden.
2) Der Betrag wird rot markiert.
2) Ein Warnhinweis erscheint: „Möchtest du wirklich den vollen Betrag erstatten?“
4) Neben dem blauen Button "Rückerstattung" wird…
2 votes -
Shopping experiences: "Topseller" sort for product-slider
There are different values for sorting within the configuration of the product slider. The ‘Topseller’ selection is missing at this point, which would result in a further and useful customisation of the configuration. This would make sense at this point and is requested by customers.
7 votes -
B2B: Product catalogue restriction
B2B users with the specific rights should be able to define, which roles are allowed to see which products in the storefront. Not all products are necessarily needed for all roles.
Only seeing the relevant product reduces the effort of finding the desired product.
2 votes -
replace Tiny Slider as the default slider
The current default slider integration with tinyslider seems not be maintained anymore.
It would be good to switch to a maintained slider lib again as tinyslider has a multitude of issues, espacially with accessibilty and it is not really customizable.4 votes -
SAML/OAuth SSO support
In discussions with large and important customers, SAML/OAuth SSO support is repeatedly asked for, as this is sometimes required/prescribed in large companies or corperations.
In view of large companies and corporations, there should be an implementation here.
2 votes -
Differentiation between manufacturer and brand
Currently you can only specify the manufacturer of a product. However, the manufacturer is not automatically the brand of the product, so it would be nice if there was an extra field here that also allows you to specify the brand.
1 vote -
Long category names go beyond the grid.
If the category names are slightly longer, they can no longer be displayed in the fixed grid, and a scrollbar is created. As a result, you always have to scroll first to access the three dots.
3 votes -
Ability to duplicate shipping methods
For shipping methods with complex price matrix structures it would be helpful to have the ability to duplicate the shipping methods.
Für Versandmethoden mit komplexen Preismatrix-Strukturen wäre es hilfreich, die Möglichkeit zu haben, die Versandmethoden zu duplizieren.
3 votes -
Overview pages - Filters: Add a "Select All" button
In our Admin we have several overview pages to check the products, orders and customers. These pages offer filtering based on different information. Currently you can only select single values in the filter.
For instance if you want to create filter, that only shows the products assigned to 24 of your 25 Saleschannels, you will need to select all 24 salechannels individually.
It would be more convenient, if we had a "Select All" button, where I can afterwards deselect the one Saleschannel, which I do not want in the results.
There are multiple filter options where this could be very useful. Here are just some further examples:
Categories, Manufacturers, Tags, Customer group, Billing & Shipping country and so on.In our Admin we have several overview pages to check the products, orders and customers. These pages offer filtering based on different information. Currently you can only select single values in the filter.
For instance if you want to create filter, that only shows the products assigned to 24 of your 25 Saleschannels, you will need to select all 24 salechannels individually.
It would be more convenient, if we had a "Select All" button, where I can afterwards deselect the one Saleschannel, which I do not want in the results.
There are multiple filter options where this could be very…
2 votes -
Promotions: Calculate discount based on other price fields (e.g. listprice, custom fields)
Currently you can only calculate discounts in promotions based on the selling price. It is often desired though, to not use the current selling price but the RRP for instance.
Example:
Product Price: 79.99
RRP: 100€
Desired discount: 10% of RRP (10€)Would be nice, if you can select any price field, that is available in your shop.
2 votes -
Prefill register form with inferred and previously filled values
For a smoother checkout experience, it would be great to pre-fill some of the fields on the registration form.
The country field could be inferred from the context language.
When selecting an alternate shipping address, most or all fields can be pre-filled with values previously entered as the billing address.This feature should be optional and can be toggled via administration.
2 votes -
Improvements of the Order creation in the administration.
One of our customers with a relatively large number of customers and orders has some problems with creating orders in the administration. Here are a few suggestions:
The search for customers takes a very long time with several customers (More than 500k customers in the system). After selecting a customer, the grid seems to reload which may be superfluous?
You could take some pain here if the way to create an order via the customer module would select the customer directly, but here you have to search for the customer again, which makes no sense.If a product is to be added to the order, it is hardly possible with somewhat longer product names with variants because the column is too small. This should generally be fixed, as it is the same component as for orders. This could be a good quick fix.
One of our customers with a relatively large number of customers and orders has some problems with creating orders in the administration. Here are a few suggestions:
The search for customers takes a very long time with several customers (More than 500k customers in the system). After selecting a customer, the grid seems to reload which may be superfluous?
You could take some pain here if the way to create an order via the customer module would select the customer directly, but here you have to search for the customer again, which makes no sense.If a product is to…
2 votes -
Bulk edit product cover image
Currently you can bulk edit product media, so you can add images for multiple products at once. However this does not effect / set the cover image. Therefore it would be great if there is an option in the bulk edit to set an image as cover image for multiple products at once.
10 votes -
Links and downloads input for products
In sw5 there was a tab where you could enter links and downloads.
Would be nice to have this as standard in SW6.It would also be nice for the function to take over this maintained data when migrating from SW5 to SW6.
14 votes -
Searching and editing variant properties
EN
A store with many variant-forming properties cannot search efficiently for the required property set. For example, if I have the property black several times and now want to add a variant in white, I get all such properties displayed by searching for “black”, but the matching “white” is missing. I then have to scroll through step by step and check when a property set has multiple properties selected. Even with more than 10 pages, this becomes a tedious task, as I can neither enter “Go to page 26” nor search specifically for the name of the set. An improved search or selection would significantly improve handling.DE
Ein Shop mit vielen variantenbildenden Eigenschaften kann das benötigte Eigenschaften-Set nicht effizient suchen. Wenn ich zum Beispiel mehrmals die Eigenschaft schwarz habe und nun eine Variante in weiß hinzufügen möchte, bekomme ich durch die Suche nach "schwarz" alle solchen Eigenschaften angezeigt, aber das passende "weiß" fehlt. Dafür muss ich dann Schritt für Schritt durchblättern und prüfen, wann ein Eigenschafts-Set mehrere Eigenschaften ausgewählt hat. Bereits bei mehr als 10 Seiten wird das eine langwierige Sache, da ich weder eingeben kann "Gehe zu Seite 26" noch gezielt nach dem Namen des Set suchen kann. Eine verbesserte Suche oder Auswahl würde das Handling bedeutend verbessern.EN
A store with many variant-forming properties cannot search efficiently for the required property set. For example, if I have the property black several times and now want to add a variant in white, I get all such properties displayed by searching for “black”, but the matching “white” is missing. I then have to scroll through step by step and check when a property set has multiple properties selected. Even with more than 10 pages, this becomes a tedious task, as I can neither enter “Go to page 26” nor search specifically for the name of the set. An improved…3 votes -
Enable Backend-Search for Custom Fields values
At the moment it is not possible to search for values within custom fields with the backend search. Please add this function to the backend search. We often have other numbers or UUIDs from our ERP or PIM system which we automatically store in custom fields. We often have to search for these values in the backend to synchronize data or change them manually.
2 votes
- Don't see your idea?