- or
1356 results found
-
E 164 standard for telephone numbers
The normalization of telephone numbers according to the E 164 standard should be implemented. Shopware currently allows any values and text in the checkout and customer account when entering telephone numbers. However, this results in problems, as telephone numbers are used for many purposes in ecommerce. For example, DHL Express ODD, Custom Audiences in Google/Meta, international callbacks in customer service, integration of marketing automation for SMS/WhatsApp, etc. The quality of telephone numbers should therefore be standardized and of high quality to make Shopware 6 merchants competitive in a growing international market.
8 votes -
Sorting of properties should be possible via drag and drop and be inheritable from other languages
If you want to use the same sorting of properties for different languages, it is currently very cumbersome, as the sorting cannot be inherited from other languages and cannot be moved in the product using drag and drop.
1 vote -
Digital Sales Rooms structured statistics (appointment outcome)
It would be nice to store in Shopware the outcome of each appointment, linked to the presenter's account (for guided selling and hybrid approaches, but it may be nice to also have it for the self-service):
customers connected, orders, wishlists.
So, every sales manager could see the results of each appointment and take actions. The data is already available in real time during the session, so we just miss the data storage.1 vote -
Add infinite scrolling for listing pages
In Shopware 5 we had a popular feature with infinite scrolling. Assuming this was not removed because of technical limitations (which I doubt), it would be nice to have this feature added again as often times, customers do not switch pages and instead only look at the first one.
21 votes -
Allow to decorate ElasticSearch CriteriaParser so we can have custom parsing
We are implementing service products, which are products for which you pay in intervals (for example monthly) and don't have to be physical products (like a mobile phone subscription).
For this we also have a cheapest initial recurring price on these products, similar to the cheapest price of products.
We successfully mimicked the logic to update these fields both in the database as well as in ElasticSearch.
However we also need a custom CriteriaParser to parse these fields. We can do this by decorating the CriteriaParser and implementing all public methods, however this is not ideal currently:
- There is no abstract CriteriaParser class so we need to extend the class itself, which is a bit weird if you also decorate it.
- Properties and methods (like isCheapestPriceField, getCheapestPriceParameters and getCheapestPriceAccessors) are private, meaning we can't use them in our logic and have to reimplement things similar to it.
- The class is marked internal, so what we are doing can break any moment.
It would be nice if there is official support for such a use case.
We are implementing service products, which are products for which you pay in intervals (for example monthly) and don't have to be physical products (like a mobile phone subscription).
For this we also have a cheapest initial recurring price on these products, similar to the cheapest price of products.
We successfully mimicked the logic to update these fields both in the database as well as in ElasticSearch.
However we also need a custom CriteriaParser to parse these fields. We can do this by decorating the CriteriaParser and implementing all public methods, however this is not ideal currently:
- There is no…
2 votes -
Exclude Product from Search
As a shop owner I still want to show former products and their variants to users and keep the URLs valid.
Only recent versions and products not excluded from search should appear within the in-store search.
https://store.shopware.com/de/esmx267827209428m/artikel-aus-suche-ausschliessen.html lists the extension's feature to be available with Shopware 6.
Actually it is not.
While you can exclude a product to appear in listings and you being able to exclude it from listings AND search ... there is no option to exclude it from search only.
2 votes -
Manufacturer link should be translatable
We often use this as a "brand"-link to link internally on the website. Would be awesome if translatable.
4 votes -
Migration: Possibility to deactivate Category migrations/comparison
If you start the migration the first time, it is OK to migrate all categories and its content for the first time.
But late in the process it would be nice to be able to deaktivate the category migration/comparison.For example: if you want to update the customers and orders from SW5 to SW6 it always overwrites the categories. Basically almost all preparations you did in the categories for the SW6 launch are gone.
2 votes -
default delivery time
EN
A customer would like to have an option to define a default delivery time when creating a product, which would be used if a corresponding delivery time is forgotten.DE
Ein Kunde wünscht sich, dass es bei der Anlage eines Produkts möglich wäre eine Standard Lieferzeit zu definieren, die eingesetzt wird, wenn vergessen wird eine entsprechende Lieferzeit anzugeben.2 votes -
Add Returns-Management Mappings to Order Export
Add mappings for returns lineItems, refund price, reason and such to the order export.
2 votes -
Configuration of units of measurement (height, width, length) within products.
It should be possible to configure the units of measurement (height, width, length) so that it is not necessary to work with milimeter when calculating.
It should also be possible to choose between cm and meters.
3 votes -
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 -
Assign product layouts per sales channel
Instead of only relying on languages only, product layouts should be able to be defined for each sales channel.
5 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 -
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 -
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 -
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 -
Variants not available via Dynamic Access should also be hidden on the product detail page.
If a variant is not available through Dynamic Access, it will still be displayed on the product details page. If you then select it, another variant will be selected.
There should be an option to hide unavailable variants completely so that they are no longer displayed.7 votes -
8 votes
- Don't see your idea?