- or
No existing idea results
- ~ No ideas found ~
1339 results found
-
Backend: Product Filtering and Customization - Filter Value
The product filters section needs more customization and can be optimized.
Here is an example of the main shortcomings:
1 - Allow the addition of custom fields and properties.
2 - Allow the use of operators such as: "Like," "=", "And," "Or," "Starts with," etc.
3 - Allow filtering by entering multiple values in a search field.7 votes -
Use Thumbnails for Property Images in Filter
Please adjust the default template
Resources/views/storefront/component/listing/filter/filter-property-select.html.twig
so that when images are assigned to properties, the appropriate thumbnail images are used instead of the full original images.Currently, the original image is loaded, which can negatively impact page load performance.
In our instance, I’ve already implemented a manual fix by replacing:
{% set media = element.media.url %}
with:
{% set media = element.media.thumbnails | filter(t => t.width == 100 and t.height == 100) | first.url %}This ensures that a 100x100 thumbnail is used when available.
3 votes -
Add informal (Du) text snippets for German language
It would be useful to have an offical "Du"-Version of the de-DE snippets, either natively or through the language pack.
5 votes -
Add hreflang support across multiple sales channels
Currently hreflang only applies to different domains within one sales channel. It would be useful to be able to define other languages for hreflang tags across multiple sales channels (i.e. separate sales channels for EU and US, linking to each other)
6 votes -
CMS Extension: Allow custom form to be used for newsletter sign-up
Currently, a custom form provided by the CMS extension can only be used to have a customer send a request to a predefined e-mail address. The ability to also use a custom form for newsletter registration would allow the shop owner to customize the layout or add some basic things, i.e. their own mandatory terms & conditions checkboxes.
3 votes -
Language inheritance for Custom Fields
Just like other fields in the products (title, description, etc.) the custom fields should inherit the values from a parent language unless overwritten. Currently, they just remain empty.
5 votes -
Add calculation possibility to rule builder
In some cases, the total height or width of a load is required. This may differ from the height of a single product, so such a rule would be helpful.
2 votes -
Vermeidung von Fehlern bei PayPal-Teilrückerstattungen
Die in Shopware eingebaute PayPal-API ermöglicht Rückerstattungen mit einem Klick. Leider passieren bei Teilrückerstattungen in der Hektik des Kundenservice-Alltags oft Fehler – statt z. B. 20 € Nachlass wird aus Versehen der Gesamtbetrag (z. B.100 €) erstattet. Das passiert jedem MItarbeiter mindestens einmal im Monat, weil im Feld „Betrag“ standardmäßig der gesamte Betrag voreingetragen ist und man leicht vergisst, ihn anzupassen.
Mögliche Lösungen:
1) Das Feld "Betrag" ist leer, und der Betrag muss aktiv eingetragen werden.
2) Der Betrag wird rot markiert.
2) Ein Warnhinweis erscheint: „Möchtest du wirklich den vollen Betrag erstatten?“
4) Neben dem blauen Button "Rückerstattung" wird ein zweiter, farblich weniger gesättigter Button "Teilrückerstattung" platziert
Kann Shopware oder PayPal hier etwas tun oder gibt es dazu bereits eine Lösung?
Die in Shopware eingebaute PayPal-API ermöglicht Rückerstattungen mit einem Klick. Leider passieren bei Teilrückerstattungen in der Hektik des Kundenservice-Alltags oft Fehler – statt z. B. 20 € Nachlass wird aus Versehen der Gesamtbetrag (z. B.100 €) erstattet. Das passiert jedem MItarbeiter mindestens einmal im Monat, weil im Feld „Betrag“ standardmäßig der gesamte Betrag voreingetragen ist und man leicht vergisst, ihn anzupassen.
Mögliche Lösungen:
1) Das Feld "Betrag" ist leer, und der Betrag muss aktiv eingetragen werden.
2) Der Betrag wird rot markiert.
2) Ein Warnhinweis erscheint: „Möchtest du wirklich den vollen Betrag erstatten?“
4) Neben dem blauen Button "Rückerstattung" wird…
6 votes -
Native support of IndexNow
Whats this?
"IndexNow is an easy way for websites owners to instantly inform search engines and web crawlers used for information retrieval (“search engines”) about latest content changes on their website. In its simplest form, IndexNow is a simple ping so that search engines know that a URL and its content has been added, updated, or deleted, allowing search engines to quickly reflect this change in their search results."
Currently supports: Microsoft Bing, Naver, Seznam.cz, Yandex, YepWebsite: https://www.indexnow.org/index
3 votes -
Make first- and last name optional for company accounts
First- and last name should be optional if setting up a new customer entry through the administration or by using the register form IF it is a company account.
23 votes -
Enable Search for Custom Fields in B2B Quick orders search field
The B2B Components Quick Order feature should be extended to support searching by custom fields.
This would allow companies to tailor the search experience to their specific data models—for example, enabling search by internal article numbers, supplier SKUs, or industry-specific identifiers. Enhancing the search logic in this way significantly improves usability and efficiency for B2B customers who rely on custom attributes in their ordering processes.
2 votes -
Media: Media search with storage location information
If, for example, you search for an image in the media, you will receive the image and some additional details, but it is not clear in which folder within a potentially large structure the image is located.
In order to check the storage location, it is essential to have information about where the file is located or the option to open the folder directly under “Actions.”
2 votes -
Show admin user who created an order
Currently there is only a static badge that shows if an order was created by an administrator.
It would be nice if the actual user could be displayed, for example as a tooltip in the order list and directly in the badge in the order details.
5 votes -
AI enable headless shop to use the features
EN
If a headless store wants to use the AI features, there is no API endpoint that can be used for this. At least there is no reference to this in the developer documentation.
So the idea is to make AI features usable via API and document the functionality.DE
Wenn ein headless shop die AI Features nutzen möchte, gibt es keinen API Endpunkt, der dafür genutzt werden kann. Zumindest ist in der Entwicklerdokumentation diesbezüglich kein Hinweis zu finden.
Idee ist also: AI feature über API nutzbar zu machen und die Funktionalität zu dokumentieren.2 votes -
Using AI texts in emails
EN
The wish would be that the AI-generated text can also be accessed in an email. This would require appropriate variables and, of course, a way to trigger the generation if this does not happen automatically. For example: The AI-generated completion message is inserted as text in the order confirmation.DE
Der Wunsch wäre, dass auf die AI generierten Text auch in einer E-Mail zugegriffen werden kann. Dazu würden entsprechende Variablen benötigt und natürlich eine Möglichkeit die Generierung zu triggern, falls das nicht automatisch passiert. Als Beispiel: Die AI generierte Abschluss Nachricht wird in der Bestellbestätigung als Text eingefügt.2 votes -
Store default currency in the customer account like the default language
It would be great if you could also store the default currency in the customer account. At the moment you can only select the default language.
2 votes -
Show detailed error message why a voucher could not be redeemed.
Regardless of whether a promotion is no longer valid (end date reached) or the maximum number of redemptions has already been reached, the error message in the offCanvas is always the same and therefore confusing for the customer.
Currently, the content from snippet ‘checkout.promotion-not-found’ is displayed per se.
It would be desirable if the exact reason why the voucher code cannot be used was given in relation to the above examples, i.e.
- ‘Promotion is no longer valid / expired’
- ‘Maximum number of redemptions already reached....’
4 votes -
Define sorting criteria for Admin Search
I would like to be able to define sorting criteria within the admin search. This should ensure that I can sort the search results (for orders, for example) in ascending/descending order number order.
3 votes -
Unsaved changes reminder before leaving
When you apply changes to products as an example, and you by mistake click on the "return to overview" button, all changes are lost. It would be nice, if before leaving the page, a pop up with a unsaved changes reminder would show up.
1 vote -
Keep admin menu open
Please stop auto collapsing the menu sidebar, when clicking on the page editor (Erlebniswelten). Its so annoying and completely unnecessary on large screens.
4 votes
- Don't see your idea?