345 results found

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

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

3. Change configuration category layout / homepage configuration

   Recurring support tickets indicate that the shop's homepage configuration is not centralized enough.

   Firstly, the shop's homepage is determined by the category layout. Secondly, the homepage can also be set within the category itself (under the "General" tab -> "Homepage" option).

   These numerous different configuration options conflict with each other and lead to unnecessary support tickets. The configuration should therefore be simplified.

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

4. Quantity-based surcharges in Custom Products

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

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

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

   Example: Option “Sawing”

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

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

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

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

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

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

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

   Avoidance of workarounds or external pricing logic

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

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

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

   Example: Option “Sawing”

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

   Desired behavior:… more

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

5. Toggle for readonly custom-fields

   It would be nice to have a toggle for custom fields to mark them readonly (at least in the UI).
   We often have the case that custom field values are imported from other systems (like a PIM) and should not be modified through the Shopware Admin UI. But it's nontheless nice to see their values there.
   So it would be a really nice option to be able to mark them as readonly.

   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

   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.

6. Make the display of search suggestions configurable in the backend

   When searching for customers in the backend, the first name and surname are displayed first, which is not ideal for B2B customers. In this case, it would be better to display the company name.

   We would therefore like an option that allows us to choose which piece of information is displayed first in the search suggestion. The screenshot illustrates the relevant section in the backend.

   •  

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

   Gathering Feedback

   
   

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

   
   

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

7. Product visibility: Only when customer has specific prices

   There have been a few requests by B2B shop owners where the challenge is as follows:

   Products should only be visible IF the observer/customer has specific prices for them. Basically, this means that no products are visible UNLESS the customer has a set price for it.

   From the perspective of a former B2B procurement manager: This is a relatively common thing to see. I purchased tools for the manufacturing personnel, for example. I'd contact the potential suppliers once a year, we'd sit down, talk projected order volumes, figures and conditions.

   After that was all negotiated, I'd get a price list for the various categories with individual prices, bonuses, conditions and so forth and the supplier would set it up on their end so that I could place orders online (if I wanted to) in their shop. Strictly speaking, I'd find all/most of the other items in their shop as well, but I would have preferred if I didn't - so my line of thinking aligns with the requests we got about this in Support, because I already negotiated every item which was relevant to the company I represented ahead of time - I don't need and don't want to see things I had no interest in and likely have no price list for either.

   So - two birds with one stone:

   1) The observer sees all the items they have a specific price for
   2) The observer does not need to filter what is/was relevant to them

   The implementation screams B2B Components. But I think the implementation is potentially simpler if done via Dynamic Access:

   If we had a condition which checks whether or not the observer has custom prices of any sort (be it via customer group - this should be the first condition in my mind - extended prices OR customer specific prices, we'd have all the rest covered already.

   There have been a few requests by B2B shop owners where the challenge is as follows:

   Products should only be visible IF the observer/customer has specific prices for them. Basically, this means that no products are visible UNLESS the customer has a set price for it.

   From the perspective of a former B2B procurement manager: This is a relatively common thing to see. I purchased tools for the manufacturing personnel, for example. I'd contact the potential suppliers once a year, we'd sit down, talk projected order volumes, figures and conditions.

   After that was all negotiated, I'd get a price list… 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

   1 comment  ·  B2B  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

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

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

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

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

   •  

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

9. B2B Components: Include divergent mail addresses in search results

   Shop owners sometimes report having difficulties finding B2B root accounts when provided with little more than a mail address of an employee in case it is not conforming to the companies' mail structure.

   For example:

   Our B2B root account is company@example.com.
   Our employee's mail address is employee@shopware.com.

   Since the mail addresses don't match, when searching for employee@shopware.com, we will find no results for customers. This is sometimes the case where entire departments have separate mail addresses like a purchase department.

   So the request is to have an option to index employee mail addresses and associate them with the B2B account for search results.

   Shop owners sometimes report having difficulties finding B2B root accounts when provided with little more than a mail address of an employee in case it is not conforming to the companies' mail structure.

   For example:

   Our B2B root account is company@example.com.
   Our employee's mail address is employee@shopware.com.

   Since the mail addresses don't match, when searching for employee@shopware.com, we will find no results for customers. This is sometimes the case where entire departments have separate mail addresses like a purchase department.

   So the request is to have an option to index employee mail addresses and associate them with… more

   4 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

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

10. Enable swiping of product images in the gallery

    When a customer views a product page on a mobile device, it is possible to swipe through the different product images.

    However, once the gallery (full screen) is opened, it is no longer possible to navigate through the images by swiping, and only the arrow keys can be used.

    This behavior is not transparent and therefore not comprehensible to the customer, making it feel like an error.

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

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

11. Shopware Analytics - allow selection of common (and custom?) separators

    Currently, we're using comma as a separator for Shopware Analytics exports. Turns out that this is not a one-size-fits-all solution because commas are not that unusual and can appear in product names as well.

    OnPrem, this is a relatively simple customisation I imagine, but Shopware Analytics is also used in cloud shops, where this approach is not possible.

    Hence, it would be nice if no individual customization is required at all and we offer some sort of setting or something in the Admin itself so shop owners can comfortably set their own separator which best fits their setup.

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

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

13. Add promotion code via link

    It would be a nice feature if discount codes could be redeemed via link in the same way that EasyCoupon does it for example. This would allow merchants to send mails already including a working link to get the customer shopping with their discount. For the customers, this would make the journey smoother because they don't need to back and forth to get some code and find the field to enter it and so on.

    Plus, the customer is probably much more likely to actually complete the checkout if they see their shiny discount applied at all times right from the moment they visit the store.

    It would be a nice feature if discount codes could be redeemed via link in the same way that EasyCoupon does it for example. This would allow merchants to send mails already including a working link to get the customer shopping with their discount. For the customers, this would make the journey smoother because they don't need to back and forth to get some code and find the field to enter it and so on.

    Plus, the customer is probably much more likely to actually complete the checkout if they see their shiny discount applied at all times right from… more

    7 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Marketing & Promotions  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

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

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

    •  

    •  

    •  

    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.

15. Advance payment for subscription for a fixed subscription period

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

    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

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

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

16. Improvements to the thumbnail generator

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

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

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

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

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

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

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

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

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

    This is the only… more

    8 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    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

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

18. Standardize shortName for Categories to ensure App and Headless stability

    Shopware provides a shortName for SalesChannels to enable environment-agnostic identification, yet this primitive is missing for Categories. This inconsistency forces App developers and Headless integrators to rely on volatile SEO URLs or environment-specific UUIDs to identify "Page Types" (e.g., Home, Support, Landing Page).

    By extending shortName to the Category entity, Shopware would provide a stable, indexed, and semantic developer contract. This eliminates the need for redundant repository searches or brittle Custom Field lookups, which currently penalize performance and complicate CI/CD pipelines. Standardizing this across core entities ensures that external systems can resolve both "Shop Context" and "Location Context" using the same native logic, drastically simplifying the integration of marketing, tracking, and CMS-driven Apps.

    Shopware provides a shortName for SalesChannels to enable environment-agnostic identification, yet this primitive is missing for Categories. This inconsistency forces App developers and Headless integrators to rely on volatile SEO URLs or environment-specific UUIDs to identify "Page Types" (e.g., Home, Support, Landing Page).

    By extending shortName to the Category entity, Shopware would provide a stable, indexed, and semantic developer contract. This eliminates the need for redundant repository searches or brittle Custom Field lookups, which currently penalize performance and complicate CI/CD pipelines. Standardizing this across core entities ensures that external systems can resolve both "Shop Context" and "Location Context" using the… 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  ·  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.

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

20. Custom Delivery Statuses for Advanced Logistics Processes

    Many merchants require delivery statuses that go beyond the standard statuses provided by Shopware, especially when operating complex warehouse and fulfillment processes with ERP/WMS integrations and B2B workflows.

    The current set of delivery statuses is often insufficient to accurately reflect real operational states within the fulfillment process.

    Examples of commonly needed custom delivery statuses include:

    • On Hold
    • Partially Pickable
    • Waiting for Stock
    • B2B Special Process

    A valuable enhancement would be the ability to create and manage custom delivery statuses within the administration and use them throughout the order and fulfillment workflow.

    This would enable merchants to better represent their internal logistics processes, improve transparency for customer service teams, and support more complex B2B and warehouse management scenarios without relying on workarounds or custom developments.

    Many merchants require delivery statuses that go beyond the standard statuses provided by Shopware, especially when operating complex warehouse and fulfillment processes with ERP/WMS integrations and B2B workflows.

    The current set of delivery statuses is often insufficient to accurately reflect real operational states within the fulfillment process.

    Examples of commonly needed custom delivery statuses include:

    • On Hold
    • Partially Pickable
    • Waiting for Stock
    • B2B Special Process

    A valuable enhancement would be the ability to create and manage custom delivery statuses within the administration and use them throughout the order and fulfillment workflow.

    This would enable merchants to better represent their internal… 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  ·  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.