- or
No existing idea results
- ~ No ideas found ~
330 results found
-
Hide buy button for specific products on sales channel level
Implement an option that allows hiding the buy button for specific products. Moreover, it should be possible to hide the buy button for specific sales channels while it continues to be displayed in other sales channels.
6 votes -
1 vote
-
Payment method icon supports text | Icon für Zahlungsart sprachfähig
Only one global logo can be set for each payment method; language-specific logos are not supported. However, for ‘Prepayment’ or ‘Invoice’, it would be useful to be able to set different logos for German and English, for example.
Es lässt sich für jede Zahlungsart nur ein globales Logo hinterlegen, kein sprachenabhängiges.
Bei "Vorkasse" oder "Rechnung" wäre es aber sinnvoll, z.B. für deutsch/englisch unterschiedliche Logos hinterlegen zu zu können.
1 vote -
Enable swiping of product images in the gallery
When a customer views a product page on a mobile device, it is possible to swipe through the different product images.
However, once the gallery (full screen) is opened, it is no longer possible to navigate through the images by swiping, and only the arrow keys can be used.
This behavior is not transparent and therefore not comprehensible to the customer, making it feel like an error.
5 votes -
Let B2B Employees changed their own password
It should be a standard functionality that a user can change their password.
This is currently not possible.
Please implement this.
3 votes -
Order number prefix/suffix as in the PayPal plugin
Since switching from the PayPal plugin to Shopware Payments, I miss being able to add a prefix to the order number for each sales channel. This made it very easy to match incoming payments in PayPal to the relevant sales channel.
1 vote -
Checkout gateway mechanism for calculating delivery charges
Die vorhandenen Commands des Checkout Gateways (https://developer.shopware.com/docs/guides/plugins/apps/gateways/checkout/command-reference.html) lassen es nicht zu, die Versandkosten des Warenkorbs zu berechnen oder zu setzen.
Dies wäre aber wünschenswert, um z.B. kompliziertere Versandkostenberechnungen vom ERP erledigen zu lassen.–
The existing commands in the Checkout Gateway (https://developer.shopware.com/docs/guides/plugins/apps/gateways/checkout/command-reference.html) do not allow the shipping costs for the shopping basket to be calculated or set.
However, this would be desirable, for example, to allow the ERP system to handle more complex shipping cost calculations.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.
-
Warenkorb Spalte "Produktnummer" auch für Angebote
Im Backend besteht derzeit im Warenkorb von Angeboten keine Möglichkeit, die Spalte „Produktnummer“ einzublenden, um die Artikelnummern der hinzugefügten Produkte direkt sehen zu können.
Da diese Funktion bei Aufträgen bereits verfügbar ist, wäre es sinnvoll und hilfreich, die Anzeige der Produktnummer auch für Angebote zu ermöglichen.
___EN below_______
Shopping cart column "Product number" also for offers: Currently, in the backend, there is no option to display the "Product number" column in the shopping cart for offers, so that the article numbers of the added products can be viewed directly. Since this function is already available for orders, it would be useful and helpful to enable the display of the product number for offers as well.
Im Backend besteht derzeit im Warenkorb von Angeboten keine Möglichkeit, die Spalte „Produktnummer“ einzublenden, um die Artikelnummern der hinzugefügten Produkte direkt sehen zu können.
Da diese Funktion bei Aufträgen bereits verfügbar ist, wäre es sinnvoll und hilfreich, die Anzeige der Produktnummer auch für Angebote zu ermöglichen.
___EN below_______
Shopping cart column "Product number" also for offers: Currently, in the backend, there is no option to display the "Product number" column in the shopping cart for offers, so that the article numbers of the added products can be viewed directly. Since this function is already available for orders, it…
2 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.
-
JSON LD
JSON LD ist seit über einem Jahrzehnt das Standardformat, um Produktdaten in Online Shops strukturiert vorzuhalten.
Es ist deutlich einfacher zu warten, separiert die Daten klar von der Markup ... und ist von Shopware zu erwarten ;)
–
JSON LD has been the standard format for storing product data in online shops in a structured manner for over a decade.
It is much easier to maintain, clearly separates the data from the markup ... and is to be expected from Shopware ;)
9 votes -
Zusätzlicher Filter in der Bestellübersicht / Additional Filter in the Admin Orderoverview
In der Bestellübersicht wäre es hilfreich, wenn auch die Kundennummer als Spalte angezeigt werden würde. So könnte nicht nur nach Namen oder Emailadresse sondern auch nach Kundennummer sortiert werden. Das würde uns die Arbeit beim Zusammenfassen der Bestellungen deutlich erleichtern, da wir einige Kunden haben die mehrere Kundenkonten besitzen.
ENG: It would be helpful if the customer number could also be displayed as a column in the order overview. This would allow orders to be sorted not only by customer name or email address, but also by customer number. It would significantly simplify our workflow when consolidating orders, as we have several customers who maintain multiple customer accounts.
In der Bestellübersicht wäre es hilfreich, wenn auch die Kundennummer als Spalte angezeigt werden würde. So könnte nicht nur nach Namen oder Emailadresse sondern auch nach Kundennummer sortiert werden. Das würde uns die Arbeit beim Zusammenfassen der Bestellungen deutlich erleichtern, da wir einige Kunden haben die mehrere Kundenkonten besitzen.
ENG: It would be helpful if the customer number could also be displayed as a column in the order overview. This would allow orders to be sorted not only by customer name or email address, but also by customer number. It would significantly simplify our workflow when consolidating orders, as we…
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.
-
Form field company name also for B2C shops
An additional field for entering a company name should be added to the registration form. There are often B2C customers who wish to have their order delivered to their work address. An optional form field for company names is therefore required.
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.
-
Improve checkout message performance
The AI-generated checkout message sometimes takes 10 seconds to generate if there are many products in the shopping cart.
Many customers close the page during this time. It would be better if the messages were generated in the background beforehand or if a faster AI model were used.
4 votes -
Automatically remind users who abandon the shopping cart
Automatic reminder for shopping basket cancellations. Optionally with an incentive such as a discount code. Remind users who abandon their shopping basket (including guests) and optionally bring them back to the shop.
17 votes -
Inheritable category and menu visibility in organizational units (B2B)
Currently, category and product visibility settings can only be explicitly configured per category within organizational units.
When a parent category is selected, the subcategories beneath it are not automatically included.
This leads to the following problems with extensive category structures (several hundred subcategories):
- very high manual maintenance effort
- increased susceptibility to errors
- poor maintainability when structural changes are made
- limited scalability in a B2B contextIn addition, the main menu must be controlled indirectly via individual assignments to the contained categories, as a blanket menu activation is not possible.
Target Image:
- Selecting a parent category should optionally include all subcategories automatically.
- Menu visibility should be configurable independently of individual assignments.
- Reduction of administrative effort for complex B2B structures.Specific Improvement Suggestions
A) Inheritable Category Visibility
Option 1: "Include Subcategories" CheckboxWhen selecting a category in the organizational unit:
☐ Automatically include subcategories
Behavior:
- Recursively activates all child categories.
- New subcategories are automatically included.
- Optionally overridable at the subcategory level.Technically feasible:
- Flag at the category assignment level
- Recursive query in the CategoryTreeLoader
- Lazy resolution in the Visibility ResolverB) Global Menu Sharing
New option in the organizational unit:☐ Show full main menu
Behavior:
- Menu structure is displayed
- Visibility of individual products remains adjustable
- Alternatively: Combination with category filter logicOptional:
- Visibility only structural (navigation visible, product access checked)Benefits
For Customers
- Massive time savings
- Significantly improved maintainability
- Scalability for large catalogs
- Fewer misconfigurationsFor Shopware
- Stronger B2B positioning
- Reduced support requests
- Less need for custom development
- Competitive advantage with enterprise customersCurrently, category and product visibility settings can only be explicitly configured per category within organizational units.
When a parent category is selected, the subcategories beneath it are not automatically included.
This leads to the following problems with extensive category structures (several hundred subcategories):
- very high manual maintenance effort
- increased susceptibility to errors
- poor maintainability when structural changes are made
- limited scalability in a B2B contextIn addition, the main menu must be controlled indirectly via individual assignments to the contained categories, as a blanket menu activation is not possible.
Target Image:
- Selecting a parent category…4 votes -
Allow pasting prices with comma as decimal separator
Title:
Allow pasting prices with comma as decimal separatorDescription:
Currently, Shopware 6 does not accept prices that are pasted with a comma as the decimal separator.For example:
12,95 → only 12 is inserted (the decimal part is ignored)
This is inconvenient for European merchants, because prices are often copied from:
Excel
ERP systems
Supplier price lists
Websiteswhere the comma is the standard decimal separator.
Expected behavior
When a user pastes a price such as:
12,95
1234,56Shopware should automatically convert it to the correct internal decimal format instead of discarding everything after the comma.
This would improve usability significantly and prevent incorrect prices from being entered.
Benefit
Better user experience
Fewer input errors
Better support for European number formats
Faster product maintenanceTitle:
Allow pasting prices with comma as decimal separatorDescription:
Currently, Shopware 6 does not accept prices that are pasted with a comma as the decimal separator.For example:
12,95 → only 12 is inserted (the decimal part is ignored)
This is inconvenient for European merchants, because prices are often copied from:
Excel
ERP systems
Supplier price lists
Websiteswhere the comma is the standard decimal separator.
Expected behavior
When a user pastes a price such as:
12,95
1234,56Shopware should automatically convert it to the correct internal decimal format instead of discarding everything after the comma.
This would improve…
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.
-
Allow for CMS elements to be hidden on category pages when product listing page is not the first page
When a category layout contains some text or images together with the product listing element, that text or element may be indexed by search engines multiple times for each page of the listing, leading to duplicate indexing and results.
It would be helpful if certain elements could be hidden once the customer or the indexing bot navigates through the listing pages, or a URL contains the ?p= parameter. This would prevent redundant indexing.
3 votes -
sorting by publication date should also be possible ascending and descending order
When sorting products by publication date, it should also be possible to choose between ascending and descending order. Now only descending is possible
Man sollte bei der Produktsortierung nach Erscheinungsdatum auch ab- oder aufsteigend auswählen können. Aktuell nur ist nur absteigend möglich
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.
-
Option to hide editing tools in the image editor
It would be great if there were a way to hide the editing tools in the image editor.
The advantage of this is that they would no longer take up a large portion of the screen.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.
-
Incorrect plugin names and icons displayed for partner accounts
We have noticed that we see different plugin names and icons in a customer’s extension list than the customer does.
After checking, we found that the data shown to the customer is correct and matches the respective plugin definitions. When we log out of our partner account, ottscho@ottscho.de, the correct data is displayed again. As soon as we log back in, the incorrect data reappears.
It seems that plugin data is retrieved differently for partner accounts and is currently displayed incorrectly. Please investigate this issue. It is extremely inconvenient when a customer refers to a plugin that we cannot find because it is shown under a different name in our account.
In this case, the plugin is called “Gutscheine für Gratisartikel” for the customer, while it appears as “Kostenloser Artikel mit Gutschein im Warenkorb” for us. However, “Gutscheine für Gratisartikel” is the correct current name according to the composer.json file and the database.
The second plugin named “Gutscheine für Gratisartikel” also displays a different icon for us, even though the plugin was freshly installed.
Original Anfrage
Wir haben festgestellt, dass wir andere Plugin Bezeichnungen und Icons in der Erweiterungsliste eines Kunden sehen als er. Bei der Nachprüfung hat sich ergeben, dass die Daten welche der Kunde sieht die korrekten Daten aus den jeweiligen Plugin Definitionen sind. Bei ausloggen aus unserem Partner Account ottscho@ottscho.de wurden auch wieder die korrekten Daten angezeigt. Bei einloggen wieder die falschen. Scheinbar werden die Daten bei einem Partneraccount anders herangezogen, und zwar falsch. Bitte prüfen, das ist äußerst unschön, wenn der Kunde von einem Plugin spricht welches wir gar nicht finden, weil wir nach einem anderen Namen suchen.
In dem Fall war es das Plugin "Gutscheine für Gratisartikel" was bei uns "Kostenloser Artikel mit Gutschein im Warenkorb" heißt. Ersteres ist aber der korrekte aktuelle Name laut composer.json und Datenbank. Auch das zweite Plugin "Gutscheine für Gratisartikel" hat bei uns ein anderes Icon, obwohl das Plugin frisch installiert wurde
We have noticed that we see different plugin names and icons in a customer’s extension list than the customer does.
After checking, we found that the data shown to the customer is correct and matches the respective plugin definitions. When we log out of our partner account, ottscho@ottscho.de, the correct data is displayed again. As soon as we log back in, the incorrect data reappears.
It seems that plugin data is retrieved differently for partner accounts and is currently displayed incorrectly. Please investigate this issue. It is extremely inconvenient when a customer refers to a plugin that we cannot…
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.
-
Change configuration category layout / homepage configuration
Recurring support tickets indicate that the shop's homepage configuration is not centralized enough.
Firstly, the shop's homepage is determined by the category layout. Secondly, the homepage can also be set within the category itself (under the "General" tab -> "Homepage" option).
These numerous different configuration options conflict with each other and lead to unnecessary support tickets. The configuration should therefore be simplified.
5 votes
- Don't see your idea?