- or
1510 results found
-
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 vote -
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 -
Add "Creation Date" as product sorting criteria
Currently there is no product sorting criteria option for the creation date, in order to present recent created products more prominently on category pages.
There is the option to use the "Release Date" as sorting criteria, but this value is not automatically filled while the creation date is created with every new product created.
7 votes -
Further development of analytics
Who, if not the store itself, knows the key figures of a store that an operator cannot do without?
Analytics must therefore be developed further. For example, with AI prompts (which product was sold or clicked on the most last week) or shopping cart abandonments.
From a customer perspective, it is questionable why this theme is not prioritized when it should actually be part of the store.
3 votes -
Pre-filled custom forms with URL parameters
It would be great if custom forms in Shopware 6 could be pre-filled using URL parameters – for example, in use cases like invoice corrections. This way, values like order number, invoice number, or customer ID could automatically appear in the form when the link is printed on an invoice.
Example URL:
www.shop.com/invoice-correction?orderid=123&billingid=456&customerid=789As a result, the order number in the custom form invoice-correction should now be pre-filled with 123, the invoice number with 456, and the customer number with 789.
At the moment, this only works via third-party plugins (e.g., ACRIS CMS Pro). It would be great to have native support for this in Shopware.
It would be great if custom forms in Shopware 6 could be pre-filled using URL parameters – for example, in use cases like invoice corrections. This way, values like order number, invoice number, or customer ID could automatically appear in the form when the link is printed on an invoice.
Example URL:
www.shop.com/invoice-correction?orderid=123&billingid=456&customerid=789As a result, the order number in the custom form invoice-correction should now be pre-filled with 123, the invoice number with 456, and the customer number with 789.
At the moment, this only works via third-party plugins (e.g., ACRIS CMS Pro). It would be great to have…
2 votes -
Add proper postal code validation
The current postal code validation is not only disabled by default, but also has very rudimentary Regex rules as default, for example \d{4} for Germany.
To prevent malicious sign-ups, the validation should be improved by shipping better default Regex strings for the post code validation, to ensure that spam sign-ups are at least a bit more restricted.
2 votes -
Shopware Publisher: Improve viisbility of changes
It is currently difficult to see what exactly has been changed in the world of experience, as the relevant areas are not really made recognizable. This only works with “Block added”.
4 votes -
delivery time as variable for email templates
enable display of delivery time per item within the e-mail template via variable
8 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.
12 votes -
Edit orders from overview
It would be nice if you could already edit orders from the order overview and, for example, adjust the status or add a consignment number.
4 votes -
Totals function for orders & articles after filtering in the admin area
Summenfunktion für Bestellungen & Artikel nach Filterung im Admin-Bereich
Im Admin-Bereich von Shopware 6 fehlt eine grundlegende Funktion zur einfachen Auswertung:
Es gibt keine Möglichkeit, summierte Werte wie Gesamtumsatz, Artikelmengen oder Bestellanzahl nach Filterung anzuzeigen – z. B. für einen bestimmten Zeitraum oder ein bestimmtes Produkt.Diese Funktion war in Shopware 5 und vielen anderen Shopsystemen Standard und wird im täglichen Betrieb dringend benötigt – z. B. für:
Umsatz- oder Absatz-Auswertung nach Zeitraum
Analyse von Produktverkäufen
Schnelle Lager- und Vertriebsentscheidungen
Monats- oder Jahresabschlüsse ohne Plugin-Zwang
Vorschlag zur Umsetzung:
Summenzeile am Ende der Bestell-/Produkt-Tabelle im Admin
Zeigt je nach Spalte: Anzahl, Gesamtsumme (brutto/netto), Menge etc.
Dynamisch aktualisiert je nach gesetztem Filter
Warum das wichtig ist:
Für viele Händler ist diese Funktion Teil des Grundbedarfs im Tagesgeschäft. Dass diese Option nur über aufwändige Exporte, SQL-Abfragen oder Drittanbieter-Plugins möglich ist, passt nicht zum Anspruch eines modernen Shopsystems. Es macht die Arbeit unnötig kompliziert und ist ein Rückschritt gegenüber Vorgängerversionen.Ziel:
Bitte implementiert eine einfache, filterabhängige Summenfunktion im Admin-Bereich – das spart Zeit, erhöht die Datenübersicht und stärkt Shopware als durchdachtes, praxisnahes System.–
EN
Totals function for orders & articles after filtering in the admin area
The admin area of Shopware 6 lacks a basic function for simple evaluation:
There is no option to display totaled values such as total sales, item quantities or order count after filtering - e.g. for a specific time period or a specific product.This function was standard in Shopware 5 and many other store systems and is urgently needed in day-to-day operations - e.g. for
Turnover or sales analysis by time period
Analysis of product sales
Quick stock and sales decisions
Monthly or annual financial statements without the need for a plugin
Suggestion for implementation:
Totals row at the end of the order/product table in Admin
Shows depending on column: Number, total (gross/net), quantity etc.
Dynamically updated depending on the filter set
Why this is important:
For many retailers, this function is part of the basic requirements in day-to-day business. The fact that this option is only possible via complex exports, SQL queries or third-party plugins does not fit in with the requirements of a modern store system. It makes work unnecessarily complicated and is a step backwards compared to previous versions.Goal:
Please implement a simple, filter-dependent totals function in the admin area - this saves time, increases the data overview and strengthens Shopware as a well thought-out, practical system.Summenfunktion für Bestellungen & Artikel nach Filterung im Admin-Bereich
Im Admin-Bereich von Shopware 6 fehlt eine grundlegende Funktion zur einfachen Auswertung:
Es gibt keine Möglichkeit, summierte Werte wie Gesamtumsatz, Artikelmengen oder Bestellanzahl nach Filterung anzuzeigen – z. B. für einen bestimmten Zeitraum oder ein bestimmtes Produkt.Diese Funktion war in Shopware 5 und vielen anderen Shopsystemen Standard und wird im täglichen Betrieb dringend benötigt – z. B. für:
Umsatz- oder Absatz-Auswertung nach Zeitraum
Analyse von Produktverkäufen
Schnelle Lager- und Vertriebsentscheidungen
Monats- oder Jahresabschlüsse ohne Plugin-Zwang
Vorschlag zur Umsetzung:
Summenzeile am Ende der Bestell-/Produkt-Tabelle im Admin
Zeigt je nach Spalte: Anzahl, Gesamtsumme (brutto/netto),…
3 votes -
Shopware Services in the Admin
Shopware Services – cloud-based extensions that deliver new features quickly and flexibly, and can be activated directly in the Admin.
Help us improve it by sharing your feedback, ideas, or suggestions how we can improve the Admin interface for Shopware Services, what's missing or what you would like to see.
3 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 vote -
List all assignments of a Dynamic Product Group
EN
In the Rule Builder, there is an overview with the assignments for each rule. Such an overview would also be a great addition for the dynamic product groups, because the more product groups are used in categories, product comparisons, cross-selling etc., the more difficult it becomes to determine where a particular product group is used.DE
Im Rule Builder gibt es für jede Regel eine Übersicht mit den Zuordnungen. Eine solche Übersicht wäre auch für die Dynamischen Produktgruppen eine super Ergänzung, denn je mehr Produktgruppen in Kategorien, Producktvergleichn, Cross Sellings etc. zum Einsatz kommen, um so schwieriger wird es festzustellen, an welchen Stelle eine bestimmte Produktgruppe genutzt wird.EN
In the Rule Builder, there is an overview with the assignments for each rule. Such an overview would also be a great addition for the dynamic product groups, because the more product groups are used in categories, product comparisons, cross-selling etc., the more difficult it becomes to determine where a particular product group is used.DE
Im Rule Builder gibt es für jede Regel eine Übersicht mit den Zuordnungen. Eine solche Übersicht wäre auch für die Dynamischen Produktgruppen eine super Ergänzung, denn je mehr Produktgruppen in Kategorien, Producktvergleichn, Cross Sellings etc. zum Einsatz kommen, um so schwieriger wird es…7 votes -
custom form: address variables directly and add them to code in E-Mail-Templates
If you use the email template to send the content of a custom form, there is no way to use a TWIG variable directly in the template. For example if you have a field with technical name bla you can't use for example {{ bla.technicalName }}. The code part in the templates is not filled neither.
2 votes -
Handling of category editing improved
Working in the categories with large shops and a nested category structure takes a lot of time and is very cumbersome and tedious. This causes a lot of frustration for large customers.
This is due to the fact that the window with the categories cannot be enlarged, despite the fact that monitors are now large everywhere. The view can only be moved using a bar.
This is not enough for large customers. It must be possible to enlarge the window vertically.
4 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…
11 votes -
Separate categories and landing pages for editing and assigning
Something that is not clear to us is that a category right has an influence on the landing pages and that those who are responsible for the landing pages can also make category changes.
We therefore have the following suggestion:
From the fact that both landing pages and categories can be found under the same ‘Categories’ menu item, it makes sense that both areas may also have overlapping rights. However, it makes little sense to us that editing categories and adding layouts to a landing page are controlled via the ‘Edit categories’ permission.
From our use case, we can therefore only suggest that landing pages and categories be better separated from each other.
It would be nice if both areas could be managed separately with their own rights.
I would also find it much clearer if the landing pages had their own menu item in addition to the categories with separate rights.
For us, the two areas have little in common in terms of handling, except that from a technical perspective they are both elements that a customer can navigate to in the shop. However, this grouping would already be given by the superordinate menu item ‘Catalogues’.
In terms of maintenance and care, the areas are completely different for us, so that the common page of the two topics does not contribute to the clarity and separation of the areas.
While the categories are part of the products and thus the maintenance of the product data, the landing pages and their design are part of the marketing area. In our view, the two otherwise separate areas are currently combined on the categories page for no recognisable reason.
Something that is not clear to us is that a category right has an influence on the landing pages and that those who are responsible for the landing pages can also make category changes.
We therefore have the following suggestion:
From the fact that both landing pages and categories can be found under the same ‘Categories’ menu item, it makes sense that both areas may also have overlapping rights. However, it makes little sense to us that editing categories and adding layouts to a landing page are controlled via the ‘Edit categories’ permission.
From our use case,…
5 votes -
Possibility to delete documents
It should be possible to delete documents, especially invoices.
Several reasons why it should be possible are listed here: https://forum.shopware.com/t/loeschen-von-dokumenten-nicht-mehr-moeglich/97011
Without this function you cannot really test the invoice generation on a production system and you cannot change false invoices that customers have never received.
Due to a bug multiple invoices can be created for the same order with the only difference of the invoice number. Currently you cannot delete the redundant invoice.
52 votes
- Don't see your idea?