- or
1511 results found
-
Rule Builder: Topseller from the last x days/weeks/months
In order to build additional interesting categories, with the help of dynamic groups, it would be very helpful and useful to have the rule builder rule "top sales of the last x days/weeks/months".
In combination with other conditions (e.g. from the free time category, etc.), you could use this to build exciting rules that can be stored in a wide variety of places.
10 votes -
Categories with list view
At the moment, products are shown in a "grid view." To be more efficient and order products faster, it would help to have a "list view." Just list all products among each other, with just a small picture, SKU, price, and amount; that´s it. Like it is in the existing B2B Suite.
2 votes -
Review marked as verified purchase
To enhance the validity of a review, it should be displayed if the review was written by an author who bought the product in the shop (Verified Purchase).
14 votes -
Cancellation invoice: Negative total amount like credit note
Like the credit note, the cancellation invoice should have a negative total amount.
At the moment, everything except the total amount is negative (Cancellation invoice). This can lead to problems when exporting or connecting to a CRM.
3 votes -
Digital Sales Rooms - Should be customisable like themes
It should be easy to customize Digital Sales Rooms like themes, including colors and logo.
2 votes -
Mark rules as active/inactive in the Rule Builder
Improve the visibility of active and inactive status of rules within the Rule Builder.
It is possible to extend the list view to check where the rule is assigned but that clutters the GUI with unnecessary information.
An added red or green light would probably do the trick.
That would make it easier for the admin or editors to delete old and unused rules.18 votes -
Product Bundles
With this feature, merchants can provide their customers ready-to-buy bundles (with and without discounts) and increase their sales revenue.
82 votesHi there! Thanks again for your input — it really helps us shape the product.
We’ve officially started the project on Product Bundles and are now developing a first blueprint! We’ll keep you updated on our progress.
-
Item-related discounts in the shopping cart and invoice.
We have a big problem with the fact that the discounts are only displayed as a single item. In the case of partial deliveries, the customer only receives the (too high) discount on one invoice and no discount is displayed on the second partial delivery. If products from a partial delivery are canceled, this has no effect on the discount.
3 votes -
"Contains one" or "does not contain any of" condition in the Rule Builder
It should be possible to have a condition with "contains one of" or "does not contain any of" in addition to the condition "is one of" or "is not one of" for certain conditions. This also allows you to filter for only a certain part of the text in order to obtain further options from the rule builder.
4 votes -
Remove Admin Worker - CLI Worker as Default
Get rid of the admin worker and use cli worker as default.
24 votes -
Allow SEO main category to be edited via Import/Export or any other comfortable way
It would be great if it was possible to edit the SEO main category of products in an easy efficient way - as in, not having to do this product after product by hand or via API because the former takes forever if you have a lot of products and the latter exceeds what most shop owners are capable of doing on a technical level.
A DB mapping for it in Import/Export would be a huge improvement already or perhaps a way to do this via Bulk Edit in the Admin would be another way to handle this. That way, you could go into the category overview, select a bunch of items and then set the main category for them in bulk, saving you lots of time.
It would be great if it was possible to edit the SEO main category of products in an easy efficient way - as in, not having to do this product after product by hand or via API because the former takes forever if you have a lot of products and the latter exceeds what most shop owners are capable of doing on a technical level.
A DB mapping for it in Import/Export would be a huge improvement already or perhaps a way to do this via Bulk Edit in the Admin would be another way to handle this. That way,…
8 votes -
Telephone number of the customer as a separate column in the customer overview
Shopware version 6.5.6.0 enables the query of the customer's telephone number as a mandatory field in the registration process. It would be very desirable (especially in the B2B area) if this telephone number were also prominently displayed in the customer overview as a separate column.
Currently, the telephone number can only be reached in a very cumbersome way by jumping to the customer processing and editing the address there.6 votes -
Enable to reference categories/properties etc. by other fields than ID
In shopware version 6.5.5.2 it is possible to reference certain mappings in the product import profile by fields other than the id of an entity, which is certainly helpful.
Unfortunately, there is no possibility to do it the same way in the column referencing the properties or categories of a product. No matter which other alternative mapping one chooses, e.g. when exporting the custom product export/import profile in the column for properties/categories the entities are always referenced by their internal IDs separated by "|".
It would be practical to have an option to reference these aforementioned entities by other mappings and additionally declare a separator symbol for them in the profile.
In shopware version 6.5.5.2 it is possible to reference certain mappings in the product import profile by fields other than the id of an entity, which is certainly helpful.
Unfortunately, there is no possibility to do it the same way in the column referencing the properties or categories of a product. No matter which other alternative mapping one chooses, e.g. when exporting the custom product export/import profile in the column for properties/categories the entities are always referenced by their internal IDs separated by "|".
It would be practical to have an option to reference these aforementioned entities by other mappings…
7 votes -
Product number in the category assignment
If you want to assign products in the category configuration, they are only displayed with their name but without a product number.
For products with the same or similar names, it can be difficult to assign the correct products.
The product numbers should also be displayed here.2 votes -
picture & text of properties
It should be possible to show:
the name of the color next to the picture
or
a short description next to image
with properties applied.Reason:
- names for people with color weakness
- some shops have several variants of, for example red. So the name or color code would be very useful
- description for not self explaining pictures would be much better for customers1 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 -
Separators in Advanced Search
In Advanced Search it should be possible to define the separators. Many article numbers have a " , ". Because the search interprets this as a separator, the search result is bad.
8 votes -
setting up Link-category could be transferred to other languages? (Language inheritance for landing pages)
I first set up a category as link (f.e. a link to an entity, like "category") on my standard language storeview and save.
But then I switch to the french language in the admin, the link has to be set up all over again.
It is possibly intended behaviour with good reason, but one could say that shopware would be perfectly capable to re-use the link to the "french" equivalent of the attached entity.
the answer would be: that is is not sure that is would be 1 on 1 that you would want it the same.
While this is true, i think dat it could be possible to have it initially one on one, with te possibility to "overwrite" it on the other store-language.
In tat case the user would'nt have to go trough '"double" work when in some cases multiple of these link categories would have to be created.
I first set up a category as link (f.e. a link to an entity, like "category") on my standard language storeview and save.
But then I switch to the french language in the admin, the link has to be set up all over again.
It is possibly intended behaviour with good reason, but one could say that shopware would be perfectly capable to re-use the link to the "french" equivalent of the attached entity.
the answer would be: that is is not sure that is would be 1 on 1 that you would want it the same.
While this is…
1 vote -
List Settings
Topic: Interface/List Settings for Customers, Products, and all other list views
The current configuration is very minimalist and limited. Previously, it was possible to display and edit fields such as the customs tariff number. This functionality was tremendously time-saving and practical for quick changes. We strongly urge the reinstatement of these fields.
Ideally, it would be beneficial to extend this feature to include fields that were not previously available, such as displaying and modifying phone numbers via the list view. This would further enhance usability and efficiency.
Thanks.
1 vote -
Rollback feature for shopware Update
In support tickets and in various forums you often read about problems with Shopware updates. It is not uncommon for the store (frontend and admin) to no longer be accessible after an update.
To avoid destroying the entire store or the customer's test environment, the update should check the accessibility of the frontend/admin at the end. If, for example, the browser returns an error 500, a rollback should be triggered to restore the store to its previous state.
Currently, the customer is often faced with an unsolvable problem in this case and loses a lot of time until the store works again.
In support tickets and in various forums you often read about problems with Shopware updates. It is not uncommon for the store (frontend and admin) to no longer be accessible after an update.
To avoid destroying the entire store or the customer's test environment, the update should check the accessibility of the frontend/admin at the end. If, for example, the browser returns an error 500, a rollback should be triggered to restore the store to its previous state.
Currently, the customer is often faced with an unsolvable problem in this case and loses a lot of time until the store…
2 votes
- Don't see your idea?