- or
1510 results found
-
Improve "Add product" UI function in orders
Shopware allows to add new products within existing orders. How ever, the way the button is currently designed is quite counter intuitiv and causes confusion.
The button consists of two parts: "Add product" and an area with an arrow, indicating further options. Users tend to interprate it as in they need to click on the arrow area in order to access all options to add a new product. How ever, there are only the option "Add custom item" or "Add credit".
This could be prevented by simply also showing the "Add product" option here as well.
2 votes -
Be able to create new Address Snippets
Currently, there is only a predefined set of snippets, that can be selected in "Settings > Shop > Countries > 'SELECT_COUNTRY' > Address Handling" for the Address Markup.
Adding new Snippets would be great for instance to add a new snippet for the street number or to customize the Address markup as you need it.
2 votes -
Tabs on the mask to create/edit products should be re-sortable
It would be helpful if the tabs in the mask for creating/editing products could be sorted or arranged individually.
Especially with regard to the extension of these tabs by plugins/apps, this makes sense, as otherwise important and frequently used tabs disappear from the display area and can only be accessed by constantly scrolling back and forth.
2 votes -
Add address validation options
It would be useful to have the ability to validate addresses inserted by customers against rules that can be defined in the Admin area for each country. Perhaps something like a regex validation.
This would allow for filtering of invalid characters, to validate the syntax in certain countries or in case of international shipping the filtering of entire character sets (i.e. Greek, Cyrillic, Chinese, Japanese). This helps with the creation of shipping labels and especially the latter use case would make it easier for shop owners to ship their products to those countries.
2 votes -
Uninstallation via cli should delete the folder of an uninstalled extension
If an extension is uninstalled via cli, the folder in plugins is not removed. This may lead to incorrect licence warnings. The folder should therefore also be deleted when uninstalling.
2 votes -
No mandatory fields for Import
The fact that there are mandatory fields during import means that unnecessary data (e.g. stock in the event of a price change) is transferred, but this only delays the duration of the import and makes no sense.
For example, it is not necessary to change the stock when changing prices. This is not necessary and only delays the duration of the import. For large customers, the import takes many hours.
It would therefore be desirable to be able to deactivate the dependencies.
4 votes -
Presets for roles
There should be fixed roles for employees. The classic roles such as customer service (read only) and SEO should be available as standard. Access to each individual setting point should be separately selectable.
1 vote -
Delete extensions from the "My extension" overview in the Admin
Extensions, which are added via our Extension Shop are shown permanently in the "My extension" overview in the Admin. These Extensions can only disappear from the overview, if customers archive the license in their Shopware Account.
This is not really selfexplanatory and creates confusion and frustration.
Either the documentation musst be clearer (tool tips, docs, etc.) or a function to perform the archiving in the Admin would be highly appreciated.
4 votes -
Loading times of the article sliders
The article sliders currently take about one second to load properly. Until then, the first product of the slider is usually displayed briefly in large format.
An optimization of the loading time for article sliders with many products would be desirable.3 votes -
Admin Search: set if the search used fuzzy search (fault tolerant) or not
EN:
Set if the search used fuzzy search (fault tolerant) or not because we have the problem there are to many search results, if type the exact mail address in the customer search field, of the mail address domain. If typed in the exact mail address only one or two results (if there is a customer and a guest account with the same mail address should the shown). If entered the mail address domain only all customer with the exact mail address domain should be shown.The search bar in the admin for customers is in great need of improvement.
DE:
Es soll festgelegt werden können, ob bei der Suche Fuzzy-Suche (fehlertolerant) ist oder nicht, da wir das Problem haben, dass es zu viele Suchergebnisse gibt, wenn die genaue E-Mail-Adresse der E-Mail-Adressdomäne in das Kundensuchfeld eingeben werden. Wenn die genaue E-Mail-Adresse eingeben, werden nur ein oder zwei Ergebnisse angezeigt (wenn ein Kunden- und ein Gastkonto mit derselben E-Mail-Adresse vorhanden sind, sollten diese angezeigt werden). Bei Eingabe der E-Mail-Adressdomäne sollten nur alle Kunden mit der genauen E-Mail-Adressdomäne angezeigt werden.Die Suchleiste im Admin bei den Kunden ist stark verbesserungsbedüftig.
EN:
Set if the search used fuzzy search (fault tolerant) or not because we have the problem there are to many search results, if type the exact mail address in the customer search field, of the mail address domain. If typed in the exact mail address only one or two results (if there is a customer and a guest account with the same mail address should the shown). If entered the mail address domain only all customer with the exact mail address domain should be shown.The search bar in the admin for customers is in great need of improvement.
…
7 votes -
Properly display error messages for customer-facing formfields
Currenty, Showpare (default skin) does not reliably display error messages on missing or wrong form fields when submitted by the users, e.g.
- When logging in with wrong credentials
- When registering an account (most fields)
- When using the newsletter registration form.
Shopware will highlight the fields in red and there are internal attributes (data-form-validation-required-messag) on the fields that do contain error messages, but these are not displayed reliably to the user. There seems to be something in place that will sometimes client-validate those error messages and display them, but that hardly happens / seems broken. (Not a bug accordinging to Shopware support, redirected here instead)
We would expect any error messages attached to wrongly filled or empty obligatory fields to be displayed at a sensible space (below?) the form field.
See attached Screenshots.
Currenty, Showpare (default skin) does not reliably display error messages on missing or wrong form fields when submitted by the users, e.g.
- When logging in with wrong credentials
- When registering an account (most fields)
- When using the newsletter registration form.
Shopware will highlight the fields in red and there are internal attributes (data-form-validation-required-messag) on the fields that do contain error messages, but these are not displayed reliably to the user. There seems to be something in place that will sometimes client-validate those error messages and display them, but that hardly happens / seems broken. (Not a bug accordinging to Shopware…
4 votes -
Bulk translation editor for CMS element config in Layout tab
Currently, when managing translations for CMS configurations (such as a text block, images, ...) within product or category pages, the process is quite time-consuming. We need to manually switch languages and update the field one-by-one for each language. For stores with multiple languages, this creates a lot of overhead for even small content updates like updating a photo.
I’d like to propose a bulk translation editor that allows us to edit the config of a CMS element across multiple languages in one view, similar to how snippet management already works at this moment. This would greatly improve usability and efficiency for content managers working in multilingual shops.
Ideally, this editor could be opened from the CMS config card in the Layout tab and show a table or structured form where we can input translations for each language side-by-side.
Additionally, bonus points for a way to copy a translated config for a certain element to all other languages would be great. An image for example is often not translated, thus does not need a specific config for each language.
Currently, when managing translations for CMS configurations (such as a text block, images, ...) within product or category pages, the process is quite time-consuming. We need to manually switch languages and update the field one-by-one for each language. For stores with multiple languages, this creates a lot of overhead for even small content updates like updating a photo.
I’d like to propose a bulk translation editor that allows us to edit the config of a CMS element across multiple languages in one view, similar to how snippet management already works at this moment. This would greatly improve usability and…
1 vote -
gallery slider is not compatible with different sizes
When the pictures are very different in size or ratio, the gallery slider pops out downside or shrinks back upside, which is not very nice
an option to choose a certain height so that the pictures scale to it would be nice
1 vote -
Display of variants in product-sliders and cross sellings if assigned via dynamic product group
The display of variants within product sliders - if assigned via dynamic product groups - is based on the configuration from the storefront presentation. Even if individual variant options are explicitly assigned to the dynamic product group, it is still possible that the main product or a different variant will be displayed, unless it has been specified that the variants should be fanned out.
If I want to ensure that only certain variants are displayed in a product slider, the individual variants must currently be manually assigned to the product slider. This is because changes to the storefront display always have a direct effect on the listing at the same time, even though this may not be desired and the configuration should only relate to the slider.
The display of variants within product sliders - if assigned via dynamic product groups - is based on the configuration from the storefront presentation. Even if individual variant options are explicitly assigned to the dynamic product group, it is still possible that the main product or a different variant will be displayed, unless it has been specified that the variants should be fanned out.
If I want to ensure that only certain variants are displayed in a product slider, the individual variants must currently be manually assigned to the product slider. This is because changes to the storefront display always…
3 votes -
Add search for blocks and elements at cms page editing
Add a search bar to block sidebar and element selection to get blocks and elements quicker.
Important when more elements/blocks are added with plugins/apps.2 votes -
predefined periods for products / add an expiration date
In Shopware 6 it would be very useful if it were possible to activate products for a set period of time.
Since there is already a “release date”, it would be very useful to add an end to it.
In certain sectors, products may only be offered for a period of time x, e.g. for pesticides as these have approvals with an end date.
2 votes -
Different flows for different forms
It is currently not possible to send different actions, for example different e-mail templates, if different forms are sent.
A differentiation through a rule in the Rule Builder or different flow triggers would be helpful here.2 votes -
Automated Birthday Greetings with Discounts
I would like to suggest an enhancement to Shopware 6 that brings back a popular and valuable feature from Shopware 5: automatically sending birthday emails with discount codes or greetings to customers.
The Issue:
Currently, Shopware 6 lacks the functionality to automate birthday-related actions through the Rule Builder and Flow Builder. This prevents shop owners from creating personalized birthday campaigns, which are an effective tool for customer engagement and loyalty.Proposed Solution:
Enhance the Rule Builder and Flow Builder with the ability to:Identify Birthdays:
Add a rule condition that checks the "Date of Birth" field in customer profiles.
Allow dynamic filtering, such as "is today," "is in the next X days," or "has already occurred this year."
Automated Email Trigger:Enable automated email workflows based on the customer's birthday, either on the exact date or as part of a pre-scheduled campaign.
Custom Discount Code Generation:Integrate the ability to generate unique, single-use discount codes as part of the workflow.
Include these codes dynamically in the email template.
Personalized Messaging:Allow email templates to include dynamic fields, such as the customer's name or age (optional), to make the greetings feel personal.
Benefits for Shop Owners:Strengthened Customer Loyalty: Birthday emails are a great way to engage customers on a personal level and show appreciation.
Increased Sales Opportunities: Discounts incentivize customers to make a purchase, driving revenue.
Time Efficiency: Automating this process saves time for shop owners, especially for shops with a large customer base.
Customer Delight: A thoughtful gesture like a birthday greeting can leave a lasting positive impression.I would like to suggest an enhancement to Shopware 6 that brings back a popular and valuable feature from Shopware 5: automatically sending birthday emails with discount codes or greetings to customers.
The Issue:
Currently, Shopware 6 lacks the functionality to automate birthday-related actions through the Rule Builder and Flow Builder. This prevents shop owners from creating personalized birthday campaigns, which are an effective tool for customer engagement and loyalty.Proposed Solution:
Enhance the Rule Builder and Flow Builder with the ability to:Identify Birthdays:
Add a rule condition that checks the "Date of Birth" field in customer profiles.
Allow…3 votes -
Order details - Show customer group, company name etc.
Add information just like "customer group", "company name" and "vat id" to the order details. To get those kind of information you currently need to open the customer record itself.
4 votes -
youtube & vimeo link in product picture and in product description
At amazon it is standard to have product videos in product description and product pictures.
So Shopware should have the function:
- product picture (the last one) to us it for product video
- link youtube & vimeo videos at the end of the product description or optional as separated tabFor me: product picture (the last one) to us it for product video is very important for us, becausing using a lot of videos for using the product and describing the product.
32 votes
- Don't see your idea?