1434 results found
-
search term history for the frontend
It should be possible to store the last used search terms of a guest or active customer.
He should be able to review his last entered search terms.This may be activated via option.
12 votes -
Add Sha512 as legacyEncoder
Currently, only Sha256 and Md5 are supported as legacyEncoders for customer passwords. Please extend this to Sha512.
5 votes -
Invert the filter criteria
Sometimes a filter result is needed, that does not show the result where the criteria fits but where it doesn't fit. As examples:
All customers outside my country that don't pay with XXX
All customers that don't belong to the customer goup xxxOne way for a solution could be to add a check box that leads to an invertion of the selected filter criteria.
3 votes -
Add promotion code via link
It would be a nice feature if discount codes could be redeemed via link in the same way that EasyCoupon does it for example. This would allow merchants to send mails already including a working link to get the customer shopping with their discount. For the customers, this would make the journey smoother because they don't need to back and forth to get some code and find the field to enter it and so on.
Plus, the customer is probably much more likely to actually complete the checkout if they see their shiny discount applied at all times right from…
3 votes -
Hide Price and Add to Cart Button – Show “Request Quote” Only
In B2B scenarios, it is often necessary to offer products without displaying prices or allowing direct purchases. I propose adding a feature to the B2B Components that allows specific products to be configured so that the price and “Add to Cart” button are hidden. Instead, only a “Request Quote” button should be displayed.
This would enable merchants to:
Offer products where prices are negotiated individually.
Streamline the quoting process for high-value or custom items.
Improve compliance with B2B pricing strategies and contractual agreements.The configuration should be product-specific and easy to manage via the admin panel, ideally with bulk selection…
6 votes -
Feedback regarding voucher/promotion response in the shopping cart
Topic: Missing User Feedback for Unactivated Coupon Promotions
Description:
When a customer enters a coupon code linked to a promotion during checkout, it is technically validated.If the promotion cannot be activated due to the current contents of the shopping cart (e.g., due to product category or discount restrictions), the customer receives no feedback on the front end.
From the customer's perspective, nothing happens – even though the code would be valid.
Current Behavior (Default):
- Coupon is checked in the background.
- No error message or information is displayed if conditions are not met.
- The customer does not…3 votes -
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 -
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…
3 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…
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 -
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 -
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 -
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 -
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.
10 votes -
Custom fields as filters in categories
In Shopware 5 the free text fields could be directly used as catgory filter and the filters have been configurable (Anzeige Modus). That means the customer could define how a selection of value shall be in the frontend (Slider, Checkbox, Simple, Multiselection).
The second thing: Using custom fields cannot be done directly. You have to add a property, then it can be used with the limits of the usual behaviour of catalogue > properties.
It would be great if this will be easier to use custom field in future a filter criteria.
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 -
It should be optionally possible to create orders only after the payment has been successful.
Es soll optional möglich sein, Bestellungen erst dann zu erstellen, wenn die Zahlung erfolgreich war. Wenn der Bezahlvorgang abbricht, soll auch der Bestellvorgang abbrechen.
It should be optionally possible to create orders only after the payment has been successful. If the payment process is aborted, the order process should also be aborted.
12 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.
11 votes
- Don't see your idea?