- or
No existing idea results
- ~ No ideas found ~
1498 results found
-
Customers also bought
There used to be the ‘Customers also bought’ function in Shopware 5, which automatically displayed products that were bought by customers who also bought the product that was called up.
There is already the option to display such products via cross-selling, but not automatically, which would be a helpful improvement.
9 votes -
Adjustment of address format for countries as a bulk adjustment
Adjusting the address format for countries as a bulk adjustment would be an improvement, as this currently has to be done individually for each country and cannot be controlled centrally for all countries if, for example, you simply want to add the salutation.
3 votes -
Different texts for error messages regarding promotion codes provide clearer instructions to the buyer. Currently, only one text is possible
We want different texts for error messages with a promotion code showing our customers why they can not use this code - for example 150 Euros + ... then 5% discount - 100 euro in the shipping card - text " buy for 50 more euros to get the 5%" ... something like that.
2 votes -
Possibility to assign multiple custom products templates per product
As a merchant I want to assign multiple custom product templates per product.
1 vote -
Don't use the first page of a paginated sequence as the canonical page
Use URLs correctly:
- Give each page a unique URL. For example, include a ?page=n query parameter, as URLs in a paginated sequence are treated as separate pages by Google.
- Don't use the first page of a paginated sequence as the canonical page. Instead, give each page its own canonical URL.
Currently, the canonical page in categories is always the first page. Without pagination URLs.
According to Google, the canonical URL should be set up including pagination.
Please correct this.
2 votes -
Force customers to assign a new password after creation via the administration
There should be an option to force customers - that have been set up through the administration - to change their password after the initial login.
3 votes -
Default Theme: Footer and Category Overview Background Color Not Customizable
As a shop owner,
I want to configure the background colors of the footer and category overview within the default theme settings,
so that I can easily create a consistent design for dark or light themed shops without custom CSS overrides.When using the Shopware Default Theme, the background color of the footer and the category overview cannot be adjusted through the theme configuration.
This limitation causes issues for shop owners who want to build a dark-themed store, since the default bright background colors do not match and result in a visually inconsistent and unprofessional appearance.
Actual Behavior:
These areas cannot be adjusted via the theme settings.
Only by overriding CSS/SCSS manually can the styles be changed.
Expected behaviour
The footer background color can be customized via the theme configuration.
The category overview background color can be customized via the theme configuration.As a shop owner,
I want to configure the background colors of the footer and category overview within the default theme settings,
so that I can easily create a consistent design for dark or light themed shops without custom CSS overrides.When using the Shopware Default Theme, the background color of the footer and the category overview cannot be adjusted through the theme configuration.
This limitation causes issues for shop owners who want to build a dark-themed store, since the default bright background colors do not match and result in a visually inconsistent and unprofessional appearance.
Actual Behavior:
These areas…
3 votes -
ZIP code validation only takes effect once all other mandatory fields have been filled in during checkout.
While testing the checkout process, I noticed inconsistent behavior when validating the postal code.
Steps to reproduce:
Go to checkout.
Select country.
Enter an invalid value in the “Postal code” field (e.g., asdasd or asd123).
Leave at least one other required field blank.
Click “Continue.”
Result:
All required fields are marked as incorrect except for country and zip code.
The zip code is not displayed as invalid in this state.Further behavior:
As soon as the previously missing required field is filled in, the zip code validation takes effect retrospectively and the field is then marked as incorrect.Expected behavior:
The ZIP code should be validated immediately as soon as an invalid format is entered, regardless of the status of other required fields or alternatively, a uniform validation behavior should be applied to all required fields.Note:
Even though this case is likely to occur rarely, the behavior appears inconsistent to users and could lead to confusion.While testing the checkout process, I noticed inconsistent behavior when validating the postal code.
Steps to reproduce:
Go to checkout.
Select country.
Enter an invalid value in the “Postal code” field (e.g., asdasd or asd123).
Leave at least one other required field blank.
Click “Continue.”
Result:
All required fields are marked as incorrect except for country and zip code.
The zip code is not displayed as invalid in this state.Further behavior:
As soon as the previously missing required field is filled in, the zip code validation takes effect retrospectively and the field is then marked as incorrect.Expected behavior:…
2 votes -
A kind of mini GitLab/GitHub for plugins
Shopware flies the flag for open source and community involvement in further development, bug fixing, etc.
You also offer a store with extensions from others, where these can be purchased. However, this is where the idea of contributing ends. The plugin is a state secret until it is purchased and can be imported using
composer, at which point the code becomes known.In order to request changes to plugins or report bugs, you have to create a ticket in your account, in which you then try to insert code for which the editor is not at all suitable. Everything is complicated and cumbersome.
Idea: provide a kind of mini Gitlab/Github for plugins, where the ‘customers’ of the plugins themselves can make pull requests for plugins, so that plugin manufacturers and contributing developers can quickly make fixes or feature requests. This could certainly be restricted so that you only see plugins that you have purchased.
Shopware flies the flag for open source and community involvement in further development, bug fixing, etc.
You also offer a store with extensions from others, where these can be purchased. However, this is where the idea of contributing ends. The plugin is a state secret until it is purchased and can be imported using
composer, at which point the code becomes known.In order to request changes to plugins or report bugs, you have to create a ticket in your account, in which you then try to insert code for which the editor is not at all suitable. Everything…
3 votes -
Add Custom Text Field per Cart Line Item (B2B Commission Feature)
Would be great to have a feature within the Shopware 6 - B2B Components that allows B2B customers to add a custom text field for each cart line item (like a Commission). This enhancement aims to improve flexibility and support B2B customer-specific internal processes during order creation.
In many B2B scenarios, customers need to add additional information for each product in their shopping cart — for example, internal article numbers, project references, delivery notes, or other customer-specific comments. Currently, there is no native option to capture such information directly at the line-item level.
3 votes -
Generate ZUGFeRD e-invoices via Bulk Edit
It is currently not possible to create an e-invoice using bulk edit.
You can only send the e-invoice, but not generate it directly using bulk edit.1 vote -
Option to automatically show new reviews
It would be nice to have an option for reviews to be shown automatically. Currently you have to enable this individually for each review.
11 votes -
Add FlowBuilder Trigger for when Customers edit their adress information
A few shops let their customers rent products and when these customers move to another place the shop owner wants to be informed
5 votes -
Custom forms: Easy reply to the customer
There is already this feedback / feature request: https://feedback.shopware.com/forums/942607-shopware-6-product-feedback-ideas/suggestions/50220672-add-cc-bcc-and-reply-to-features-to-the-mail-func.
In addition it should be possible to define an email adress, that custom forms (or default forms) can reply to.
Of course one can add an email field in the form fields. But this cannot be used to open the form mail and click on reply to "customer email"
2 votes -
Image keyword assistant should let you set store-wide keywords or prompts
That way, issues like https://github.com/shopware/shopware/issues/13175 could be prevented by setting keywords that tell the AI to focus on certain groups of products and/or exclude certain product categories that will never appear in the store.
3 votes -
Make font size configurable in document footers
Make font size configurable in document footers via option in document settings.
1 vote -
Recipient "Employee" should be available inside the flow builder
Currently the recipient employee is not generally available inside the flow builder. As a new actor within the B2B suite this role should be added. So we can freely use the flow builder with the B2B suite.
The specific employee flows seem hardcoded within the B2B suite as illustrated in my screenshot. Employees do receive the correct mail, but it's not configurable/visible in the flow builder.
2 votes -
Handling growing order numbers
With growing order numbers, the performance of loading these orders decreases.
It would be great if this decreasing of loading performance could be avoided, e.g. by loading older orders than X only on request.2 votes -
Image keyword assistant webp support
The image keyword assistant should be able to process the default webp format.
3 votes -
Delivery period display in the shopping basket / Lieferzeitraum-Anzeige Warenkorb
The delivery period display makes no sense if the system cannot calculate the weekends and perhaps also understand the maximum time up to which orders can be processed immediately.
Our GLS parcel service takes everything that we receive as an order by 10 a.m. on the same day and delivers it the next WORKING DAY or after a maximum of two days. So it's a great advertising factor for us to state the delivery time as 1-2 working days.
But if customers then see in the delivery period: 24-25 May (that's Saturday and Sunday) then it confuses them or, in the worst case, annoys them.
If I set the time more broadly, the advertising effect fizzles out...
Die Lieferzeitraum-Anzeige macht keinen Sinn, wenn das System nicht die Wochenenden rausrechnen kann und vielleicht auch versteht, bis zu welcher Uhrzeit Bestellungen maximal gleich bearbeitet werden können.
Unser GLS Paketdienst nimmt alles, was am selben Tag bis 10 Uhr bei uns als Bestellung eingeht noch mit und stellt am nächsten WERKTAG zu bzw. maximal nach zwei Tagen. So gesehen ein toller Werbefaktor für uns, die Lieferzeit mit 1-2 Werktagen anzugeben.
Wenn die Kunden dann aber im Lieferzeitraum sehen: 24.-25.05. (das ist Samstag und Sonntag) dann verwirrt es sie, oder im schlimmsten Fall verärgert es sie..
Wenn ich die Zeit großflächiger einstelle, verpufft der Werbeeffekt..
The delivery period display makes no sense if the system cannot calculate the weekends and perhaps also understand the maximum time up to which orders can be processed immediately.
Our GLS parcel service takes everything that we receive as an order by 10 a.m. on the same day and delivers it the next WORKING DAY or after a maximum of two days. So it's a great advertising factor for us to state the delivery time as 1-2 working days.
But if customers then see in the delivery period: 24-25 May (that's Saturday and Sunday) then it confuses them or, in…
6 votes
- Don't see your idea?