284 results found

1. Checkout gateway mechanism for calculating delivery charges

   Die vorhandenen Commands des Checkout Gateways (https://developer.shopware.com/docs/guides/plugins/apps/gateways/checkout/command-reference.html) lassen es nicht zu, die Versandkosten des Warenkorbs zu berechnen oder zu setzen.
   Dies wäre aber wünschenswert, um z.B. kompliziertere Versandkostenberechnungen vom ERP erledigen zu lassen.

   –

   The existing commands in the Checkout Gateway (https://developer.shopware.com/docs/guides/plugins/apps/gateways/checkout/command-reference.html) do not allow the shipping costs for the shopping basket to be calculated or set.
   However, this would be desirable, for example, to allow the ERP system to handle more complex shipping cost calculations.

   1 vote

   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  ·  App System  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

2. Zusätzlicher Filter in der Bestellübersicht / Additional Filter in the Admin Orderoverview

   In der Bestellübersicht wäre es hilfreich, wenn auch die Kundennummer als Spalte angezeigt werden würde. So könnte nicht nur nach Namen oder Emailadresse sondern auch nach Kundennummer sortiert werden. Das würde uns die Arbeit beim Zusammenfassen der Bestellungen deutlich erleichtern, da wir einige Kunden haben die mehrere Kundenkonten besitzen.

   ENG: It would be helpful if the customer number could also be displayed as a column in the order overview. This would allow orders to be sorted not only by customer name or email address, but also by customer number. It would significantly simplify our workflow when consolidating orders, as we have several customers who maintain multiple customer accounts.

   In der Bestellübersicht wäre es hilfreich, wenn auch die Kundennummer als Spalte angezeigt werden würde. So könnte nicht nur nach Namen oder Emailadresse sondern auch nach Kundennummer sortiert werden. Das würde uns die Arbeit beim Zusammenfassen der Bestellungen deutlich erleichtern, da wir einige Kunden haben die mehrere Kundenkonten besitzen.

   ENG: It would be helpful if the customer number could also be displayed as a column in the order overview. This would allow orders to be sorted not only by customer name or email address, but also by customer number. It would significantly simplify our workflow when consolidating orders, as we… more

   1 vote

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

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

3. Form field company name also for B2C shops

   An additional field for entering a company name should be added to the registration form. There are often B2C customers who wish to have their order delivered to their work address. An optional form field for company names is therefore required.

   1 vote

   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  ·  Content management  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

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

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

   5 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Orders & Customers  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

5. Reintroduce CLI commands (functionality) for Migrations

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

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

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Migration & Im-/Export  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

6. Allow saving changes by pressing Enter in the Admin

   Allow saving changes by pressing Enter in the Admin

   Description:
   In Shopware 5, it was possible to save many changes simply by pressing the Enter key after editing a field. This made product maintenance much faster because users did not have to move their hand from the keyboard to the mouse to click Save or the checkmark.

   In Shopware 6, after editing fields such as prices, users always have to click the save/checkmark button with the mouse.

   For merchants maintaining hundreds or thousands of products every day, this results in many unnecessary mouse clicks and slows down the workflow.

   Expected behavior

   After editing a field (for example a price), pressing Enter should:

   Confirm the edited value.
   Save or apply the change (depending on the context).
   Allow the user to continue working without using the mouse.

   This should work consistently throughout the Shopware Admin where appropriate.

   Benefits

   Faster product maintenance.
   Better keyboard workflow.
   Fewer mouse movements.
   Increased productivity for power users.
   Similar workflow to Shopware 5, making migration easier.

   Allow saving changes by pressing Enter in the Admin

   Description:
   In Shopware 5, it was possible to save many changes simply by pressing the Enter key after editing a field. This made product maintenance much faster because users did not have to move their hand from the keyboard to the mouse to click Save or the checkmark.

   In Shopware 6, after editing fields such as prices, users always have to click the save/checkmark button with the mouse.

   For merchants maintaining hundreds or thousands of products every day, this results in many unnecessary mouse clicks and slows down the workflow.

   Expected… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

7. Allow pasting prices with comma as decimal separator

   Title:
   Allow pasting prices with comma as decimal separator

   Description:
   Currently, Shopware 6 does not accept prices that are pasted with a comma as the decimal separator.

   For example:

   12,95 → only 12 is inserted (the decimal part is ignored)

   This is inconvenient for European merchants, because prices are often copied from:

   Excel
   ERP systems
   Supplier price lists
   Websites

   where the comma is the standard decimal separator.

   Expected behavior

   When a user pastes a price such as:

   12,95
   1234,56

   Shopware should automatically convert it to the correct internal decimal format instead of discarding everything after the comma.

   This would improve usability significantly and prevent incorrect prices from being entered.

   Benefit

   Better user experience
   Fewer input errors
   Better support for European number formats
   Faster product maintenance

   Title:
   Allow pasting prices with comma as decimal separator

   Description:
   Currently, Shopware 6 does not accept prices that are pasted with a comma as the decimal separator.

   For example:

   12,95 → only 12 is inserted (the decimal part is ignored)

   This is inconvenient for European merchants, because prices are often copied from:

   Excel
   ERP systems
   Supplier price lists
   Websites

   where the comma is the standard decimal separator.

   Expected behavior

   When a user pastes a price such as:

   12,95
   1234,56

   Shopware should automatically convert it to the correct internal decimal format instead of discarding everything after the comma.

   This would improve… more

   1 vote

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

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

8. sorting by publication date should also be possible ascending and descending order

   When sorting products by publication date, it should also be possible to choose between ascending and descending order. Now only descending is possible

   Man sollte bei der Produktsortierung nach Erscheinungsdatum auch ab- oder aufsteigend auswählen können. Aktuell nur ist nur absteigend möglich

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

9. Option to hide editing tools in the image editor

   It would be great if there were a way to hide the editing tools in the image editor.
   The advantage of this is that they would no longer take up a large portion of the screen.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

   Gathering Feedback

   
   

   We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

   
   

   Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

10. Maximum amount of products or maximum sum for the cart

    Currently, there is no elegant way to set order limits with product amounts or the total sum per order.

    One can create rules via the rule builder and use them to hide shipping methods once the limit is surpassed, but there is no transparent message for the customer that there are limits or that they have been reached.

    Analogous to the “Maximum quantity” in the cart settings it would be useful to set order limits similarly, perhaps on a per sales channel basis or even on a customer group basis. Once the limit has been reached, the storefront could hinder the user from adding more items to the cart with a clear error message.

    Currently, there is no elegant way to set order limits with product amounts or the total sum per order.

    One can create rules via the rule builder and use them to hide shipping methods once the limit is surpassed, but there is no transparent message for the customer that there are limits or that they have been reached.

    Analogous to the “Maximum quantity” in the cart settings it would be useful to set order limits similarly, perhaps on a per sales channel basis or even on a customer group basis. Once the limit has been reached, the storefront could hinder… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

11. dynamic product group: preview should include the SKU / dynamische Produktgruppe mit Produktnummer in Vorschau

    EN:
    The dynamic product groups > preview > should include SKU

    DE:
    Die dynamische Produktgruppe > Vorschau > sollte die SKU / Produktnummer beinhalten

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

12. Incorrect plugin names and icons displayed for partner accounts

    We have noticed that we see different plugin names and icons in a customer’s extension list than the customer does.

    After checking, we found that the data shown to the customer is correct and matches the respective plugin definitions. When we log out of our partner account, ottscho@ottscho.de, the correct data is displayed again. As soon as we log back in, the incorrect data reappears.

    It seems that plugin data is retrieved differently for partner accounts and is currently displayed incorrectly. Please investigate this issue. It is extremely inconvenient when a customer refers to a plugin that we cannot find because it is shown under a different name in our account.

    In this case, the plugin is called “Gutscheine für Gratisartikel” for the customer, while it appears as “Kostenloser Artikel mit Gutschein im Warenkorb” for us. However, “Gutscheine für Gratisartikel” is the correct current name according to the composer.json file and the database.

    The second plugin named “Gutscheine für Gratisartikel” also displays a different icon for us, even though the plugin was freshly installed.

    Original Anfrage

    Wir haben festgestellt, dass wir andere Plugin Bezeichnungen und Icons in der Erweiterungsliste eines Kunden sehen als er. Bei der Nachprüfung hat sich ergeben, dass die Daten welche der Kunde sieht die korrekten Daten aus den jeweiligen Plugin Definitionen sind. Bei ausloggen aus unserem Partner Account ottscho@ottscho.de wurden auch wieder die korrekten Daten angezeigt. Bei einloggen wieder die falschen. Scheinbar werden die Daten bei einem Partneraccount anders herangezogen, und zwar falsch. Bitte prüfen, das ist äußerst unschön, wenn der Kunde von einem Plugin spricht welches wir gar nicht finden, weil wir nach einem anderen Namen suchen.

    In dem Fall war es das Plugin "Gutscheine für Gratisartikel" was bei uns "Kostenloser Artikel mit Gutschein im Warenkorb" heißt. Ersteres ist aber der korrekte aktuelle Name laut composer.json und Datenbank. Auch das zweite Plugin "Gutscheine für Gratisartikel" hat bei uns ein anderes Icon, obwohl das Plugin frisch installiert wurde

    We have noticed that we see different plugin names and icons in a customer’s extension list than the customer does.

    After checking, we found that the data shown to the customer is correct and matches the respective plugin definitions. When we log out of our partner account, ottscho@ottscho.de, the correct data is displayed again. As soon as we log back in, the incorrect data reappears.

    It seems that plugin data is retrieved differently for partner accounts and is currently displayed incorrectly. Please investigate this issue. It is extremely inconvenient when a customer refers to a plugin that we cannot… more

    1 vote

    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  ·  Shopware Account  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

13. PayPal Smart Buttons bypass discount logic when the payment method is changed after the fact

    If a customer changes the payment method after the order has been placed, existing discount or shopping cart rules may not be applied correctly if the change is made via the PayPal Smart Buttons.

    In this specific case, a customer initially selects Payment Method A when placing the order and receives a discount as a result. After completing the order, the customer can then switch to payment method B using the PayPal Smart Buttons. However, the previously granted discount remains in effect, even though it is intended to apply exclusively to payment method A.

    This results in a commercially significant error: The customer continues to benefit from the discount even though they subsequently use a payment method for which the discount is not intended.

    Expected Behavior:

    If an order was originally completed using payment method A and a discount was granted as a result, a subsequent switch to payment method B should not result in the discount remaining in effect.

    In this case, Shopware should either:

    block the payment method change based on the existing discount/shopping cart rule,
    re-evaluate the discount logic correctly when the payment method is changed,
    or prevent extensions or PayPal Smart Buttons from bypassing this Shopware core logic.

    The reverse process should remain possible: If a payment using payment method B fails or is canceled, the customer should still be able to switch to payment method A.

    If a customer changes the payment method after the order has been placed, existing discount or shopping cart rules may not be applied correctly if the change is made via the PayPal Smart Buttons.

    In this specific case, a customer initially selects Payment Method A when placing the order and receives a discount as a result. After completing the order, the customer can then switch to payment method B using the PayPal Smart Buttons. However, the previously granted discount remains in effect, even though it is intended to apply exclusively to payment method A.

    This results in a commercially significant… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

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

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

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

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

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

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

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

    An optional offline or developer mode for local development environments—intended exclusively for non-production systems—would be beneficial. Alternatively, a way to clearly designate… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

15. Artikelübersichtstabelle (Kataloge|Produkte) | Improve product lists

    Es wäre sehr hilfreich, wenn im Backend bei der Artikelübersicht weitere Spalten zur Ansicht ein-/ausgeblendet werden könnten, so wie in SW5. Wenn man eine schnelle Übersicht haben will, welche Artikel z.B. eine bestimmte Eigenschaft haben.

    Filterbar sind Eigenschaften auch nicht. Dies wäre eine hilfreiche alternative Funktion.

    So ist eine Pflege mehrerer Artikel sehr umständlich. Da war SW5 deutlich besser.

    Diese Funktionalität wäre für mich eigentlich eine Standardfunktion. Wann wird hier nachgebessert?

    –

    It would be very helpful if additional columns could be toggled on or off in the backend product overview, just like in SW5—for instance, to get a quick overview of which products have a specific property.

    Properties cannot be filtered either; that would be a useful alternative feature.

    As it stands, managing multiple products is very cumbersome. SW5 was significantly better in this regard.

    To me, this is essentially a standard feature. When will this be improved?

    Es wäre sehr hilfreich, wenn im Backend bei der Artikelübersicht weitere Spalten zur Ansicht ein-/ausgeblendet werden könnten, so wie in SW5. Wenn man eine schnelle Übersicht haben will, welche Artikel z.B. eine bestimmte Eigenschaft haben.

    Filterbar sind Eigenschaften auch nicht. Dies wäre eine hilfreiche alternative Funktion.

    So ist eine Pflege mehrerer Artikel sehr umständlich. Da war SW5 deutlich besser.

    Diese Funktionalität wäre für mich eigentlich eine Standardfunktion. Wann wird hier nachgebessert?

    –

    It would be very helpful if additional columns could be toggled on or off in the backend product overview, just like in SW5—for instance, to get a quick… more

    •  

    •  

    •  

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

16. AI-Powered Image Editing Directly in the Product

    It would be helpful to have image editing capabilities directly within the product instead of having to go through the Media section.

    1 vote

    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  ·  AI  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

17. Product visibility options in dynamic product group

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

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

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

    DE
    
    Wenn in einem Produkt die Produktsichtbarkeit auf in Produklisten und Suche ausblenden gestellt ist, werden die Produkt in der Storefront entsprechend nicht angezeigt. Wenn eine Dynamische Produktgruppe… more

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

18. JSON-basierte Konfigurationen importieren, exportieren und versionieren

    EN:
    I just read this interesting LinkedIn post about n8n workflows:
    https://www.linkedin.com/posts/fs-net_n8n-workflows-baue-ich-gr%C3%B6%C3%9Ftenteils-nicht-ugcPost-7470006922243391488-e6gC

    The core idea: workflows should not only be edited in the UI, but also managed as structured JSON files that can be versioned, reviewed, and deployed automatically.

    A similar approach would be extremely valuable for Shopware Nexus:

    Configurations, mappings, flows, and middleware logic could be exported and imported as JSON. This would make them cleanly versionable in Git, reviewable via pull requests, and deployable between test and production environments.

    The AI aspect would be especially exciting: if Nexus configurations existed as well-documented JSON structures, AI coding agents could work directly with them. New integrations, mapping changes, or validations could be generated via prompt instead of configuring everything manually in the UI.

    Important mechanisms would include placeholders for environment-specific values, separate credential references, validation scripts, and drift checks between the UI and the repository.

    The UI would still remain important for overview, debugging, and manual adjustments. But JSON as an additional technical representation would open up Nexus much more strongly to professional development processes, CI/CD, and AI-assisted configuration.

    Ich habe gerade diesen spannenden LinkedIn-Beitrag zu n8n-Workflows gelesen:
    https://www.linkedin.com/posts/fs-net_n8n-workflows-baue-ich-gr%C3%B6%C3%9Ftenteils-nicht-ugcPost-7470006922243391488-e6gC

    Der zentrale Gedanke: Workflows nicht nur im UI bearbeiten, sondern als strukturierte JSON-Dateien verwalten, versionieren, reviewen und automatisiert deployen.

    Für Shopware Nexus wäre ein ähnlicher Ansatz extrem wertvoll:

    Konfigurationen, Mappings, Flows und Middleware-Logik könnten als JSON exportiert und importiert werden. Damit wären sie sauber in Git versionierbar, per Pull Request reviewbar und zwischen Test- und Produktivumgebungen deploybar.

    Besonders spannend wäre außerdem der KI-Aspekt: Wenn Nexus-Konfigurationen als gut dokumentierte JSON-Strukturen vorliegen, könnten AI Coding Agents direkt darauf arbeiten. Man könnte per Prompt neue Integrationen, Mapping-Änderungen oder Validierungen erzeugen lassen, statt alles manuell im UI zu konfigurieren.

    Wichtig wären dabei Mechanismen wie Platzhalter für umgebungsspezifische Werte, getrennte Credential-Referenzen, Validierungsskripte und Drift-Checks zwischen UI und Repository.

    Das UI bleibt weiterhin wichtig für Übersicht, Debugging und manuelle Anpassungen. Aber JSON als zusätzliche technische Repräsentation würde Nexus deutlich besser für professionelle Entwicklungsprozesse, CI/CD und AI-gestützte Konfiguration öffnen.

    EN:
    I just read this interesting LinkedIn post about n8n workflows:
    https://www.linkedin.com/posts/fs-net_n8n-workflows-baue-ich-gr%C3%B6%C3%9Ftenteils-nicht-ugcPost-7470006922243391488-e6gC

    The core idea: workflows should not only be edited in the UI, but also managed as structured JSON files that can be versioned, reviewed, and deployed automatically.

    A similar approach would be extremely valuable for Shopware Nexus:

    Configurations, mappings, flows, and middleware logic could be exported and imported as JSON. This would make them cleanly versionable in Git, reviewable via pull requests, and deployable between test and production environments.

    The AI aspect would be especially exciting: if Nexus configurations existed as well-documented JSON structures, AI coding agents could… more

    1 vote

    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  ·  Nexus  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

19. Expand Flow Builder for Advanced B2B and Logistics Workflows

    The current Flow Builder is a powerful automation tool, but it does not provide sufficient coverage for many real-world B2B and logistics processes.

    Merchants often need to implement custom workarounds because important triggers and actions for fulfillment, warehouse operations, and B2B workflows are not available out of the box.

    Examples of commonly requested capabilities include:

    • Shipment Ready trigger
    • Warehouse and fulfillment process triggers/actions
    • B2B-specific workflow triggers/actions
    • Automated status changes based on logistics events
    • More granular control over order and delivery processes

    A valuable enhancement would be to significantly expand the available Flow Builder triggers and actions to better support advanced operational workflows.

    Key benefits include:

    • Reducing the need for custom development and workarounds
    • Enabling merchants to automate complex fulfillment and logistics processes
    • Supporting more sophisticated B2B business requirements
    • Increasing flexibility and scalability for growing merchants

    A broader set of native triggers and actions would allow businesses to automate critical operational processes directly within Shopware and unlock the full potential of the Flow Builder for enterprise and B2B use cases.

    The current Flow Builder is a powerful automation tool, but it does not provide sufficient coverage for many real-world B2B and logistics processes.

    Merchants often need to implement custom workarounds because important triggers and actions for fulfillment, warehouse operations, and B2B workflows are not available out of the box.

    Examples of commonly requested capabilities include:

    • Shipment Ready trigger
    • Warehouse and fulfillment process triggers/actions
    • B2B-specific workflow triggers/actions
    • Automated status changes based on logistics events
    • More granular control over order and delivery processes

    A valuable enhancement would be to significantly expand the available Flow Builder triggers and actions to better support advanced… more

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Automation  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.

20. Automatic Country Restrictions Based on Manufacturer

    Many merchants need to restrict the sale of specific brands or manufacturers in certain countries due to contractual, legal, or distribution agreements.

    Currently, country restrictions must be assigned manually on a product-by-product basis. This becomes error-prone and difficult to maintain, especially for large product catalogs and when new products are added regularly.

    A valuable enhancement would be the ability to define country restrictions at the manufacturer level and automatically apply them to all associated products.

    Key benefits include:

    • Automatically inheriting country restrictions for newly created products of a manufacturer
    • Reducing manual maintenance and the risk of human error
    • Ensuring compliance with brand-specific distribution agreements
    • Improving scalability for merchants managing large product catalogs

    This would provide a more efficient and reliable way to manage international sales restrictions while significantly reducing administrative effort.

    Many merchants need to restrict the sale of specific brands or manufacturers in certain countries due to contractual, legal, or distribution agreements.

    Currently, country restrictions must be assigned manually on a product-by-product basis. This becomes error-prone and difficult to maintain, especially for large product catalogs and when new products are added regularly.

    A valuable enhancement would be the ability to define country restrictions at the manufacturer level and automatically apply them to all associated products.

    Key benefits include:

    • Automatically inheriting country restrictions for newly created products of a manufacturer
    • Reducing manual maintenance and the risk of human error
    • Ensuring compliance… more
    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Orders & Customers  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Gathering Feedback  ·  AdminMoritz Naczenski (Admin, shopware AG) responded

    Gathering Feedback

    
    

    We’re gathering feedback on this idea to better understand the need, use cases, and potential impact. At this stage, no implementation decision has been made.

    
    

    Please continue to vote and share details about how this would help you. Your feedback will support our evaluation and help us decide whether to move the idea forward.