- or
109 results found
-
Allow customers to manage subscriptions in STATE_PAYMENT_FAILED
Currently, subscriptions with the state STATEPAYMENTFAILED can no longer be managed by the customer through the storefront customer account.
While the subscription itself remains active and its next execution date continues to be calculated, the available subscription actions are no longer displayed. As a result, customers cannot react to a failed payment themselves, for example by pausing or cancelling the subscription.
The subscription can still be managed through the Administration, which means customers need to contact the merchant's support team to make these changes.
Current behavior:
When a subscription enters STATEPAYMENTFAILED, the customer cannot use the…1 vote -
Clean the cache partially
It should be possible to clean the cache partially. In this way the server is not forced to rebuild everything, and it's really important for performances (also PSH told me that). Check how Adobe manage it: https://experienceleague.adobe.com/en/docs/commerce-operations/configuration-guide/cli/manage-cache
1 voteNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Support partial quantities and decimals in order quantity & inventory
As a merchant, I want to manage and sell products in partial quantities or decimals, so that I can efficiently handle use cases like selling goods by weight, length, or volume, and better meet the needs of industries requiring fractional units.
This will improve flexibility for different business models and ensure seamless inventory management and customer satisfaction.
2 votesNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Managable Baskets per Project
Currently it is not possible to order for multiple projects - you only have one basket at a time. In B2B companies employees might have different projects they work and have to order stuff for. Also, budgets and contingents can only be assigned on role level but not project specifically.
Current workaround: Customizing and/or doing manual paperwork to document project specific purchases1 vote -
Cooperation with PIM software
Cooperation with PIM (Product Information Management) software like Pimcore or Akeneo. These both software tools are Open Source. Goal is to better and faster integrate the PIM software with Shopware 6.
1 voteNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Bulk translation editor for CMS element config in Layout tab
Currently, when managing translations for CMS configurations (such as a text block, images, ...) within product or category pages, the process is quite time-consuming. We need to manually switch languages and update the field one-by-one for each language. For stores with multiple languages, this creates a lot of overhead for even small content updates like updating a photo.
I’d like to propose a bulk translation editor that allows us to edit the config of a CMS element across multiple languages in one view, similar to how snippet management already works at this moment. This would greatly improve usability and efficiency…
1 voteNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
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…
2 votesGathering 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.
-
Mark debtors and employees better
At the moment it is not possible to recognize debtors and employees of the debtor in the administration. It would be good if this can be better recognized in the administration. If necessary, it would be useful to be able to manage customers of the customer directly in the administration (add, edit, delete, etc.).
2 votes -
B2B: Customer specific rebates
It is possible right now to manage customer specific prices. Several businesses are working the other way round and using the MSRP together with a customer specific rebate. As this data already sits in the ERP systems, it should also be usable in the Shopware B2B components.
1 vote -
Management of "Basic information" (Stammdaten) / Brands
Challenge:
Currently its not possible to maintain all data of the shop (address, banking etc.) centrally and display it flexibly in documents, imprint, mail templates...2 votesThis problem does only apply to a very niche target group and is mainly useful if a customer does want to try out new markets "quick and dirty".
Usually, there are other processes and concepts in place to handle those main information and merchants do not need additional small configuration help within the shopware admin to represent their company structure setting in terms of addresses.
-
Show detailed discounts in the cart overview
When using the quote management function in the B2B components, as the one asking for the offer I want to see what type of discount has been given.
Right now, you can only see the substracted discount but not if it is a total discount in € or a percentage discount.1 voteNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Folder structure for documents
An enterprise customer is looking for a way to implement a "Aktenschrank" of sorts. He wants all sorts of documents sorted in one place. He wants to be able to see and manage the complete correspondence with the merchants. Orders, invoices, cancellations, and individual documents such as a "data sheet" or a "laboratory report" could be stored here.
1 voteHi there!
Thank you for sharing this idea with us and for your patience while it’s been on the portal. After reviewing it again, we’ve decided not to move forward—our priorities have shifted since it was first posted. Please keep the feedback coming; your insights continue to shape what we build next!
-
Advanced product catalogue -> display new products but deactivate buy function
Extend the existing Advanced Product Catalog functionality
The existing Advanced Product Catalog should be extended to allow new added products and categories in the shop to be visible in the storefront but not purchasable by default (Not Show Add to Basket Button).
Only after explicitly adding them to the active B2B catalog should they become available for purchase. This enables merchants to showcase their full product range—e.g. for previews, B2B catalogs, or product teasers—without making new items immediately orderable. It supports better assortment planning, pre-marketing, and channel-specific catalog management.
3 votesNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Native Multi-Vendor Marketplace Engine + Next.js Headless Support
Shopware 6 is excellent for single-vendor eCommerce, but it lacks core features required to build true multi-vendor marketplaces like Amazon, Etsy, or Alibaba. I propose a Marketplace Engine as a core module or premium extension with:
Vendor Accounts: Sellers can register and manage their own products, orders, and store settings from a dedicated dashboard.
Split Payments & Commissions: Automated payment distribution using Stripe Connect, PayPal Payouts, etc., with platform-level commission control.
Product & Seller Reviews: Customer reviews for products and vendors with moderation workflows, boosting trust and SEO.
Search Personalization: Intelligent search with vendor filters, ratings, and behavior-based ranking. Ideal…
1 voteNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Unstable Behavior of the Rich Text Editor in Content Modules
Background:
As a team that works extensively with Shopware’s CMS and builds sophisticated pages via Shopping Experiences, we’ve repeatedly encountered critical usability issues with the built-in rich text editor used in content modules and custom fields.Problem:
The current text editor behaves inconsistently and creates significant friction in content workflows:It frequently injects arbitrary CSS classes into the HTML output without user input.
There is no easy way to reset text color back to the default.
When applying formatting such as bold, it sometimes adds font color tags even though no color change is intended or visible.
Bullet points are…
2 votesNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
If this is still important for your setup, a Shopware developer can build it as a custom extension. Shopware's architecture is designed to be extended, so requirements of this nature can typically be addressed at project level.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Add admin ownership to all (sales channel) entities
There have to be two types of admin users:
1. Super admin with all privelegies
2. Admin userThe super admin can see and edit all entities.
The admin user can see/use all public entites (for example categories) where the userId is NULL. He can create private entities, only visible for himself or super admins, the userId is the current admin user.
Why this idea makes sense?
Technically we just add a new context variable like the salesChannelId or languageId, the admin user can manage his own product sets without any risk to delete other products.
We could also make…1 voteNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
-
Improved coupon code generation: Reuse of patterns & exclusion of certain characters
Problem:
Currently, coupon templates (e.g., SHOP-{random}) can only be used once. If the same template is used in a subsequent campaign, Shopware prevents its creation with a message indicating that the template already exists.Furthermore, it is not possible to exclude specific characters from the random code, which can lead to potential confusion (e.g., I vs. l or 0 vs. O).
Solution/Request:
A pattern may be used multiple times as long as no duplicates are created in the generated codes.During generation, the system only checks whether a code already exists, not whether the pattern has already been used.
Optional…
2 votesGathering 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.
-
Offline/Developer mode for the commercial plugin in local development environments
Partners and agencies often work on multiple client projects simultaneously. Consequently, a local development environment may contain extensions for various clients, even though those extensions are neither actively used nor tested there.
The commercial plugin currently checks installed extensions and their license status but cannot distinguish between an extension that is merely part of the local development environment and one that is actually in use. In development environments, this can lead to unexpected license checks or subsequent actions.
An optional offline or developer mode for local development environments—intended exclusively for non-production systems—would be beneficial. Alternatively, a way to clearly designate…
2 votesGathering 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.
-
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…
2 votesGathering 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.
-
Customer Group Not Stored with Order Could Lead to Inconsistent Behavior
Actual behaviour:
It seems that Shopware does not store the customer group with the order, instead retrieving it from the customer record when the order is updated. This behavior might lead to potential inconsistencies in how orders are processed, especially if the customer group changes over time.
Additional Notes:
Other shop systems store the customer group along with the order to maintain consistency.
Shopware triggers specific rules or actions based on the customer group, so this behavior may cause issues with rule application or order management.
While this may be intentional, it could lead to unintended changes in customer-specific behavior,…1 voteNot enough interest
We’re closing this idea because it has not received significant interest or activity over the past 12 months. This helps us keep the idea portal focused on the topics that are most relevant to our community.
Thank you for taking the time to submit and support it. We’ll continue to monitor customer needs and may reconsider the topic if interest grows in the future.
- Don't see your idea?