1453 results found
-
Custom forms: Easy reply to the customer
There is already this feedback / feature request: https://feedback.shopware.com/forums/942607-shopware-6-product-feedback-ideas/suggestions/50220672-add-cc-bcc-and-reply-to-features-to-the-mail-func.
In addition it should be possible to define an email adress, that custom forms (or default forms) can reply to.
Of course one can add an email field in the form fields. But this cannot be used to open the form mail and click on reply to "customer email"
2 votes -
Expanding columns under products, customers or orders
We've received requests from several departments asking if we could add additional columns for products, customers, or orders.
For example, the customer's last login date.
The reason for this is that customers often create multiple accounts (guest accounts).
This field would make it easier for our customer service to identify which account the customer is referring to, since 99% of the time it's the account that last logged in.
'Sales' would also be a really helpful column for us for products.
The standard fields should simply be available as optional items to simplify daily work.
4 votes -
Image keyword assistant should let you set store-wide keywords or prompts
That way, issues like https://github.com/shopware/shopware/issues/13175 could be prevented by setting keywords that tell the AI to focus on certain groups of products and/or exclude certain product categories that will never appear in the store.
3 votes -
Handling growing order numbers
With growing order numbers, the performance of loading these orders decreases.
It would be great if this decreasing of loading performance could be avoided, e.g. by loading older orders than X only on request.2 votes -
Support cron jobs per application in Shopware Native PaaS
Some business processes (like product imports) need automated scripts to run on a schedule. Shopware Native PaaS should support cron jobs per application, ideally managed through sw-paas.
5 votes -
E-invoice for cancellation invoice, too
Currrently only the invoice itself is abvailable for creating as a Zugferd format. The cancellation invoice should added as soon as possible, because this may lead to irriatations at accounting.
12 votes -
Show regulation price in listings only if there ist a discount
Our suggestion In order to comply with both the PAngV and a clean UX, a small piece of logic would be useful:
If regulationPrice == price.unitPrice → no output. (This happens very often in practice.)
This would both comply with the legal situation and meet actual customer expectations.
- Legal situation (PAngV § 11) According to § 11 of the Price Indication Regulation (PAngV), the ‘lowest total price of the last 30 days’ only becomes mandatory if the retailer advertises a price reduction. Source (legal text): https://www.gesetze-im-internet.de/pangv_2022/BJNR492110021.html#BJNR492110021BJNG000201377
It clearly states: ‘If goods are offered to consumers with reference to a price…
2 votes -
Taxes: Deactivation of unused Tax settings
Sometimes it's thought that additional taxes are needed. If they were used, it is not possible to remove them completely.
As a second stumbling block it is not possible to deactivate tax rates or change the order. Some customers have huge problems with this beheaviour because the "wrong" tax rate is always the first to select.It would be a great improvement, dor decativate taxes and / or change the order.
2 votes -
Option to automatically show new reviews
It would be nice to have an option for reviews to be shown automatically. Currently you have to enable this individually for each review.
10 votes -
Use the document language to determine the email template language when sending documents
Currently, when documents are manually transferred via the order via send document, the email template language is determined by the admin user’s backend language, not by the language in which the customer placed the order.
This leads to additional steps every time a document needs to be sent manually:
The admin must first check the order language, switch the backend language accordingly, and only then send the document so that the email is generated in the correct language.The expected behavior is that the document’s language (or order language) should define which email template is used for sending, ensuring consistent…
2 votes -
Flow Builder | Define dynamic mail recipients using variables
We need to send order confirmation emails to additional recipients whose email addresses are stored in custom fields of the order’s shipping address. Currently, the Flow Builder does not allow dynamic email addresses in the “Send Email” → “Custom recipient” field.
2 votes -
Remove hardcoded title suffix from static pages
There is currently no way to configure a global meta title suffix for static pages in Shopware without modifying the shop’s base meta information or implementing a custom plugin. For example, in CheckoutCartPageLoader::setMetaInformation(), meta titles are hard-coded, making it impossible to centrally manage suffixes for static or system pages. A global text snippet or configuration option for defining a meta title suffix applicable to all (or all static) pages would greatly simplify consistent SEO management and avoid unnecessary custom development.
2 votes -
It should be optionally possible to create orders only after the payment has been successful.
Es soll optional möglich sein, Bestellungen erst dann zu erstellen, wenn die Zahlung erfolgreich war. Wenn der Bezahlvorgang abbricht, soll auch der Bestellvorgang abbrechen.
It should be optionally possible to create orders only after the payment has been successful. If the payment process is aborted, the order process should also be aborted.
12 votes -
Placeholder system for properties & custom fields
The desired function allows the use of placeholders such as
{{ product.properties.<name> }} or
{{ product.customFields.<fieldName> }}
in various product fields. These should then be automatically replaced with the respective values.
✅ Potential benefits for retailers:
- Reduced manual maintenance effort
- Consistent and accurate product data
- Particularly helpful with many variants or large catalogs
- Works in the cloud without individual template adjustments2 votes -
B2B Components: Approval Rules: Add organization unit option
Currently you can only create approval rules that are active for all organization units. It would be great if we could also create approval rules specifically for an organization unit, in case I want different conditions to be applied for different org units.
2 votes -
Budgets: Add visibility permission
Currently, when you create different budgets for different organization units, all users can see all budgets if they have the permission to view the budgets. How ever, a user assigned to a specific organization unit does not need to see the budget of a different unit. For that reason we should have a permission checkbox that allows users to only see the budgets assigned to their organization units.
We do this already for example for the orders and quotes.
2 votes -
Allow setting time zone for logs
Add the possibility to modify the time zone for the log files. This would make it easier to parse them, both by reading and via scripts or other means.
2 votes -
Two-factor authentication for Cloud shops
Damit der Zugriff auf den Cloud Shop Admin sicherer wird, sollte dort eine Zweifaktor Authentifizierung möglich sein. Diese wäre dann vermutlich auch für den Shopware-Account notwendig.
2 votes -
Admin order creation: Allow guests
Currently, it is not possible to create an order via our Admin unless the customer is registered. This presents an annoyance because it is still somewhat customary in some industries to place orders by calling a customer support hotline or something along those lines.
As it is now, when calling a merchant running a Shopware 6 shop, we first have to enter the customer menu, register a new customer (and ask our customer all their data) and THEN do the same thing after switching menus to orders again.
It would be a neat QoL feature to be able to do…
2 votes -
Improve export of products - better handling of variant data
The current situation is, that inherited field stay empty when a product export is done. This makes it more difficult to exchange data with other software or just to use spreadsheets to gain special information.
It's a topic that currently needs a workaround for many customers. Perhaps it could be possible to create several export profiles: one for exchange and editing data just for Shopware and one for external exchange.
3 votes
- Don't see your idea?