- or
1394 results found
-
"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 -
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 -
Gift card product
Special product type - gift card, which is also related to store credit and virtual products. Gift card can be physical and virtual.
52 votes -
SEO: meta description by AI
It would help if the meta description was generated by AI.
7 votes -
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 -
Remove Admin Worker - CLI Worker as Default
Get rid of the admin worker and use cli worker as default.
23 votes -
Rule-based activation of "B2B Component" features
As a shop owner, I want to be able to activate B2B features for specific customers based on rules. For example, all customers from the customer group "B2B" can use "Quick orders" and "Order lists".
7 votesHi there!
Thank you for sharing this idea with us and for your patience while it’s been on the portal. After reviewing it again, we’ve decided not to move forward—our priorities have shifted since it was first posted. Please keep the feedback coming; your insights continue to shape what we build next!
-
Make it possible to change the saleschannel of the customer
If the customer registers in a wrong sales channel (e.g. in a B2C store, although it is B2B) you cannot adjust this in the admin afterwards.
It would be very helpful if you can customize this in the admin so that the customer does not have to be deleted and recreated.
8 votes -
Property Representation in product definable.
In Shopware 5, it was possible to set the display of the properties for the products specifically.
In Shopware 6, the display of the property is defined globally in the property itself, and it is no longer possible to display it differently for individual products in the product.
For example. The Size property is defined via the property itself and displayed globally as text. However, there is a product in which it makes more sense to display the size as a dropdown for display reasons. This is currently not possible in Shopware 6.If, for example, the display of the property could be defined again in the product itself, e.g. under Storefront presentation, this would be very helpful for many customers.
In Shopware 5, it was possible to set the display of the properties for the products specifically.
In Shopware 6, the display of the property is defined globally in the property itself, and it is no longer possible to display it differently for individual products in the product.
For example. The Size property is defined via the property itself and displayed globally as text. However, there is a product in which it makes more sense to display the size as a dropdown for display reasons. This is currently not possible in Shopware 6.If, for example, the display of the…
2 votes -
Language-specific SEO URL templates
There should be a way to create language-specific SEO URL templates, i.e. have a language switch in the administration page just like in most other settings.
Simple translations of category or product data are already possible via the corresponding .translated property, but it would be better to have full control over how the SEO URLs are generated per shop language.
This would also allow adding translatable strings to the templates (such as substituting special characters in product or category names with a language-specific URL-friendly string), which currently isn't possible.
4 votes -
Provide a new variable "shopping.description" for the layout section.
If you create a shopping page in the shopping experiences, e.g. for shipping costs or payment methods, and insert the content there, the content is displayed in the modal window.
If you now create a corresponding category for the store footer, you can assign the layout, but the content is not displayed when you click on the link in the footer.
Unfortunately, there is obviously no variable available yet that can be used to achieve the data mapping.
Just like the variable "category.description", a new variable such as "shopping.description" is therefore required.If there is another way that I have not found, please let me know.
As it is now, you have to create the content in the experience world for the modal window and also for the footer link in the layout section - standard. The content must therefore be maintained twice.
If you create a shopping page in the shopping experiences, e.g. for shipping costs or payment methods, and insert the content there, the content is displayed in the modal window.
If you now create a corresponding category for the store footer, you can assign the layout, but the content is not displayed when you click on the link in the footer.
Unfortunately, there is obviously no variable available yet that can be used to achieve the data mapping.
Just like the variable "category.description", a new variable such as "shopping.description" is therefore required.If there is another way that I have…
2 votes -
Dicount description
Add a description field to the promotions as the promotions name is not enough to identify them if you have many active promotions and the naming of the promotion is used as name in the cart so it is not possible to use an indentifyable name in the backend
1 vote
- Don't see your idea?