1461 results found

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

   28 votes

   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  ·  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

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

   7 votes

   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

3. 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?

   7 votes

   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

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

   11 votes

   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

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

   7 votes

   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

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

   8 votes

   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

7. Shopware Analytics - Beta Phase

   Following the launch of the first iteration of Shopware Analytics, we are continuing to develop the next iterations, which will further enhance functionalities. Additionally, we will steadily introduce a series of new dashboards featuring more metric visualizations. These updates will be rolled out independently of Shopware minor releases, leveraging the flexibility of our App-based service.

   We invite you to explore the new features of Shopware Analytics and share your feedback. Your insights and feedback will be considered during development to ensure continuous improvement.

   Here you can find the original feedback, which was the base of the first iteration: https://feedback.shopware.com/forums/942607/suggestions/45651289

   •  

   89 votes

   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

   182 comments  ·  Analytics & Dashboards  ·  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
   STARTED  ·  AdminTim Jurchen (Product Manager Shopware Core, shopware AG) responded

   We already started the further development and already added new statistics:

   Added a new KPI “Promotion codes”

   Added a new KPI “Sales by manufacturer”

   Added a new KPI Sales by country

   Added a new KPI Best selling products

   UI enhancements and technical improvements

8. Checkbox für AGB entfernen, weil rechtlich unnötig

   Laut https://www.heise.de/hintergrund/Warum-im-Netz-Checkboxen-fuer-AGB-und-Datenschutz-meist-ueberfluessig-sind-10449542.html braucht man keine Checkboxen für Datenschutzerklärung und AGB.

   Durch das Entfernen der Checkbox für die AGB im Checkout ist der Checkout viel schneller und einfacher.

   Bei der verlinkten Seite sind Formulierungen für den Text angegeben. Ohne Checkbox muss der Text angepasst werden.

   Viele Besucher übersehen die Checkbox, klicken auf den Kaufen-Button und bekommen dann eine Fehlermeldung, dass sie erst einen Haken setzen müssen.

   15 votes

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

9. Revocation button for Online-Shops

   The revocation button for online stores will become mandatory in the near future. You should therefore keep an eye on this now.

   https://www.versandhandelsrecht.de/2024/03/27/widerrufsbutton/

   https://www.golem.de/news/neuerungen-bei-onlinekaeufen-der-widerrufs-button-kommt-2507-197913.html

   https://www.bmjv.de/SharedDocs/Gesetzgebungsverfahren/DE/2025_GAendVVVR.html?nn=110490

   15 votes

   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

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

    5 votes

    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  ·  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

11. Quantity-based surcharges in Custom Products

    Current Situation / Problem:
    Custom Products allow merchants to offer additional services or configurations (e.g. sawing, drilling, processing) with fixed surcharges per selected option.
    These surcharges are currently static and independent of the ordered quantity of the main product.

    While tiered pricing can be configured on the product level, it cannot be applied to Custom Product options or their surcharges.

    Concrete Use Case
    A merchant sells steel beams (e.g. HEB / HEA) and offers optional processing services via Custom Products.

    Example: Option “Sawing”

    • Sub-options: Fixed cut, Center cut, Mitre cut
    • Current behavior: fixed surcharge, e.g. €15 per cut

    Desired behavior:
    The price per cut should change depending on the ordered quantity of the main product, for example:

    • 1–3 items → €15 per cut
    • 4–10 items → €10 per cut
    • 11+ items → €7 per cut

    The price tier is not based on the number of selected options, but on the product quantity in the cart.

    Why Existing Features Are Not Sufficient:
    - Advanced pricing on the product level applies globally to the product quantity, but does not affect Custom Product surcharges
    - Rule-based surcharges can be enabled or disabled, but do not support tiered pricing
    - Product variants are not a viable alternative because:
    - They would result in a very large number of variants
    - Custom Products are intentionally used for flexible, customer-specific configurations

    Business Value / Benefits:
    Relevant use case for:
    - Metal processing
    - Cutting and machining services
    - Printing, engraving, personalization

    Key benefits:
    - Realistic representation of volume-based discounts for services
    - Reduction of manual pricing agreements and individual offers
    - Increased competitiveness for B2B shops

    Avoidance of workarounds or external pricing logic

    Current Situation / Problem:
    Custom Products allow merchants to offer additional services or configurations (e.g. sawing, drilling, processing) with fixed surcharges per selected option.
    These surcharges are currently static and independent of the ordered quantity of the main product.

    While tiered pricing can be configured on the product level, it cannot be applied to Custom Product options or their surcharges.

    Concrete Use Case
    A merchant sells steel beams (e.g. HEB / HEA) and offers optional processing services via Custom Products.

    Example: Option “Sawing”

    • Sub-options: Fixed cut, Center cut, Mitre cut
    • Current behavior: fixed surcharge, e.g. €15 per cut

    Desired behavior:… more

    3 votes

    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

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

    5 votes

    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  ·  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

13. Adjustment of Document File Names with Placeholders for Customer Data

    Shopware does not support the use of placeholders for customer number, customer name, company name, and date in document file names. This makes efficient and precise management of generated files more challenging.

    To optimize the categorization and archiving of documents, it would be highly beneficial to allow placeholders for the mentioned customer data in both the prefix and suffix of the file name. This would significantly simplify the handling of documents and improve the overall user experience of the software.

    We kindly request that this functionality be integrated into a future version.

    •  

    4 votes

    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. Improvements to the thumbnail generator

    One customer noticed these limitations of the thumbnail generator:
    Square dimensions are used by default. This means that images with different widths and heights can vary greatly in quality when portrait and landscape images are used at the same time.

    The media manager allows the width and height to be set differently, but thumbnails that deviate from this format will be of poorer quality.

    In the customer's words:
    A square display is rarely the case. The most common display is landscape format.

    For optimal quality, the shortest side should be used rather than the longest side.

    This is the only way to ensure that images are always (!) optimally used in the respective resolution and based on the srcset / sizes attributes.

    One customer noticed these limitations of the thumbnail generator:
    Square dimensions are used by default. This means that images with different widths and heights can vary greatly in quality when portrait and landscape images are used at the same time.

    The media manager allows the width and height to be set differently, but thumbnails that deviate from this format will be of poorer quality.

    In the customer's words:
    A square display is rarely the case. The most common display is landscape format.

    For optimal quality, the shortest side should be used rather than the longest side.

    This is the only… more

    7 votes

    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  ·  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

15. Advance payment for subscription for a fixed subscription period

    The following use case occurs very frequently in our business model:
    A person gives away a subscription for 3, 6, or 12 months. The giver does not want to pay for each individual shipment separately, but rather pay the total amount once at the beginning, and the subscription ends after the prepaid period.

    4 votes

    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

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

    12 votes

    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

17. Improving admin management for product reviews

    In order to work effectively with product reviews, improvements are needed in the admin management for product reviews.
    Currently, managing reviews is not possible; there are no filters (e.g. product, stars, sales channel, language, approved, date) and after editing a review, you are taken straight back to the first page.

    •  

    5 votes

    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  ·  Other  ·  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. Add more granular permissions for PayPal

    Currently, every admin user with the permission to edit an order (order.editor) can issue refunds of PayPal payments. It would be very helpful to add more granular permissions so that employees can modify orders but cannot issue refunds.

    4 votes

    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  ·  PayPal & Braintree  ·  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. AI: Productstreams / Crossselling

    Little has happened since the introduction of AI.

    The use of AI to generate customer-specific product streams for cross-selling would be indispensable and a major step forward. For example, based on order history. This is very important for the customer.

    Cross-selling is currently very rigid. AI could be used to analyze the customer's order and then make specific suggestions. This would be a huge step and benefit for customers and a game changer.

    13 votes

    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

20. Quick check for plugin and dependency updates compatible with current Shopware version

    Right now, there’s no quick way to see which plugin or dependency updates are actually compatible with the installed Shopware version.

    composer outdated shows all new versions, ignoring compatibility.

    The Admin popup just says “updates available” without details.

    It would be very helpful to have a CLI command and/or an Admin view that lists only installable updates based on the current Shopware version.

    6 votes

    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