157 results found

1. Clean the cache partially

   It should be possible to clean the cache partially. In this way the server is not forced to rebuild everything, and it's really important for performances (also PSH told me that). Check how Adobe manage it: https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/cli/manage-cache

   1 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

2. SW6 - erweitertes / verbessertes Logging für Production (DEV log for PROD)

   https://forum.shopware.com/t/sw6-erweitertes-logging-dev-log-fuer-live-systeme-production-app-evn-production/103341

   https://issues.shopware.com/issues/NEXT-34433

   EN:
   Description: The production environment of Shopware 6 lacks a logging function to be able to trace errors in particular. This was much better and easier with Shopware 5. In Shopware 6 it is only possible to get a halfway usable logging for a production environment with a lot of expertise and trickery.

   Problem: A (longer-term) changeover from a production environment to a DEV environment is not an option for 99% of store operators, as the frontend naturally changes as a result and becomes debuggable for everyone, etc. The second problem is that some errors only occur in LIVE operation (e.g. customer-specific errors / empty shopping baskets / session errors etc.) which logically cannot or can only be partially reproduced in a test environment.

   Therefore, a useful logging extension would not only be desirable, but in my opinion a mandatory program for every professional store system.

   Suggestion for improvement: -> integrate different logging options for the production environment -> integrate an overview like the "Frosh Tools" plugin to make logging easy for every store operator. (possibly also similar to Shopware 5)

   How you can currently convert the entire logging manually (temporary solution) is described here: https://stackoverflow.com/a/78143930/23062645

   ––

   DE:
   Beschreibung: In der production Umgebung von Shopware 6 fehlt eine Logging-Funktion um insbesondere bei Fehlern diese nachvollziehen zu können. Das war bei Shopware 5 weitaus besser und einfacher gelöst. In Shopware 6 ist es nur mit viel Fachwissen und Tricksereien möglich ein halbwegs brauchbares Logging für eine Produktivumgebung hin zu bekommen.

   Problem: Ein (längerfristiges) Umstellen von Produktivumgebung auf DEV Umgebung ist für 99% der Shopbetreiber keine Option, da sich natürlich auch das Frontend hierdurch verändert und für jeden debugbar wird usw. Das zweite Problem liegt darin, dass einige Fehler nur im LIVE-Betrieb auftreten (z.B. kundenspezifische Fehler / leere Warenkörbe / Session Fehler etc.) die in eine Testumgebung logischerweise nicht oder nur teilweise nachgestellt werden können.

   Daher wäre eine brauchbare Logging Erweiterung nicht nur wünschensert sondern in meinen Augen Pflichtprogramm für jedes professionelles Shopsystem.

   Verbesserungsvorschlag: -> verschiedene Loggingoptionen für Production Umgebung integrieren -> Übersicht integrieren wie durch das "Frosh Tools" Plugin um das Logging auch für jeden Shopbetreiber unkompliziert darstellen zu können. (ggf. auch so ähnlich wie bei Shopware 5)

   Wie man das ganze Logging aktuell manuell umbauen kann (tempräre Lösung), ist hier beschrieben: https://stackoverflow.com/a/78143930/23062645

   Für den Anfang wäre ein Optionsfeld mit verschiedenen Logging-Stufen erstmal ausreichend:
   Logging Typ: [Prod-Log (Standard) ]( Dev-Log | Dev-Log ohne "deprecated" Meldungen (empfohlen bei Fehlern) )

   Vorschlag: Unter "Administration - Einstellungen - System" den Button "Ereignis Logs" in "Logging" umbenennen und darunter die Logfiles nach dem Schema von Frosh-Tools auswählen und anzeigen lassen. Alternativ einen neuen Button hinzufügen, wenn das Ereignis Log nicht so mal eben erweiterbar ist... In dem Fall bitte eien Hinweistext mit einem Link mit einbauen "für die Ereignis-Logs klicken sie >hier<" und bei den Ereignis Logs "für weitere Log-Dateien klicken Sie >hier<") ;)

   --

   Spätere Erweiterungen / Verbesserungsvorschläge:

   Wenn man damit intern die Monolog.yaml konfiguriert, könnte man auch noch eine Optionsfeld einfügen mit dem Text "Split Log-Files into daily files (default) | single log-file". (type: rotating_file | stream)
   
   Ein Input-Feld mit Keyword-Filter (auszuschließende Keywords) (z.B. deprecated) schön.
   

   In der Log-View:

   Input Feld "Filtern nach ..."
   Ein "Download-Logfile" Button.
   

   EDIT: Auf die grandiose Formatierung dieses Beitrags habe ich keinen Einfluss, weil schlichtweg die Buttons fehlen... Aber darüber rege ich mich nicht weiter auf... Baustellen gibts hier genug...

   https://forum.shopware.com/t/sw6-erweitertes-logging-dev-log-fuer-live-systeme-production-app-evn-production/103341

   https://issues.shopware.com/issues/NEXT-34433

   EN:
   Description: The production environment of Shopware 6 lacks a logging function to be able to trace errors in particular. This was much better and easier with Shopware 5. In Shopware 6 it is only possible to get a halfway usable logging for a production environment with a lot of expertise and trickery.

   Problem: A (longer-term) changeover from a production environment to a DEV environment is not an option for 99% of store operators, as the frontend naturally changes as a result and becomes debuggable for everyone, etc. The second problem is that some errors only occur in… more

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

3. Extend ScheduledTask "delete_newsletter_recipient_task"

   It seems that the deletenewsletterrecipient_task only removes unconfirmed newsletter subscribers that remain in that particular state for longer than x-days. It would be good, if we could automatically remove all newsletter recipents that already unsubscribed and remain in status "Awaiting deletion". Those currently have to be deleted manually.

   9 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

4. Searchable comments

   Customers can add comments on the checkout page

   Issue is that in the Administration, it is until now not possible to search for comments of customers

   Example:
   
   - customer calls the shop owner and asks if the comment made was considered
   - customer wants something excluded or special made

   10 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

5. Payment methods only available for admin orders / Hide specific payment methods in checkout

   It should be possible to enable certain payment methods for admin orders only, without them being visible in the frontend.

   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

   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

6. Country-specific taxes for warehouses

   International companies can have warehouses in different countries. However, this cannot currently be mapped because the warehouses' and the tax matrix do not receive any information about the shipping type location. This means that a German company that has set up a warehouse in France, for example, would apply EU tax to a delivery within France and treat a delivery to Germany as a domestic sale.

   I think this would be a feature that is needed in the future.

   ---

   International Unternehmen können Warenhäuser in unterschiedlichen Ländern haben. Das kann aber aktuell nicht abgebildet werden, weil das Warenhaus und die Steuermatrix keinerlei Informationen über den Versandartort erhalten. Somit würde ein deutsches Unternehmen, das bspw. ein Warenhaus in Frankreich eingerichtet hat, bei einer Lieferung innerhalb Frankreichs EU Steuer anwenden und eine Lieferung nach Deutschland wie einen Inlandsverkauf behandeln.

   Ich denke, das wäre ein Feature was zukünftig gebraucht wird.

   International companies can have warehouses in different countries. However, this cannot currently be mapped because the warehouses' and the tax matrix do not receive any information about the shipping type location. This means that a German company that has set up a warehouse in France, for example, would apply EU tax to a delivery within France and treat a delivery to Germany as a domestic sale.

   I think this would be a feature that is needed in the future.

   ---

   International Unternehmen können Warenhäuser in unterschiedlichen Ländern haben. Das kann aber aktuell nicht abgebildet werden, weil das Warenhaus und die Steuermatrix… more

   2 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

7. Add (database)-flag that indicates if a custom field (set) is in use

   Implement a flag that indicates, if a custom field (set) is in use. Currently, if you would like to delete specific custom fields or a whole set, you don't really see, if they are still assigned in any of the 27 potential entities you can assign a custom field set to.

   On top of that, we currently don't check if a custom field (set) is in use while deleting it.

   1 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  ·  Edit…  ·  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: menu bar permanent collapsed

   Possibility to set the menu bar permanent collapsed or not.

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

9. Extend ruling / possibilties for shipping methods

   EN
   The number of requests to expand the options for shipping methods is increasing. Many customers who come from Shopware 5 miss the option of entering individual calculations or combining standard shipping methods with surcharge or discount shipping methods. I'll take DHL as an example here. When shipping abroad, the EU / non-EU distinction is used, the destination countries are divided into zones, there is a basic price and a surcharge per kilogramme.
   This can of course be mapped with Rule Builder and the current shipping methods, but if I send goods weighing up to, say, 100 kg, it means creating a price matrix with at least 100 entries. This also involves manually calculating which basic price with which number of kilograms results in which total price.

   The price per kilogram remains the same in the scenario, so the whole thing would be relatively easy for our customers to map if it were possible to specify a calculation, for example "total weight * 1.50 EUR", the basic prices are staggered according to kilogram ranges, which could already be easily mapped now. It would only be necessary to add the two together to produce a final shipping price. Percentage surcharges etc. are also missing.

   DE
   Die Anfragen zu einer Erweiterung der Möglichkeiten für Versandarten nehmen zu. Viele Kunden, die von Shopware 5 kommen, vermissen die Möglichkeit individuelle Berechnungen zu erfassen oder Standardversandarten mit Aufschlags- oder Abschlagsversandarten zu kombinieren. Als ein Beispiel nehme ich hier DHL. Bei dem Versand ins Ausland wird die Unterscheidung EU / Nicht EU angewendet, die Zielländer sind in Zonen aufgeteilt, es gibt eine Grundpreis und einen Aufschlag pro Kilogramm. Das lässt sich mit Rule Builder und den aktuellen Versandmethoden natürlich abbilden, aber allein wenn ich Versandgut bis sagen wird 100 Kg verschicke, bedeutet es eine Preismatrix mit mindestens 100 Einträgen anzulegen. Dabei muss dann auch noch manuell berechnet werden, welcher Grundpreis mit welcher Kilozahl welchen Gesamtpreis ergibt.

   Der Preis pro Kilogramm bleibt in dem Szenario gleich, somit wäre das Ganze für unsere Kunden relativ leicht abzubilden wenn es die Möglichkeit gäbe eine Berechnung anzugeben, zum Beispiel "Gesamtgewicht * 1,50 EUR", die Grundpreise sind nach Kilogrammbereichen gestaffelt, das ließe bereits jetzt einfach abbilden. Es müsste nur beides zusammen gerechnet einen Versandendpreis ergeben. Vermisst werden außerdem prozentuale Aufschläge usw.

   EN
   The number of requests to expand the options for shipping methods is increasing. Many customers who come from Shopware 5 miss the option of entering individual calculations or combining standard shipping methods with surcharge or discount shipping methods. I'll take DHL as an example here. When shipping abroad, the EU / non-EU distinction is used, the destination countries are divided into zones, there is a basic price and a surcharge per kilogramme.
   This can of course be mapped with Rule Builder and the current shipping methods, but if I send goods weighing up to, say, 100 kg, it means… 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  ·  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

10. Demotivating update strategy

    I don't understand why new versions are constantly being released. Shopify releases an update twice a year. Can't you do the same with Shopware? Collect everything or once a quarter and you know in advance what will be optimised. And the release date is fixed, so you can prepare for it. It would simply be structured. Security updates run separately.

    We pay a lot of money for updates because many functionalities are no longer available in the Shopware core and we always have to test all plugins to see if they are compatible again. I'm not even going to mention external systems such as ERP or the like. Developers even complain to us that Shopware's version updates are random and that they then have to catch up quickly and features can't be developed because they have to guarantee compatibility. Is Shopware aware of this?

    And I suspect that this situation is annoying - for the developers of the plugins and also for the retailers.

    We are currently trying to upgrade to Shopware 6.6.7.1 and I already know that a new version is coming.

    It's demotivating.

    I don't understand why new versions are constantly being released. Shopify releases an update twice a year. Can't you do the same with Shopware? Collect everything or once a quarter and you know in advance what will be optimised. And the release date is fixed, so you can prepare for it. It would simply be structured. Security updates run separately.

    We pay a lot of money for updates because many functionalities are no longer available in the Shopware core and we always have to test all plugins to see if they are compatible again. I'm not even going to mention… more

    1 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  ·  Edit…  ·  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. Permissions for extension settings

    I like to set up permission for the admin user only for configuration/managment of one specific extension.

    1 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

12. Add snippet inheritance

    If we added snippet inheritance, it would be easy to edit versions of a snippet which only requires minor changes.

    For example, let's say German-Swiss. If we had an inheritance on a snippet basis, we could edit only the snippets for shipping costs in the checkout, for example, since it's likely that they differ from the local German shipping cost and/or require different texts for the snippets in the checkout.

    Sure, we could simply create a new snippet set. But that inherits from a base file and every change we make in the German snippet set for example are NOT inherited down to German-Swiss. That in turn requires editing TWO sets.

    Since we already have the inheritance logic in place for many things, it would be nice to have it for snippets too. Simply going by the logic

    "Does the snippet set (German-Swiss) have different text for this snippet than the set it inherits from?

    -> Yes: Use that snippet content
    -> No: Use the content the set inherits from.

    That way, we minimize the manual effort involved in taking care of this content.

    We have this in place for Shopping Experiences, for example, where it's quite useful. But shopping experiences don't let us edit the content of the snippets we have in the checkout for example.

    If we added snippet inheritance, it would be easy to edit versions of a snippet which only requires minor changes.

    For example, let's say German-Swiss. If we had an inheritance on a snippet basis, we could edit only the snippets for shipping costs in the checkout, for example, since it's likely that they differ from the local German shipping cost and/or require different texts for the snippets in the checkout.

    Sure, we could simply create a new snippet set. But that inherits from a base file and every change we make in the German snippet set for example are NOT… 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

    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

13. Bitte die Mehrfachänderung für Lieferantenbestellungen hinzufügen.

    Bitte die Mehrfachänderung für Lieferantenbestellungen hinzufügen.

    Es ist sehr Zeitaufwendig die Preise und die Stückzahl für jeden einzelnen Artikel, in meinem Fall Variantenartikel, anzupassen.

    Nach jeder einzelnen Variante speichert das System, das verlängert diesen Bearbeitungsprozess für den Benutzer.

    ---

    Please add the multiple change for supplier orders.

    It is very time consuming to adjust the prices and quantity for each individual item, in my case variant items.

    The system saves after each individual variant, which prolongs this editing process for the user.

    1 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. Make response code of maintenance page configurable either in config or backend

    Overwriting the method doesnt help in our case because plugins are deactivated on update.

    •  

    1 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

15. Extend rate limit to storefront operations optionally

    We can protect most "vulnerable" parts of the store already with a rate limiter. This includes the contact form or login & password reset pages for both the frontend and the Admin.

    However, there are "vulnerable" parts for the cart (and potentially other parts) as well. A shop owner monitored that presumably a bot rapidly added products to a cart over and over again over hours, placing high load on the database due to the spam collecting in the cart table.

    Since we already have a rate limiter in the code, it would be nice and possibly fairly simple to include other areas of the store to optionally apply the rate limiter here as well.

    We can protect most "vulnerable" parts of the store already with a rate limiter. This includes the contact form or login & password reset pages for both the frontend and the Admin.

    However, there are "vulnerable" parts for the cart (and potentially other parts) as well. A shop owner monitored that presumably a bot rapidly added products to a cart over and over again over hours, placing high load on the database due to the spam collecting in the cart table.

    Since we already have a rate limiter in the code, it would be nice and possibly fairly simple to… more

    1 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  ·  Edit…  ·  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. Rule Builder: “Order quantity” and “Minimum stock”

    The “Order quantity” and “Minimum stock” should also be used as conditions via the Rule Builder.

    This allows you to offer special shipping methods, for example, if these conditions have reached a certain value.

    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

    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

17. Improvement of the function: page layout settings in Categories

    Currently, there are three ways to activate the Erlebniswelten design in the shop:

    Through the CMS editor, where you can assign the layout to a category.

    Directly in the category, under the "Layout" tab.

    In the "General" tab of the category, using the "Configure homepage" button in the navigation section.

    In my opinion, these options are confusing as they can override each other. Specifically, the "Configure homepage" button overwrites settings from both the CMS editor and the "Layout" tab, which can lead to changes not being reflected in the frontend if the original configuration in that button is forgotten.

    It would be ideal to have only one way to configure the layout or to ensure that settings don't overwrite each other but apply globally. The current setup, with multiple configuration options in the backend, is not particularly user-friendly from a UX perspective.

    Currently, there are three ways to activate the Erlebniswelten design in the shop:

    Through the CMS editor, where you can assign the layout to a category.

    Directly in the category, under the "Layout" tab.

    In the "General" tab of the category, using the "Configure homepage" button in the navigation section.

    In my opinion, these options are confusing as they can override each other. Specifically, the "Configure homepage" button overwrites settings from both the CMS editor and the "Layout" tab, which can lead to changes not being reflected in the frontend if the original configuration in that button is forgotten.

    It… more

    1 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  ·  Edit…  ·  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. Email log

    It would be great if there was an email log again, like in Shopware 5, in which you can clearly see all the emails that have been sent.

    25 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

19. Define basic information for different languages

    It is currently possible to change the language under Basic information, but the content, e.g. for the shop's bank details field, is maintained globally for all languages and it is not possible to maintain this for one language. This is not user-friendly, as in a sales channel with several languages it should also be possible to make different entries here.

    2 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

20. Flowbuilder - form related triggers

    Implement triggers that validate on specific fields / entries within a (custom)-form.

    For example: If field1 (checkbox) is true / checked, then perform action xy on customers.

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