- or
No existing idea results
- ~ No ideas found ~
1561 results found
-
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 -
Scraper
In Odoo they have a website scraper which allows you to put the url of an existing website/ecommerce and it will create the shop and the website with the theme and snippets/images and so on from the existing website. Especially for demo purposes this could be very powerful to give a product showcase with a very personalized and themed style of the prospect's branding.
1 vote -
QOL User Experience Settings
I will take the example of warehouses but it's a general QOL functionality that could be handy. I used to work for Odoo and I'm suggesting some nice general UI improvements that would reduce clicks and manual work.
1) When you click on WH1 you open it, you don't need to click on the 3 dots
2) Once you are in WH2 on the right there would be an arrow to go to the previous or next record (in this case warehouses)
3) In the Warehouse Group when you start typing you could create a new group directly on the go by typing the name and click on create new
4) You don't need to manually click Save every time. It would save automatically for you if you go back, to the next record or to another menu item.
5) On the product page in the backend it would be nice to have a button to go directly to the frontend page to see how it looks there.I will take the example of warehouses but it's a general QOL functionality that could be handy. I used to work for Odoo and I'm suggesting some nice general UI improvements that would reduce clicks and manual work.
1) When you click on WH1 you open it, you don't need to click on the 3 dots
2) Once you are in WH2 on the right there would be an arrow to go to the previous or next record (in this case warehouses)
3) In the Warehouse Group when you start typing you could create a new group directly on the…1 vote -
Use Categories en Gender form category tree in filters
If you organize your categories by gender in Shopware, you have a clear gender-specific funnel with clear and structured navigation. Why aren't these also used in the filters, or why do you have the option to do so?
Applying all filters via attributes doesn't work well. Especially not on the brands page, where you don't have good SEO-friendly pages based on brand/category. If we enable categories and genders in the filters, we only see the male gender for unisex products when filtering for women, whereas you don't want to see men at all when you are in the women's funnel. And if we enable categories, we see duplicate categories for all genders on the brands page (deduplication is not possible). If you then click on "sneaker," for example, you don't know which gender you are going to.
For complex websites, let users choose for themselves what they want to link to the attributes (filters). The standard category tree seems best to me in that case.
Also, make categories, brands, and quicklinks dynamic. So if there are no active products from the brand or category, automatically disable them for the front-end (including the quicklink).
The brand page could also be much better in the default settings: navigate by brand by gender, meta titles and meta descriptions, search field in navigation.
If you organize your categories by gender in Shopware, you have a clear gender-specific funnel with clear and structured navigation. Why aren't these also used in the filters, or why do you have the option to do so?
Applying all filters via attributes doesn't work well. Especially not on the brands page, where you don't have good SEO-friendly pages based on brand/category. If we enable categories and genders in the filters, we only see the male gender for unisex products when filtering for women, whereas you don't want to see men at all when you are in the women's funnel.…
1 vote -
Revocation request trigger - Setting an automatic revocation tag at the relevant orders
When the revocation request trigger is used in the flow builder, it is only possible to activate the "send e-mails" or "stop the flow" process.
It would be great if the revocation request trigger would also allow to automatically set a revocation tag at the relevant order. This would help to easily mark the orders, which have been revoked.
1 vote -
Multi-user support for customer service representatives – login as any company employee in a B2B environment
In B2B transactions, customer service representatives regularly handle and process orders on behalf of customers, especially for telephone orders or orders requiring extensive consultation.
Currently, they log in to the backend with administrator rights and then use the "Log in as customer" function in the frontend to place orders directly in the shop or to assist customers with their use.
However, this approach currently only works for the primary user of a company account.
In cases where a customer uses multiple employee accounts within a company structure, it is not possible to log in as another employee of that company to, for example, place an order on behalf of a specific employee or to review their purchase approvals.
Goal / Benefit
To enable customer service representatives or administrators to log in to the shop as any employee of a company account.
This allows support staff to authentically process telephone orders, approval processes, or reorders on behalf of the correct employee.
Improved traceability (correct customer, correct rights and approvals) and simplification of customer support in the B2B environment.
In B2B transactions, customer service representatives regularly handle and process orders on behalf of customers, especially for telephone orders or orders requiring extensive consultation.
Currently, they log in to the backend with administrator rights and then use the "Log in as customer" function in the frontend to place orders directly in the shop or to assist customers with their use.
However, this approach currently only works for the primary user of a company account.
In cases where a customer uses multiple employee accounts within a company structure, it is not possible to log in as another employee of that company…
5 votes -
Allow B2B employee deletion when pending orders exist - GDPR compliance
Currently deleting a B2B employee who has pending orders fails with a raw FK constraint error (SQLSTATE 23000). The only workaround suggested is cascade-deleting the orders, which is unacceptable.
Real-world scenario: An employee leaves the company. The organization is legally required under GDPR (right to erasure) to remove that person's personal data. However, pending orders are financial records of the organization, not the employee's personal data, and must be preserved.
The fix does not require decoupling orders from customers. It only requires allowing employee_id on pending orders to be nullified (SET NULL) or reassigned to another employee before deletion. The order record stays intact, only the link to the former employee is removed.
Impact: Every B2B merchant with employee turnover faces this. In the EU, GDPR compliance is not optional - merchants cannot tell regulators "Shopware doesn't support it."
Suggested solution:
1. Change FK fk.pendingorder.employeeid to ON DELETE SET NULL
2. Provide a way to reassign pending orders to another employee before deletionCurrently deleting a B2B employee who has pending orders fails with a raw FK constraint error (SQLSTATE 23000). The only workaround suggested is cascade-deleting the orders, which is unacceptable.
Real-world scenario: An employee leaves the company. The organization is legally required under GDPR (right to erasure) to remove that person's personal data. However, pending orders are financial records of the organization, not the employee's personal data, and must be preserved.
The fix does not require decoupling orders from customers. It only requires allowing employee_id on pending orders to be nullified (SET NULL) or reassigned to another employee before deletion. The…
2 votes -
Let B2B Employees changed their own password
It should be a standard functionality that a user can change their password.
This is currently not possible.
Please implement this.
2 votes -
Nexus (Open Beta)
Nexus is an event orchestration platform that allows you to develop critical business workflows with 3rd party systems (ERP, CRM, PIM, etc).
2 votes
- Don't see your idea?