99 results found

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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. 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 for content managers working in multilingual shops.

   Ideally, this editor could be opened from the CMS config card in the Layout tab and show a table or structured form where we can input translations for each language side-by-side.

   Additionally, bonus points for a way to copy a translated config for a certain element to all other languages would be great. An image for example is often not translated, thus does not need a specific config for each language.

   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… more

   •  

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Content management  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. 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 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Orders & Customers  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   DECLINED  ·  AdminMarie Reckendrees (Product Manager, shopware AG) responded

   Hi 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!

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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. 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 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Sales Channels  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   DECLINED  ·  AdminVanessa Brauch (Product Targeting Manager, shopware AG) responded

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

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

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. 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 for large catalogs and vendor competition.

   Additionally, I recommend official Next.js storefront support for better performance (SSG/ISR), React developer adoption, and edge rendering via Vercel. While Shopware PWA is great, Next.js would accelerate frontend development and modernize the developer experience.

   Use Cases:

   A retailer wants to build a regional platform where independent artisans can sell directly to consumers, with the platform managing logistics, payments, and reviews.

   An eCommerce enterprise needs a scalable platform for thousands of vendors offering competitive pricing, search-filtered by seller, and user-driven trust signals.

   These features would position Shopware as a strong alternative to Magento or Shopify Plus for multi-vendor businesses and open doors to large-scale SaaS and marketplace use cases.

   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… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. 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 user

   The 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 a step forward and add userGroupId as the owner, so a selected group of admins can access their own data.
   This would also give a good base to make Shopware 6 ready to use as a marketplace system.

   There have to be two types of admin users:
   1. Super admin with all privelegies
   2. Admin user

   The 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… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  System & Settings  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. 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 configurable exclusion list for specific characters.

    Relevance increases with the growing number of parallel voucher campaigns (marketing, promotion, campaign management). Customers with f.e. 400+ promotions are having a very difficult time due to the current situation.

    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… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. 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 difficult to handle correctly — indentation from the left margin is often broken, and formatting differs inconsistently between modules or contexts.

    These bugs and inconsistencies make it unnecessarily difficult to edit and style text, especially for more complex layouts.

    Wish / Recommendation:
    We would like to see a more robust and predictable editor with the following improvements:

    Clean and controlled HTML output without injected inline styles or classes.

    A reset function for colors and formatting.

    Standardized and reliable bullet point behavior across modules.

    Generally more stability and polish, especially for professional users managing large-scale CMS layouts.

    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… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Content management  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. 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, such as pricing or discounts.

    Expected behaviour:

    It would be preferable for the customer group to be stored with the order so that it reflects the state of the customer group at the time the order was placed. This is a behavior that other shop systems commonly implement to avoid inconsistencies when updating or modifying orders.

    Would it be possible to store the customer group directly with the order upon placement to avoid potential discrepancies when editing an order later? If this is not intended behavior, it might be worth revisiting the design.

    How to reproduce:

    Steps to Reproduce:

    • Place an order with a specific customer group.
    • Update the order at a later time.
    • If the customer group has changed in the meantime, the updated order may reflect the new customer group rather than the one that was originally assigned.

    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,… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Orders & Customers  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Permissions for extension settings

    I like to set up permission for the admin user only for configuration/managment of one specific extension.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  System & Settings  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Add "Closeout" Filter to Product Overview

    A filter to show only closeout products in the product overview would simplify stock management and make it easier to identify and update these items. This is especially useful for larger catalogs and shops with frequent assortment changes.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Products, Prices & Properties  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Multi inventory data on OMS and linked to delivery points for pickup in store

    Show which warehouse was chosen in the order management. Also: show in the PDP the addresses linked to the pickup points (now one store can just have 1 address) to do omnichannel. If you want I can show you how VTEX works.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Inventory  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Customers pays for features like the B2B components

    Make it possible for the shop owner to monetize features that the shop owner activates for its customers, currently "only" the B2B components. The shop owner activates "quick orders" and "employee management" for the customer and the customer pays the shop owner money for this "package".

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Delivery status for digital products

    A delivery status should also be maintained for digital products. As some externally connected merchandise management programs import the products based on the delivery status, this leads to complications, errors and unnecessary manual intervention with digital products.

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Products, Prices & Properties  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Use image URLs in Shopping Experience layouts

    Currently it is only possible to add images to shopping experience layouts when the those files are uploaded in Shopwares Media Folder. How ever, when external systems like PIMs are used for the product data management, including pictures, it would be convinient to just add a the image URL from the external system into the shopping experience image block. This could look simular to how Youtube and Vimeo videos are integrated, where you also simply add the URL to the file.

    This is technically already possible with an HTML element, but since not everyone is familiar with working with HTML, it would be more user friendly to add this option to the configuration of Image Elements.

    Currently it is only possible to add images to shopping experience layouts when the those files are uploaded in Shopwares Media Folder. How ever, when external systems like PIMs are used for the product data management, including pictures, it would be convinient to just add a the image URL from the external system into the shopping experience image block. This could look simular to how Youtube and Vimeo videos are integrated, where you also simply add the URL to the file.

    This is technically already possible with an HTML element, but since not everyone is familiar with working with HTML,… more

    1 vote

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Content management  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Retail Media Capabilities

    Challenge/Problem:
    What is Retail Media: https://www.criteo.com/blog/wtf-is-retail-media-guide/

    Selling paid content within a shop. Currently, it would involve a lot of custom & manual effort to create & maintain paid content in SW6.

    Possible Constraints for retail media:
    * Different methods how to defining prices such as KPI based (by CR, by Traffic, by Clicks, etc.) or fixed prices
    * Time limitation of active content (fixed period, max. number of Klicks/CR/Traffic, etc.)
    * Legal requirements (paid content and product position must be clearly indicated as an advertisement)
    * Integration of third-party system
    * Integration of external admin users (e.g. paid influencer who writes a blogpost and pushes it to SW6)

    Possible use cases for retail media:
    * Teaser and Banner (PLP, PDP, Homepage, Navigation, Blogposts, LPs)
    * Paid rankings (Search, search results, PLP sorting, Recos)
    * Paid blog posts
    * Paid brand category pages
    * Paid LPs

    Solution/Approach:
    Some sort of management for marketing to create, maintain and automate paid content within admin.

    Target Group:
    Beyond
    Retail media requires a certain size and reach of an online shop within its industry in order to be attractive for brands so that their paid content would lead to significant higher sales of their products in the corresponding onlineshop.

    Challenge/Problem:
    What is Retail Media: https://www.criteo.com/blog/wtf-is-retail-media-guide/

    Selling paid content within a shop. Currently, it would involve a lot of custom & manual effort to create & maintain paid content in SW6.

    Possible Constraints for retail media:
    * Different methods how to defining prices such as KPI based (by CR, by Traffic, by Clicks, etc.) or fixed prices
    * Time limitation of active content (fixed period, max. number of Klicks/CR/Traffic, etc.)
    * Legal requirements (paid content and product position must be clearly indicated as an advertisement)
    * Integration of third-party system
    * Integration of external admin users (e.g. paid influencer who… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Content management  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    DECLINED  ·  AdminJonas Fuchs (Product Manager Data & Services, shopware AG) responded

    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—There is not enough interest. Please keep the feedback coming; your insights continue to shape what we build next!