13 results found
-
Make first- and last name optional for company accounts
First- and last name should be optional if setting up a new customer entry through the administration or by using the register form IF it is a company account.
24 votes -
Extended debugging e-mail/template dispatch
Many customers customize the email templates for their shop. It often happens that certain e-mail templates are no longer sent because, for example, variables are incorrect.
Troubleshooting the cause is then very difficult and time-consuming because:
- There are no errors in the log with indications of the cause.
- The e-mail test function still works with the e-mail template because variables are ignored.
As a result, the e-mail template and the variables have to be checked with a great deal of effort and there are a lot of support tickets for this, as customers quickly reach their limits.
In order to…
16 votes -
Remove Admin Worker - CLI Worker as Default
Get rid of the admin worker and use cli worker as default.
22 votes -
Import/Export improvements
We continuously work on improving import and export capabilities.
Please let us know in the comments what is still missing for you.
36 votes -
Permission control based on sales channels
As a multi-language shop owner, I want my employees to have specific permissions based on sales channels e.g. they only see the orders and products according to the sales channel they are working with.
46 votes -
Preview / Simulation for Shop
A possibility to preview the complete Shop at a specific timeframe, for specific customer groups, rule-based etc.
- Categories
- CMS
- Products
- Promotions
- etc
41 votes -
Deactivate manufacturers in filters
Not every manufacturer should be filterable. Therefore it should be possible to deactivate manufacturers in filters.
7 votes -
Improve email template UX
The email templates have an outdated user experience and need easier options to edit and customise them.
16 votes -
Scheduled import/export
Implement an option that allows to schedule imports/exports periodically.
7 votes -
Import rules for dyn. product groups
As a shop owner over 100 rules for product groups have to be configured. Therefore it would be helpful to import these rule at once.
3 votes -
Dedicated rights for users in administration
Some partners manage the stores for their customers. Therefore it would be great if it is possible to give users more specific rights.
Example A: a user should be able to update the homepage with the shopping experiences, but not the content of the imprint.
Example B: a user is able to edit Flow A of the Flow Builder but not Flow B.
If it is not really comfortable to edit this in the administration, maybe it could be done over a config file, Yaml or Json.5 votes -
Merge Rule Builder and Dyn. Product Groups
Add all rules from Dyn. Product Groups into the Rule Builder and merge the Dyn. Product Groups with the Rule Builder. Advantage: The shop owner has one single point of truth where to configure all conditions within the shop. The developers have to maintain one feature instead of two.
1 vote -
Provide more migration profiles
As a merchant who wants to migrate to Shopware 6, I want a solution to minimise the effort of data migration from my current shop platform to Shopware 6.
Example areas:
- products
- categories
- custom products
- customer data
- order history
- content
- blog
- etc.3 votes
- Don't see your idea?