- or
41 results found
-
Enable Search for Custom Fields in B2B Quick orders search field
The B2B Components Quick Order feature should be extended to support searching by custom fields.
This would allow companies to tailor the search experience to their specific data models—for example, enabling search by internal article numbers, supplier SKUs, or industry-specific identifiers. Enhancing the search logic in this way significantly improves usability and efficiency for B2B customers who rely on custom attributes in their ordering processes.
2 votes
1464 results found
-
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 -
E-invoice for cancellation invoice, too
Currrently only the invoice itself is abvailable for creating as a Zugferd format. The cancellation invoice should added as soon as possible, because this may lead to irriatations at accounting.
13 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 -
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 -
Expanding columns under products, customers or orders
We've received requests from several departments asking if we could add additional columns for products, customers, or orders.
For example, the customer's last login date.
The reason for this is that customers often create multiple accounts (guest accounts).
This field would make it easier for our customer service to identify which account the customer is referring to, since 99% of the time it's the account that last logged in.
'Sales' would also be a really helpful column for us for products.
The standard fields should simply be available as optional items to simplify daily work.
4 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 -
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 -
Support cron jobs per application in Shopware Native PaaS
Some business processes (like product imports) need automated scripts to run on a schedule. Shopware Native PaaS should support cron jobs per application, ideally managed through sw-paas.
5 votes -
Show regulation price in listings only if there ist a discount
Our suggestion In order to comply with both the PAngV and a clean UX, a small piece of logic would be useful:
If regulationPrice == price.unitPrice → no output. (This happens very often in practice.)
This would both comply with the legal situation and meet actual customer expectations.
- Legal situation (PAngV § 11) According to § 11 of the Price Indication Regulation (PAngV), the ‘lowest total price of the last 30 days’ only becomes mandatory if the retailer advertises a price reduction. Source (legal text): https://www.gesetze-im-internet.de/pangv_2022/BJNR492110021.html#BJNR492110021BJNG000201377
It clearly states: ‘If goods are offered to consumers with reference to a price reduction, the lowest total price charged by the trader within the last 30 days [...] must be indicated.’ ➡ Without a price reduction, there is no obligation to display the price.
- Confirmation by legal commentary (e.g. the article you linked to) Your linked article also clearly states that this obligation only applies to reduced prices and serves precisely to prevent misleading ‘bogus discounts’: https://www.ratgeberrecht.eu/aktuell/30-tage-bestpreis/ If the current price is identical to the 30-day price, there is no price reduction and the display ‘Lowest price in the last 30 days’ would rather suggest a false discount effect.
Our suggestion In order to comply with both the PAngV and a clean UX, a small piece of logic would be useful:
If regulationPrice == price.unitPrice → no output. (This happens very often in practice.)
This would both comply with the legal situation and meet actual customer expectations.
- Legal situation (PAngV § 11) According to § 11 of the Price Indication Regulation (PAngV), the ‘lowest total price of the last 30 days’ only becomes mandatory if the retailer advertises a price reduction. Source (legal text): https://www.gesetze-im-internet.de/pangv_2022/BJNR492110021.html#BJNR492110021BJNG000201377
It clearly states: ‘If goods are offered to consumers with reference to a price…
2 votes -
Taxes: Deactivation of unused Tax settings
Sometimes it's thought that additional taxes are needed. If they were used, it is not possible to remove them completely.
As a second stumbling block it is not possible to deactivate tax rates or change the order. Some customers have huge problems with this beheaviour because the "wrong" tax rate is always the first to select.It would be a great improvement, dor decativate taxes and / or change the order.
2 votes -
Use the document language to determine the email template language when sending documents
Currently, when documents are manually transferred via the order via send document, the email template language is determined by the admin user’s backend language, not by the language in which the customer placed the order.
This leads to additional steps every time a document needs to be sent manually:
The admin must first check the order language, switch the backend language accordingly, and only then send the document so that the email is generated in the correct language.The expected behavior is that the document’s language (or order language) should define which email template is used for sending, ensuring consistent customer communication and reducing unnecessary manual steps.
Implementing this would streamline workflow, avoid mistakes, and provide a more intuitive and customer-centric process.
Currently, when documents are manually transferred via the order via send document, the email template language is determined by the admin user’s backend language, not by the language in which the customer placed the order.
This leads to additional steps every time a document needs to be sent manually:
The admin must first check the order language, switch the backend language accordingly, and only then send the document so that the email is generated in the correct language.The expected behavior is that the document’s language (or order language) should define which email template is used for sending, ensuring consistent…
2 votes -
Flow Builder | Define dynamic mail recipients using variables
We need to send order confirmation emails to additional recipients whose email addresses are stored in custom fields of the order’s shipping address. Currently, the Flow Builder does not allow dynamic email addresses in the “Send Email” → “Custom recipient” field.
2 votes -
Remove hardcoded title suffix from static pages
There is currently no way to configure a global meta title suffix for static pages in Shopware without modifying the shop’s base meta information or implementing a custom plugin. For example, in CheckoutCartPageLoader::setMetaInformation(), meta titles are hard-coded, making it impossible to centrally manage suffixes for static or system pages. A global text snippet or configuration option for defining a meta title suffix applicable to all (or all static) pages would greatly simplify consistent SEO management and avoid unnecessary custom development.
2 votes
- Don't see your idea?