- or
No existing idea results
- ~ No ideas found ~
1498 results found
-
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 -
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 -
Tax-free for states/regions
It should be possible to use the option "tax-free" for countries also for states/regions.
The Canary Islands in Spain are tax-free. There is no possibility to sell products to the Canary Islands tax-free.
It´s not an option to set the tax to 0% for this region because the product will then bei sold for the gross price just with 0% tax.1 vote -
manifest.xml - Allow more customFields entites
The manifest.xml should allow more custom field entity types.
Currently we suggest to add the entity
order_line_item.Currently available types:
<xs:complexType name="entity-list">
<xs:choice maxOccurs="unbounded">
<xs:element name="product" type="empty" minOccurs="0"/>
<xs:element name="order" type="empty" minOccurs="0"/>
<xs:element name="category" type="empty" minOccurs="0"/>
<xs:element name="customer" type="empty" minOccurs="0"/>
<xs:element name="customer_address" type="empty" minOccurs="0"/>
<xs:element name="media" type="empty" minOccurs="0"/>
<xs:element name="product_manufacturer" type="empty" minOccurs="0"/>
<xs:element name="sales_channel" type="empty" minOccurs="0"/>
<xs:element name="landing_page" type="empty" minOccurs="0"/>
<xs:element name="promotion" type="empty" minOccurs="0"/>
<xs:element name="product_stream" type="empty" minOccurs="0"/>
<xs:element name="property_group" type="empty" minOccurs="0"/>
<xs:element name="product_review" type="empty" minOccurs="0"/>
<xs:element name="event_action" type="empty" minOccurs="0"/>
<xs:element name="country" type="empty" minOccurs="0"/>
<xs:element name="currency" type="empty" minOccurs="0"/>
<xs:element name="customer_group" type="empty" minOccurs="0"/>
<xs:element name="delivery_time" type="empty" minOccurs="0"/>
<xs:element name="document_base_config" type="empty" minOccurs="0"/>
<xs:element name="language" type="empty" minOccurs="0"/>
<xs:element name="number_range" type="empty" minOccurs="0"/>
<xs:element name="payment_method" type="empty" minOccurs="0"/>
<xs:element name="rule" type="empty" minOccurs="0"/>
<xs:element name="salutation" type="empty" minOccurs="0"/>
<xs:element name="shipping_method" type="empty" minOccurs="0"/>
<xs:element name="tax" type="empty" minOccurs="0"/>
</xs:choice>
</xs:complexType>
The manifest.xml should allow more custom field entity types.
Currently we suggest to add the entity
order_line_item.Currently available types:
<xs:complexType name="entity-list">
<xs:choice maxOccurs="unbounded">
<xs:element name="product" type="empty" minOccurs="0"/>
<xs:element name="order" type="empty" minOccurs="0"/>
<xs:element name="category" type="empty" minOccurs="0"/>
<xs:element name="customer" type="empty" minOccurs="0"/>
<xs:element name="customer_address" type="empty" minOccurs="0"/>
<xs:element name="media" type="empty" minOccurs="0"/>
<xs:element name="product_manufacturer" type="empty" minOccurs="0"/>
<xs:element name="sales_channel" type="empty" minOccurs="0"/>
<xs:element name="landing_page" type="empty" minOccurs="0"/>
<xs:element name="promotion" type="empty" minOccurs="0"/>
<xs:element name="product_stream" type="empty" minOccurs="0"/>
<xs:element name="property_group" type="empty" minOccurs="0"/>
<xs:element name="product_review" type="empty" minOccurs="0"/>
<xs:element name="event_action" type="empty" minOccurs="0"/>
<xs:element name="country" type="empty" minOccurs="0"/>
<xs:element name="currency" type="empty" minOccurs="0"/>
<xs:element name="customer_group" type="empty" minOccurs="0"/>
<xs:element name="delivery_time" type="empty" minOccurs="0"/>
<xs:element name="document_base_config"7 votes -
HTML Sanitizer + Custom Fields
Fields sind ein zentrales Konzept, werden aber in der Doku bezüglich dem HTML Sanitizer in 6.5 ausgespart.
Doku + mit Core ausgelieferte shopware.yml
https://docs.shopware.com/de/shopware-6-de/tutorials-und-faq/html-sanitizer
https://github.com/shopware/shopware/blob/6.5.x/src/Core/Framework/Resources/config/packages/shopware.yamlFragen
1) Ist eine Konfiguration für ein einzelnes customfield überhaupt möglich?
2) Ist eine Konfiguration für alle customfields einer Tabelle möglich.Siehe auch
Siehe https://forum.shopware.com/t/html-sanitizer-ausnahme-fuer-zusatzfelder/100536/2
Custom2 votes -
Automate cheapest price calculation
Right now, the field "cheapest price last 30 days" needs to be manually updated, which can lead to an enormous workload. It would be simpler to have an automatism that automatically picks out the cheapest price within the last 30 days.
40 votes -
Orders: anonymize
In order to comply with the GDPR, it is necessary to enable the anonymization of details within the order.
Customers themselves can be renamed. But not the details within the orders.
2 votes -
Adjust the number of items in the watch list
It is currently not possible to change the number of items in the watch list. It would be desirable to be able to change the number of items.
Aktuell kann man in der Merkliste keine Änderungen an der Artikelanzahl vornehmen. Wünschenswert wäre, dass die Artikelanzahl verändert werden kann.
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).
13 votes -
Fallback product-layout if NO Layout is assigned
If the values for columns
cms_page_idandcmsPagewithin tableproductwill be set to "NULL", the "original" default layout for product pages will be used, although I've managed to set up a new product-page layout and marked it as "default" beforehand.Since a different layout was defined as default layout, this particular one should also be used as fallback whenever no layout is assigned.
Steps to reproduce:
- Create custom product layout
- Mark it as new default layout for product pages
- For already existing entries --> set values for mentioned columns to "NULL" or simply remove the layout assignment in the layout-tab of a product
- clear caches and check the layout used in the storefront
Result: The "original" default layout will still be used as fallback , not the newly created one.
To sum up: It would make sense if the newly created default layout would be used as fallback layout and not the shopware original one.
If the values for columns
cms_page_idandcmsPagewithin tableproductwill be set to "NULL", the "original" default layout for product pages will be used, although I've managed to set up a new product-page layout and marked it as "default" beforehand.Since a different layout was defined as default layout, this particular one should also be used as fallback whenever no layout is assigned.
Steps to reproduce:
- Create custom product layout
- Mark it as new default layout for product pages
- For already existing entries --> set values for mentioned columns to "NULL" or simply remove the layout assignment in…
6 votes -
Rule Builder: access to domains of a sales channel
Hi
we would need access in the RuleBuilder to the different domains that are configured in a sales channel.
This is because the domain - in our case - indicates which country specific part of the shop the user is currently in and we need to calculate the shipping costs based on the country.1 vote
- Don't see your idea?