- or
No existing idea results
- ~ No ideas found ~
1558 results found
-
Allow approvers to edit orders in B2B-Approval-Workflows
Problem Description:
In the current B2B approval workflow, users with an Approver can only approve or reject orders that are subject to approval rules.
Even if the role permissions are explicitly set to allow order-related actions, the approver cannot make any changes to the order before approving it.
This is a limitation for real-world B2B processes, where ordering mistakes are common and must be corrected by the approver instead of rejecting and recreating the order.
Current Behavior:
When an order requires approval:
- The approver can only approve or reject the order
- The approver cannot:
- Change product quantities
- Remove order positions
- Change payment method
- Change shipping method
- Edit billing or shipping addresses
- Write a comment on the order, regardless of approvalThis behavior applies even if the corresponding permissions are assigned to the approver role.
Expected Behavior:
Approvers should be able to edit an order before approval, according to the permissions defined for their role.
If the role permissions allow it, an approver should be able to:
- Remove order line items
- Adjust product quantities
- Change payment method
- Change shipping method
- Edit billing and shipping addresses
- Regardless of approval or rejection, write a comment on the orderThe approval decision (approve/reject) should then apply to the modified order.
Business Impact:
In B2B commerce, approval workflows are meant to:
- Correct ordering mistakes
- Ensure compliance with company rules
- Avoid unnecessary rejections and re-ordersRestricting approvers to only approve or reject orders leads to:
- Inefficient workflows
- Increased manual effort
- Poor user experience for B2B customersThis behavior does not reflect common B2B purchasing processes, where approvers are expected to correct errors rather than reject orders entirely.
Problem Description:
In the current B2B approval workflow, users with an Approver can only approve or reject orders that are subject to approval rules.
Even if the role permissions are explicitly set to allow order-related actions, the approver cannot make any changes to the order before approving it.
This is a limitation for real-world B2B processes, where ordering mistakes are common and must be corrected by the approver instead of rejecting and recreating the order.
Current Behavior:
When an order requires approval:
- The approver can only approve or reject the order
- The approver cannot:
- Change product quantities…6 votes -
Structured data for AI readability
I recently stumbled upon this press release by one of our partners - basically an ad for their plugin: https://www.openpr.de/news/1299320/Shopware-Shops-werden-KI-sichtbar-mitho-veroeffentlicht-KI-Agentic-Commerce-Plugin.html
However, as Shopware wants to go ahead with AI massively, the proposed features seem to be basic when it comes towards being prepared for AI readability:
- structured product and category feeds in JSON format
- llms.txt and other manifests for AI
- precise microdata and JSON descriptions of variants, prices, shipping etc.
7 votes -
Central Management and Exclusion of Image Keywords in Shopware
Problem:
The Shopware Image Keyword Assistant generated irrelevant and misleading keywords for a product image. In this specific case, keywords such as “Kanalisation,” “Kanalschacht,” and “Loch” were detected or generated — likely based on a small detail within the image — and do not accurately represent the product. These terms are inappropriate and not acceptable from a merchant’s perspective.
Example of generated keywords:
“Loch, Abtropfen lassen, Kanalisation, Kanalschacht, Loch, Abtropfen lassen, Kanalisation, Kanalschacht, Bodenmatte, Gepäckmatte, Autoabdeckung, Kofferraummatte, Rutschfeste Matte, matte de, tappetino auto, sotto-pavimento?, antiscivolo, tappeto auto”
The terms “Kanalisation,” “Kanalschacht,” and “Loch” are clearly not relevant and do not meet expected quality standards.
Current Limitation:
At present, Shopware does not provide a way for merchants to centrally exclude or remove unwanted keywords. The only option is to manually edit keywords per media item in the media library. This becomes highly inefficient when the issue affects multiple assets (e.g., 50 images all containing the same incorrect keyword like “Kanalisation”).
Proposed Solution:
Introduce a centralized/global keyword management feature that allows merchants to:
- Define a list of excluded keywords (blacklist)
- Automatically prevent these keywords from being generated in the future
- Remove these keywords across all existing media assets in bulk
- Optionally trigger an update of affected metadata (e.g., alt texts) when keywords are removed
This would significantly improve efficiency, ensure higher data quality, and give merchants better control over automatically generated content.
Problem:
The Shopware Image Keyword Assistant generated irrelevant and misleading keywords for a product image. In this specific case, keywords such as “Kanalisation,” “Kanalschacht,” and “Loch” were detected or generated — likely based on a small detail within the image — and do not accurately represent the product. These terms are inappropriate and not acceptable from a merchant’s perspective.
Example of generated keywords:
“Loch, Abtropfen lassen, Kanalisation, Kanalschacht, Loch, Abtropfen lassen, Kanalisation, Kanalschacht, Bodenmatte, Gepäckmatte, Autoabdeckung, Kofferraummatte, Rutschfeste Matte, matte de, tappetino auto, sotto-pavimento?, antiscivolo, tappeto auto”
The terms “Kanalisation,” “Kanalschacht,” and “Loch” are clearly not relevant and do not…
3 votes -
Shopware Account Plugin License List Update
The current license list overview of the shop in the account.shopware.com is sadly not really handy for customers / agencies.
When updating to later Shopware Versions, you need mostly plugin updates to get back from a broken to a working state (e.g. 6.6 > 6.7, php bin/console fails as well):
- Therefore I have to go to said website, search for the plugin name (somehow over name / description mixed, because names are handled differently in the search)
- Then click on the plugin (when i finally found it) and get the update version.
- Another plugin must be found the same way again.
A better solution would be:
- Make the search icon search over all tab categories (rent + free + archived..)
-> faster search of single plugins
- Show the technicalName in the license list table to make it "searchable" and or via CMD/STRG+F
-> Plugin Descriptions are different in store than in plugin composer.json -> always hard to find (especially with german/english translations)
- Add function to shopware-cli that you can update / migrate plugins from custom/plugins structure to composer.json
-> handy one command to select a list of plugins to update the latest version / migrate to composerThe current license list overview of the shop in the account.shopware.com is sadly not really handy for customers / agencies.
When updating to later Shopware Versions, you need mostly plugin updates to get back from a broken to a working state (e.g. 6.6 > 6.7, php bin/console fails as well):
- Therefore I have to go to said website, search for the plugin name (somehow over name / description mixed, because names are handled differently in the search)
- Then click on the plugin (when i finally found it) and get the update version.
- Another plugin must be found the same way…
2 votes -
Checkbox für AGB entfernen, weil rechtlich unnötig
Laut https://www.heise.de/hintergrund/Warum-im-Netz-Checkboxen-fuer-AGB-und-Datenschutz-meist-ueberfluessig-sind-10449542.html braucht man keine Checkboxen für Datenschutzerklärung und AGB.
Durch das Entfernen der Checkbox für die AGB im Checkout ist der Checkout viel schneller und einfacher.
Bei der verlinkten Seite sind Formulierungen für den Text angegeben. Ohne Checkbox muss der Text angepasst werden.
Viele Besucher übersehen die Checkbox, klicken auf den Kaufen-Button und bekommen dann eine Fehlermeldung, dass sie erst einen Haken setzen müssen.
23 votes -
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…
2 votes -
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…
2 votes -
Packaging Unit Recommendation for B2B Products
Many B2B merchants sell products that are physically supplied in packaging units (e.g., 20 pieces per carton) while still allowing customers to order any quantity on a per-piece basis.
Currently, Shopware provides features such as tier pricing, minimum order quantities, and quantity steps. However, there is no native way to define a packaging unit for a product and use it as a recommendation rather than a restriction.
A valuable addition would be the ability to:
- Define a packaging unit size per product (e.g., 20 pieces)
- Display a recommendation in the buy box suggesting the next full packaging multiple based on the selected quantity
- Optionally provide convenience actions such as “+1 packaging unit”
- Encourage ordering full packaging units without enforcing quantity restrictions
The underlying product and inventory logic should remain unchanged:
- No product variants are required
- No separate products for packaging units are required
- Inventory should continue to be managed on the regular product level
- The cart should continue to process only the actual ordered piece quantity
This would help B2B merchants optimize logistics and packaging efficiency while maintaining maximum flexibility for customers.
Many B2B merchants sell products that are physically supplied in packaging units (e.g., 20 pieces per carton) while still allowing customers to order any quantity on a per-piece basis.
Currently, Shopware provides features such as tier pricing, minimum order quantities, and quantity steps. However, there is no native way to define a packaging unit for a product and use it as a recommendation rather than a restriction.
A valuable addition would be the ability to:
- Define a packaging unit size per product (e.g., 20 pieces)
- Display a recommendation in the buy box suggesting the next full packaging multiple based on…
2 votes -
Revocation button for Online-Shops
The revocation button for online stores will become mandatory in the near future. You should therefore keep an eye on this now.
https://www.versandhandelsrecht.de/2024/03/27/widerrufsbutton/
https://www.golem.de/news/neuerungen-bei-onlinekaeufen-der-widerrufs-button-kommt-2507-197913.html
https://www.bmjv.de/SharedDocs/Gesetzgebungsverfahren/DE/2025_GAendVVVR.html?nn=110490
21 votes -
Easier customization of email templates
Customizing email templates is usually quite complex and hardly feasible for the average customer. For example, adding the manufacturer's name for each item in the order confirmation.
The entire process of customizing email templates should be significantly simplified and made much more intuitive. We also receive a large number of support requests regarding this.
4 votes -
AI Product Advisor
Not sure if this is on the roadmap or to be announced at SCD but I was looking for some skin care products and asking Gemini to find the right ones from a specific webshop were I always order so I asked Gemini if it would not be a good move to have this embedded directly in the webshop and this was the result:
You are hitting on the exact nerve center of where e-commerce has moved. Using an LLM as a "use-case to product" translator is a night-and-day upgrade from classical parametric search (clicking checkboxes for sizes, brands, and colors).
To answer your question directly: Yes, this absolutely exists today—both via ecosystem plugins and natively. However, the market is currently split between the "Enterprise Giants" rolling out massive native consumer assistants, and "Platform Ecosystems" relying on app stores/plugins to bridge the gap.
Here is a breakdown of how this capability looks across Shopware and its major competitors right now:
1. Shopware
Since you are working at Shopware, you'll be glad to know the community has already started building this.
- The Reality: It currently exists primarily as a plugin/extension layer rather than a core, out-of-the-box native feature.
- How it works: Extensions like the AI Product Advisor (available in the Shopware Store) integrate directly into the Shopware 6 CMS via API. It connects OpenAI assistants (like GPT-4o-mini) to the store's product catalog. It can read product properties, ask dynamic follow-up questions, and map a user's prose back into valid Shopware filters to display exact product matches with tailored explanations.
2. Shopify
Shopify has been very aggressive with its AI suite, Shopify Magic and its AI sidekick, Sidekick.
- The Reality: Native focus is mostly merchant-facing (generating copy, editing images, analyzing store data). For the front-end consumer-facing conversational shopping assistant, Shopify still relies heavily on its App Store.
- How it works: The Shopify App Store is flooded with highly advanced solutions (like Shoply AI, eesel AI, or Prefixbox). These apps embed a widget directly into the storefront, ingest the live Shopify product feed, track real-time inventory, and offer a "chat-to-checkout" experience where the AI handles the "why this product fits your goal" explanation.
3. Adobe Commerce (Magento)
Adobe treats AI through a highly enterprise, data-centric lens using Adobe Sensei / Adobe AI.
- The Reality: Magento’s native AI focuses heavily on behavioral and catalog data processing rather than an open-ended "chat box." It looks at a shopper's real-time intent and automatically injects Product Recommendation Units onto the page.
- How it works: If you want a fully conversational "explain why this works for your use case" assistant on Magento, merchants typically use third-party MCP (Model Context Protocol) servers or enterprise conversational AI integrations. This allows external LLMs to securely "query" the Magento database via natural language to help the shopper.
4. The Megabrands (The Native Benchmarks)
If you want to look at who is doing this natively at scale without plugins, look to the massive marketplaces:
- Amazon's Rufus: Rolled out globally, Rufus lives right in the search bar. You can type, "I want to start a backyard container garden in a rainy climate, what do I need?" and Rufus will curate a list of pots, soil, and seeds, explaining exactly why it chose them based on listing data and millions of user reviews.
- Walmart's Sparky: A fully agentic assistant embedded natively in their app that handles complex, goal-oriented shopping queries.
The Strategic Opportunity for Shopware
As someone shaping the future of Shopware, the massive opportunity here lies in Native Platform Integration rather than leaving it to third-party plugins.
When a shopping assistant is a third-party plugin, it frequently suffers from latency, disconnected data silos, and "hallucinated" answers because it doesn't truly understand real-time inventory or complex B2B pricing rules.
If Shopware can make a Semantic Search & Use-Case Advisor a native, core capability of its core platform, it would give merchants a massive advantage. Imagine a merchant being able to simply check a box in the Shopware Admin that says "Enable AI Conversational Discovery," and the platform natively builds the vector embeddings of the catalog—ensuring 100% accurate product recommendations with context-aware explanations.
Not sure if this is on the roadmap or to be announced at SCD but I was looking for some skin care products and asking Gemini to find the right ones from a specific webshop were I always order so I asked Gemini if it would not be a good move to have this embedded directly in the webshop and this was the result:
You are hitting on the exact nerve center of where e-commerce has moved. Using an LLM as a "use-case to product" translator is a night-and-day upgrade from classical parametric search (clicking checkboxes for sizes, brands, and…
2 votes -
Custom Products: Add weight to option values and include it in shipping weight calculation
In some cases the shipping weight may change substantially depending on product configuration using the Custom Products extension. However, merchants cannot define additional properties such as weight for custom products options at the moment. This makes it more difficult to calculate appropriate shipping costs.
2 votes -
Allow copying and moving banner elements within Shopping Experiences without losing links
In Shopware 5, it was possible to move individual banners within a landing page using clipboard functionality without losing the assigned links.
In Shopware 6, this is currently not possible. Images have to be reselected from the media library, text has to be rewritten, and links have to be reassigned manually.
Especially for homepages and landing pages with multiple banners, it would be highly beneficial to allow copying and repositioning content within a Shopping Experience while keeping all existing configurations (images, text, links) intact.
3 votes -
Hide buy button for specific products on sales channel level
Implement an option that allows hiding the buy button for specific products. Moreover, it should be possible to hide the buy button for specific sales channels while it continues to be displayed in other sales channels.
6 votes -
Mark quotes with message in the quote listing
EN
When requesting quotes via B2B Components, shop customers have the option to send a message. Unfortunately, there is no indication in the quote list that a message has been sent. No additional fields are available either. Our client’s request is as follows: please mark quotes that include a message directly in the listing, for example using a speech bubble icon or similar.
DE
Wenn über B2B Components Angebote angefragt werden, hat der Shopkunde die Möglichkeit dabei eine Nachricht zu schicken. Leider ist in der Angebotsliste kein Hinweis darauf zu finden, dass es eine Nachricht gibt. Weitere Felder stehen ebenfalls nicht zur Verfügung, Der Wunsch unseres Kunden lautet: Bitte Angebote mit Nachricht bereits im Listing markieren, zum Beispiel durch ein Sprechblasensymbol oder ähnliches.EN
When requesting quotes via B2B Components, shop customers have the option to send a message. Unfortunately, there is no indication in the quote list that a message has been sent. No additional fields are available either. Our client’s request is as follows: please mark quotes that include a message directly in the listing, for example using a speech bubble icon or similar.
DE
Wenn über B2B Components Angebote angefragt werden, hat der Shopkunde die Möglichkeit dabei eine Nachricht zu schicken. Leider ist in der Angebotsliste kein Hinweis darauf zu finden, dass es eine Nachricht gibt. Weitere Felder stehen ebenfalls…2 votes -
Warenkorb Spalte "Produktnummer" auch für Angebote
Im Backend besteht derzeit im Warenkorb von Angeboten keine Möglichkeit, die Spalte „Produktnummer“ einzublenden, um die Artikelnummern der hinzugefügten Produkte direkt sehen zu können.
Da diese Funktion bei Aufträgen bereits verfügbar ist, wäre es sinnvoll und hilfreich, die Anzeige der Produktnummer auch für Angebote zu ermöglichen.
___EN below_______
Shopping cart column "Product number" also for offers: Currently, in the backend, there is no option to display the "Product number" column in the shopping cart for offers, so that the article numbers of the added products can be viewed directly. Since this function is already available for orders, it would be useful and helpful to enable the display of the product number for offers as well.
Im Backend besteht derzeit im Warenkorb von Angeboten keine Möglichkeit, die Spalte „Produktnummer“ einzublenden, um die Artikelnummern der hinzugefügten Produkte direkt sehen zu können.
Da diese Funktion bei Aufträgen bereits verfügbar ist, wäre es sinnvoll und hilfreich, die Anzeige der Produktnummer auch für Angebote zu ermöglichen.
___EN below_______
Shopping cart column "Product number" also for offers: Currently, in the backend, there is no option to display the "Product number" column in the shopping cart for offers, so that the article numbers of the added products can be viewed directly. Since this function is already available for orders, it…
2 votes -
Shopware Analytics - Beta Phase
Following the launch of the first iteration of Shopware Analytics, we are continuing to develop the next iterations, which will further enhance functionalities. Additionally, we will steadily introduce a series of new dashboards featuring more metric visualizations. These updates will be rolled out independently of Shopware minor releases, leveraging the flexibility of our App-based service.
We invite you to explore the new features of Shopware Analytics and share your feedback. Your insights and feedback will be considered during development to ensure continuous improvement.
Here you can find the original feedback, which was the base of the first iteration: https://feedback.shopware.com/forums/942607/suggestions/45651289
95 votesWe already started the further development and already added new statistics:
Added a new KPI “Promotion codes”
Added a new KPI “Sales by manufacturer”
Added a new KPI Sales by country
Added a new KPI Best selling products
UI enhancements and technical improvements
-
JSON LD
JSON LD ist seit über einem Jahrzehnt das Standardformat, um Produktdaten in Online Shops strukturiert vorzuhalten.
Es ist deutlich einfacher zu warten, separiert die Daten klar von der Markup ... und ist von Shopware zu erwarten ;)
–
JSON LD has been the standard format for storing product data in online shops in a structured manner for over a decade.
It is much easier to maintain, clearly separates the data from the markup ... and is to be expected from Shopware ;)
9 votes -
Improve checkout message performance
The AI-generated checkout message sometimes takes 10 seconds to generate if there are many products in the shopping cart.
Many customers close the page during this time. It would be better if the messages were generated in the background beforehand or if a faster AI model were used.
4 votes -
Inheritable category and menu visibility in organizational units (B2B)
Currently, category and product visibility settings can only be explicitly configured per category within organizational units.
When a parent category is selected, the subcategories beneath it are not automatically included.
This leads to the following problems with extensive category structures (several hundred subcategories):
- very high manual maintenance effort
- increased susceptibility to errors
- poor maintainability when structural changes are made
- limited scalability in a B2B contextIn addition, the main menu must be controlled indirectly via individual assignments to the contained categories, as a blanket menu activation is not possible.
Target Image:
- Selecting a parent category should optionally include all subcategories automatically.
- Menu visibility should be configurable independently of individual assignments.
- Reduction of administrative effort for complex B2B structures.Specific Improvement Suggestions
A) Inheritable Category Visibility
Option 1: "Include Subcategories" CheckboxWhen selecting a category in the organizational unit:
☐ Automatically include subcategories
Behavior:
- Recursively activates all child categories.
- New subcategories are automatically included.
- Optionally overridable at the subcategory level.Technically feasible:
- Flag at the category assignment level
- Recursive query in the CategoryTreeLoader
- Lazy resolution in the Visibility ResolverB) Global Menu Sharing
New option in the organizational unit:☐ Show full main menu
Behavior:
- Menu structure is displayed
- Visibility of individual products remains adjustable
- Alternatively: Combination with category filter logicOptional:
- Visibility only structural (navigation visible, product access checked)Benefits
For Customers
- Massive time savings
- Significantly improved maintainability
- Scalability for large catalogs
- Fewer misconfigurationsFor Shopware
- Stronger B2B positioning
- Reduced support requests
- Less need for custom development
- Competitive advantage with enterprise customersCurrently, category and product visibility settings can only be explicitly configured per category within organizational units.
When a parent category is selected, the subcategories beneath it are not automatically included.
This leads to the following problems with extensive category structures (several hundred subcategories):
- very high manual maintenance effort
- increased susceptibility to errors
- poor maintainability when structural changes are made
- limited scalability in a B2B contextIn addition, the main menu must be controlled indirectly via individual assignments to the contained categories, as a blanket menu activation is not possible.
Target Image:
- Selecting a parent category…4 votes
- Don't see your idea?