83 results found
-
Rule Builder: Depending conditions
Time and again, customers want to create the following discount structure, for example:
Article from manufacturer A
Number of articles: 0-9 = 0% discount
Number of articles: 10-19 = 5% discount
.
.
.However, a condition with the Rule Builder is not possible here, as there is no way for a condition to refer exclusively to the results of a previous condition.
This means that you cannot use the Rule Builder to say, check whether there are 10 items from manufacturer X in the shopping basket.
The discount scenario mentioned above can therefore only be implemented using the extended…
1 vote -
Improved first-time Setup (First Run Wizard)
The revised First Run Wizard for Shopware is designed to better meet the individual needs of each merchant by dynamically adapting to specific requirements and opportunities within the ecosystem. As part of the redesign, continuous support will also be implemented, providing assistance beyond the initial setup to enable merchants to use the Shopware platform more efficiently and purposefully.
1 vote -
Make ShopwareBundle extend from Symfony AbstractBundle
https://github.com/shopware/shopware/blob/trunk/src/Core/Framework/Bundle.php#L22
It would be great if a Shopware Bundle would extend from the Symfony AbstractBundle class to be able to add bundle configuration aligned to Symfony bundles more easily. See https://symfony.com/doc/6.4/bundles/configuration.html#using-the-abstractbundle-class
1 vote -
Delayed dispatch of the "order placed" flow
For the "placed order" flow, there should be the option of a delay, as in many cases the payment method changes shortly after the order has been placed, e.g. because purchase on account is declined or the customer changes their mind.
In these cases, the order confirmation has already been sent via this flow and the mail therefore contains the wrong payment method.
Also very important if there are different e-mail templates for the different payment methods. Here too, this often leads to a problem, which could be solved by a delay.
1 vote -
Name the next major version just "Shopware"
After the Shopware 5 era and the two different products, Shopware 5 and Shopware 6, the next version should be named just "Shopware" (version 7.0.0) to get rid of this "Shopware 5" and/or "Shopware 6" thingy. It´s just "Shopware" in a specific version in the future.
Let "Shopware 6" don´t be the next Typo 3. 😉1 vote -
Correction of incompatibility with extensions
There is currently no Shopware guideline for extension manufacturers that extensions must be compatible with each other.
If an incompatibility between two extensions becomes apparent, manufacturers should be obliged (possibly contractually) to correct this incompatibility, as customers may end up paying for both extensions.
If you are dependent on two extensions, you currently have to hope for the goodwill of the manufacturers to correct the error.
1 vote -
Custom field (labels) should be translatable
It should be possible to translate the additional field labels. If I tick "Maintain in all administrator languages" in the settings, I can still only translate in DE and EN.
1 vote -
Deactivate the newsletter in the footer of the Showroom theme
It should be possible to deactivate the newsletter field in the footer of the Showroom theme by default without the need for any extra template customization.
This would be a useful extension for many users if it could be easily deactivated in the admin.1 vote -
Restrict renaming media
If a medium (e.g. image) is used in an article or a post, it should not be possible to rename it via "Content > Media", as otherwise the article will appear in the frontend without an image.
1 vote -
Mobile View: Number of shopping cart items (badget), when using a promotion
Within the mobile view, a number is displayed next to the shopping cart symbol, which describes the number of items.
However, the number also increases if there is a discount in the shopping cart, even though the customer may only have one item (badge shows 2) in the shopping cart.
This confuses customers. The badge should check whether there is a discount and deduct it from the number.
1 vote -
Note: Order for another xxx € to receive your order free
Comparable to Shopware 5, there should be the option in the standard to display the message "Order for another xxx € to receive your order free".
1 vote -
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 -
Shopping Experiences: Product slider with less than 3 products
If you insert a product slider into a shopping experience and you use less than 3 products, the products will not be centred on the page but left-aligned.
If you want to adjust this via the layout settings (for example 500px left margin), the mobile display is no longer centred.
It should therefore be possible to centre the slider regardless of the number of products stored.
1 vote -
Database ENGINE=InnoDB;
When Shopware creates new database tables, it should always add tags like the following. At least when these are the collations that are needed. Otherwise a little database misconfiguration can stop you from installing B2B-Suite for example.
COLLATE=\'utf8unicodeci\'
ENGINE=InnoDB;1 vote -
AI for error messages
More and more people without solid programming knowledge are entering e-commerce and encounter problems as soon as they encounter error messages. To counteract this, it would be helpful to install an AI solution in which the error messages can be entered, which then outputs an explanation of the message and in some cases also provides a solution.
1 vote -
Offer fraud prevention & detection for US region
Many of the payment providers in the EU handle fraud detection so there is not a division like there is in the US. Would likely need to evaluate what steps need to be taken in order for merchants to be able to use a fraud solution as well as a payment provider.
1 vote -
Entities should be aware that they are being edited
Entities that are currently being edited in the administration, whether a product, manufacturer, category, etc., should not be allowed to leave without an appropriate notice that the changes just made will be lost.
1 vote -
To do list in admin
As a store owner, I would like to inform every employee who has access to the admin about what still needs to be done in the shop (e.g. adjust product description of product x). It would increase efficient performance as everyone who has access to the admin can read and edit this to-do list. It's like a to-do list like we had in Shopware 5.
1 vote -
Make use of a template override system
Status quo
Presently, if you want to make even slight changes to an existing theme, it is necessary to write a plugin/app for this alteration.In order to lower the "barriers of entry" for non-developers and to de-clutter the amount of necessary plugins, it might be a good choice to introduce a template override/overwrite system.
Depending on the necessary resources, this might be applied either database of file based.
File based: have a custom theme folder that only contains changed template files (in original structure) and will never been overwritten by an update/upgrade. If this folder contains any altered files,…1 vote -
Multi-client capability
As a shop owner, I want to be able to operate several stores (clients) in one installation. Each store should be able to be filled, operated, and configured independently. Users can be assigned to one or more stores (clients).
1 vote
- Don't see your idea?