- or
No existing idea results
- ~ No ideas found ~
1403 results found
-
Display in the customer overview in which sales channel the customer has registered
Even if you have set that a customer can log in to all sales channels with the login data, it is important to see in which sales channel they have registered.
For example, if you only enable purchase on account for registered customers after activation, you cannot find out which sales channel the customer has registered for and therefore cannot send them a suitable email.
"Dear customer, we have activated you in our sales channel *** (?) for ordering on account."
1 vote -
Add last order items to the content element "Product slider"
Some customers want to buy products they already bought in an order before as fast as possible again. Therefore, it would be great to add the products the customer bought in the last order to the "product slider" element in the shopping experience. Just add "last order products" to the "Product assignment" element after "manual assignment" and "Dynamic product group"
1 vote -
Exclude discounts from the total amount of products at checkout
We see 3 products on the checkout but we only have 1. The other 2 are discounts.
It would be amazing to only show the real products.2 votes -
Search field for selecting delivery & billing address modal (huge amount of addresses)
We have plenty addresses for a account in big companies, because we import all addresses according to the company, that user can select into there account. Often there are 200-300 addresses. So there is a need to have an search field for searching the company name, street, zip code, country and an individual programmed customer number field for each address.
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!
-
Button to go back to the last open window
Function back in the backend menu.
e.g.: I go to the product overview on page 3 and jump to an article.
If I click back I end up back on page 1 and have to click back to page 3.
Sometimes it's also the case that if you're in one area and you jump from there to another, you can't come back.
E.g.: I open a product in an order. If I click on back I end up in the product overview and I have no choice but to look for the order again and open it again.
The only workaround is to open everything in separate tabs or to use the browser's back button, which you then have to click several times.
In SW 5 there were tabs within the backend for this.
Function back in the backend menu.
e.g.: I go to the product overview on page 3 and jump to an article.
If I click back I end up back on page 1 and have to click back to page 3.
Sometimes it's also the case that if you're in one area and you jump from there to another, you can't come back.
E.g.: I open a product in an order. If I click on back I end up in the product overview and I have no choice but to look for the order again and open it again.
The only…
6 votes -
Rule Builder - radius restriction
Please allow us to create a Rule builder to restrict Product visibility to customers who are within a certain radius of a location.
E.g. shop is located in 3 Street Name, Suburb, Postcode. I only want customers whose address is within 30km of that shop to be able to see products from that shop. Customers outside of that radius should not be able to see the products.
Thanks!
1 vote -
Allow adding multiple values to multi-select fields (e.g. list of products, list of countries, etc.) by pasting a list
Currently, at many places in the administration, there is the option to use an auto-completer to add values to a field one at a time. An example for this would be "add products to a 'product is one of...' field in the rule builder or the selection of products assigned to a category.
It would be helpful to paste a list of identifiers (e.g. product numbers) into these fields and get them assigned in one go. Specifically with large lists, that would save a lot of "clickwork" in the administration. Some simple reporting (failures / successes) in a message window would be helpful.
Currently, at many places in the administration, there is the option to use an auto-completer to add values to a field one at a time. An example for this would be "add products to a 'product is one of...' field in the rule builder or the selection of products assigned to a category.
It would be helpful to paste a list of identifiers (e.g. product numbers) into these fields and get them assigned in one go. Specifically with large lists, that would save a lot of "clickwork" in the administration. Some simple reporting (failures / successes) in a message window…
6 votes -
Prevent leading spaces in registration fields
When registering as a new customer, it is possible to enter leading / trailing whitespaces in all the fields. There is no validation that prevents the user from doing that and the values are saved like that into the database. This can lead to users in Shopware with leading / trailing whitespaces in their name.
2 votes -
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 -
Manual orders via admin: Selection of deactivated payment and shipping methods
It should be possible to select deactivated payment methods and shipping methods for manual orders in the admin.
There are often special payment and shipping methods for manual orders, but these should not be available to customers in the frontend. These are therefore always deactivated, but should still be selectable via the admin.1 vote -
Extend Order Overview
Implement an additional + optional(?) column for "payment method" and "shipping method"
16 votes -
New customer address on order creation
In 6.4 it was possible to add new billing and/or shipping address to a customer during order creation in admin. Since 6.5 it is no longer the case.
It would be nice to have that functionality back so that when new order is created manually, there is no need to first adjust a customer by adding a new address in sw-customer module, but to add that address directly via sw-order module and use that address in that order.5 votes -
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"6 votes -
Mobile Interface - Menu button in the administration does not seem to work properly
When you open the administration (mobile) and click on the menu, you will notice that there is no close button, and even when you click outside the menu, it would not close.
From the Shopware issue tracker, i understand now that the Shopware administration currently does not support any mobile view, so this could be an improvement (specially for customers that approach the administration with their cellphones).
3 votes -
Flag whether Shopware takes content from shopping experience or category/content
When a layout is created and activated, it will display the actual content from the layout. Once content got changed via categories/layout, it only takes the content from the category. Changing the content again via the page builder does not have an effect anymore, which is correct as the inheritance changed but is confusing.
It would be beneficial and facilitate daily work if one would see the inheritance from the content in the categories, whether it takes the text from the category/content or the layout.
44 votes -
Pre configured "Category filtering" page
In the current situation you need to manually add a attribuut to the category filter.
This takes allot of time and is not always flawless, since you need to build up the entire filter every single time when there is a new category added to the shop.What i would like to see is a "pre configure filtering" page. On this page you can configure a filter so you only need to add this filter in like a drop down menu so you only need to select a pre configured filter once you made a new category page, something like the "Essential characteristics" page.
In the current situation you need to manually add a attribuut to the category filter.
This takes allot of time and is not always flawless, since you need to build up the entire filter every single time when there is a new category added to the shop.What i would like to see is a "pre configure filtering" page. On this page you can configure a filter so you only need to add this filter in like a drop down menu so you only need to select a pre configured filter once you made a new category page, something like…
2 votes -
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 -
AI gets access to central information about the shop
Central information about the store, target groups, brands, and wording can be accessed by the AI.
This will help to improve the sales channel context and polish the tone of voice.
1 vote -
Search for custom product templates
Currently, it is not yet possible to search the product templates of the Custom Product extension. If you have a lot of templates here, it is very tedious to find the desired one in the overview. Here, it would be good if this is included, for example, via the admin search.
4 votes -
OPcache clearing with admin and API
We occasionally have customers who have errors (PHP exception, 404 etc.) after updating extensions (SW6: Paypal extension, security plugin etc.).
A reset of the opcache helps in many cases.
As in Shopware 5, resetting the OPCache should also be possible in Shopware 6 via the admin or via API. This can solve many problems with extension updates.
2 votes
- Don't see your idea?