- or
102 results found
-
Optimization of plugin management and configuration in Shopware 6 Admin
We are having difficulties finding and managing the apps and plugins installed in Shopware 6 within the admin area. Since many standard features from SW5 have been removed and must now be replaced by apps, there is no central overview for these extensions. The apps are spread out across different sections, without a clear indication of which plugin provides which functionality. This leads to issues with managing and identifying extensions.
Note from Shopware Support:
We think it's a very good idea. For many colleagues in support, it is often very difficult to find out which plugin inserts which functions and where these are configured.Main Issues:
Scattered Apps: Apps are spread out across various sections of the admin area (e.g., Marketing, System, Settings), making them difficult to find.
No Clear Function Assignment: After installation, it is often unclear which plugin is responsible for which function. Only after disabling a plugin does it become apparent what it was doing.
Challenges with CMS Plugins: With multiple CMS plugins active at the same time, it’s almost impossible to figure out which plugin is being used in which Shopping Experience without manually testing each one.
Shopify Example:
We find that Shopify has a clear structure where all apps are centrally located under one "Apps" section, with direct access to configuration, making it super easy to manage.Use Cases for Clarification:
1 - Finding an App:
If i want to configure a recently installed plugin. However, it is scattered across the admin area (e.g., partly under Marketing, partly under System), and there is no central overview. The user wastes time searching for the app.Use Case 2 - Unclear Function Assignment:
As a shop owner, i noticed a functionality in our shop (e.g., "Products in saved shopping carts" under Marketing) but does not know whether it’s part of the core system or added by a plugin. Suggestion: Clearly indicate which function is provided by which plugin.Wanted improvements:
Introduce a central "Plugin" section where all installed extensions are listed and can be configured.
Clearly label in the admin area which functions belong to which plugins. Maybe with an Icon and text on hover.
Improve the identification of CMS plugins within Shopping Experiences.
We are having difficulties finding and managing the apps and plugins installed in Shopware 6 within the admin area. Since many standard features from SW5 have been removed and must now be replaced by apps, there is no central overview for these extensions. The apps are spread out across different sections, without a clear indication of which plugin provides which functionality. This leads to issues with managing and identifying extensions.
Note from Shopware Support:
We think it's a very good idea. For many colleagues in support, it is often very difficult to find out which plugin inserts which functions and…3 votes -
"not specified" salutation handling
This is handled rather inconsistently in Shopware. In some but not all places, if you leave out the salutation, Shopware searches the database for the "not_specified" entry that comes with the installation and inserts it if found. If also sometimes inserts it just for display in the Administration if the real salutation reference is null, so you wouldn't even know the real value without looking directly into the database, but again, not always.
Crucially, that "not_specified" entry can be changed and deleted at will, so there's no guaranteed meaning behind it.
Also, sometimes like in the contact form the salutation is randomly required. You can delete it for addresses and the database has a default value of null, but then there is a non-configurable validator that won't let you through the checkout process if no salutation is given. And again, "given" can just mean that you set the "not_specified" salutation, which can have any meaning you assign to it.
This is an intransparent mess and should be changed. The very legality of requiring a salutation is now even in question. Just allow null values for all salutations in the application, it's already allowed in the DB structure, stop enforcing it in random places without a way to turn it off, and make the display name of a "null" salutation translatable via config.
This is handled rather inconsistently in Shopware. In some but not all places, if you leave out the salutation, Shopware searches the database for the "not_specified" entry that comes with the installation and inserts it if found. If also sometimes inserts it just for display in the Administration if the real salutation reference is null, so you wouldn't even know the real value without looking directly into the database, but again, not always.
Crucially, that "not_specified" entry can be changed and deleted at will, so there's no guaranteed meaning behind it.
Also, sometimes like in the contact form the…
1 vote
1451 results found
-
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.
1 vote -
Möglichkeit, die Anrede in allen Formularen zu entfernen
Die Anrede sollte in allen Formularen entfernt werden, wenn man sie ausstellt.
Im Kontaktformular wird sie angezeigt, wenn man die Anrede im Registrierungsformular deaktiviert (Shopware 6.7.1.2).
Formulare sind ohne Anrede einfacher und schneller ausgefüllt. Viele Nutzer sind von der Auswahl der Anrede genervt.
The salutation should be removed in all forms if you display it.
It is displayed in the contact form if you deactivate the salutation in the registration form (Shopware 6.7.1.2).
Forms are easier and quicker to fill out without a salutation. Many users are annoyed by the choice of salutation.
2 votes -
Ensure “Success” build status means the environment is ready
In Shopware Native PaaS, a build from a commit SHA can sometimes show as “Success” even though the environment isn’t actually accessible and returns a 404 error. This causes downtime and confusion. The build process should only mark a build as “Success” once the environment is fully functional.
2 votes -
Exclude Variants From Sitemap If Canonicals Are Used
Please implement an option that allows to exclude variants from sitemap generation. Especially in cases where all variants are using a cononical which points to the main product it would be good to exclude these kind of entries, which all refer to the same product anyway.
3 votes -
Product overview (Admin): Filter by all product settings
The product overview should be filtered for all items that can be added to products. This is important, for example, to pass on graduated prices to other marketplaces.
All product functions should therefore be available.
Examples
- Sale
- Delivery time
- Free shipping
- Visibility
- Weight
and much more.4 votes -
Custom product descriptions per saleschannel
It would be nice to allow inserting a custom product description per saleschannel for products. This way it would be possible to easily adjust the voice of tone and the highlighted information to my target group (ex. B2B & B2C). It could be also relevant for other text fields in the product like the title.
1 vote -
AI generated content for all text fields
It would be helpful to have the option to create a text via AI (as it is possible in shop experiences and product desrciption) would be available to all text fields, including custom fields, when creating/editing a product.
1 vote -
B2B Components: Include divergent mail addresses in search results
Shop owners sometimes report having difficulties finding B2B root accounts when provided with little more than a mail address of an employee in case it is not conforming to the companies' mail structure.
For example:
Our B2B root account is company@example.com.
Our employee's mail address is employee@shopware.com.Since the mail addresses don't match, when searching for employee@shopware.com, we will find no results for customers. This is sometimes the case where entire departments have separate mail addresses like a purchase department.
So the request is to have an option to index employee mail addresses and associate them with the B2B account for search results.
Shop owners sometimes report having difficulties finding B2B root accounts when provided with little more than a mail address of an employee in case it is not conforming to the companies' mail structure.
For example:
Our B2B root account is company@example.com.
Our employee's mail address is employee@shopware.com.Since the mail addresses don't match, when searching for employee@shopware.com, we will find no results for customers. This is sometimes the case where entire departments have separate mail addresses like a purchase department.
So the request is to have an option to index employee mail addresses and associate them…
1 vote -
Social Shopping / Product comparison: Media URL with sales channel domain
EN
We often receive enquiries about how image links in product comparisons or social shopping can be adjusted to use the domain of the exporting sales channel. There were already tickets for this in the old issue tracker: e.g. https://issues.shopware.com/issues/NEXT-17674.However, this ticket was then created last year https://github.com/shopware/shopware/issues/4807, reporting that CDN media were receiving the wrong domain.
Programme request:
Please adjust the URL determination for media so that the handling of media links follows the same pattern as the product links within a product comparison. Of course, it must be possible to resolve the link. CDNs must also be taken into account, whereby the request was also made that it should be possible to resolve the domains per sales channel.According to tests in Shopware 6.7.4.2, the domain from APP_URL is used during export; no adjustment to other sales channels is made. Neither AI nor humans can find any information in the (dev) documentation as to whether and, if so, how it is possible to change this behaviour. If there are already settings options for the media link, it would be necessary to document these clearly and display them in the search.
DE
Es kommt öfter die Nachfrage, wie in Produktvergleichen oder Social Shopping die Bildlinks so angepasst werden können, dass sie die Domäne des exportierenden Verkaufskanals nutzen. Da zu gab es im alten Issuetracker bereits Tickets: z.B. https://issues.shopware.com/issues/NEXT-17674.Jedoch wurde im letzten Jahr dann dieses Ticket erstellt https://github.com/shopware/shopware/issues/4807, worin gemeldet wurde, dass CDN Medien die falsche Domain erhielten.
Programmwunsch:
Bitte die URL Ermittlung für Medien so anpassen, dass die Behandlung von Medienlinks dem gleichen Schema folgt wie die Produktlinks innerhalb eines Produktvergleichs. Natürlich muss der Link aufgelöst werden können. Außerdem berücksichtigt werden müssen naturlich CDNs, wobei hier auch der Wunsch geäußert wurde, dass es ebenfalls möglich sein soll die Domänen pro Verkaufskanal aufzulösen.Gemäß Versuchen in Shopware 6.7.4.2 wird beim Export die Domäne aus der APP_URL verwendet, eine Anpassung an andere Verkaufskanäle erfolgt nicht. Weder KI noch Mensch finden in der (Dev-)Dokumentation Hinweise, ob und wenn ja wie, eine Änderung des Verhaltens möglich ist. Falls es bereits Einstellmöglichkeiten für den Medienlink gibt, wäre es notwendig diese verständlich zu dokumentieren und in der Suche anzuzeigen.
EN
We often receive enquiries about how image links in product comparisons or social shopping can be adjusted to use the domain of the exporting sales channel. There were already tickets for this in the old issue tracker: e.g. https://issues.shopware.com/issues/NEXT-17674.However, this ticket was then created last year https://github.com/shopware/shopware/issues/4807, reporting that CDN media were receiving the wrong domain.
Programme request:
Please adjust the URL determination for media so that the handling of media links follows the same pattern as the product links within a product comparison. Of course, it must be possible to resolve the link. CDNs must…1 vote -
Admin content language selection
When you currently access an overview in our Admin (e.g. Product overview), the content will always be shown in the system default language, no matter what your admin user setting is. I have attached a screenshot, where you can see, that the menus overall are all in english but the content is showing the german language instead, since it's the default system language.
This really annoying since it forces me to switch in every menu the content language back to english.
My suggestion would be to take the language settings of the admin user into account and always show the content also in that language.
When you currently access an overview in our Admin (e.g. Product overview), the content will always be shown in the system default language, no matter what your admin user setting is. I have attached a screenshot, where you can see, that the menus overall are all in english but the content is showing the german language instead, since it's the default system language.
This really annoying since it forces me to switch in every menu the content language back to english.
My suggestion would be to take the language settings of the admin user into account and always show the…
1 vote -
API extension: Make trial status for plugin rentals queryable
For extensions with usage-based features (e.g., character quotas, API limits, etc.), it would be very helpful to be able to query the current trial status of a plugin rental via API.
Specifically, the following scenario applies:
For plugins that unlock the full range of functions during the trial month (e.g., a translation plugin that can translate almost the entire shop), we are increasingly observing that users take advantage of the free month to translate the entire shop once and then cancel. Without a technical way to recognize the trial month, it is difficult to limit this fairly.A simple flag would be desirable, e.g., isTrialActive, which can be queried via API. This would allow us to activate a transparent limitation during the trial period and automatically unlock full functionality after it expires.
Example application:
During the trial month:
- quota of, for example, 100,000 characters.
- All functions can be tested realistically.
- However, the free trial month is not used as a full “free full version.”After the end of the trial: Automatic release of the full quota/scope with active rental
Such a trial flag would make it possible to design fair trial periods – both for merchants (realistic testing) and for developers (protection against abuse) – without complicated workarounds or external billing logic.For extensions with usage-based features (e.g., character quotas, API limits, etc.), it would be very helpful to be able to query the current trial status of a plugin rental via API.
Specifically, the following scenario applies:
For plugins that unlock the full range of functions during the trial month (e.g., a translation plugin that can translate almost the entire shop), we are increasingly observing that users take advantage of the free month to translate the entire shop once and then cancel. Without a technical way to recognize the trial month, it is difficult to limit this fairly.A simple flag…
1 vote -
Enhanced in-app purchase API for usage-based models
We want to develop extensions that are billed entirely via IAP (comment from Shopware: IAP stands for In App Purchases) – without our own subscription logic or external billing. Typical use cases are usage-based features such as quotas (e.g., search volume per month), limits, or activations with periodic renewal.
Currently, Shopware.InAppPurchase.isActive(‘MyExtensionName’, ‘my-iap-identifier’) only returns a Boolean (purchased: true/false).
However, for usage-based models, we lack the specific billing period, e.g., to reliably reset quotas when transitioning to the new period.Our request/feature request:
In addition to isActive(), minimal contract information would be helpful, e.g.:
- Purchase or start date of the current billing period
- Billing interval (e.g., monthly, annually)
- Flag indicating whether it is a wildcard/stage environmentThis would allow usage-based features (such as search volume, API quotas, free requests, etc.) to be implemented correctly, transparently, and fairly— without having to implement a parallel subscription or billing solution alongside Shopware IAPs.
We want to develop extensions that are billed entirely via IAP (comment from Shopware: IAP stands for In App Purchases) – without our own subscription logic or external billing. Typical use cases are usage-based features such as quotas (e.g., search volume per month), limits, or activations with periodic renewal.
Currently, Shopware.InAppPurchase.isActive(‘MyExtensionName’, ‘my-iap-identifier’) only returns a Boolean (purchased: true/false).
However, for usage-based models, we lack the specific billing period, e.g., to reliably reset quotas when transitioning to the new period.Our request/feature request:
In addition to isActive(), minimal contract information would be helpful, e.g.:
- Purchase or start date of the…1 vote -
Use Flow Builder for automatic refunds
If an order's status is changed to 'cashback', the Flow Builder should automatically trigger a PayPal refund for that order. This reduces the need for manual work and eases the burden on customer support.
1 vote -
Net margin of sold products
Hello,
We are missing the net margin of products sold that day. It would be cool if this could be added e.g. an average margin for all sales and a margin per supplier and/or product.
(price.net-purchaseprice.net)/price.net
Thanks in advance!
Kind regards,
5 votes -
Create Quote-Documents before sending the Quote
Currently, in the quote module, generating quote documents is only technically possible when the quote is sent. This means that employees cannot review the details and final layout of the documents in advance or coordinate with colleagues. Especially in complex B2B processes, where quality assurance and coordination are essential, this causes unnecessary sources of error and additional effort.
Specific Improvement Proposal:
The function for generating quote documents (e.g., PDF) should be decoupled from the sending process.
It should be possible at any time—at the latest after saving the quote as a “draft”—to create, download, and review the final quote document before the quote is actually sent.
Optionally, a release workflow can be integrated, allowing, for example, the sales or back-office teams to approve or comment on the documents before they are sent to the customer.Added Value and Benefits:
Checkability: Employees can internally review quotes in advance and prevent errors in content or layout.
Transparency: The final document is visible for parallel approval processes before it is sent.
More Efficient Processes: Reduces returns, customer queries, and deletions due to faulty quotes, saving time in daily operations.
Currently, in the quote module, generating quote documents is only technically possible when the quote is sent. This means that employees cannot review the details and final layout of the documents in advance or coordinate with colleagues. Especially in complex B2B processes, where quality assurance and coordination are essential, this causes unnecessary sources of error and additional effort.
Specific Improvement Proposal:
The function for generating quote documents (e.g., PDF) should be decoupled from the sending process.
It should be possible at any time—at the latest after saving the quote as a “draft”—to create, download, and review the final quote document…2 votes -
Separate customer e-mail address for sending invoices (billing address)
Deutsch:
Die Erfahrung zeigt, dass die meisten Geschäftskunden eine eigene E-Mail-Adresse für den Rechnungsempfang haben, um ihre Buchhaltung zu organisieren und Rechnungen zentral zu sammeln. Aus diesem Grund sollte Shopware 6 es den Kunden ermöglichen, nicht nur eine separate Rechnungsadresse, sondern auch eine separate E-Mail-Adresse für den Rechnungsempfang anzugeben. Diese sollte dann auch zum Export (via API etc.) in das ev. angebundene ERP zur Verfügung stehen.Englisch:
Experience shows that most business customers have a separate email address for receiving invoices in order to organise their accounting and collect invoices centrally. For this reason, Shopware 6 should allow customers to specify not only a separate billing address, but also a separate email address for receiving invoices. This should then also be available for export (via API etc.) to any connected ERP.Deutsch:
Die Erfahrung zeigt, dass die meisten Geschäftskunden eine eigene E-Mail-Adresse für den Rechnungsempfang haben, um ihre Buchhaltung zu organisieren und Rechnungen zentral zu sammeln. Aus diesem Grund sollte Shopware 6 es den Kunden ermöglichen, nicht nur eine separate Rechnungsadresse, sondern auch eine separate E-Mail-Adresse für den Rechnungsempfang anzugeben. Diese sollte dann auch zum Export (via API etc.) in das ev. angebundene ERP zur Verfügung stehen.Englisch:
Experience shows that most business customers have a separate email address for receiving invoices in order to organise their accounting and collect invoices centrally. For this reason, Shopware 6 should allow customers to…5 votes -
Add “tax column instead of unit price” option to cart as well
In Shopware 6.7.1 the option to display either the unit price or the VAT of the respective line item was introduced. However, it only changes the list in the checkout. It would be useful to have the same option for the cart as well.
DE: In Shopware 6.7.1 wurde die Option “Steuerspalte anstatt Stückpreis” eingeführt, die entweder den Stückpreis oder die Mehrwertsteuer der jeweiligen Position anzeigt. Diese Änderung betrifft jedoch nur die Liste im Checkout. Es wäre sinnvoll, dieselbe Option auch für den Warenkorb zu haben.
3 votes -
Products offeren ONLY in subscriptions
Currently products can already be offered as subscription products within the Beyond plan. In the frontend can than be selected if it should be a subscription or a regular order. Unfortunately it is not possible to make products available ONLY as subscriptions products and deactivate the possibility to order it once for that product.
1 vote -
Migrate advanced search configuration to all Storefronts
The configuration options in the advanced search are numerous and complex to maintain.
If you want to set boostings, actions and synoyms in all storefronts, the same configuration has to be made 24 times in our case, although we only have 4 different languages.
This maintenance effort could be considerably simplified by a migration feature/option.9 votes -
Use Thumbnails for Property Images in Filter
Please adjust the default template
Resources/views/storefront/component/listing/filter/filter-property-select.html.twig
so that when images are assigned to properties, the appropriate thumbnail images are used instead of the full original images.Currently, the original image is loaded, which can negatively impact page load performance.
In our instance, I’ve already implemented a manual fix by replacing:
{% set media = element.media.url %}
with:
{% set media = element.media.thumbnails | filter(t => t.width == 100 and t.height == 100) | first.url %}This ensures that a 100x100 thumbnail is used when available.
4 votes
- Don't see your idea?