125 results found

1. Extended debugging e-mail/template dispatch

   Many customers customize the email templates for their shop. It often happens that certain e-mail templates are no longer sent because, for example, variables are incorrect.

   Troubleshooting the cause is then very difficult and time-consuming because:

   • There are no errors in the log with indications of the cause.
   • The e-mail test function still works with the e-mail template because variables are ignored.

   As a result, the e-mail template and the variables have to be checked with a great deal of effort and there are a lot of support tickets for this, as customers quickly reach their limits.

   In order to help customers and reduce the number of support tickets, it would therefore be useful to have extended debugging for sending emails. It should be possible to recognise from which line the e-mail dispatch fails.

   This would allow the customer or the support team to name and recognise the line directly and, if necessary, find the error within seconds. This leads to less time for troubleshooting and frustration for customers.

   Many customers customize the email templates for their shop. It often happens that certain e-mail templates are no longer sent because, for example, variables are incorrect.

   Troubleshooting the cause is then very difficult and time-consuming because:

   • There are no errors in the log with indications of the cause.
   • The e-mail test function still works with the e-mail template because variables are ignored.

   As a result, the e-mail template and the variables have to be checked with a great deal of effort and there are a lot of support tickets for this, as customers quickly reach their limits.

   In order to… 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  ·  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

2. Resend order confirmation

   Implement a function / Add button to resend order confirmations

   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

   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

3. Make first- and last name optional for company accounts

   First- and last name should be optional if setting up a new customer entry through the administration or by using the register form IF it is a company account.

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

4. When I work in the Admin, I don't want to fall back into the overviews again and again, but to the last editing location.

   When I'm in the admin and search for something in products, for example, then edit it and go back, I expect to return to the last search result and not end up in the overview.

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

5. Mailer: Different SMTP data for different sales channels

   More and more providers are prohibiting the sending of emails that do not come from the same domain.

   However, as you can only store the access data of one domain in the mailer, this becomes a major problem as soon as you enter several sales channels with different domains.

   From that moment on, not all messages can be sent or are rejected by the provider.

   "mailbox unavailable\r\n 550 Sender address is not allowed.""

   It should therefore be possible to configure the mailer settings for each sales channel.

   18 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

   3 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

6. Different sender email addresses for outgoing emails

   Englisch:

   It would be helpful if you could store multiple sender email addresses in the system settings for different purposes such as status emails, sending invoices and shipping confirmations. For example, invoices could come from the email address invoice@Example.de, but status emails could come from info@Example.de. Shipping confirmations, however, could be sent from noreply@Example.de.

   It would also be helpful if you could assign a customer a second email address, which would then be automatically selected when the invoice is sent. This is particularly necessary in the B2B sector, as the invoice usually goes to a different recipient than the original order confirmation

   Deutsch:

   Es wäre hilfreich, wenn man in den Systemeinstellungen mehrere Absender E-Mail-Adressen für verschiedene Zwecke wie zum Beispiel Statusmails, Rechnungsversand und Versandbestätigungen hinterlegen könnte.

   So könnten zum Beispiel Rechnungen von der Mail-Adresse invoice@Beispiel.de kommen, Statusmails allerdings von der info@Beispiel.de.
   Versandbestätigungen hingegen könnten von noreply@Beispiel.de versendet werden.

   Zudem wäre es auch hilfreich, wenn man einem Kunden eine zweite E-Mail-Adresse zuordnen könnte, welche dann beim Rechnungsversand automatisch ausgewählt wird. Dies ist gerade im B2B Bereich notwendig, da die Rechnung meist an einen anderen Empfänger als die ursprüngliche Bestellbestätigung geht..

   Englisch:

   It would be helpful if you could store multiple sender email addresses in the system settings for different purposes such as status emails, sending invoices and shipping confirmations. For example, invoices could come from the email address invoice@Example.de, but status emails could come from info@Example.de. Shipping confirmations, however, could be sent from noreply@Example.de.

   It would also be helpful if you could assign a customer a second email address, which would then be automatically selected when the invoice is sent. This is particularly necessary in the B2B sector, as the invoice usually goes to a different recipient… 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

   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

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

8. Optimization of plugin management and configuration in Shopware 6 Admin

   We are having difficulties finding and managing the apps and plugins installed in Shopware 6 within the admin area. Since many standard features from SW5 have been removed and must now be replaced by apps, there is no central overview for these extensions. The apps are spread out across different sections, without a clear indication of which plugin provides which functionality. This leads to issues with managing and identifying extensions.

   Note from Shopware Support:
   We think it's a very good idea. For many colleagues in support, it is often very difficult to find out which plugin inserts which functions and where these are configured.

   Main Issues:

   Scattered Apps: Apps are spread out across various sections of the admin area (e.g., Marketing, System, Settings), making them difficult to find.

   No Clear Function Assignment: After installation, it is often unclear which plugin is responsible for which function. Only after disabling a plugin does it become apparent what it was doing.

   Challenges with CMS Plugins: With multiple CMS plugins active at the same time, it’s almost impossible to figure out which plugin is being used in which Shopping Experience without manually testing each one.

   Shopify Example:
   We find that Shopify has a clear structure where all apps are centrally located under one "Apps" section, with direct access to configuration, making it super easy to manage.

   Use Cases for Clarification:

   1 - Finding an App:
   If i want to configure a recently installed plugin. However, it is scattered across the admin area (e.g., partly under Marketing, partly under System), and there is no central overview. The user wastes time searching for the app.

   Use Case 2 - Unclear Function Assignment:
   As a shop owner, i noticed a functionality in our shop (e.g., "Products in saved shopping carts" under Marketing) but does not know whether it’s part of the core system or added by a plugin. Suggestion: Clearly indicate which function is provided by which plugin.

   Wanted improvements:

   Introduce a central "Plugin" section where all installed extensions are listed and can be configured.

   Clearly label in the admin area which functions belong to which plugins. Maybe with an Icon and text on hover.

   Improve the identification of CMS plugins within Shopping Experiences.

   We are having difficulties finding and managing the apps and plugins installed in Shopware 6 within the admin area. Since many standard features from SW5 have been removed and must now be replaced by apps, there is no central overview for these extensions. The apps are spread out across different sections, without a clear indication of which plugin provides which functionality. This leads to issues with managing and identifying extensions.

   Note from Shopware Support:
   We think it's a very good idea. For many colleagues in support, it is often very difficult to find out which plugin inserts which functions and… 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

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

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

    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

    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

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

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

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

    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

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

15. Deactivate user

    In addition to creating and deactivating users, it should also be possible to temporarily deactivate users in the admin (Settings > System > Users).

    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

    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

16. Hausnummer von Straße trennen

    Es fehlt die Möglichkeit die Straße und die Hausnummer in zwei getrennten Kästchen anzeigen zu lassen und im Backend seperat angezeigt zu bekommen.

    Wir haben in der Woche ca. 50 Bestellungen wo nur die Straße ohne Hausnummer eingefügt wird und wir diese Bestellungen nicht versenden können.

    Es gibt zwar einen Workaround über das "Straße & Hausnummer in 2 Felder Plugin" aber es wäre wirklich nett, wenn man das von Haus aus direkt im System einstellen könnte.

    22 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

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

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

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

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

    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