- or
No existing idea results
- ~ No ideas found ~
1339 results found
-
Shopware Services in the Admin
Shopware Services – cloud-based extensions that deliver new features quickly and flexibly, and can be activated directly in the Admin.
Help us improve it by sharing your feedback, ideas, or suggestions how we can improve the Admin interface for Shopware Services, what's missing or what you would like to see.
1 vote -
Rulebuiler condition which detects the change of payment method
Condition in the rulebuiler which determines the (non-balanced) change of payment method.
Something like: Used payment method was > Incoice > is now > prepayment
For example, in the flow builder you could influence the mails that are sent when the status changes, so that a distinction is made between manual switching (by the admin) or automated switching (by payment integrations) and the payment method change by the customer in the frontend.
Since the order also reaches the status “canceled” when the customer changes the payment method in the frontend, these mails could be prevented here, as they can be confusing.
Condition in the rulebuiler which determines the (non-balanced) change of payment method.
Something like: Used payment method was > Incoice > is now > prepayment
For example, in the flow builder you could influence the mails that are sent when the status changes, so that a distinction is made between manual switching (by the admin) or automated switching (by payment integrations) and the payment method change by the customer in the frontend.
Since the order also reaches the status “canceled” when the customer changes the payment method in the frontend, these mails could be prevented here, as they can be…
2 votes -
Benutzerdefinierter Dokumenttyp / Custom document type
DE
Anlegen von benutzerdefiniertem Dokumenttyp. Nicht jeder Shopbetreiber nutzt eine externe WaWi bzw Shopware 6 sollte die Standardfunktionen bieten, um auch ohne externe Software auszukommen. Wichtig wäre es, über das Backend mindestens noch 1 oder 2 eigene Dokumententypen wie zB Auftragsbestätigung oder Angebot unter "Dokumente" anlegen zu können. Derzeit kann nur ein vorhandenes durch ein eigenes ersetzt werden, was aber nicht das Problem löst.EN
Creating a custom document type. Not every shop operator uses an external ERP system or Shopware 6 should offer the standard functions to get by without external software. It would be important to be able to create at least 1 or 2 of your own document types via the backend, such as order confirmation or offer under "Documents". Currently, you can only replace an existing one with your own, but that does not solve the problem.DE
Anlegen von benutzerdefiniertem Dokumenttyp. Nicht jeder Shopbetreiber nutzt eine externe WaWi bzw Shopware 6 sollte die Standardfunktionen bieten, um auch ohne externe Software auszukommen. Wichtig wäre es, über das Backend mindestens noch 1 oder 2 eigene Dokumententypen wie zB Auftragsbestätigung oder Angebot unter "Dokumente" anlegen zu können. Derzeit kann nur ein vorhandenes durch ein eigenes ersetzt werden, was aber nicht das Problem löst.EN
Creating a custom document type. Not every shop operator uses an external ERP system or Shopware 6 should offer the standard functions to get by without external software. It would be important to be able…8 votes -
Line item rule amount of products within a dynamic product group for discounts
Currently it is not possible to add a rule to a discount that checks the amount of products per lineitem and additonal conditions.
e. g.
You want to ensure that only products with a tag and an amount of 10/above is in the cart. This has to be checked by lineitem, so products and variants that include the TAG but have only an amount of 1 in the cart do not apply to the discount.
if you use the condition "amount of products" it is related to all itemlines of the cart.
If you choose "Item quantity" it matches, but you have to add all related products manually in the condition of the rule.
It would help if there is a condition "item quantity of products within a dynamic prouduct group", to achieve the possibility to count items by line and use the discount per lineitem instead of the complete cart.
When a position has only 1 item an the TAG, the discount does not apply.
Currently it is not possible to add a rule to a discount that checks the amount of products per lineitem and additonal conditions.
e. g.
You want to ensure that only products with a tag and an amount of 10/above is in the cart. This has to be checked by lineitem, so products and variants that include the TAG but have only an amount of 1 in the cart do not apply to the discount.
if you use the condition "amount of products" it is related to all itemlines of the cart.
If you choose "Item quantity" it matches, but…
1 vote -
external order id / externe Auftragsnummer
EN:
In B2B, it is common practice for the purchaser to provide an external order number to ensure matching within customer accounting. Therefore, an optional field with “external order number” should be possible in the shop when placing the order (can be switched on/off in admin and per channel). This should be displayed in the order overview for the customer when logged in.DE:
Im B2B ist es üblich eine externe Auftragsnummer seitens des Bestellers zu übergeben, um das matchen innerhalb der Kundenbuchhaltung zu gewährleisten. Daher sollte ein optionales Feld mit "externe Auftragsnummer" im Shop bei der Bestellabgabe möglich sein (im admin ein/ausschaltbar und das pro Channel). Dieses sollte für den Kunden einloggt in der Bestellübersicht angezeigt werden.EN:
In B2B, it is common practice for the purchaser to provide an external order number to ensure matching within customer accounting. Therefore, an optional field with “external order number” should be possible in the shop when placing the order (can be switched on/off in admin and per channel). This should be displayed in the order overview for the customer when logged in.DE:
Im B2B ist es üblich eine externe Auftragsnummer seitens des Bestellers zu übergeben, um das matchen innerhalb der Kundenbuchhaltung zu gewährleisten. Daher sollte ein optionales Feld mit "externe Auftragsnummer" im Shop bei der Bestellabgabe möglich sein…11 votes -
Automatically include vouchers in returns management
Currently, if the vouchers are not taken into account when an order is placed, if an item is returned via Return Management.
Although the amount of the return can be adjusted and the value including the voucher is suggested, it is not applied automatically.
An option for automation would be useful here.3 votes -
Cloud: Better debugging in case of error
There is no way for a SaaS user to find error in theme or extensions, that are in use on the SaaS environment. It would be helpful to increase the gainable information while debugging.
3 votes -
Drafting: Create a draft state of your changes
Problem:
Users cannot currently create and manage a comprehensive draft state for changes across their storefronts. This makes it difficult to plan, test, or iterate on updates without affecting the live environment. As a result, merchants may delay changes, work in risky live environments, or rely on inefficient workarounds — increasing the likelihood of errors and reducing agility in campaign or content management.Solution:
Create and manage a draft state for all kinds of changes in Shopware before publishing them live. This allows you to bundle multiple updates, such as content, design, and promotions, into a draft, enabling safe workflows and reviews without affecting your live store. By facilitating collaboration and approval workflows, this feature improves control, reduces errors, and streamlines shop updates.Problem:
Users cannot currently create and manage a comprehensive draft state for changes across their storefronts. This makes it difficult to plan, test, or iterate on updates without affecting the live environment. As a result, merchants may delay changes, work in risky live environments, or rely on inefficient workarounds — increasing the likelihood of errors and reducing agility in campaign or content management.Solution:
Create and manage a draft state for all kinds of changes in Shopware before publishing them live. This allows you to bundle multiple updates, such as content, design, and promotions, into a draft, enabling safe workflows…2 votes -
Better filter options within e.g. customer and order overview
If you work with the customer and order overview on a daily basis, this quickly leads to frustration.
For example, the number per page cannot be set and is far too low. This should be 100 or 200. Otherwise the unnecessary effort is too high and the work quickly becomes frustrating.
Also, the filter or listing is often reset when changing pages. This also takes an incredible amount of time.
We would like to see better handling here.
2 votes -
Further evaluation of the customer search
There should be an evaluation of customer search queries within the Shopware search.
This means that the search can be adapted to customers in ever greater detail. This is requested time and again by large customers.
2 votes -
B2B: Add option to product detail page like cost center, project, etc.
It would be great, if B2B store would have the option to add selection or comment fields on product detail pages.
This could be used, so that buyers can directly select the cost center or the project, which the product is bought for. This information could then be automatically integrated into the invoices, saving a lot of manually effort for the finance department.
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 -
Unlinking properties should be bound to a detailed privilege.
It is currently not possible to delete properties via the small X (see screenshot) using a detailed privilege.
The deletion is currently bound to the technical privilege “product.deleter”, which cannot be found in the admin and can only be given via API/DB or the general deletion permission for products.
Using "Configure properties", you can also delete the properties via a detailed privilege, but it should also be possible to simply delete properties using the small X.
1 vote -
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.
15 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 -
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 -
compact overview on the returnpage
English:
I noticed that on the return page, the info fields are currently stacked vertically, while the shipping and payment details sit at the very bottom in a separate box. This forces users to search for key information or scroll extensively to see everything grouped together.Suggestion:
1. Place the summary and status info side by side – important return informations and shipping & payment status visible at a glance.
2. Put the product table directly below – immediately shows which items can be returned and any relevant details.
3. Use page space compactly and create a clear information hierarchy – arrange all key elements logically and efficiently. (conceptpicture attached)
Deutsch:
Mir ist aufgefallen, dass auf der Retourenseite die Informationsfelder momentan untereinander stehen, während Versand- und Zahlungsinformationen ganz unten in einem separaten Kästchen liegen. Das führt dazu, dass man nach wichtigen Details suchen oder viel mit der Maus scrollen muss, um alle Infos gebündelt zu sehen.Vorschlag:
1. Zusammenfassung und Statusinfos nebeneinander anordnen – wichtige Rücksendeinformationen sowie Versand- und Zahlungsstatus sofort im Blick.
2. Direkt darunter die Produktübersicht platzieren – zeigt auf einen Blick, welche Artikel retourniert werden können und alle relevanten Details.
3. Seitenplatz kompakt nutzen und klare Informationsstruktur schaffen – alle wichtigen Elemente logisch und platzsparend anordnen. (conceptpicture attached)English:
I noticed that on the return page, the info fields are currently stacked vertically, while the shipping and payment details sit at the very bottom in a separate box. This forces users to search for key information or scroll extensively to see everything grouped together.Suggestion:
1. Place the summary and status info side by side – important return informations and shipping & payment status visible at a glance.
2. Put the product table directly below – immediately shows which items can be returned and any relevant details.
3. Use page space compactly and create a clear information hierarchy…1 vote
- Don't see your idea?