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

33 results found

  1. After manual status change in the orders, even if I delete all the flows in the shop, Shopware6 always asks me to send emails to the actual customers. I need settings the skip this step.

    8 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

    1 comment  ·  Automation  ·  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. Backend Notification when multiple users working in parallel

    Providing a way for shopware to handle multiple people editing the same

    The following frosh feature (FroshSimultaneousEditNotification) for sw6 in the core
    https://github.com/FriendsOfShopware/FroshSimultaneousEditNotification

    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

    1 comment  ·  Automation  ·  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. The current order status triggers in the Flow Builder are limited, requiring users to set up individual triggers for each specific order status. To react to "any order status change" you would currently have to set up multiple identical flows.
    We propose the addition of a more versatile "Order Status Changed" trigger that allows users to create workflows responding to any change in order status.
    This applies to order status, payment status, delivery status, ... any fields that are currently very strict and could be handled more generally as well.

    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

    1 comment  ·  Automation  ·  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. There is currently no flow/trigger for the expiry of subscriptions or the renewal of subscriptions.
    So far, this is only possible via time-controlled flows, but this is not very practical for customers.
    It would be essential for customers to be able to create a flow for a subscription that is about to expire and a flow for notifying them of the renewal of a subscription.

    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  ·  Automation  ·  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. Make it possible to transform images (especially product images) into into webp or avif. Here, you should select which one to use. Also: if you want to delete the original from the media storage.
    Why: For SEO, you get a better rank while the website loading faster. The plugins for doing this are terrible.

    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  ·  Automation  ·  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 nice to have the possibility to use SQL commands for filling fields in a store page. It would be helpful, for example, to automatically display an overview of the store's shipping costs or to automatically implement values from the database that are relevant for customers in a store page without having to adapt all store pages with these values when changes are made.

    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  ·  Automation  ·  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. Currently, at many places in the administration, there is the option to use an auto-completer to add values to a field one at a time. An example for this would be "add products to a 'product is one of...' field in the rule builder or the selection of products assigned to a category.

    It would be helpful to paste a list of identifiers (e.g. product numbers) into these fields and get them assigned in one go. Specifically with large lists, that would save a lot of "clickwork" in the administration. Some simple reporting (failures / successes) in a message window…

    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  ·  Automation  ·  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. It should be possible to have a condition with "contains one of" or "does not contain any of" in addition to the condition "is one of" or "is not one of" for certain conditions. This also allows you to filter for only a certain part of the text in order to obtain further options from the rule builder.

    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  ·  Automation  ·  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. Adding a condition in the Rule Builder to find out the number of different manufacturers of the products in the shopping basket. This can be used, for example, for discounts on products from different manufacturers. Currently, it is only possible to use the general number of products in the Rule Builder as a condition.

    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  ·  Automation  ·  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. Currently, all your flows are in one continuous list, all the actions across the whole shop are mixed together.

    Adding a few additional flows can be enough to have a bad experience in overseeing all your flows.
    It would be great, if you can organize your flows with custom groups.

    Group examples:
    1. Initial order flows
    2. Status mail update flows
    3. Login flows
    4. Review flows

    Functionality
    1. You see your custom added groups
    2. You are able to reorganize your groups and the flows to different or new groups.

    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  ·  Automation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Improve the visibility of active and inactive status of rules within the Rule Builder.
    It is possible to extend the list view to check where the rule is assigned but that clutters the GUI with unnecessary information.
    An added red or green light would probably do the trick.
    That would make it easier for the admin or editors to delete old and unused rules.

    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  ·  Automation  ·  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. The problem: As soon as you have to generate more than 1000 variants in the Administration, it always terminates with the error message Serialization failure: 1213 Deadlock found when trying to get lock . The problem can be found via Google very often in relation to Shopware 6 also, that if you ever want to generate more than 1000-2000 variants, it constantly aborts because of a database error.

    It would be great if you can outsource the variant generation in the message queue, so that you do not have to actively leave the page open for hours for 100k products.…

    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  ·  Automation  ·  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. If a webhook call in a Flow
    Builder flow fails today, it is captured in a log, but no action is
    taken on it beyond that. This makes the webhooks unreliable
    as if there is ever a failure, the customer wouldn't know
    without actively monitoring the logs. Adding a configurable
    retry process (number of times to retry and retry interval)
    would allow customers to have more confidence in using
    Flow Builder webhooks.

    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  ·  Automation  ·  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. Currently the rule builder has some usability traps that could be improved.
    This is esp. important for merchants working with a lot of different rule with different users.

    10 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

    3 comments  ·  Automation  ·  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. Description of the opportunity: In Flow Builder, the webhooks are effectively notifications only. By extending the capabilities to be able to consume the response from the calling system and pull information out of the response, we could do further no-code business logic rules in Flow Builder.
    For example, as part of a shopper registration workflow, Shopware could potentially submit that information via webhook to System A, System A might make some decisions internally about what customer group that shopper should belong to and respond to the webhook with an answer. Based on the response, in the flow, Shopware could determine…

    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  ·  Automation  ·  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. There are missing a lot of conditions that would be very helpful in the Rule Builder, for example:
    - order placed by a customer in frontend or manual order by admin in the backend
    - order has a document xy (to check e.g. if invoice has been already generated)
    - more entities with custom fields as condition, for example "Order with custom field" or "Payment / shipping method with custom field"
    - and a lot more

    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  ·  Automation  ·  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. Shopware has some custom attributes that can be set on the order via Flow Builder or via API. However, these seem only to be able to be placed on the order, nothing on the line item, product, or customer.

    Challenge we're trying to solve: Adding custom attributes allows merchants a lot more flexibility in how to handle line items, products and users and could be used for many different purposes provided that they are readily available via webhooks and APIs

    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  ·  Automation  ·  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. There should be a trigger in the Flow Builder for customers who give a feedback. So it will be possible to send them an email automatically.

    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  ·  Automation  ·  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. As a shop owner, I want to be informed about anomalies in my shop. Example: At a normal day, the shop makes 100 offers per day. But in case of a price error the shop makes 1000 order per hour. For this it would be great so set "alerts" based on rule. Condition: "amount orders per second/minute/hour/day greater than 1000" > mailt to shop owner.

    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

    1 comment  ·  Automation  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Current problem: You cannot send e-mails with "back-in-stock" notifications or use mailings for your internal staff if products need to be reordered
    Proposed approach: certain product related attributes should be triggerable in the flow builder

    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  ·  Automation  ·  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?