- or
1266 results found
-
Add snippet inheritance
If we added snippet inheritance, it would be easy to edit versions of a snippet which only requires minor changes.
For example, let's say German-Swiss. If we had an inheritance on a snippet basis, we could edit only the snippets for shipping costs in the checkout, for example, since it's likely that they differ from the local German shipping cost and/or require different texts for the snippets in the checkout.
Sure, we could simply create a new snippet set. But that inherits from a base file and every change we make in the German snippet set for example are NOT inherited down to German-Swiss. That in turn requires editing TWO sets.
Since we already have the inheritance logic in place for many things, it would be nice to have it for snippets too. Simply going by the logic
"Does the snippet set (German-Swiss) have different text for this snippet than the set it inherits from?
-> Yes: Use that snippet content
-> No: Use the content the set inherits from.That way, we minimize the manual effort involved in taking care of this content.
We have this in place for Shopping Experiences, for example, where it's quite useful. But shopping experiences don't let us edit the content of the snippets we have in the checkout for example.
If we added snippet inheritance, it would be easy to edit versions of a snippet which only requires minor changes.
For example, let's say German-Swiss. If we had an inheritance on a snippet basis, we could edit only the snippets for shipping costs in the checkout, for example, since it's likely that they differ from the local German shipping cost and/or require different texts for the snippets in the checkout.
Sure, we could simply create a new snippet set. But that inherits from a base file and every change we make in the German snippet set for example are NOT…
3 votes -
Add order tab in product variant
It would be great if you could add a tab called orders in the product variant (backend). Sometimes there is the need to check if there are any orders on this variant.
1 vote -
order confirmation - Auftragsbestätigung im Backend (Bestellungen) als neuen Dokumententyp
Hi, im Gegensatz zu SW5 fehlen in SW6 wichtige Funktionen im Backend bei der Bestellverwaltung und auch in der Statistik. Was gar nicht geht, ist die fehlende und teilweise auch rechtlich verbindliche Auftragsbestätigung. Diese ist als Dokumententyp in SW6 nicht vorgesehen bzw nicht so ohne weiteres realisierbar. Nur eine Bestellbestätigung, die ja nur einen Bestelleingang signalisiert, reicht für viele nicht aus. Teiweise ist eine Auftragsbestätigung auch in den AGB der jeweiligen Nutzer festgeschrieben. Zumindest ist im Status "In Bearbeitung" ist also ein Dokumententyp Auftragsbestätigung, ZB auf Basis der Rechnungsvorlage zwingend nötig und liesse sich relativ zeitnah auch umsetzen. Danke und VG M.Staake
_
EN
Hi, in contrast to SW5, SW6 is missing important functions in the backend for order management and also in the statistics. What does not work at all is the missing and partly legally binding order confirmation. This is not provided as a document type in SW6 or cannot be realised so easily. Just an order confirmation, which only signals that an order has been received, is not enough for many people. In some cases, an order confirmation is also stipulated in the terms and conditions of the respective user. At the very least, an order confirmation document type, e.g. based on the invoice template, is absolutely necessary in the "In progress" status and could be implemented relatively quickly. Thank you and VG M.StaakeHi, im Gegensatz zu SW5 fehlen in SW6 wichtige Funktionen im Backend bei der Bestellverwaltung und auch in der Statistik. Was gar nicht geht, ist die fehlende und teilweise auch rechtlich verbindliche Auftragsbestätigung. Diese ist als Dokumententyp in SW6 nicht vorgesehen bzw nicht so ohne weiteres realisierbar. Nur eine Bestellbestätigung, die ja nur einen Bestelleingang signalisiert, reicht für viele nicht aus. Teiweise ist eine Auftragsbestätigung auch in den AGB der jeweiligen Nutzer festgeschrieben. Zumindest ist im Status "In Bearbeitung" ist also ein Dokumententyp Auftragsbestätigung, ZB auf Basis der Rechnungsvorlage zwingend nötig und liesse sich relativ zeitnah auch umsetzen. Danke und…
4 votes -
Product name Bulk edit
It is not yet possible to change the title of a product or, in the case of variants, the title of the variants using the multiple change function.
This would be helpful for customers who want to quickly change the name of variant articles.1 vote -
Order and customer overview: compact view
Order overview: the table is 170 pixel line height
Customer overview: the table is 278 pixel line heightBoth should be equal with max. 100 pixel line height to see more entries per page with less scrolling.
13 votes -
404 Meta title
The 404 page should get an own Meta Title to better track visits on the 404 via GA4
7 votes -
Filter for products on sale in administration
As an admin I require to filter for products on sale.
1 vote -
Change payment in backend
Especially with Stripe we see a high rate of un-completed payments via Giropay and Creditcard.
We then want and have to change the payment type from Stripe to invoice pre-payment, which was possible in SW5 and should be possible in SW6.11 votes -
Bulk edit: product cross selling
Currently there is no option to bulk edit the product cross selling of multiple products at once.
2 votes -
Manage GDPR config for YouTube/Vimeo globally
Different settings for multiple YouTube doesn't make much sense for Data protection. Customizing every video element and every new one for data protection can be time-consuming.
Config:
- YouTube/Vimeo: Advanced privacy mode
- YouTube/Vimeo: Load video only after confirmation by the user2 votes -
Possibility to upload videos to media
It would be great if videos were not some custom CMS blocks but could be added as media and then used in all blocks where images can be selected to display a video there and rename the block group to media.
44 votes -
Custom document generator
Currently, it's not possible to register a document generator for a custom document type when writing an App. I would appreciate it if that could be done through the manifest by declaring a custom document type with a POST endpoint, like:
<admin>
<documentType technical_name="my_document_type" url="https://app.server/my-post-endpoint">
<label>My Document Type</label>
<documentType/>
</admin>The response of the endpoint would be a PDF document.
In addition, (or alternatively) it would be nice if a custom document type could be marked as “cannot be generated” so that the option to generate a document is not offered in the admin UI.
Then the app could either inject its controls to generate the document or generate the document in a web-hook.Currently, it's not possible to register a document generator for a custom document type when writing an App. I would appreciate it if that could be done through the manifest by declaring a custom document type with a POST endpoint, like:
<admin>
<documentType technical_name="my_document_type" url="https://app.server/my-post-endpoint">
<label>My Document Type</label>
<documentType/>
</admin>The response of the endpoint would be a PDF document.
In addition, (or alternatively) it would be nice if a custom document type could be marked as “cannot be generated” so that the option to generate a document is not offered in the admin UI.
Then the app could either…1 vote -
Lazy loading
Lazy loading should be a standard function of modern ecommerce systems, so please implement this function into shopware core.
Why:
- faster loading times
- better SEO10 votes -
8 votes
-
Bitte die Mehrfachänderung für Lieferantenbestellungen hinzufügen.
Bitte die Mehrfachänderung für Lieferantenbestellungen hinzufügen.
Es ist sehr Zeitaufwendig die Preise und die Stückzahl für jeden einzelnen Artikel, in meinem Fall Variantenartikel, anzupassen.
Nach jeder einzelnen Variante speichert das System, das verlängert diesen Bearbeitungsprozess für den Benutzer.
Please add the multiple change for supplier orders.
It is very time consuming to adjust the prices and quantity for each individual item, in my case variant items.
The system saves after each individual variant, which prolongs this editing process for the user.
1 vote -
Promotions: Max uses per company
There are companies in our customer base that have several buyers. However, the voucher can only be redeemed once per company, regardless of how many buyers this company has. This means that not every customer should be able to use the voucher once, but only each company once in total.
2 votes -
Show propery position column in properties table
The table view does not contain the position colomn.
1 vote -
Make properties mandatory
Option to make a property mandatory for all products based on (dynamic) categories and/or saleschannel.
1 vote -
Individual tax calculation: Tax calculation based on the country of delivery
Shopware always calculates the tax based on the country of delivery. There are always enquiries from customers in support where the tax has to be calculated based on the country of dispatch. This is not currently mapped in Shopware, but is being requested more and more frequently.
Therefore, an adjustment or option for tax calculation would be advantageous here in order to be able to map more scenarios.
1 vote -
The active product should not be displayed in cross-selling
If the opened item is part of the product group selected for crosselling, it should not be displayed in crosselling.
5 votes
- Don't see your idea?