- or
No existing idea results
- ~ No ideas found ~
342 results found
-
"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 salutation…
1 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
Display order details clearly on one page instead of using tabs (similar to Shopware 6.4)
The details of an order should be clearly displayed on one page. Unfortunately, the details are currently spread across several tabs.
Clicking around, loading the various tabs and changing details takes longer than if everything could be done on one page.
Shopware 6.4 is clearer than Shopware 6.7.
Please change this.
1 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
Add selection field in user profile settings for measurement preferences
When a user changes the unit in a product, this change is applied at the user level and stored in the database in the
user_configtable with the keymeasurement.preferenceUnit. If there is already a dedicated entry for this in the database, it would be nice if the selection could be changed directly in the user profile.1 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
organisation unit should be defined in new emplyee
As the organisation units are available with version 6.7, it should be possible to map the unit for new employees.
Currently only the role can be set.
Employees can only be mapped within the organisation unit when the employee is active (invitation link is clicked within the 2 hours reaction time).
If organisation units are active in the customer and units are defined, it should be possible to map it within the employee mask. For existing and new employees.
1 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
Add empty alt tags to untagged thumbnails in image galleries
Untagged images in the gallery get an empty alt tag when not tagged, which is a good default behaviour. The thumbnails in the gallery also need this. Currently, untagged images don't get any alt tag at all. This is an accessibility problem!
1 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
CAPTCHAs: Different keys per sales channel
You can currently only store one key pair per CAPTCHA in the Basic information. If you change the sales channel in the
Basic information and enter another key, the previous one will be overwritten.9 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 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
delivery time as variable for email templates
enable display of delivery time per item within the e-mail template via variable
9 votes -
Set product sorting permanently.
The sorting under Catalogs - Products cannot currently be changed permanently. For example, if sorting by the creation date is desired, it must always be triggered manually and cannot be defined per user.
13 votesGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
UI / UX Improvements on Data Mapping in Shopping Experiences
Please add pagination and search field to the data mapping (Datenzuordnung) list in CMS elements.
1 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
Multi Inventory - Adding stock redirects annoyingly
When working with the Shopwares Multi Inventory feature and wanting to assign stock to products, there is an annoying redirect to the first Warehouse Group after every update of stock in another Warehouse group.
I have recorded this to showcase:
https://www.awesomescreenshot.com/video/44724575?key=28cd44e9f3bd2e226b5b66e013185d70As you can see in the video, whenever I apply changes to warehouse group 2 & 3, you get redirected to the group 1 again, even if I might still need more changes applied in those previous groups. This interrupts and slows down the process, because I have to navigate back to either group 2 & 3 again.
1 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
Add "Show password" button to registration form and account profile
It's currently not possible to see the password you've entered when registering or changing your existing password in your account profile
6 votes -
Replace Webpack with Vite in Shopware Administration Panel
Switching from Webpack to Vite in the Shopware Administration Panel would significantly improve development speed and the developer experience. Vite offers faster builds, better HMR (Hot Module Replacement), and modern JavaScript tooling. Its optimized build process and plugin ecosystem make it a future-proof choice for modern frontend development.
By adopting Vite, Shopware developers would benefit from shorter feedback loops during development and an overall more efficient and enjoyable workflow. Additionally, it aligns Shopware with the latest frontend development trends, ensuring continued relevance and appeal to a broader developer community.
9 votes -
Individual mandatory fields in the components
In Shopware, there are both optional and required fields for the billing address and delivery addresses, where this assignment makes no sense in the B2B sector. A personal contact person is, in most cases, an optional addition in the B2B sector.
The typical billing information for a company address is: Mustermann GmbH Musterweg 1 12345 Musterhausen
Persons are also rarely listed in the delivery addresses. Here, too, it should only be an option. In the delivery addresses, it may be necessary to explicitly list a recipient: Mustermann GmbH, Attn: Marketing Department - Uwe Kleemann, Musterweg 1 12345 Musterhausen.
Currently, the following required fields are available:
First name, Last name, Street and house number, City, Countryand the following
optional
fields: Company, Department, ZIP code, StateThe following distribution would make sense for the B2B sector, and therefore for us:
Required fields:
Company, Street and house number, ZIP code, City, CountryOptional fields:
First name, Last name, Department, StateIn Shopware, there are both optional and required fields for the billing address and delivery addresses, where this assignment makes no sense in the B2B sector. A personal contact person is, in most cases, an optional addition in the B2B sector.
The typical billing information for a company address is: Mustermann GmbH Musterweg 1 12345 Musterhausen
Persons are also rarely listed in the delivery addresses. Here, too, it should only be an option. In the delivery addresses, it may be necessary to explicitly list a recipient: Mustermann GmbH, Attn: Marketing Department - Uwe Kleemann, Musterweg 1 12345 Musterhausen.
Currently, the…
1 voteGathering Feedback
We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.
Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.
-
Orders: Subsequent change of shipping method and payment method in Admin
It must also be possible to change the shipping method and payment method later in the admin.
A scenario that occurs again and again and must be possible.
Example:
A customer orders online (prepayment and DHL shipping). However, the customer now comes to us directly. Now we need to be able to change the customer's payment method and shipping method in the store backend as an admin.Or I have to change the shipping method for a company order from DHL to freight forwarding.
41 votes -
Better Utilization of Screen Space (UX)
The product variant management page in Shopware 6 wastes significant screen space on larger monitors, forcing unnecessary horizontal and vertical scrolling. The table is too narrow and doesn’t adapt to the available screen size, making key information harder to access.
Proposed Solution:
- Dynamically resize the table to fill the available screen space.
- Add options for compact view and column customization.
- Enable full-screen mode for data-intensive pages. These changes will enhance usability, save time, and improve the user experience.
Problem Description:
The current user interface of the Shopware 6 product variant management page does not efficiently utilize the available screen space ("real estate") on larger monitors. As shown in the provided screenshot, key issues include:
Wasted Horizontal Space: Despite having significant unused space on the left and right margins, the main table displaying product variants is confined to a narrow section of the screen. This results in truncated or hidden information that requires unnecessary scrolling, especially horizontally.
Limited Vertical Display: Similarly, the vertical space is underutilized. Only a small number of variants are visible at one time, forcing users to scroll repeatedly to view or edit the entire list.
Horizontal Scrolling for Key Information: Important columns, such as media previews and additional details, require horizontal scrolling to access. This disrupts the workflow, especially when reviewing large datasets or making bulk edits.
Suggested Solution:
Dynamic Table Resizing:
The width of the table should dynamically adjust based on the screen resolution and browser window size. Allow the table to expand horizontally to fill the available space, minimizing the need for scrolling.
Adjustable Row Height or Compact View:Introduce a "compact view" or allow users to adjust row heights, enabling more rows to be visible at once in the table without excessive scrolling.
Column Customization and Visibility Toggle:Allow users to customize which columns are displayed and their order. This flexibility would let users prioritize the most relevant information and avoid unnecessary horizontal scrolling.
Full-Screen Mode for Data-Intensive Pages:Implement a full-screen mode for data-intensive pages, such as product variant management. This feature would temporarily hide sidebars and headers, maximizing the display area for the main content.
Responsive Design Improvements:Enhance the responsive behavior of tables to make better use of large monitors while still ensuring usability on smaller devices.
User Benefits: These changes would improve efficiency and usability for users managing large datasets, reducing unnecessary scrolling and clicks. It aligns with modern UI/UX standards and ensures a smoother, more professional experience for Shopware 6 users.The product variant management page in Shopware 6 wastes significant screen space on larger monitors, forcing unnecessary horizontal and vertical scrolling. The table is too narrow and doesn’t adapt to the available screen size, making key information harder to access.
Proposed Solution:
- Dynamically resize the table to fill the available screen space.
- Add options for compact view and column customization.
- Enable full-screen mode for data-intensive pages. These changes will enhance usability, save time, and improve the user experience.
Problem Description:
The current user interface of the Shopware 6 product variant management page does not efficiently utilize the available screen space…
11 votes -
Delete media - folders get not removed
If a medium is deleted manually in Contents > Media, the folder path, e.g.
/media/38/85/66/1728367134/, is retained, only the file is removed. The same phenomenon also occurs when deleting/clearing up via Command line. Even if each directory only takes up a small amount of space, many empty directories quickly accumulate, which means that a lot of unnecessary space is taken up.Please also remove the directories when cleaning up.
Wenn ein Medium in Inhalte > Medien manuell gelöscht wird, bleibt der Ordnerpfad z.B.
/media/38/85/66/1728367134/erhalten, nur die Datei wird entfernt. Das gleiche Phänomen tritt auch auf, wenn die Löschung / das Aufräumen über Command line erfolgen. Auch wenn jedes Verzeichnis nur wenig Platz belegt, sammeln sich da schnelle viele leere Verzeichnisse an, wodurch insgesamt, viel unnötiger Platz belegt wird.Die Verzeichnisse bitte beim Aufräumen auch entfernen.
If a medium is deleted manually in Contents > Media, the folder path, e.g.
/media/38/85/66/1728367134/, is retained, only the file is removed. The same phenomenon also occurs when deleting/clearing up via Command line. Even if each directory only takes up a small amount of space, many empty directories quickly accumulate, which means that a lot of unnecessary space is taken up.Please also remove the directories when cleaning up.
Wenn ein Medium in Inhalte > Medien manuell gelöscht wird, bleibt der Ordnerpfad z.B.
/media/38/85/66/1728367134/erhalten, nur die Datei wird entfernt. Das gleiche Phänomen tritt auch auf, wenn die Löschung…12 votes -
external order id / externe Auftragsnummer
EN:
In B2B, it is common practice for the purchaser to provide an external order number to ensure matching within customer accounting. Therefore, an optional field with “external order number” should be possible in the shop when placing the order (can be switched on/off in admin and per channel). This should be displayed in the order overview for the customer when logged in.DE:
Im B2B ist es üblich eine externe Auftragsnummer seitens des Bestellers zu übergeben, um das matchen innerhalb der Kundenbuchhaltung zu gewährleisten. Daher sollte ein optionales Feld mit "externe Auftragsnummer" im Shop bei der Bestellabgabe möglich sein (im admin ein/ausschaltbar und das pro Channel). Dieses sollte für den Kunden einloggt in der Bestellübersicht angezeigt werden.EN:
In B2B, it is common practice for the purchaser to provide an external order number to ensure matching within customer accounting. Therefore, an optional field with “external order number” should be possible in the shop when placing the order (can be switched on/off in admin and per channel). This should be displayed in the order overview for the customer when logged in.DE:
Im B2B ist es üblich eine externe Auftragsnummer seitens des Bestellers zu übergeben, um das matchen innerhalb der Kundenbuchhaltung zu gewährleisten. Daher sollte ein optionales Feld mit "externe Auftragsnummer" im Shop bei der Bestellabgabe möglich sein…17 votes -
Breadcrumb missing for dynamic product groups - categories / Breadcrumb fehlt bei dynamischen Produktgruppen - Kategorien
Wir nutzen die SW Funktion dynamische Produktgruppen, um automatisiert eine große Anzahl an Artikeln einer Kategorie zuzuordnen. Das funktioniert hervorragend, hat jedoch einen kleinen Fehler im Gepäck.
Leider wird kein Breadcrumb erzeugt, welcher für die SEO und Usability relevant wäre, wenn die Artikel auf diese Weise der Kategorie zugeordnet werden.
Dies klingt zunächst logisch, da der Artikel nicht direkt sondern nur dynamisch zugeordnet wurde, allerdings konnten wir mit einem Plugin einen Breadcrumb automatisch erzeugen.
Die erforderlichen Informationen sind also vorhanden, der Breadcrumb wurde bei der Entwicklung der dynamischen Produktgruppen vermutlich nur nicht berücksichtigt.Es wäre aus Sicht der SEO und der Usability wichtig dies zu korrigieren.
-
We use the SW function dynamic product groups to automatically assign a large number of items to a category. This works great, but has a small flaw.
Unfortunately, no breadcrumb is created that would be relevant for SEO and usability when the articles are assigned to the category in this way.
This sounds logical at first, since the article was not assigned directly but only dynamically, but we were able to create a breadcrumb automatically using a plugin.
So the necessary information is available, the breadcrumb was probably not taken into account when developing the dynamic product groups.From an SEO and usability perspective, it would be important to correct this.
Wir nutzen die SW Funktion dynamische Produktgruppen, um automatisiert eine große Anzahl an Artikeln einer Kategorie zuzuordnen. Das funktioniert hervorragend, hat jedoch einen kleinen Fehler im Gepäck.
Leider wird kein Breadcrumb erzeugt, welcher für die SEO und Usability relevant wäre, wenn die Artikel auf diese Weise der Kategorie zugeordnet werden.
Dies klingt zunächst logisch, da der Artikel nicht direkt sondern nur dynamisch zugeordnet wurde, allerdings konnten wir mit einem Plugin einen Breadcrumb automatisch erzeugen.
Die erforderlichen Informationen sind also vorhanden, der Breadcrumb wurde bei der Entwicklung der dynamischen Produktgruppen vermutlich nur nicht berücksichtigt.Es wäre aus Sicht der SEO und…
7 votes -
Shopping experiences: "Topseller" sort for product-slider
There are different values for sorting within the configuration of the product slider. The ‘Topseller’ selection is missing at this point, which would result in a further and useful customisation of the configuration. This would make sense at this point and is requested by customers.
10 votes
- Don't see your idea?