- or
No existing idea results
- ~ No ideas found ~
1345 results found
-
Extend ruling / possibilties for shipping methods
EN
The number of requests to expand the options for shipping methods is increasing. Many customers who come from Shopware 5 miss the option of entering individual calculations or combining standard shipping methods with surcharge or discount shipping methods. I'll take DHL as an example here. When shipping abroad, the EU / non-EU distinction is used, the destination countries are divided into zones, there is a basic price and a surcharge per kilogramme.
This can of course be mapped with Rule Builder and the current shipping methods, but if I send goods weighing up to, say, 100 kg, it means creating a price matrix with at least 100 entries. This also involves manually calculating which basic price with which number of kilograms results in which total price.The price per kilogram remains the same in the scenario, so the whole thing would be relatively easy for our customers to map if it were possible to specify a calculation, for example "total weight * 1.50 EUR", the basic prices are staggered according to kilogram ranges, which could already be easily mapped now. It would only be necessary to add the two together to produce a final shipping price. Percentage surcharges etc. are also missing.
DE
Die Anfragen zu einer Erweiterung der Möglichkeiten für Versandarten nehmen zu. Viele Kunden, die von Shopware 5 kommen, vermissen die Möglichkeit individuelle Berechnungen zu erfassen oder Standardversandarten mit Aufschlags- oder Abschlagsversandarten zu kombinieren. Als ein Beispiel nehme ich hier DHL. Bei dem Versand ins Ausland wird die Unterscheidung EU / Nicht EU angewendet, die Zielländer sind in Zonen aufgeteilt, es gibt eine Grundpreis und einen Aufschlag pro Kilogramm. Das lässt sich mit Rule Builder und den aktuellen Versandmethoden natürlich abbilden, aber allein wenn ich Versandgut bis sagen wird 100 Kg verschicke, bedeutet es eine Preismatrix mit mindestens 100 Einträgen anzulegen. Dabei muss dann auch noch manuell berechnet werden, welcher Grundpreis mit welcher Kilozahl welchen Gesamtpreis ergibt.Der Preis pro Kilogramm bleibt in dem Szenario gleich, somit wäre das Ganze für unsere Kunden relativ leicht abzubilden wenn es die Möglichkeit gäbe eine Berechnung anzugeben, zum Beispiel "Gesamtgewicht * 1,50 EUR", die Grundpreise sind nach Kilogrammbereichen gestaffelt, das ließe bereits jetzt einfach abbilden. Es müsste nur beides zusammen gerechnet einen Versandendpreis ergeben. Vermisst werden außerdem prozentuale Aufschläge usw.
EN
The number of requests to expand the options for shipping methods is increasing. Many customers who come from Shopware 5 miss the option of entering individual calculations or combining standard shipping methods with surcharge or discount shipping methods. I'll take DHL as an example here. When shipping abroad, the EU / non-EU distinction is used, the destination countries are divided into zones, there is a basic price and a surcharge per kilogramme.
This can of course be mapped with Rule Builder and the current shipping methods, but if I send goods weighing up to, say, 100 kg, it means…5 votes -
404 Meta title
The 404 page should get an own Meta Title to better track visits on the 404 via GA4
8 votes -
Warehouses as condition and stocks
A Warehouse should be selectable for the definition of Dynamic Product groups
The stock of the warehouse should be possible to use for condition, example: Stock in Warehouse 1 > 1
The warehouse stocks should change the main stock in the Product listing.
2 votes -
B2B checkout: Order reference and deliverydate
SW6 B2B Component should have same functionality as the previous B2B-suite. In Order process (checkout) merchants should have form-fields for own Order-Reference and wishes for the delivery-date.
(order.customFields.b2bOrderReferenceHolder, order.customFields.b2bDeliveryDateHolder)
4 votes -
Quick orders - CSV format
When a CSV file is created on a standard Windows PC, as most users still do, it is in DOS ANSI encoding (the normal user does not care about this but simply creates a file). This format is not supported by the quick orders (in the upload).
It would be great if more formats were supported, OR if a hint text was added to the upload field for the UTF-8 format.
1 vote -
Define database fields yourself | Datenbankfelder selbst definieren
DE
Datenbankfelder selbst definieren, um die Nachvollziehbarkeit und business-individuelle Zweckhaftigkeit der Auswertungen zu steigern.
–
EN
Define database fields yourself to increase the traceability and business-specific usefulness of the evaluations.1 vote -
Fallback for Variant Pre-Selection
The storefront presentation can be used to define a specific variant preselection for the listing as well as for the detail page.
If the main article is now selected for display in the listing, but no variant is defined for the preselection on the detail page, any variant is preselected seemingly at random, even if it is no longer available in terms of stock.
Here it would be desirable if we could simply select the next available variant option as a fallback.
16 votes -
Add translations for order statuses
Currently, it is not possible to add translations for order, payment and delivery status as the entries appear to be hardcoded.
There is an issue ticket already which was closed (despite having 18 votes, which seems like nothing to sneeze at), which can be found here:
https://issues.shopware.com/issues/NEXT-15282
Contrary to what is written in that ticket, translations ARE used IF present and that is the issue really. They can't be added in the admin anywhere.
We CAN circumvent this by adding them manually in the database, but we can't expect shop owners to do this because that way is rather technical and comes with certain risks.
An elegant way would be to have them register as snippets so they can be translated like most other content.
Currently, it is not possible to add translations for order, payment and delivery status as the entries appear to be hardcoded.
There is an issue ticket already which was closed (despite having 18 votes, which seems like nothing to sneeze at), which can be found here:
https://issues.shopware.com/issues/NEXT-15282
Contrary to what is written in that ticket, translations ARE used IF present and that is the issue really. They can't be added in the admin anywhere.
We CAN circumvent this by adding them manually in the database, but we can't expect shop owners to do this because that way is rather technical…
4 votes -
simplify import of new Products
The import of new products should be significantly simplified. As in SW5, it should be possible to edit profiles more easily and make ALL nodes/extensions for advanced prices, media, properties, cross-selling, etc. available to provide ALL relevant data for new products in one upload.
In its current form, the import and export process is extremely cumbersome and very inconvenient.3 votes -
Demotivating update strategy
I don't understand why new versions are constantly being released. Shopify releases an update twice a year. Can't you do the same with Shopware? Collect everything or once a quarter and you know in advance what will be optimised. And the release date is fixed, so you can prepare for it. It would simply be structured. Security updates run separately.
We pay a lot of money for updates because many functionalities are no longer available in the Shopware core and we always have to test all plugins to see if they are compatible again. I'm not even going to mention external systems such as ERP or the like. Developers even complain to us that Shopware's version updates are random and that they then have to catch up quickly and features can't be developed because they have to guarantee compatibility. Is Shopware aware of this?
And I suspect that this situation is annoying - for the developers of the plugins and also for the retailers.
We are currently trying to upgrade to Shopware 6.6.7.1 and I already know that a new version is coming.
It's demotivating.
I don't understand why new versions are constantly being released. Shopify releases an update twice a year. Can't you do the same with Shopware? Collect everything or once a quarter and you know in advance what will be optimised. And the release date is fixed, so you can prepare for it. It would simply be structured. Security updates run separately.
We pay a lot of money for updates because many functionalities are no longer available in the Shopware core and we always have to test all plugins to see if they are compatible again. I'm not even going to mention…
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.
6 votes -
New document type in orders: order confirmation
EN:
There should be a new document type: order confirmation. The order confirmations generated via ERP can contain more information (e.g. contact person based on zip code) and can therefore be important for the customer.DE:
Es sollte einen neuen Dokumententyp: Bestellbestätigung geben. In den per ERP generierten Auftragsbestätigungen können mehr Informationen (z.B. Ansprechpartner basierend anhand er Postleitzahl) enthalten sein und damit wichtig für den Kunden sein.3 votes -
Permissions for extension settings
I like to set up permission for the admin user only for configuration/managment of one specific extension.
1 vote -
Direct links in the account
Shopware provides a lot of website with a lot of interesting data, like feedback.shopware.com, brand.shopware.com and others. As a partner it would be helpful to have links to these site directly in the account. SSO makes it possible to log me in directly.
2 votes -
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.
14 votes -
Authorisation to display statistics
At present, the display of authorisations is still linked to the right to display and edit orders.
As employees often also process orders but should not be able to view the statistics, a special right is required in the configuration of the authorisations in order to be able to show and hide this display individually for users.
1 vote -
Promotions should be combined with discounts in subscriptions
Discounts are not enabled for subscriptions by default.
A discount should be also available for subscriptions in addition to the discount that is already set in the subscription.
E.G. a subscription has a 10% discount set. A regular discount is defined via promotion and is used for a reqular cart. When the same produdct is used in a subscription the discount from the promotion is not applied.
If a merchant want´s to apply both discounts within a subscription an option is needed in the promotion to use it also within subscritions.
2 votes -
Include dashboard in the user rights
It would be good if you could select the dashboard as an individual right in the user rights in the admin. There are users who are allowed to see orders but should not have access to the dashboard.
2 votes -
Product feed templates for price comparison platforms
Customers ask for additional templates for product feeds for pricing comparison platforms like Idealo once in a while. Maybe we could add some of the most common.
DE
Kunden fragen ab und zu nach weiteren Vorlagen für Produkt Feeds für Anbieter von Produkt- und Preisvergleichen wie Idealo. Vielleicht können wir weitere für die bekanntesten Anbieter ergänzen.2 votes -
It should also be possible to process discount promotions if orders with this discount have already been placed.
It should also be possible to process discount promotions if orders with this discount have already been placed.
Some discounts are intended to be used permanently, except that the discount itself changes from time to time. However, this is currently not possible.
1 vote
- Don't see your idea?