- or
1565 results found
-
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 -
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 -
Commercial: improve organization units for shopping lists
Currently, the organization unit field on shopping lists is purely an informational indicator from which unit the list was originally created.
The following improvements should be added to give this more utility:
- The OU field should be definable during creation (i.e. by admins or the customer account) and changeable / re-assignable afterwards when needed.
- Role permissions should be added that define which lists from which OU an employee can see - this allows better separation between units which should not see lists from other departments.
2 votes -
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…
1 vote -
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…
7 votes -
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…
1 vote -
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 -
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…
8 votes -
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 -
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…
2 votes -
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-e6gCThe 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-e6gCDer 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-e6gCThe 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…
1 vote -
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…
1 vote -
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…
1 vote -
ZIP code validation only takes effect once all other mandatory fields have been filled in during checkout.
While testing the checkout process, I noticed inconsistent behavior when validating the postal code.
Steps to reproduce:
Go to checkout.
Select country.
Enter an invalid value in the “Postal code” field (e.g., asdasd or asd123).
Leave at least one other required field blank.
Click “Continue.”
Result:
All required fields are marked as incorrect except for country and zip code.
The zip code is not displayed as invalid in this state.Further behavior:
As soon as the previously missing required field is filled in, the zip code validation takes effect retrospectively and the field is then marked as incorrect.Expected behavior:
The ZIP code should be validated immediately as soon as an invalid format is entered, regardless of the status of other required fields or alternatively, a uniform validation behavior should be applied to all required fields.Note:
Even though this case is likely to occur rarely, the behavior appears inconsistent to users and could lead to confusion.While testing the checkout process, I noticed inconsistent behavior when validating the postal code.
Steps to reproduce:
Go to checkout.
Select country.
Enter an invalid value in the “Postal code” field (e.g., asdasd or asd123).
Leave at least one other required field blank.
Click “Continue.”
Result:
All required fields are marked as incorrect except for country and zip code.
The zip code is not displayed as invalid in this state.Further behavior:
As soon as the previously missing required field is filled in, the zip code validation takes effect retrospectively and the field is then marked as incorrect.Expected behavior:…
4 votes -
Improving admin management for product reviews
In order to work effectively with product reviews, improvements are needed in the admin management for product reviews.
Currently, managing reviews is not possible; there are no filters (e.g. product, stars, sales channel, language, approved, date) and after editing a review, you are taken straight back to the first page.6 votes -
Role permissions for the image editor
Currently, it is not possible to enable or disable the image editor for users of a role.
Only the designated administrators have access to the image editor on Content > Image Editor.
3 votes -
import / export individual coupon codes
It should be possible to import / export individual coupon codes for easy use in other third-party systems.
1 vote -
Orderdetails should show the B2B employee mail address
If an order is initiated by a B2B employee, we display the employee's first and last name in the order details (admin), but the email address associated with that employee is not listed. Instead, the email address of the “main customer” is displayed by default.
We already had a feature request about this topic BUT in regards to the old B2B Suite here:
1 vote -
Finetune the personalized Checkout Message
Currently the checkout messages can’t be adjusted to exclude certain items or be fine-tuned. To customize the checkout message more precisely to your needs, it would be great to add further configurations to it.
2 votes -
Configurable mapping of the buyer reference in e-invoices (ZUGFeRD / XRechnung)
In the current default behavior, the <BuyerReference> field in the generated e-invoice (ZUGFeRD / EN16931) is populated with the purchase order number.
However, for invoices to public sector clients (government agencies), the routing ID is generally required in the <BuyerReference> field. If the purchase order number is used instead, this can lead to:
- Validation errors in ERP/accounting systems (e.g., Lexware)
- Rejections by public sector clients
- Problems with input tax deduction
- Rejection by Peppol/XRechnung validators
Currently, there is no configuration option in the admin panel to adjust the BuyerReference mapping.
Problem:
- The<BuyerReference>parameter is not flexibly configurable by default.
- Merchants with government clients must provide the routing ID.
- - Currently, customization is only possible via:
- custom code
- event subscriber (ZugferdInvoiceGeneratedEvent)
- plugin customizations.
- This results in unnecessary implementation effort for a common scenario.Proposal
Introduce a configurable option in the document/e-invoice setup:Option A – Selection field in the Admin
In the section:
"Settings → Documents → E-Invoice"Configurable mapping field for BuyerReference (fe):
- Dropdown:
- Order number
- Customer number
- Custom field (from Customer)
- Custom field (from Order)
- Freely definable mapping (e.g., via Twig expression)In the current default behavior, the <BuyerReference> field in the generated e-invoice (ZUGFeRD / EN16931) is populated with the purchase order number.
However, for invoices to public sector clients (government agencies), the routing ID is generally required in the <BuyerReference> field. If the purchase order number is used instead, this can lead to:
- Validation errors in ERP/accounting systems (e.g., Lexware)
- Rejections by public sector clients
- Problems with input tax deduction
- Rejection by Peppol/XRechnung validators
Currently, there is no configuration option in the admin panel to adjust the BuyerReference mapping.
Problem:
- The<BuyerReference>parameter is not flexibly configurable by default.…3 votes
- Don't see your idea?