- or
No existing idea results
- ~ No ideas found ~
1347 results found
-
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 -
Layout for manufacturer page
Implement a dedicated layout for manufacturer pages
12 votesInitial status update
-
Cooperation with PIM software
Cooperation with PIM (Product Information Management) software like Pimcore or Akeneo. These both software tools are Open Source. Goal is to better and faster integrate the PIM software with Shopware 6.
1 vote -
Reduce data amount in checkout
Modern checkout processes only ask for necessary e.g. only e-mail & password for initial registration and then later in the checkout address step for address information.
In SW6 merchants don't have the flexibility to decide what data and at which step in the checkout it is collected.
More options to configure and individualise would help to increase CR, lower frustration potential on the customer side, and adapt to country specific requirements.13 votes -
Click & Collect
Introduce the option for merchants with local brick & mortar stores to offer click & collect in the checkout.
13 votes -
Configure password complexity
Currently, you can only configure how long a password should be and whether it should be entered twice.
It should be possible to specify the password complexity (minimum number of characters, special characters, numbers, letters, etc.). At the moment you need an extension for this.9 votes -
Setting options in the admin for potentially harmful code
Setting options in the admin for potentially harmful code, where you can set which HTML tags should be allowed and which shouldn't. This is currently mapped via shopware.yaml, but is rather laborious for customers and not possible at all for cloud customers.
2 votes -
Allocation of the sales channel directly in the shipping costs
There should be a way to assign the sales channels directly to the shipping methods in order to keep track of which sales channel the shipping method takes place in.
Currently only possible in the sales channel itself.1 vote -
Migration from various platforms
Either standard migrations from the most common platforms like Shopify would be good, and alternatively a documentation on best-practice and a guideline on how to migrate from other platforms.
Like with Magento we have used the one from Shopware, which works good. Like with Shopify we have had to write our own set of CLI tools to migrate products etc over to Shopware, but this should be a more general feature.
1 vote -
AI Copilot - ChatGPT Code Interpreter Integration
Integrate ChatGPT specifically for the use of code interpreter to be able to create shop data analysis and data visualisation for different shop entities e.g. for order statistics, (anonymised) customer behaviour, product data, recommendation performances, search statistics, etc.
More info about ChatGPT Code Interpreter: https://openai.com/blog/chatgpt-plugins#code-interpreter1 vote -
Basic Recommendation Engine
As a shop owner, I want to show cross-selling based on my customer's preferences like "other customers bought", "Recently viewed products", etc.
12 votes -
Improve Variant generator
Simplify and fix the generating of variants with several Improvements like automatically assign the properties to the variant product that have been choosen to generate it etc
13 votes -
Theme config per saleschannel
If you want to have more than one saleschannel with the same theme but have a different setting (e.g. primary color) you need to create a copy of the theme, because the theme config is not stored on the saleschannel (where it should be imho).
1 vote -
Build scss with node-sass
If nodejs is available on the system use node-sass instead of PHP Scss and Autoprefixer to compile the theme.
2 votes -
"tag"-filter in order overview
The "tag"-filter should validate on tags within the "product" entity and therefore show orders, which include articles with this specific tag / these specific tags.
2 votes -
Login with mobile number
Not everyone has an email address, but most have a cell phone number. Therefore, it would be cool if you could register in the store with your cell phone number instead of your email address, optionally if necessary.
2 votes -
Product configurator
Somewhat similar to custom products: There's no option tho to change "normal" variant, for example if a "blue" variant should always cost 5€ more than the main product. When Changing the price of the main product, the variant price should be changed automatically aswell.
3 votes -
Remove limitation to 25 results in lists, comboxes, etc.
Remove the limitation to 25 results in lists, comboxes, etc.
If you manage more than 25 languages or have more than 25 promotion rules with similar names - this problem is easy to understand. There are various places in the admin where pagination or auto-reload is given when scrolling.
The request to Shopware:
Please make this universal, and don't limit it to max 25 search results.
8 votes -
Flow Action improvements
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: allow boolean fields to be converted to string
3) Documentation for Flow Action xml is wrong
here are examples how we can define the options inside flow-action.xml
the correct way to do so is
<options>
<option value="yes">
<label>Yes</label>
<label lang="de-DE">Ja</label>
</option>
<option value="no">
<label>No</label>
<label lang="de-DE">Nein</label>
</option>
</options>there is no id or value tags which are defined in the xsd.
Solution: Either change xsd or change the documentation
4) Flow Action webhooks does not contain any information about the app like the shopId
this part just use the configured content and sends it to the webhook. if we want to execute something via flow builder action instead of app action, we cannot do this because shopId is missing.
Solution: Add app related data over headers to the Flow Action hook
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 -
Structure elements in menus: Choose visibility on viewports
If customers use structure elements in menus, these elements will lead to another click in the mobile menu. Example: Our standard menu clothing > ladies. If you add a structure element clothing > clothing > ladies, the second clothing will be ignored in the desktop menu. In mobile view you have to click on the first clothing and then on the second clothing to open the menu you wanted to reach. Make it decisible for clients.
1 vote
- Don't see your idea?