- or
1402 results found
-
Contact Form: Remove salutation Requirement
In most places, the salutation is no longer a requirement, but for some reason, in the contact form, it still is.
If you want to override this via an extension, you have to override not only the template but also the validation as well as the ContactFormRoute since it builds criteria with the salutationId and assumes it to be set.
There doesn't seem to be a good reason to force this requirement. At the very least, there should be a config to make the field optional.1 vote -
Check plugin compatibility before updates in Shopware Native PaaS
Unlike self-hosted Shopware, Shopware Native PaaS doesn’t show whether installed plugins are compatible with the next Shopware version before updating. This forces manual checks — and internal plugins can’t be checked at all. A compatibility check tool in sw-paas or a dashboard would save time and reduce update risks.
2 votes -
Allow application updates without logging all Admin users out
Updating an application in Shopware Native PaaS currently forces all Admin users to log out, interrupting work. Updates should be possible without logging everyone out.
2 votes -
Show only compatible updates in composer outdated
The composer outdated command lists updates even if they aren’t compatible with the current Shopware version. It would be more useful if it only showed updates that can actually be applied.
1 vote -
Show which plugins have updates in the Admin
When the “Extension updates are available” popup appears in the Admin, it’s unclear which plugins need updating. The affected plugins should be listed directly in the Admin.
2 votes -
Allow SSH or SFTP access to applications
Debugging plugins and themes in Shopware Native PaaS would be much easier if developers could connect directly to files and the database via SSH or SFTP.
2 votes -
Provide a GUI for non-technical tasks in Shopware Native PaaS
Not everyone is comfortable using sw-paas commands for everyday tasks. A simple dashboard for creating apps, cloning environments, etc would make Shopware Native PaaS easier to use for less technical users.
2 votes -
Shorten and simplify the sw-paas build history display
The build history in sw-paas grows very long, making it hard to find the latest entry. By default, show only the most recent few builds with an option to expand the full history. Clear formatting and a summary line like “Latest build: SUCCESS at 14:35” would make it much easier to read.
2 votes -
Command to fully clone an environment in sw-paas
Setting up a new staging or testing environment in Shopware Native PaaS is slow because everything has to be reinstalled and reconfigured manually. A single sw-paas command could copy the database, settings, and plugins from an existing environment in one step, saving significant time.
2 votes -
Make it easy to hide deleted apps in sw-paas
Right now, the sw-paas list shows apps that have already been deleted. This clutters the view and makes it harder to find what’s actually active. It would be great if deleted apps were either hidden or clearly marked so they’re easy to ignore.
2 votes -
Make first- and last name optional for company accounts
First- and last name should be optional if setting up a new customer entry through the administration or by using the register form IF it is a company account.
25 votes -
Zahlungsart ändern
Die Zahlungsart sollte man nach dem Kauf ändern können. Es passiert oft, dass eine Zahlung fehlschlägt (über Amazon Pay oder PayPal) oder die Zahlung abgebrochen wird und der Kunde trotzdem die Ware möchte.
Momentan kann man leider nicht die Zahlungsart auf "Kauf auf Rechnung" ändern. Auf den Rechnungen steht dann die falsche Zahlungsart drauf.
Außerdem sollte man die vorausgewählte Zahlungsart der Kunden wieder ändern können. Mit 6.7.x ist diese Funktion entfernt worden.
ENG: The payment method should be changeable after a purchase.
It often happens that a payment fails (for example via Amazon Pay or PayPal) or is cancelled, but the customer still wants to receive the goods.At the moment, it’s unfortunately not possible to change the payment method to “Invoice purchase”. As a result, the wrong payment method is shown on the invoices.
In addition, it should be possible to change the preselected payment method for customers again.
This function was removed with version 6.7.x.Die Zahlungsart sollte man nach dem Kauf ändern können. Es passiert oft, dass eine Zahlung fehlschlägt (über Amazon Pay oder PayPal) oder die Zahlung abgebrochen wird und der Kunde trotzdem die Ware möchte.
Momentan kann man leider nicht die Zahlungsart auf "Kauf auf Rechnung" ändern. Auf den Rechnungen steht dann die falsche Zahlungsart drauf.
Außerdem sollte man die vorausgewählte Zahlungsart der Kunden wieder ändern können. Mit 6.7.x ist diese Funktion entfernt worden.
ENG: The payment method should be changeable after a purchase.
It often happens that a payment fails (for example via Amazon Pay or PayPal) or is cancelled, but…1 vote -
Add newsletter subscription checkbox on account registration
Add the ability to activate newsletter subscribe checkbox on the account registration (/account/login and /checkout/register). So a switch in the admin settings (probably Log-in & sign-up or Newsletter), when it's turned on, a checkbox in the registration pages appear to subscribe for the newsletter, just above the CTA.
6 votes -
Image keyword assistant for logos
The image keyword assistant should be able to recognize well-known logos, not just objects.
For example, when you upload the Shopware logo, only “Logo” appears as the alt text. When you upload Facebook logo, “Symbol, sign, cross” appears, which isn't really accurate, and nothing appears at all for Instagram logo.
1 vote -
Show "Already Subscribed" on Product Page (prevent duplicate subscriptions)
Display a clear and unobtrusive notice on the product detail page when a logged-in customer already has an active subscription for this product (incl. variant match) to prevent accidental duplicate subscriptions/purchases and reduce support friction.
1 vote -
Mail Templates - Show Order Employee Details
It should be possible to show the first and last name of the order employee in mail templates - just like order confirmation.
4 votes -
Add a "budget functionality" to the B2B Components
The permission management of the B2B Components does not properly fill out the function of managing budgets for each B2B Components user.
Someone needs to keep track on how much a customer has bought and if his/her budget is spent.
They also need to know how high the budget is with no indication of that being given via our B2B Components.I good way to solve this would be to build a budget functionality as in the B2B Suite.
That would make it easier to keep track of the budget and it would reduce the amount of controlling.12 votes -
Unstable Behavior of the Rich Text Editor in Content Modules
Background:
As a team that works extensively with Shopware’s CMS and builds sophisticated pages via Shopping Experiences, we’ve repeatedly encountered critical usability issues with the built-in rich text editor used in content modules and custom fields.Problem:
The current text editor behaves inconsistently and creates significant friction in content workflows:It frequently injects arbitrary CSS classes into the HTML output without user input.
There is no easy way to reset text color back to the default.
When applying formatting such as bold, it sometimes adds font color tags even though no color change is intended or visible.
Bullet points are difficult to handle correctly — indentation from the left margin is often broken, and formatting differs inconsistently between modules or contexts.
These bugs and inconsistencies make it unnecessarily difficult to edit and style text, especially for more complex layouts.
Wish / Recommendation:
We would like to see a more robust and predictable editor with the following improvements:Clean and controlled HTML output without injected inline styles or classes.
A reset function for colors and formatting.
Standardized and reliable bullet point behavior across modules.
Generally more stability and polish, especially for professional users managing large-scale CMS layouts.
Background:
As a team that works extensively with Shopware’s CMS and builds sophisticated pages via Shopping Experiences, we’ve repeatedly encountered critical usability issues with the built-in rich text editor used in content modules and custom fields.Problem:
The current text editor behaves inconsistently and creates significant friction in content workflows:It frequently injects arbitrary CSS classes into the HTML output without user input.
There is no easy way to reset text color back to the default.
When applying formatting such as bold, it sometimes adds font color tags even though no color change is intended or visible.
Bullet points are…
2 votes -
Add hreflang support across multiple sales channels
Currently hreflang only applies to different domains within one sales channel. It would be useful to be able to define other languages for hreflang tags across multiple sales channels (i.e. separate sales channels for EU and US, linking to each other)
6 votes -
CMS Extension: Allow custom form to be used for newsletter sign-up
Currently, a custom form provided by the CMS extension can only be used to have a customer send a request to a predefined e-mail address. The ability to also use a custom form for newsletter registration would allow the shop owner to customize the layout or add some basic things, i.e. their own mandatory terms & conditions checkboxes.
3 votes
- Don't see your idea?