- or
No existing idea results
- ~ No ideas found ~
1518 results found
-
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 space…
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, we can therefore…
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 -
Add possibility to extend page format for documents
It should be easier to extend the available page formats for documents.
For example we want to print our delivery note on a label printer or thermal printer as we have already seen with some retailers. Shopware does not currently offer a solution for this.1 vote -
Custom Products: Enable price reduction like surchages
EN
In Custom Products it is possible to define a discount/reduction via relative surcharges for an option. However, as soon as this is to be done with fixed amounts, it is not possible to enter e.g. -15 EUR. However, some customers require CP options where the product becomes cheaper if the corresponding option is selected.DE
in Custom Products in es möglich über relative Zuschläge für eine Option einen Abschlag/Nachlass festzulegen. Sobald das aber mit festen Beträgen passieren soll, ist die Eingabe von z.B. -15 EUR nicht möglich. Einige Kunden benötigen aber CP Optionen, bei denen das Produkt günstiger wird, wenn die entsprechende Option gewählt wird.EN
In Custom Products it is possible to define a discount/reduction via relative surcharges for an option. However, as soon as this is to be done with fixed amounts, it is not possible to enter e.g. -15 EUR. However, some customers require CP options where the product becomes cheaper if the corresponding option is selected.DE
in Custom Products in es möglich über relative Zuschläge für eine Option einen Abschlag/Nachlass festzulegen. Sobald das aber mit festen Beträgen passieren soll, ist die Eingabe von z.B. -15 EUR nicht möglich. Einige Kunden benötigen aber CP Optionen, bei denen das Produkt günstiger wird,…2 votes -
Add multiple changes to the Dynamic Access settings for products
At the moment it is not possible to make simple adjustments to the Dynamic Access rules via the bulk changes for products. Please add this function, as we often have to adjust many products at once.
5 votes -
Simplified import of variants
Up to now, the import of variants has only been possible via a multi-level import. If variants are imported frequently, this is very tedious and frustrating.
A single-step import would therefore be desirable so that the main article and the variants are created directly. At least one extension shows that this is possible, but unfortunately it is no longer being developed.
4 votes -
Product filter - no sales channel assignment
It is currently only possible to filter by sales channel assignment in the product overview. It is not possible to filter for products that are not assigned to a sales channel.
4 votes -
Delayed flows should also be set in minutes and seconds
Currently, the shortest delay for delayed flows is one hour. It should be possible to delay them in minutes or even seconds.
2 votes -
Read more for CMS Shopping Experiences Block / Weiterlesen bei CMS Erlebniswelten Block (Truncate text)
EN:
The possibility to select read more and read less in the CMS Shopping Experiences Block. Configuration: the lines after the button for read more is showed.DE:
Die Möglichkeit auf der CMS Erlebniswelten weiterlesen und weniger lesen anzeigen zu lassen. Konfiguration: Zeilen nachdem der Button weiterlesen und weniger lesen angezeigt wird.1 vote -
Restrict the command "Shopware\Core\Profiling\Profiling::class => ['all' => true]" to dev environments
Restrict the command "Shopware\Core\Profiling\Profiling::class => ['all' => true]" to dev environments to prevent the cache of, for example, live environments from filling up. This can happen under certain circumstances.
1 vote -
New flow trigger: Customer password changed
It would be good if there were an email to the customer to inform them about the change to their password.
This increases security somewhat and provides us as retailers with a little more information in support situations.
For this purpose, a new trigger would be required that is activated when the customer changes their password (e.g., via password recovery).1 vote -
Bulk edit product cover image
Currently you can bulk edit product media, so you can add images for multiple products at once. However this does not effect / set the cover image. Therefore it would be great if there is an option in the bulk edit to set an image as cover image for multiple products at once.
21 votes -
View/delete all unused images/media files
A way to display all unused media files in the admin panel and then delete them. This feature was available in Shopware 5.
Eine Möglichkeit im Admin alle nicht verwendeten Mediendatein anzeigen zu lassen und diese dann auch zu löschen. Diese Funktion gab es in Shopware 5.
4 votes -
SAML/OAuth SSO support
In discussions with large and important customers, SAML/OAuth SSO support is repeatedly asked for, as this is sometimes required/prescribed in large companies or corperations.
In view of large companies and corporations, there should be an implementation here.
5 votes
- Don't see your idea?