26 results found
-
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.2 votes -
Filtern beim Export
Das nur bestimmte Kunden/Bestellnummern exportiert werden können.
12 votes -
Migration: Transfer of additional fields (variants) from shopware 5 to shopware 6.
At the moment, additional fields are completely ignored during migration. However, if these fields were intensively maintained under shopware 5, they should also be present in some form in the variant on the shopware 6 side.
8 votes -
Export of order data (also after cancellation)
Show sales after cancellation...
The order data exported in the following way ‘Import / Export under Settings > Shop > Import / Export’, also show the turnover of the original shopping cart if the customer has cancelled (a product for example) in the meantime.
I need an export list of the orders that also show the turnover that the customer has made after cancelling.
And I need an export list of the orders, in which the comments are shown, which are entered in the backend when processing a cancellation.
1 vote -
Post-import Download with new Id's
After import of NEW products the funktion to download the import-data should include the new created Id's of the new products. They are needed for further import of extended prices, accessories, similars, properties and media.
That would be much easier and faster rather then picking them out of the complete stock of articles that must be downloaded again and again.1 vote -
"Sales" column in the product overview should be updated after the migration
After the migration, the "Sales" column in the product overview should also be updated.
This means that all sales from the 5 shop should also be displayed.This column is currently not updated or is write-protected.
1 vote -
Product layout - Product heading - Content export
It is possible to add new content to the product under Layout in Product heading. However, this content cannot be exported with the product, as is otherwise possible with other product values. However, it would be desirable for customers to export the content of the product heading, as it can also be useful to change this field in a product using export and import.
2 votes -
Extend import/export profile for promotions
If having quite a big amount of promotions where you would like to adjust the sales-channel assignments, you would have to do so manually or directly over the database via sql - if I am not mistaken.
It would be nice if either there would be a mapping for the sales-channel ids in the import-export profile or some kind of bulk edit for promotions.
3 votes -
It should be possible to import digital products
Right now, there is no way to import digital products. Neither using the Im-/Export feature, nor using the API.
It should at least be possible to create/import digital products using the API, because otherwise it is not possible to comfortably connect a different erp-system for digital products or to migrate from another shopware instance.
1 vote -
Implement mapping for document_number in order-export
Implement mapping for document_number in order-export
2 votes -
Enable to reference categories/properties etc. by other fields than ID
In shopware version 6.5.5.2 it is possible to reference certain mappings in the product import profile by fields other than the id of an entity, which is certainly helpful.
Unfortunately, there is no possibility to do it the same way in the column referencing the properties or categories of a product. No matter which other alternative mapping one chooses, e.g. when exporting the custom product export/import profile in the column for properties/categories the entities are always referenced by their internal IDs separated by "|".
It would be practical to have an option to reference these aforementioned entities by other mappings…
4 votes -
Export/import for worlds of experience
An export and import function would be very helpful, especially for very extensive worlds of experience.
This would allow individual backups of individual worlds of experience to be created quickly and easily without having to restore the entire store.
As experience worlds are worked on often and frequently, this would also allow experience worlds to be prepared in staging environments, for example, and quickly restored in the event of errors.
2 votes -
Support of dynamic product groups and rules for export
It would be very helpful if the export of products or other data could be restricted via a dynamic product group or via a rule. For example, I would only like to export orders from the last 2 weeks or products from a specific dynamic product group.
similar idea: https://feedback.shopware.com/forums/942607-shopware-6-product-feedback-ideas/suggestions/47229503-filtern-beim-export
1 vote -
Product export files should have standardised separators
Different decimal separators: The export file for products contains different decimal separators for the representation of fractions. A standardised representation with a point (.) or comma (,) should be defined for the entire export file. PaymentCost is currently transmitted with the separator "point". All other price details have the separator "comma".
1 vote -
Import/Export should contain more translated entries
Import/Export would benefit a lot from having the translated entries for the corresponding UUIDs to make the entries legible in the export.
For example, a commonly requested legible translation is the payment, shipping and order status as well as the product tags. Although, obviously, the more the merrier.
4 votes -
Migration: Correcting the multiple connection function
The migration tool offers the option of creating multiple connections. It is also possible to switch connections.
This is particularly interesting if you want to merge several Shopware installations (or other systems such as Magento) into one Shopware 6 installation. However, if you change the profile during a migration that has not yet been completed by the user with Complete migration, the checksums are mixed up. This behavior has been confirmed by Shopware Support.
It would therefore be a good idea to add a parameter for the active connection to the checksums to prevent mixing by switching open migrations.
If…
1 vote -
Shopware 6 CLI for import / export
For an external system I need periodically an export of the inventory.
The import/export is currently not available for shopware cli:https://docs.shopware.com/en/shopware-en/settings/importexport
https://docs.shopware.com/en/shopware-6-en/tutorials-and-faq/shopware-cli2 votes -
Export/Import opportunity for the Rule Builder, Shipping methods and Snippets
Creating rules at the Rule Builder and use those rules e.g., at the shipping methods with all the availability rules is hard and long work. Therefore, it can be very annoying, if I have to transfer Rule Builder & shipping method settings to other shops. Same story with the text snippets in several languages. It would be great if I would have the possibility to export individual or all rules at the Rule Builder and import them into another shop system. Same issue with shipping methods, which have a bunch of availability rules set up. To export/import snippets would be…
2 votes -
Migration
During migration, it should be clear in the log where information is missing/null or cannot be found.
The migration log is very difficult to read for non-developers.
1 vote -
Data clean-up within the migration
It would be great if you could contribute directly to data cleansing in the migration tool.
For example, "No guest orders", "Orders in the last X months" or similar.1 vote
- Don't see your idea?