- or
No existing idea results
- ~ No ideas found ~
1528 results found
-
Manufacturer pages in the same tab
It would be useful if the shop owner could decide/set whether the link to the manufacturer's website (click on the logo/manufacturer on the product detail page) is opened externally in the new tag or in the same tab.
If a store page for the manufacturer is to be displayed instead of the manufacturer's website, this is less useful in a new tab.
Here it would be better if the owner had the option of opening the page in a new tab or in the same one
2 votes -
Rulebuiler condition which detects the change of payment method
Condition in the rulebuiler which determines the (non-balanced) change of payment method.
Something like: Used payment method was > Incoice > is now > prepayment
For example, in the flow builder you could influence the mails that are sent when the status changes, so that a distinction is made between manual switching (by the admin) or automated switching (by payment integrations) and the payment method change by the customer in the frontend.
Since the order also reaches the status “canceled” when the customer changes the payment method in the frontend, these mails could be prevented here, as they can be confusing.
Condition in the rulebuiler which determines the (non-balanced) change of payment method.
Something like: Used payment method was > Incoice > is now > prepayment
For example, in the flow builder you could influence the mails that are sent when the status changes, so that a distinction is made between manual switching (by the admin) or automated switching (by payment integrations) and the payment method change by the customer in the frontend.
Since the order also reaches the status “canceled” when the customer changes the payment method in the frontend, these mails could be prevented here, as they can be…
2 votes -
Line item rule amount of products within a dynamic product group for discounts
Currently it is not possible to add a rule to a discount that checks the amount of products per lineitem and additonal conditions.
e. g.
You want to ensure that only products with a tag and an amount of 10/above is in the cart. This has to be checked by lineitem, so products and variants that include the TAG but have only an amount of 1 in the cart do not apply to the discount.
if you use the condition "amount of products" it is related to all itemlines of the cart.
If you choose "Item quantity" it matches, but you have to add all related products manually in the condition of the rule.
It would help if there is a condition "item quantity of products within a dynamic prouduct group", to achieve the possibility to count items by line and use the discount per lineitem instead of the complete cart.
When a position has only 1 item an the TAG, the discount does not apply.
Currently it is not possible to add a rule to a discount that checks the amount of products per lineitem and additonal conditions.
e. g.
You want to ensure that only products with a tag and an amount of 10/above is in the cart. This has to be checked by lineitem, so products and variants that include the TAG but have only an amount of 1 in the cart do not apply to the discount.
if you use the condition "amount of products" it is related to all itemlines of the cart.
If you choose "Item quantity" it matches, but…
1 vote -
Support for Option to Display Revenue Including or Excluding VAT in Overviews
EN: We’re facing a challenge where revenue is currently displayed only including VAT in overviews. Since we apply different VAT rates (low, high, and intra-community supplies), it’s not feasible for us to view our revenue excluding VAT through the tool. We believe this feature could be valuable for many businesses. Support for displaying revenue both with and without VAT would greatly simplify our accounting and reporting.
DE: Unterstützung für die Option zur Anzeige von Umsatz mit oder ohne Mehrwertsteuer in Übersichten
Wir stehen vor der Herausforderung, dass der Umsatz in den Übersichten derzeit nur inklusive Mehrwertsteuer angezeigt wird. Da wir unterschiedliche Mehrwertsteuersätze anwenden (ermäßigt, normal und innergemeinschaftliche Lieferungen), ist es für uns nicht praktikabel, unseren Umsatz ohne Mehrwertsteuer über das Tool einzusehen. Wir glauben, dass diese Funktion für viele Unternehmen wertvoll sein könnte. Die Unterstützung für die Anzeige des Umsatzes sowohl mit als auch ohne Mehrwertsteuer würde unsere Buchhaltung und Berichterstattung erheblich vereinfachen.
EN: We’re facing a challenge where revenue is currently displayed only including VAT in overviews. Since we apply different VAT rates (low, high, and intra-community supplies), it’s not feasible for us to view our revenue excluding VAT through the tool. We believe this feature could be valuable for many businesses. Support for displaying revenue both with and without VAT would greatly simplify our accounting and reporting.
DE: Unterstützung für die Option zur Anzeige von Umsatz mit oder ohne Mehrwertsteuer in Übersichten
Wir stehen vor der Herausforderung, dass der Umsatz in den Übersichten derzeit nur inklusive Mehrwertsteuer angezeigt wird. Da wir…
6 votes -
Automatically include vouchers in returns management
Currently, if the vouchers are not taken into account when an order is placed, if an item is returned via Return Management.
Although the amount of the return can be adjusted and the value including the voucher is suggested, it is not applied automatically.
An option for automation would be useful here.3 votes -
Add filters for Exports according to Shopware 5
Many customers miss the filter functionality they know from Shopware 5 especially because the AI features do not work reliably.
For example the export of orders is often needed for a year or two and the amount of data grows very quickly.8 votes -
Better filter options within e.g. customer and order overview
If you work with the customer and order overview on a daily basis, this quickly leads to frustration.
For example, the number per page cannot be set and is far too low. This should be 100 or 200. Otherwise the unnecessary effort is too high and the work quickly becomes frustrating.
Also, the filter or listing is often reset when changing pages. This also takes an incredible amount of time.
We would like to see better handling here.
2 votes -
Further evaluation of the customer search
There should be an evaluation of customer search queries within the Shopware search.
This means that the search can be adapted to customers in ever greater detail. This is requested time and again by large customers.
2 votes -
Improve UI and Logic for Postal Code Validation and Advanced Validation Rules
he current UI for the Postal Code settings is not intuitive and may confuse users. The "Advanced Validation Rules" option can only be enabled after enabling "Postal Code Validation," but there is no clear indication that these options are linked. Additionally, there is no visibility into which validation rules apply when enabling "Postal Code Validation."
Problems Identified:
Lack of clear dependency between "Postal Code Validation" and "Advanced Validation Rules."
No information on which postal code validation rules are applied by default.
Unclear if "Postal Code Required" influences the validation settings.
2 votes -
Optimierung der Dropdown Menüs (z.b. Verkaufskanal -> Auswahl Länder)
The selection of values within the dropdown menus in Shopware Admin is very error-prone.
For example, if additional countries are to be added or removed within the sales channel, the menu only ever shows 25 entries and each entry has to be clicked individually. This is very error-prone and you should also be able to select/deselect “all” entries.
This would make it easier for large customers to use the Admin, as the problem occurs at various points in the Admin.
2 votes -
Unlinking properties should be bound to a detailed privilege.
It is currently not possible to delete properties via the small X (see screenshot) using a detailed privilege.
The deletion is currently bound to the technical privilege “product.deleter”, which cannot be found in the admin and can only be given via API/DB or the general deletion permission for products.
Using "Configure properties", you can also delete the properties via a detailed privilege, but it should also be possible to simply delete properties using the small X.
1 vote -
Mailer: Different SMTP data for different sales channels
More and more providers are prohibiting the sending of emails that do not come from the same domain.
However, as you can only store the access data of one domain in the mailer, this becomes a major problem as soon as you enter several sales channels with different domains.
From that moment on, not all messages can be sent or are rejected by the provider.
"mailbox unavailable\r\n 550 Sender address is not allowed.""
It should therefore be possible to configure the mailer settings for each sales channel.
31 votes -
Form Builder: send filled form to customer mail address in CC
If a customer filled the form and send to the merchant, the customer should get a copy of the filled form in CC.
14 votes -
Copying CMS content - reusable elements
It would be nice to have the option of copying elements from the shopping experiences and using them in a different place.
Example: We have the "XY" section in the start page - this should be filled and customised once and then copied in the next step and used in another page.
27 votes -
Product overview with additional filter options on variant level
The filtering at the product level under "Catalog > Products" unfortunately only works at the master/parent product level. This option is not conducive for the following reason:
All of our products have variants and we maintain the images only at the variant level. The same applies to the product status active/inactive. Text, on the other hand, is always maintained at the master/parent product level.
This approach is deliberately chosen because variants can have different images or individual variants can be inactive.It is now important for us to be able to locate the following at the variant level:
- Product active, has image, has NO text, has stock
- Product active, has NO image, has text, has stock
- Product active, has neither image nor text, has stock
- Product inactive, has image, has NO text, has stock
- Product inactive, has NO image, has text, has stock
- Product inactive, has neither image nor text, has stock
The filtering at the product level under "Catalog > Products" unfortunately only works at the master/parent product level. This option is not conducive for the following reason:
All of our products have variants and we maintain the images only at the variant level. The same applies to the product status active/inactive. Text, on the other hand, is always maintained at the master/parent product level.
This approach is deliberately chosen because variants can have different images or individual variants can be inactive.It is now important for us to be able to locate the following at the variant level:
- Product active,…
13 votes -
I am trying to customize SEO URL slugs and encountered an issue
When I use variable meta-title in the url template, it works only for main products, not for variants, even if there is meta title inheritance enabled. But even when I check html of the variant page, meta title is not there. I don't know if you made it on purpose or it is a bug, but it means: I cannot use meta title variable for variants when creating a url.
This lead to my other thought: let's turn Use single canonical URL for all variants - because of course we do not want google to mark it as duplicates when we are using inheritance for all the descriptions and stuff. But when I turn it on, you force me to pick one of the variants. But I don't logically want it to be one of the variants, i want it to be main product. That leads me to another problem that I tried to solve with you: main product cant have the same product number as variant. So I cannot create variant as main product - so I cannot use it as main product for canonical URL. BUT! I think you would tell me: change storefront presentation, lets go to Product-Variants-Storefront presentation-Product lsitings and instead of Main product you could pick one variant and go with it. But I don't want to do it, because if I choose it as "Main product" in the storefront it is more beneficial since it shows, that there are more variants and price starts at.... You know what I mean? I don't want the specific size of the product be as main variant, you actually told me not to, since you require variant and main product to have different product number.
This is actually really frustrating. Because I want it (as it should be):
- main product - main URL - it is main product page that I want to be crawled by search engines
- variants - url with whatever slug added to the main product URL, but I don't want Google to crawl it.
Sounds pretty easy, right? And it even works like that, just not in case if I want to use MetaTitle as a slug.You give me these:
- main product - main URL (i want to use meta title for that and you allow it since it is in the list of supported variants)
- variant - can't use meta title - it makes it different url, which is ugly and not practical
- seo canonical - can use only variant, not meta title, so basically I have many duplicate pages and it takes us down from Google.When I use variable meta-title in the url template, it works only for main products, not for variants, even if there is meta title inheritance enabled. But even when I check html of the variant page, meta title is not there. I don't know if you made it on purpose or it is a bug, but it means: I cannot use meta title variable for variants when creating a url.
This lead to my other thought: let's turn Use single canonical URL for all variants - because of course we do not want google to mark it as duplicates when…
5 votes -
replace Tiny Slider as the default slider
The current default slider integration with tinyslider seems not be maintained anymore.
It would be good to switch to a maintained slider lib again as tinyslider has a multitude of issues, espacially with accessibilty and it is not really customizable.4 votes -
Adding Companies as customers instead of Users
For B2B shops, often Users are irrelevant, since companies are the customers in that cases. It would be nice, if you could create customers not only on a user level, but also on company level.
Currently Users are used as placeholders, which still requires information such as first and lastname, which does not make sense for a company. This placeholder user also gets a placeholder first- and lastname which then pops up in the storefront everywhere.
2 votes -
Differentiation between manufacturer and brand
Currently you can only specify the manufacturer of a product. However, the manufacturer is not automatically the brand of the product, so it would be nice if there was an extra field here that also allows you to specify the brand.
1 vote -
Allow orders to be moved between customers (i.e. reassign guest order to customer account)
It would be useful to move orders from one customer account to another. Currently guest orders remain assigned to the guest account, even when a customer registers afterwards. Thus they cannot see the order status. Also for other scenarios (like duplicate accounts), moving orders would be useful.
Es wäre hilfreich, Bestellungen von einem Kundenkonto auf ein anderes verschieben zu können. Derzeit bleiben Gastbestellungen dem Gastkonto zugewiesen, auch wenn sich ein Kunde später registriert. Somit kann er den Status der Bestellung nicht sehen. Auch für andere Szenarien (z. B. doppelte Konten) wäre das Verschieben von Bestellungen nützlich.
5 votes
- Don't see your idea?