1561 results found

1. More options for the listing of variants

   It would be great if there were more options for choosing which variant to display in the storefront.

   For example:
   - Lowest-priced variant
   - Best-selling variant
   - Variant with the highest stock
   - General Rule Builder rules and filter options

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Products, Prices & Properties  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Add CC, BCC and Reply-to features to the mail function in the flow builder

   Shop admins should have the possibility to define CC and BCC contacts in the mail send function within the flow builder, as well as have the option to define a reply-to address that is used whenever a customer tries to reply to a mail.

   41 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   IN RESEARCH  ·  4 comments  ·  Content management  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Change the link for the cancellation button

   Currently, the cancellation button links to a long and rather unfriendly URL.

   It would be helpful if we could set a custom URL for the cancellation page, such as /cancel-contract or /cancellation

   This would make the link easier for customers to understand and create a more consistent shopping experience in the store.

   5 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  SEO  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Legally compliant integration of EU Guarantee and Warranty Labels (EU 2024/825 & 2025/1960)

   Beschreibung:
   Ab dem 27. September 2026 müssen B2C-Online-Shops in der EU die neuen, standardisierten Gewährleistungs- und Garantielabel (GARAN-Label) anzeigen. Um Händler vor Abmahnrisiken zu schützen, sollte Shopware hierfür eine native Core-Lösung bereitstellen.

   Folgende Anforderungen sind für eine automatisierte und rechtssichere Umsetzung notwendig:

   1. Globale Steuerung & Checkout-Einbindung für das Gewährleistungslabel: Da das gesetzliche Gewährleistungslabel für jeden B2C-Artikel verpflichtend ist, muss Shopware eine flexible, globale Ausgabe ermöglichen. Händler müssen die Wahl haben, das statische Gewährleistungslabel entweder direkt auf der Produktdetailseite ODER gesammelt im Checkout unmittelbar vor dem finalen „Jetzt kaufen“-Button (z. B. im Bereich der AGB-/Widerrufs-Checkboxen) anzeigen zu lassen.

   2. Produktspezifische Einbindung des Garantielabels (Backend): Die Pflicht für das Garantielabel gilt nur für Artikel, bei denen der Hersteller eine Garantie von mehr als 2 Jahren gewährt. Im Backend (Produktstamm) muss es die Option geben, dieses Label pro Artikel zu hinterlegen.

   Shopware sollte hier zwei Wege unterstützen:

   • Option A (Datei-Upload): Ein Medienfeld, um eine vom Hersteller fertig bereitgestellte Label-Grafik (SVG/PNG) direkt am Produkt hochzuladen.

   • Option B (Dynamisches Rendering): Datenfelder für die Rohdaten (Herstellername, Modellkennung, Garantiedauer), aus denen Shopware das Label standardkonform generiert.

   Eine Bulk-Edit- und Import/Export-Funktion für diese Daten/Zuweisungen ist zwingend erforderlich.

   1. Frontend-Ausgabe (CMS / Erlebniswelten): Bereitstellung von responsive CMS-Blöcken/Elementen für die Produktdetailseite. Für das Garantielabel muss auch ein rechtssicheres, geschachteltes Format (z. B. vollständige Anzeige erst bei Mouseover/Klick auf ein kompaktes Siegel) unterstützt werden, da die EU dies für Online-Interfaces ausdrücklich erlaubt.

   2. Internationalisierung (Mehrsprachigkeit): Automatische Bereitstellung der offiziellen EU-Textbausteine und Label-Vorlagen für alle EU-Sprachen über das native Snippet-System.

   3. Dauerhafter Datenträger (Flow Builder / Mail): Automatisierte Einbindung der produktspezifischen Labels in die Bestellbestätigungs-E-Mail (z. B. via Flow Builder als Bedingung), da Händler verpflichtet sind, diese Informationen nach dem Kauf auf einem dauerhaften Datenträger bereitzustellen.

   Da es sich hierbei um eine harte gesetzliche Pflicht für alle EU-Händler handelt, wäre eine native Integration ein enormer Mehrwert für das gesamte Shopware-Ökosystem.

   ---

   English Version:

   Description:
   Starting September 27, 2026, B2C e-commerce merchants in the EU are legally required to display the new, highly standardized harmonized notice (warranty label) and harmonized label (commercial guarantee of durability / GARAN-label). To protect merchants from severe legal risks, Shopware should implement a native core solution.

   The following technical requirements are necessary for a compliant and automated implementation:

   1. Global Control & Checkout Placement for the Warranty Label: Since the legal warranty notice is mandatory for every B2C product, Shopware must provide flexible, global rendering options. Merchants need the ability to display the static warranty notice either directly on the product detail page OR globally in the checkout flow right before the final "Buy now" button.

   2. Product-Specific Integration of the Guarantee Label (Backend): The commercial guarantee label is only required if a manufacturer provides a guarantee of more than 2 years. In the product catalog, Shopware should offer a flexible way to assign this label per item, supporting two methods:

   • Option A (File Upload): A media field to upload a pre-made label graphic (SVG/PNG) provided directly by the manufacturer.

   • Option B (Dynamic Rendering): Fields for raw data (manufacturer name, model identifier, guarantee duration) where Shopware dynamically renders the standardized layout.
     Bulk-edit and import/export capabilities for these fields/assignments are essential.

   1. Frontend Rendering (CMS / Shopping Experiences): Ready-to-use CMS blocks for the product detail page. For the guarantee label, a compliant nested format (e.g., expanding the full label via mouseover/click on a compact badge) must be supported, as explicitly allowed by EU regulations for online interfaces.

   2. Internationalization (Localization): Native integration of the official EU text elements and label templates for all EU languages within the Shopware snippet system.

   3. Durable Medium (Flow Builder / Order Confirmation Mail): Automated inclusion of the product-specific labels in the order confirmation email (e.g., via Flow Builder conditions), as merchants are legally required to provide this information post-purchase on a durable medium.

   Since this is a mandatory legal requirement for all B2C merchants selling within the EU, a native core implementation would provide immense value to the entire Shopware ecosystem.

   Beschreibung:
   Ab dem 27. September 2026 müssen B2C-Online-Shops in der EU die neuen, standardisierten Gewährleistungs- und Garantielabel (GARAN-Label) anzeigen. Um Händler vor Abmahnrisiken zu schützen, sollte Shopware hierfür eine native Core-Lösung bereitstellen.

   Folgende Anforderungen sind für eine automatisierte und rechtssichere Umsetzung notwendig:

   1. Globale Steuerung & Checkout-Einbindung für das Gewährleistungslabel: Da das gesetzliche Gewährleistungslabel für jeden B2C-Artikel verpflichtend ist, muss Shopware eine flexible, globale Ausgabe ermöglichen. Händler müssen die Wahl haben, das statische Gewährleistungslabel entweder direkt auf der Produktdetailseite ODER gesammelt im Checkout unmittelbar vor dem finalen „Jetzt kaufen“-Button (z. B. im Bereich der AGB-/Widerrufs-Checkboxen) anzeigen zu lassen.

   2. Produktspezifische Einbindung des… more

   5 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   STARTED  ·  0 comments  ·  System & Settings  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Shopware App for mobiles

   Please note that most competitors have an app for mobile, to follow some real time KPI statistics. That would make sense for Shopware to have. what are the thoughts about that from Shopware?

   12 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  User Experience  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Custom fields from apps cannot be repositioned.

   Custom fields from apps cannot be repositioned. This means that, for example, such fields end up in product locations that are potentially completely unsuitable and irrelevant.

   According to the software vendor, this is due to the Shopware core. This should be adjusted.

   Feedback from the manufacturer:
   "If you create custom fields within an app, these cannot be edited in the Shopware admin panel. This is a limitation of Shopware, and unfortunately, we cannot change it. Within an app, custom fields are only 'defined' in an XML file. No programming is done here to determine how and where the field is displayed. This is decided by Shopware in the core."

   Custom fields from apps cannot be repositioned. This means that, for example, such fields end up in product locations that are potentially completely unsuitable and irrelevant.

   According to the software vendor, this is due to the Shopware core. This should be adjusted.

   Feedback from the manufacturer:
   "If you create custom fields within an app, these cannot be edited in the Shopware admin panel. This is a limitation of Shopware, and unfortunately, we cannot change it. Within an app, custom fields are only 'defined' in an XML file. No programming is done here to determine how and where the field is… more

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  App System  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Digital Sales Room - Live Queue & Direct Call Functionality

   Enhance the Digital Sales Room by introducing a real-time interaction feature (Button Frontend) that allows customers to directly request live consultations with available presenters, including a queue system for managing demand.

   Use Case Example:

   A customer browsing the Onlineshop has a question about a product or offering. Instead of waiting for a scheduled session, they can immediately request a consultation. If no presenter is available, they are placed in a queue and connected as soon as possible.

   This feature would significantly enhance the flexibility and usability of the Digital Sales Room, turning it into a hybrid tool that supports both events and real-time customer engagement.

   Enhance the Digital Sales Room by introducing a real-time interaction feature (Button Frontend) that allows customers to directly request live consultations with available presenters, including a queue system for managing demand.

   Use Case Example:

   A customer browsing the Onlineshop has a question about a product or offering. Instead of waiting for a scheduled session, they can immediately request a consultation. If no presenter is available, they are placed in a queue and connected as soon as possible.

   This feature would significantly enhance the flexibility and usability of the Digital Sales Room, turning it into a hybrid tool that supports both… more

   5 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Digital Sales Rooms  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Admin: ability to display all products of category including subcategories

   Currently, one cannot display all products from a category including subcategories in the administration. Both the filter on the product page and the assigned products page of the category will only display directly assigned products.

   It would be helpful to have a filter option to display products of subcategories as well. Otherwise, one would need to use workarounds via dynamic product groups, the API, or Import/Export.

   5 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  User Experience  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Customize Search Results in the Admin (Quick Results)

   If, for example, a company name is searched for using the search bar within the admin interface, a small window appears displaying—among other things—customer names. However, only the first and last names are displayed, not the company name itself. Since it cannot be entirely ruled out that customer names unrelated to the searched company might also be displayed, the company name should be included in this list as well.

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Search  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. B2B Components: allow modification of Employee invite timeout

    Currently there is a hard coded timeout of 2 hours when employees are invited into an organization in B2B Components. Shop owners and potentially customers should be able to modify this time to fit their needs.

    10 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    IN RESEARCH  ·  0 comments  ·  B2B  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Enhanced Pricing Flexibility for Subscriptions

    Current Limitation
    At the moment, the same base product price is used for both one-time purchases and subscription purchases. This limits flexibility in commercial models and pricing strategies.

    Requested Enhancements

    Option to Hide the One-Time Purchase Price
    It should be possible to hide the one-time purchase option entirely for products that are primarily intended to be sold as subscriptions. This would allow merchants to position certain products as “subscription-only” without displaying a regular purchase alternative.

    Individual Pricing per Subscription Interval
    If the one-time purchase price remains visible, merchants should have the ability to define separate prices per subscription interval (e.g., monthly, quarterly, yearly).
    Currently, the same product price is used as the calculation basis for both one-time and subscription models, regardless of the selected interval.

    Example Use Case

    One-time purchase: €25.000
    Monthly subscription: €480
    Quarterly subscription: €985
    Annual subscription: €2.500

    In addition to pricing flexibility, we require enhanced control over how shipping costs are calculated for subscription products.

    Requested Options

    Merchants should be able to configure whether shipping costs are:

    Charged for every subscription delivery,

    Charged only once (e.g., for the initial order), or

    Charged upfront for the minimum subscription interval (e.g., calculated once for the full minimum term).

    Currently, there is no flexible configuration for subscription-specific shipping logic.

    Current Limitation
    At the moment, the same base product price is used for both one-time purchases and subscription purchases. This limits flexibility in commercial models and pricing strategies.

    Requested Enhancements

    Option to Hide the One-Time Purchase Price
    It should be possible to hide the one-time purchase option entirely for products that are primarily intended to be sold as subscriptions. This would allow merchants to position certain products as “subscription-only” without displaying a regular purchase alternative.

    Individual Pricing per Subscription Interval
    If the one-time purchase price remains visible, merchants should have the ability to define separate prices per subscription interval (e.g.,… more

    7 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Checkout  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Custom coupon codes as variables

    It should be possible to automatically send individual coupon codes via email, for example, as a variable in email templates.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Marketing & Promotions  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. E-invoice for partial cancellation invoice

    It is currently not possible to issue a partial cancellation for a ZUGFeRD invoice. This is a necessary part of daily operations, particularly when the invoice is paid at the time of the order—for instance, via PayPal Checkout.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  System & Settings  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Expanding the Electronic Revocation Function

    Current status:
    Only the standard Shopware order number field is usable.

    Problem:
    - In professional setups, the ERP system is often the primary system.
    - The Shopware order number is not relevant internally.
    - A custom field is used instead for the ERP order number.
    - The back office works exclusively with this ERP number.

    Suggested improvement:
    - Offer a choice in the admin panel:
    - Either the standard Shopware order number
    - Or a selectable custom field (e.g., ERP order number)
    - Ideally, as a dropdown menu option in the admin panel.

    Background:
    Larger retailers with multiple sales channels often use an ERP system. Therefore, this is not an isolated case.

    Current status:
    Only the standard Shopware order number field is usable.

    Problem:
    - In professional setups, the ERP system is often the primary system.
    - The Shopware order number is not relevant internally.
    - A custom field is used instead for the ERP order number.
    - The back office works exclusively with this ERP number.

    Suggested improvement:
    - Offer a choice in the admin panel:
    - Either the standard Shopware order number
    - Or a selectable custom field (e.g., ERP order number)
    - Ideally, as a dropdown menu option in the admin panel.

    Background:
    Larger retailers with multiple sales channels… more

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    DECLINED  ·  3 comments  ·  B2B  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Inheritance of elements in CMS pages

    DE:
    Aktuelle Systematik seitens Shopware:

    Man kann CMS-Seiten erstellen und in diesen innerhalb Sektionen verschiedene Blöcke und Elemente definieren. Nun habe ich die Möglichkeit in Kategorien entweder für jede Seite ein eigenes CMS-Layout zuzuweisen. Ebenso kann man aber auch das gleiche CMS-Layout mehreren Seiten zuweisen. Hier hat man dann die Möglichkeit die Inhalte der im Layout festgelegten Elemente zu individualisieren.

    Nun entsteht dadurch folgende Problematik:

    Angenommen ich habe 50 Kategorie-Seiten, welche alle das gleiche vorgegebene CMS-Layout nutzen. Dann habe ich nur die Möglichkeit die Inhalte der Blöcke/Elemente zu bearbeiten, kann aber nicht die Blöcke/Sektionen auf diverse Unterseiten vererben.

    Sollte somit z.B. der Fall auftreten, dass ich von 10 dieser 50 Seiten mit dem gleichen Layout an erster Stelle keinen Slider mehr möchte (aber das restliche Layout soll beibehalten werden, bzw. der Aufbau aller darauf folgenden Elemente), so ist aktuell die einzige Möglichkeit für diese 10 Unterseiten neue Layouts anzulegen.

    Diese Problematik lässt sich nun hochskalieren. Nehmen wir nun an, wir wollen von den 50 Seiten, auf 10 Seiten an erster Stelle keinen Slider und von diesen 10 Seiten soll bei 4 Seiten an letzter Stelle ein anderes Element sein, müsste ich nochmals diese 4 Seiten neu erstellen.

    Obwohl von diesen 50 Seiten das Grundlayout bis auf einige Blöcke identisch ist, muss ich aktuell für jegliche Abweichung am Grundlayout neue eigene Seiten erstellen und kann nicht festlegen, dass z.B. Sektionen in einem CMS-Layout vererbbar sind.

    Über eine Lösung seitens Shopware würden wir uns sehr freuen, das würde die Contentbearbeitung bei umfangreichen Inhalten mit mehr als 1000 Seiten enorm vereinfachen und wäre ein wirklicher Mehrwert.

    ENG:
    It is possible to create CMS pages and define different blocks and elements within sections. Categories can either be assigned their own individual CMS layout per page, or the same CMS layout can be assigned to multiple pages. In this case, the content of the elements defined in the layout can be customized individually.

    This leads to the following problem:

    Assume there are 50 category pages that all use the same predefined CMS layout. In this scenario, it is only possible to edit the content of the blocks and elements, but it is not possible to inherit blocks or sections across different subpages.

    For example, if on 10 of these 50 pages the slider should no longer appear as the first element (while the rest of the layout, including the structure of all subsequent elements, should remain the same), the only current solution is to create new layouts for these 10 subpages.

    This issue can be scaled further. If, for instance, out of the 50 pages, 10 pages should not have a slider as the first element, and out of those 10 pages, 4 pages should have a different element at the last position, those 4 pages would again need to be created separately.

    Although the base layout of these 50 pages is largely identical except for a few blocks, any deviation from the base layout currently requires creating entirely new pages. It is not possible to define sections within a CMS layout as inheritable.

    We would greatly appreciate a solution from Shopware, as this would significantly simplify content management for large setups with more than 1,000 pages and would provide real added value.

    DE:
    Aktuelle Systematik seitens Shopware:

    Man kann CMS-Seiten erstellen und in diesen innerhalb Sektionen verschiedene Blöcke und Elemente definieren. Nun habe ich die Möglichkeit in Kategorien entweder für jede Seite ein eigenes CMS-Layout zuzuweisen. Ebenso kann man aber auch das gleiche CMS-Layout mehreren Seiten zuweisen. Hier hat man dann die Möglichkeit die Inhalte der im Layout festgelegten Elemente zu individualisieren.

    Nun entsteht dadurch folgende Problematik:

    Angenommen ich habe 50 Kategorie-Seiten, welche alle das gleiche vorgegebene CMS-Layout nutzen. Dann habe ich nur die Möglichkeit die Inhalte der Blöcke/Elemente zu bearbeiten, kann aber nicht die Blöcke/Sektionen auf diverse Unterseiten vererben.

    Sollte somit… more

    9 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Content management  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Highlight incomplete CAPTCHA field in checkout

    In the current Shopware SaaS checkout, which uses FriendlyCaptcha, users sometimes overlook the CAPTCHA field. After filling out all required fields, they attempt to continue the checkout process, but nothing happens. There is no indication that the CAPTCHA is missing.

    While other required fields are highlighted in red or otherwise marked when incomplete, the CAPTCHA field does not receive any visual feedback. This can lead to confusion and interrupt the checkout experience.

    It is therefore suggested that the CAPTCHA field be visually highlighted (e.g., marked in red) when it has not been completed, consistent with the behavior of other required fields. This improvement could help ensure a smoother and clearer checkout flow for users.

    In the current Shopware SaaS checkout, which uses FriendlyCaptcha, users sometimes overlook the CAPTCHA field. After filling out all required fields, they attempt to continue the checkout process, but nothing happens. There is no indication that the CAPTCHA is missing.

    While other required fields are highlighted in red or otherwise marked when incomplete, the CAPTCHA field does not receive any visual feedback. This can lead to confusion and interrupt the checkout experience.

    It is therefore suggested that the CAPTCHA field be visually highlighted (e.g., marked in red) when it has not been completed, consistent with the behavior of other required… more

    11 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Checkout  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Passwortfelder in Storefront mit "Passwort anzeigen"-Funktion ausstatten

    In der Shopware-Storefront wäre es hilfreich, Passwortfelder standardmäßig mit einer Möglichkeit zum Ein- und Ausblenden des eingegebenen Passworts auszustatten, z. B. über ein Auge-Icon.

    Das betrifft insbesondere:

    Passwort-Wiederherstellung
    Login / Registrierung

    Aus UX-Sicht ist das inzwischen ein verbreitetes Pattern und hilft Kunden, Tippfehler zu vermeiden. Gerade bei der Passwort-Wiederherstellung müssen Nutzer neue Passwörter oft mehrfach eingeben, wodurch eine Sichtbarkeitsoption die Bedienbarkeit verbessern würde.

    Wichtig wäre, dass dies nur eine reine Frontend-Funktion ist und keine Änderung an Passwortlogik, Validierung, Sicherheit oder Speicherung vornimmt.

    EN: In the Shopware Storefront, it would be helpful if password fields included an option to show and hide the entered password by default, for example via an eye icon.

    This applies in particular to:

    Password recovery
    Login / registration

    From a UX perspective, this has become a common pattern and helps customers avoid typos. Especially during password recovery, users often have to enter new passwords multiple times, so a visibility toggle would improve usability.

    It would be important that this remains a purely frontend feature and does not change any password logic, validation, security, or storage.

    In der Shopware-Storefront wäre es hilfreich, Passwortfelder standardmäßig mit einer Möglichkeit zum Ein- und Ausblenden des eingegebenen Passworts auszustatten, z. B. über ein Auge-Icon.

    Das betrifft insbesondere:

    Passwort-Wiederherstellung
    Login / Registrierung

    Aus UX-Sicht ist das inzwischen ein verbreitetes Pattern und hilft Kunden, Tippfehler zu vermeiden. Gerade bei der Passwort-Wiederherstellung müssen Nutzer neue Passwörter oft mehrfach eingeben, wodurch eine Sichtbarkeitsoption die Bedienbarkeit verbessern würde.

    Wichtig wäre, dass dies nur eine reine Frontend-Funktion ist und keine Änderung an Passwortlogik, Validierung, Sicherheit oder Speicherung vornimmt.

    EN: In the Shopware Storefront, it would be helpful if password fields included an option to show and… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  User Experience  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Automated Calculation of Fees (Customs & Taxes) in Checkout for International Orders

    Currently, Shopware 6 does not provide a native feature for automatically calculating variable fees such as customs duties, import taxes, or country-specific charges during checkout.
    However, this functionality is increasingly important for international merchants to ensure a legally compliant and transparent order process.

    Competing platforms (e.g., Shopify) already offer this functionality as a built-in feature. It enables automated calculation and display of additional fees (e.g., customs duties, import VAT, service fees) based on product value, shipping destination, product category, or customs tariff number (HS code).

    In Shopware, this can currently only be achieved through manual configuration using the shipping method price matrix, which is not dynamic and cannot handle complex calculation logic (e.g., article-based or country-based variations). Additionally, surcharges added via the price matrix are included in the cart subtotal, leading to incorrect tax and duty calculations when these are applied again on top.

    Use Cases:

    • International Shipping: Merchants shipping outside the EU (e.g., to the US, UK, Canada, or Switzerland) need to automatically calculate and display customs and import duties.

    • Legal Compliance & Transparency: Customers should be informed of all applicable fees during checkout to prevent unexpected costs or returns.

    • Automation & Efficiency: Merchants want to automate fee calculation via integrations with external tax or logistics services (e.g., Avalara, Zonos, FedEx API, etc.) rather than maintaining manual tables.

    • Competitive Edge: Competing eCommerce systems like Shopify or BigCommerce already include this capability, putting Shopware at a disadvantage, especially for international merchants.

    Suggested Implementation:

    • Introduce a dynamic fee calculation module within checkout, based on:

      • Shipping destination
      • Product item data (including tariff/HS code)
      • Total cart value
      • Potentially also carrier or fulfillment method

    • Provide API endpoints and plugin interfaces for integrating external tax or customs calculation services.

    • Add configurable admin settings to define:

      • Which fee types should be calculated (customs, taxes, service fees, etc.)
      • Whether the fees should be shown in the cart or added during checkout only.

    • The technical foundation could be a core-level extensibility module that third-party providers can build upon.

    Benefits:

    • Increased legal compliance for international trade.

    • Transparent cost display for customers.

    • Reduced cart abandonment rates due to unexpected delivery charges.

    • Improved competitiveness and attractiveness for global and enterprise merchants.

    Currently, Shopware 6 does not provide a native feature for automatically calculating variable fees such as customs duties, import taxes, or country-specific charges during checkout.
    However, this functionality is increasingly important for international merchants to ensure a legally compliant and transparent order process.

    Competing platforms (e.g., Shopify) already offer this functionality as a built-in feature. It enables automated calculation and display of additional fees (e.g., customs duties, import VAT, service fees) based on product value, shipping destination, product category, or customs tariff number (HS code).

    In Shopware, this can currently only be achieved through manual configuration using the shipping method… more

    14 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Checkout  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Option for B2B Components order related mails send to customer Orga employee mail

    In B2B environments, orders are often placed by employees acting on behalf of their organization. Currently, Shopware sends order confirmation emails only to the primary email address of the customer account (Main Account).

    However, in many cases, it is desirable for the employee who submitted the order to also receive — or solely receive — the order confirmation email or documents.

    To address this, a new configuration option should be added to the customer or organization settings, allowing administrators to define the default behavior for order confirmation emails.

    Functional Proposal:

    Add a setting in the B2B customer configuration:

    Option A: Send order confirmation to the organization’s main (default) email address.

    Option B: Send order confirmation to the email address of the employee who placed the order.

    The setting should be adjustable per organization.

    Optionally, allow sending to both addresses.

    In B2B environments, orders are often placed by employees acting on behalf of their organization. Currently, Shopware sends order confirmation emails only to the primary email address of the customer account (Main Account).

    However, in many cases, it is desirable for the employee who submitted the order to also receive — or solely receive — the order confirmation email or documents.

    To address this, a new configuration option should be added to the customer or organization settings, allowing administrators to define the default behavior for order confirmation emails.

    Functional Proposal:

    Add a setting in the B2B customer configuration:

    Option A:… more

    9 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  B2B  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Warning in Administration when APP_DEBUG=1 is enabled in production environment

    In a productive Shopware 6 installation, APPDEBUG=1 may temporarily be enabled during troubleshooting and then unintentionally remain active afterward. Based on our findings, this causes Shopware to output a noindex directive in the storefront, even when APPENV=prod is explicitly set.

    This creates a critical SEO risk because the issue can easily go unnoticed and may ultimately lead to the shop being removed from the Google index.

    Problem:
    Currently, there seems to be no visible warning in the Administration when a production environment is running with APP_DEBUG=1

    Expected Behavior:
    If APPENV=prod and APPDEBUG=1 are detected at the same time, Shopware should clearly warn administrators about this potentially dangerous configuration.

    Possible implementations could include:
    - a visible warning message in the Administration dashboard
    - a dedicated system health check
    - a notification explaining the potential SEO impact

    Benefit:
    Such a warning would help prevent accidental SEO issues caused by forgotten debug configurations in production environments.

    In a productive Shopware 6 installation, APPDEBUG=1 may temporarily be enabled during troubleshooting and then unintentionally remain active afterward. Based on our findings, this causes Shopware to output a noindex directive in the storefront, even when APPENV=prod is explicitly set.

    This creates a critical SEO risk because the issue can easily go unnoticed and may ultimately lead to the shop being removed from the Google index.

    Problem:
    Currently, there seems to be no visible warning in the Administration when a production environment is running with APP_DEBUG=1

    Expected Behavior:
    If APPENV=prod and APPDEBUG=1 are detected at the… more

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  System & Settings  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating