Skip to content

Shopware 6 - Product Feedback & Ideas

This is the space where you can share your ideas and feedback about Shopware 6.

How it works:

- Connect your Shopware Account or register with your email
- Use the search or choose a category for your idea to check if it has been submitted already
Upvote existing ideas, as opposed to creating multiple similar requests. Comment an idea to share extra details.
- If you create a new idea: Be clear with your idea; provide examples or even screenshots
- The more activity and votes an idea has, the higher the chance it will be implemented

Note:
- Contributions are not guaranteeing that we will take action on an idea. We will do our best to communicate why an idea may not work.
- For bug reporting, please refer to our Issuetracker

Shopware 6 - Product Feedback & Ideas

Categories

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

23 results found

  1. Our extension partners currently face growing hosting costs due to app development and require more dynamic pricing models. Our goal is to support our partners in covering their business models in our app ecosystem.

    A secure and user-friendly In App Purchase system will be implemented, enabling partners to offer differentiated value propositions through various pricing models within their apps. This promotes sustainable growth for developers and the Shopware platform, attracting even more users.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Right now it is not possible to fully utilize integrations like Omnisend nor Mailerlite that track abandoned carts, as we do not have an access to this information neither using the Admin API nor webhooks.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Admin Extension SDK / App System: Also allow displaySearchBar, displayLanguageSwitch and addSmartbarButton for normal modules like it is already possible for main modules. Like this it becomes easier to build CRUD pages.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. It would be nice if there was a switch under my extensions that deactivated all extensions at once, similar to the security mode in Shopware 5.

    DE

    Es wäre schön, wenn es unter meine Erweiterungen einen Schalter gäbe der alle Erweiterungen auf einmal deaktiviert, ähnlich wie es der Sicherheitsmodus in Shopware 5 getan hat.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. I would love it if, in addition to the installation date of an extension, if the update date would also be displayed in my extensions.

    As of now, I know when the extension was installed, but not when it was updated.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. It would be helpful, especially with several extensions, to be able to sort them. For example, you could distinguish between purchased and rented extensions.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. When creating a custom module via the manifest.xml, the iframe is always full-sized, nicely filling in all usable space in the Administration.
    When creating a custom module using the Admin Extension SDK, the iframe has a dynamic height and is not full sized. This is understandable when using the iframe in a 'card' component, but for a custom module, it should be an option to automatically size the iframe to fill the admin page.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. As an App developer, I want to hide the entire header of the page on my custom modules.

    It is currently only possible to hide the search bar.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. The manifest.xml should allow more custom field entity types.

    Currently we suggest to add the entity order_line_item.

    https://github.com/shopware/platform/blob/trunk/src/Core/Framework/App/Manifest/Schema/manifest-2.0.xsd

    Currently available types:


    <xs:complexType name="entity-list">
    <xs:choice maxOccurs="unbounded">
    <xs:element name="product" type="empty" minOccurs="0"/>
    <xs:element name="order" type="empty" minOccurs="0"/>
    <xs:element name="category" type="empty" minOccurs="0"/>
    <xs:element name="customer" type="empty" minOccurs="0"/>
    <xs:element name="customer_address" type="empty" minOccurs="0"/>
    <xs:element name="media" type="empty" minOccurs="0"/>
    <xs:element name="product_manufacturer" type="empty" minOccurs="0"/>
    <xs:element name="sales_channel" type="empty" minOccurs="0"/>
    <xs:element name="landing_page" type="empty" minOccurs="0"/>
    <xs:element name="promotion" type="empty" minOccurs="0"/>
    <xs:element name="product_stream" type="empty" minOccurs="0"/>
    <xs:element name="property_group" type="empty" minOccurs="0"/>
    <xs:element name="product_review" type="empty" minOccurs="0"/>
    <xs:element name="event_action" type="empty" minOccurs="0"/>
    <xs:element name="country" type="empty" minOccurs="0"/>
    <xs:element name="currency" type="empty" minOccurs="0"/>
    <xs:element name="customer_group" type="empty" minOccurs="0"/>
    <xs:element name="delivery_time" type="empty" minOccurs="0"/>
    <xs:element name="document_base_config"

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. What we need:
    It would be wonderful if there could be a way to provide custom CMS elements in apps.

    Why we need this:
    We always want to offer our customers the best possible solutions in our themes, including sales-promoting CMS elements. Due to limitations in the app system, we can currently only do this in our extensions based on the plugin system. Since we also offer our extensions on the basis of the app system, this results in an "unnecessary" duplication and "maintenance effort". A single, unified app is highly desirable.

    The app system lacks the possibility to provide…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Thanks for your contribution.

    Adding your own CMS elements via Apps is possible with the shopware version 6.4.17. It is possible to create new CMS elements via the Admin Extension SDK for both plugins and apps. Read the following docs article: https://developer.shopware.com/docs/guides/plugins/plugins/content/cms/add-cms-element-via-admin-sdk

    If you have any suggestions or improvements towards our approach, feel free to reach out to us.


    Thank you.

  11. Currently through Admin Extension SDK, we could add an extra table field (eg custom field data) in admin listing page of orders, products etc. Good to have it

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. When we uninstall the app, all custom entities will be removed. (without clicking "Remove all app data permanently"). Is there any option to prevent this and retain data"

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. It would be better if migration like system implemented for custom entities through app.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Since the app does not provide any hooks for review insert/update, we are posting
    custom generated review form request to the app server when review
    is added, and from there admin api will be triggered to insert reviews data along with custom entities data. But concerns regarding security in app url info, it can be directly seen thorough browser request and third person can exploit it.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. The App has been provided with a "product-reviews-loaded" hook, but it is triggering
    after loading all the reviews. Good to have a hook before loading reviews to add extra criteria and list reviews based on it.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Offer a way like in composer for apps to require e.g. other apps or other things.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. At this point it is only possible to inject my App UI using an iFrame and also only when Shop Administrator visit my app from the navigation menu.

    Overriding of existing admin components would provide a great improvement (similar to todays Plugin system). Adding custom content or custom UI elements to enrich the existing functionality.

    Administrators can from then on would make use of my App Extensions by just clicking on an additional button which appears on the right place in the default UI.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Flow Actions require some changes.

    1) Optional config, headers and parameters

    Currently according to the flow-action.xsd the tags header, config and parameters are required. Because of this, we had to add a config tag even if our action has no configs at all. It is strange that the meta tag is not required.

    Solution: set minOccurs="0" for config, header and parameters tag in the xsd

    2) it is not possible to pass the the configured checkbox over parameters. the checkbox is a boolean field and parameter is a string field, because of this, the action will not be triggered.

    Solution:…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. It would really increase the possibilty for app developers if every symonfy service can be extended with an App script.
    In detail every public funtion of a symfony service should be extendable by App scripts before and after.
    This would make much more features possible to implement with Apps comparing now.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We are not planning to expose every Symfony service with App Scripts, because we want to improve stability and maintainability for extension manufacturers, especially across major versions.


    We understand that the usage of app scripts is more limiting than simply overriding or decorating existing PHP services. In order to accommodate for the extension points that you need, we ask you to provide us with the specific scenarios (e.g. altering tax calculation, adding data to order line items) so we can build the most stable and expressive API for that.

  20. It would really increase the possibilty for app developers if every symonfy event can be accessed with an app hook.
    This would make much more features possible to implement with Apps comparing now.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    DECLINED  ·  1 comment  ·  App System  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1
  • Don't see your idea?