- or
No existing idea results
- ~ No ideas found ~
1357 results found
-
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 -
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 -
Deactivatable window (payment request) when creating an invoice
When creating an order in Admin, the following window appears every time
"Payment request
Would you like to ask the customer to pay the order by "Invoice"?"Many customers do not use this window as the workflow is different. As the window cannot be deactivated, this is a source of errors.
1 vote -
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 -
Product Bundles
With this feature, merchants can provide their customers ready-to-buy bundles (with and without discounts) and increase their sales revenue.
75 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,…
7 votes -
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 -
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.
7 votes -
Missing option to delete documents
EN
We removed the deletion of existing documents in orders sometime in late 2021 or early 2022. There are always users who want such a function. See tickets https://issues.shopware.com/issues/NEXT-19550 and https://issues.shopware.com/issues/NEXT-24888.In principle, I do not see it as necessary to delete the document, but there should be a way to invalidate documents and make corrections. Possibly similar to accounting, where an incorrect entry is offset with a cancellation entry.
DE
Wir haben irgendwann Ende 2021 oder Anfang 2022 das Löschen vorhandener Dokumente in Bestellungen entfernt. Es gibt immer wieder Anwender, die sich eine solche Funktion wünschen. Siehe dazu Tickets https://issues.shopware.com/issues/NEXT-19550 und https://issues.shopware.com/issues/NEXT-24888.Grundsätzlich sehe ich es nicht als notwendig an, das Dokument zu löschen, aber es sollte eine Möglichkeit geben Dokumente ungültig zu machen, Korrekturen durchzuführen und die korrekte Historie zu erkennen. Eventuell ähnlich wie in der Buchhaltung, wo eine Fehlbuchung mit einer Stornobuchung ausgeglichen wird.
EN
We removed the deletion of existing documents in orders sometime in late 2021 or early 2022. There are always users who want such a function. See tickets https://issues.shopware.com/issues/NEXT-19550 and https://issues.shopware.com/issues/NEXT-24888.In principle, I do not see it as necessary to delete the document, but there should be a way to invalidate documents and make corrections. Possibly similar to accounting, where an incorrect entry is offset with a cancellation entry.
DE
Wir haben irgendwann Ende 2021 oder Anfang 2022 das Löschen vorhandener Dokumente in Bestellungen entfernt. Es gibt immer wieder Anwender, die sich eine solche Funktion wünschen. Siehe dazu…3 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.5 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 -
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
- Don't see your idea?