42 results found
-
Manufacturer count in Rule Builder
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 -
Retry logic for webhooks
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.5 votes -
Generating variants
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 -
Rule Builder administration improvements
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.12 votes -
Bunch of new conditions for the Rule Builder
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 more2 votes -
Add Custom attributes via Flow Builder on line items, products & users
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 APIs2 votes -
Ability to use data from the response to a webhook call
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 -
Flow Builder Trigger for Customer Feedback
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.
4 votes -
Product Related Flowbuilder Reactions
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 builder7 votes -
Alerts for anomalies
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 -
Flowbuilder Timeframe Setting
Current problem: You cannot prepare campaigns or flows for a certain time period.
Current workaround: with rule setting for shopping experiences and or promotions you can already display certain content for a limited time period. However it would be handy to have the possibility to prepare whole campaign worlds upfront. For flows we do not have a workarount so far.
Hypothesis: By being able to set timeframes merchants can automate even more of their processes. Targeting of certain customer segments gets easier.
Possible scenarios: Black friday campaigning with landingpage, product visibility, e-mailings and promotion codesregular flows: every three months trigger…
3 votes -
Disable Shop/Prices with Rules
As a shop owner I want to only show prices for certain customergroups and show the MRP to all other groups.
3 votes -
Flowbuilder triggers creation of promotion
Current problem: you cannot create a promotion directly within the flow builder but have to configure many steps via tags to fulfill that purpose. That´s quite complicated and limits the customer loyalty options the flow builder could give to merchants.
Current workaround: set a tag as action in flow builder, reuse this tag on promotion level and in a separate step configure sending out an e-mail to customers with this promocode3 votes -
Rules by localization
Current problem: You cannot determine product prices based on cities/local place from where a customer wants to shop from. Ideally this is already possible without a login.
2 votes -
Event-/Ticketsystem
Implement an event-/ticket system to help merchants sell events and or tickets within one system.
A current struggle oftentimes is, that mixed baskets lead to difficulties in configurations.3 votesCurrently this will not be covered by Shopware. Most merchants using a Ticketsystem/selling events do have individual requirements that would be difficult to cover for a broad target group.
-
Rules by Referrer
As a merchant, I want to choose different layouts for a product detail page depending on the sessions referer, to address these customers optimally
Should be part of the session context and available in the conditions to decide which layout is choosen, depending on URL parameter2 votes -
Select multiple Dynamic Product Groups
Current problem: you cannot assign multiple DPG to build a category. Therefore you have to define and create a category elsewhere and cannot do it dynamically within shopware.
2 votes -
Flowbuilder Webhooks UX Improvements
The current UX for setting up a Webhook is only understandable for a "technical" person.We should ensure, that its easy understandable even for non-technical people to set up a webhook in the flow builder.
2 votes -
Shopware as a marketplace tool
As a shop owner I want to use Shopware as a market place
so that merchants have the option to sell their goods through a platform.2 votesWe are currently not planning to set up Shopware as a market place.
To connect your store to several market places you can search for plugins or apps within our store.
-
Rule combinations
Problem: It is not possible to combine two or more rules, you always have to create a completely new individual rule. If you want to refer to one condition that does not change in many cases this is a lot of additional manual work.
Description: most common example is having a promotion rule that refers to a category and defines a discount of percentage.
- rule A: category trousers + 20% discount
- rule B: category trousers + 40% discountProposed solution: you just need to change the discount condition
1 vote
- Don't see your idea?