825 results found
-
Salutation on invoice delivery documents
Customers wish to have salutations and/or titles on documents. Currently, there is no possibility to do that.
1 vote -
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 -
B2B Suite: Debtor does not have to be the orderer
In order to know which employee has placed an order, orders should not be transferred to the debtor.
6 votes -
link tracking code in customer account (frontend)
As you could possibly enter a full tracking-link to the tracking-code field within the order details, it would be nice to make it clickable for the customer within his account. Currently, it is only shown as plain text.
1 vote -
B2B Suite: Rule Builder for Sales Representative
It would be very helpful to automatically assign customers to the sales representative with the Rule Builder.
For example, based on postal code areas or tags.4 votes -
Overriting Admin Components
At this point it is only possible to inject my App UI using an iFrame and also only when Shop Administrator visit my app from the navigation menu.
Overriding of existing admin components would provide a great improvement (similar to todays Plugin system). Adding custom content or custom UI elements to enrich the existing functionality.
Administrators can from then on would make use of my App Extensions by just clicking on an additional button which appears on the right place in the default UI.
5 votes -
Shipping costs per product
In SW5 it was possible to define product specific shipping costs.
10 votes -
Identify used CMS elements
It's very difficult if you have multiple editors and a lot of elements to figure out which element they are seing in order to use the same element on a different position.
As soon as you have placed an element you can't figure out what it is.3 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 -
New layout block "Last viewed products"
It would be desirable if there would be the possibility to display the "last viewed products", e.g. as a commerce block element for category pages in the worlds of experience.
4 votes -
New layout block "Accordion"
Designing a lot of text for various topics in an appealing way is not easy. An accordion is very helpful in making a lot of content more accessible to the customer. Often used for FAQ or documentation it has established itself as a standard design element in online shops and is therefore an element that should be within reach in the shopping experiences default blocks.
2 votes -
Reply directly to a contact form
It should be possible to reply to a contact form. Email from the contact request/contact form should jump in directly as a recipient when one clicks on reply.
1 vote -
Rule for user agent
As a store owner, I want to be able to show different prices to customers who are on a mobile phone than to customers on a desktop. For this, I need the possibility to have the user agent as an option in the rule builder.
3 votes -
More user restrictions
As a store owner, I want to make sure that my CI is preserved. For this, I need the possibility to enable only certain content elements for users in the administration, who should only edit the shopping experiences.
3 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:…
2 votes -
Possibility to mix kilo and gram data and display them in the shopping cart
In the frontend, for example, you can specify 1.4 kg, but this is not transferred to the shopping cart.
4 votes -
Default layout for products
Currently, it is only possible to define default layouts for categories. As it is possible to create custom product layouts, it would also be beneficial if one could assign that layout to all existing and newly created products.
This would make it much easier to assign a new layout with several thousand products.
21 votes
- Don't see your idea?