- or
No existing idea results
- ~ No ideas found ~
1484 results found
-
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 -
Recipient "Employee" should be available inside the flow builder
Currently the recipient employee is not generally available inside the flow builder. As a new actor within the B2B suite this role should be added. So we can freely use the flow builder with the B2B suite.
The specific employee flows seem hardcoded within the B2B suite as illustrated in my screenshot. Employees do receive the correct mail, but it's not configurable/visible in the flow builder.
2 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 -
Image keyword assistant webp support
The image keyword assistant should be able to process the default webp format.
3 votes -
Delivery period display in the shopping basket / Lieferzeitraum-Anzeige Warenkorb
The delivery period display makes no sense if the system cannot calculate the weekends and perhaps also understand the maximum time up to which orders can be processed immediately.
Our GLS parcel service takes everything that we receive as an order by 10 a.m. on the same day and delivers it the next WORKING DAY or after a maximum of two days. So it's a great advertising factor for us to state the delivery time as 1-2 working days.
But if customers then see in the delivery period: 24-25 May (that's Saturday and Sunday) then it confuses them or, in the worst case, annoys them.
If I set the time more broadly, the advertising effect fizzles out...
Die Lieferzeitraum-Anzeige macht keinen Sinn, wenn das System nicht die Wochenenden rausrechnen kann und vielleicht auch versteht, bis zu welcher Uhrzeit Bestellungen maximal gleich bearbeitet werden können.
Unser GLS Paketdienst nimmt alles, was am selben Tag bis 10 Uhr bei uns als Bestellung eingeht noch mit und stellt am nächsten WERKTAG zu bzw. maximal nach zwei Tagen. So gesehen ein toller Werbefaktor für uns, die Lieferzeit mit 1-2 Werktagen anzugeben.
Wenn die Kunden dann aber im Lieferzeitraum sehen: 24.-25.05. (das ist Samstag und Sonntag) dann verwirrt es sie, oder im schlimmsten Fall verärgert es sie..
Wenn ich die Zeit großflächiger einstelle, verpufft der Werbeeffekt..
The delivery period display makes no sense if the system cannot calculate the weekends and perhaps also understand the maximum time up to which orders can be processed immediately.
Our GLS parcel service takes everything that we receive as an order by 10 a.m. on the same day and delivers it the next WORKING DAY or after a maximum of two days. So it's a great advertising factor for us to state the delivery time as 1-2 working days.
But if customers then see in the delivery period: 24-25 May (that's Saturday and Sunday) then it confuses them or, in…
6 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 -
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 reduction, the lowest total price charged by the trader within the last 30 days [...] must be indicated.’ ➡ Without a price reduction, there is no obligation to display the price.
- Confirmation by legal commentary (e.g. the article you linked to) Your linked article also clearly states that this obligation only applies to reduced prices and serves precisely to prevent misleading ‘bogus discounts’: https://www.ratgeberrecht.eu/aktuell/30-tage-bestpreis/ If the current price is identical to the 30-day price, there is no price reduction and the display ‘Lowest price in the last 30 days’ would rather suggest a false discount effect.
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 -
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 customer communication and reducing unnecessary manual steps.
Implementing this would streamline workflow, avoid mistakes, and provide a more intuitive and customer-centric process.
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 -
Products offeren ONLY in subscriptions
Currently products can already be offered as subscription products within the Beyond plan. In the frontend can than be selected if it should be a subscription or a regular order. Unfortunately it is not possible to make products available ONLY as subscriptions products and deactivate the possibility to order it once for that product.
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 -
ask for product review via mail & link to make product review in order history
ask for product review via mail:
The customer get a mail with all purchased product (like the order confirmation) after changing delivery status to shipped.Additional
link to make product review in order history:
In each order after clicking to show details: each order position add a link to mke a product review. After clicking to that the product PDS appears an scrolling down the the product review section to make a product review.1 vote -
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 -
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 -
blog Kommentare
Hallo liebes Team,
ich habe fassungslos festgestellt, dass man nicht auf Blog Kommentare antworten kann. Das ist für mich eine absolute Standardfunktion. Wozu sollte es Blogkommentare geben, wenn man nicht darauf antworten kann.
Bitte in einem zukünftigen SW Update einplanen.
Dabei auch die standardmäßige Benachrichtigung, wenn ein neuer Blogkommentar aufgegeben wurde.
Danke.Viele Grüße
Magdalena1 voteHallo und danke für das Feedback. Soweit ich das richtig sehe sind Sie mit Ihrem Shop noch auf der Version 5 von Shopware. Diese wurde bereits durch Shopware 6 ersetzt unserem zukunftsicheren Shopsystem, welches stätig weiterentwickelt wird. Shopware 5 wird somit nicht mehr weiterentwickelt.
-
VAT ID of guest accounts can't be changed via the shipping address.
If a commercial customer has an item delivered to another company in Austria and the invoice is sent to Germany, then the corresponding VAT ID should be taken from the delivery address - and not from the billing address.
The delivery address is the basis for which tax rate is used for the order.The VAT ID. field is not available under “Change delivery address”.
Registered customers change the VAT ID in the profile settings and cannot change it at all via the billing address, as guest customers do it.
The behavior should be the same for both account types and ideally you should also be able to store multiple VAT IDs.
If a commercial customer has an item delivered to another company in Austria and the invoice is sent to Germany, then the corresponding VAT ID should be taken from the delivery address - and not from the billing address.
The delivery address is the basis for which tax rate is used for the order.The VAT ID. field is not available under “Change delivery address”.
Registered customers change the VAT ID in the profile settings and cannot change it at all via the billing address, as guest customers do it.
The behavior should be the same for both account types…
8 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
- Don't see your idea?