Skip to content

Shopware 6 - Product Feedback & Ideas

Interested in a direct exchange?Are you interested in a direct exchange about your business case? We would be happy to learn more about your daily business and its requirements. For this purpose, we offer you the opportunity to discuss this directly with our product management team. Book your appointment right here:Book an appointmentDo you have a specific request that you would like to tell us about? Then the following feedback portal is the right place for you.

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
Notes

Shopware 6 - Product Feedback & Ideas

Categories

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

26 results found

  1. 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 →
  2. With our plugin we want to add something to the header or footer.
    For this it must be possible that we can add something to the header or footer pagelet loaded.
    Generally it would be nice also, if Shopware provides a hook which is called every time when the generic page loader is loaded.

    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 →

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

  3. For our app in the cart hook we need the repository service and the possibility to call our own store api routes also provided by our app.
    The reason is that we have stored our surcharges / discounts in our own custom entites database table and we can't access it in the cart.
    The store api route call we need, because we want to build our own store api route to make it possible to cash the database call for a better performance.

    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 →

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

  4. We want to manipulate the sw-cache-hash cookie based on other cookies coming from request or response. We need the functionality to provide the customer different sites from the http cache based on cookies.
    For that we need a hook for the app scripts to be fired at Symfonys event 'kernel.response'. So it should be fired every time when the kernel sends the response.
    In the hook the repository service should be possible to be called inside the app script.

    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 →

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

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

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

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

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

2 Next →
  • Don't see your idea?