398 results found

1. 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.

   8 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  ·  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
   GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

2. 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

   8 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
   GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

3. Searching for customers in the admin panel using the UUID

   It would be great if, in the admin panel, you could also search for customers by their UUID in the customer overview.

   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  ·  Orders & Customers  ·  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
   GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

4. 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
   GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

5. Improve Admin search for properties

   Bei der Suche nach Artikeleigenschaften ist uns aufgefallen, dass vollständige Ausprägungen mit Leerzeichen offenbar nicht gezielt gesucht werden können.

   Ein Beispiel:

   Eigenschaft: «Masse / Grösse»
   Gesuchte Ausprägung: «14 x 14 x 38 cm»

   Idealerweise möchten wir im Feld «Ausprägungen durchsuchen» den vollständigen Wert «14 x 14 x 38 cm» eingeben und direkt die passende Ausprägung angezeigt erhalten.

   Aktuell scheint die Suche jedoch nur einzelne Bestandteile wie «14» oder «38» zu berücksichtigen. Dadurch werden sehr viele Treffer angezeigt und die gewünschte Ausprägung muss manuell gesucht werden.

   Könnt ihr bitte prüfen, ob die Suche nach vollständigen Ausprägungen inklusive Leerzeichen und Sonderzeichen irgendwie möglich gemacht werden kann. Es ist so sehr umständlich, gerade wenn man z.B eine Zahl sucht, die in 100en von Einträgen vorkommt.

   Bei der Suche nach Artikeleigenschaften ist uns aufgefallen, dass vollständige Ausprägungen mit Leerzeichen offenbar nicht gezielt gesucht werden können.

   Ein Beispiel:

   Eigenschaft: «Masse / Grösse»
   Gesuchte Ausprägung: «14 x 14 x 38 cm»

   Idealerweise möchten wir im Feld «Ausprägungen durchsuchen» den vollständigen Wert «14 x 14 x 38 cm» eingeben und direkt die passende Ausprägung angezeigt erhalten.

   Aktuell scheint die Suche jedoch nur einzelne Bestandteile wie «14» oder «38» zu berücksichtigen. Dadurch werden sehr viele Treffer angezeigt und die gewünschte Ausprägung muss manuell gesucht werden.

   Könnt ihr bitte prüfen, ob die Suche nach vollständigen Ausprägungen inklusive Leerzeichen und Sonderzeichen irgendwie… 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  ·  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
   GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering 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.

6. 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.

   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  ·  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
   GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

7. 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
   GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

8. Offline/Developer mode for the commercial plugin in local development environments

   Partners and agencies often work on multiple client projects simultaneously. Consequently, a local development environment may contain extensions for various clients, even though those extensions are neither actively used nor tested there.

   The commercial plugin currently checks installed extensions and their license status but cannot distinguish between an extension that is merely part of the local development environment and one that is actually in use. In development environments, this can lead to unexpected license checks or subsequent actions.

   An optional offline or developer mode for local development environments—intended exclusively for non-production systems—would be beneficial. Alternatively, a way to clearly designate local development environments as such would help, allowing license checks to be adjusted accordingly.

   Added value:
   - Better support for agencies and partners managing multiple client projects.
   - Fewer unintended license conflicts in local development environments.
   - Improved developer experience with no impact on production systems.

   Partners and agencies often work on multiple client projects simultaneously. Consequently, a local development environment may contain extensions for various clients, even though those extensions are neither actively used nor tested there.

   The commercial plugin currently checks installed extensions and their license status but cannot distinguish between an extension that is merely part of the local development environment and one that is actually in use. In development environments, this can lead to unexpected license checks or subsequent actions.

   An optional offline or developer mode for local development environments—intended exclusively for non-production systems—would be beneficial. Alternatively, a way to clearly designate… 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  ·  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
   GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering 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.

9. 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
   GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

10. 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
    GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

11. Import/Export Cheapest price (last 30 days)

    There should be a way to import/export the cheapest price (last 30 days).

    There is a regulationPrice in the price field for this purpose, but it cannot currently be mapped.

    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

    2 comments  ·  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
    GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

12. 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
    GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

13. Allow approvers to edit orders in B2B-Approval-Workflows

    Problem Description:

    In the current B2B approval workflow, users with an Approver can only approve or reject orders that are subject to approval rules.

    Even if the role permissions are explicitly set to allow order-related actions, the approver cannot make any changes to the order before approving it.

    This is a limitation for real-world B2B processes, where ordering mistakes are common and must be corrected by the approver instead of rejecting and recreating the order.

    Current Behavior:

    When an order requires approval:
    - The approver can only approve or reject the order
    - The approver cannot:
    - Change product quantities
    - Remove order positions
    - Change payment method
    - Change shipping method
    - Edit billing or shipping addresses
    - Write a comment on the order, regardless of approval

    This behavior applies even if the corresponding permissions are assigned to the approver role.

    Expected Behavior:

    Approvers should be able to edit an order before approval, according to the permissions defined for their role.

    If the role permissions allow it, an approver should be able to:
    - Remove order line items
    - Adjust product quantities
    - Change payment method
    - Change shipping method
    - Edit billing and shipping addresses
    - Regardless of approval or rejection, write a comment on the order

    The approval decision (approve/reject) should then apply to the modified order.

    Business Impact:

    In B2B commerce, approval workflows are meant to:
    - Correct ordering mistakes
    - Ensure compliance with company rules
    - Avoid unnecessary rejections and re-orders

    Restricting approvers to only approve or reject orders leads to:
    - Inefficient workflows
    - Increased manual effort
    - Poor user experience for B2B customers

    This behavior does not reflect common B2B purchasing processes, where approvers are expected to correct errors rather than reject orders entirely.

    Problem Description:

    In the current B2B approval workflow, users with an Approver can only approve or reject orders that are subject to approval rules.

    Even if the role permissions are explicitly set to allow order-related actions, the approver cannot make any changes to the order before approving it.

    This is a limitation for real-world B2B processes, where ordering mistakes are common and must be corrected by the approver instead of rejecting and recreating the order.

    Current Behavior:

    When an order requires approval:
    - The approver can only approve or reject the order
    - The approver cannot:
    - Change product quantities… 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

    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
    GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

14. Product visibility options in dynamic product group

    EN
    If a product’s visibility is set to ‘Hide in product lists and search’, the product will not be displayed in the storefront. If a dynamic product group is to be used for a product comparison or product export that includes these products, then
    - the shop operator has no way of querying the product visibility settings
    - the products are exported in a feed and are therefore visible (externally) after all.

    DE
    
    Wenn in einem Produkt die Produktsichtbarkeit auf in Produklisten und Suche ausblenden gestellt ist, werden die Produkt in der Storefront entsprechend nicht angezeigt. Wenn eine Dynamische Produktgruppe für einen Produktvergleicht / Produktexport genutzt werden soll, in dem diese Produkte enthalten sind, dann
    - gibt es für den Shopbetreiber keine Möglichkeit die Optionen der Produktsichtbarkeit abzufragen
    - die Produkte werden in einem Feed exportiert und somit dann doch (extern) sichtbar.

    EN
    If a product’s visibility is set to ‘Hide in product lists and search’, the product will not be displayed in the storefront. If a dynamic product group is to be used for a product comparison or product export that includes these products, then
    - the shop operator has no way of querying the product visibility settings
    - the products are exported in a feed and are therefore visible (externally) after all.

    DE
    
    Wenn in einem Produkt die Produktsichtbarkeit auf in Produklisten und Suche ausblenden gestellt ist, werden die Produkt in der Storefront entsprechend nicht angezeigt. Wenn eine Dynamische Produktgruppe… 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  ·  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
    GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

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

    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

    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
    GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

16. 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
    GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

17. 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

    15 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
    GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

18. 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
    GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

19. Reintroduce CLI commands (functionality) for Migrations

    CLI commands for migrations have been removed from release 16 (see https://github.com/shopware/shopware/issues/10825) without proper replacement.

    As a result it is currently not possible to migrate with a finer selection via the CLI. One has to select an entire data category (i.e. all products) to migrate, making it more difficult and time-consuming in larger shops to debug issues.

    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

    0 comments  ·  Migration & Im-/Export  ·  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
    GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering 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.

20. 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
    GATHERING FEEDBACK  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering 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.