Import/Export improvements
We continuously work on improving import and export capabilities.
Please let us know in the comments what is still missing for you.
-
Marc Cheng commented
Cross selling export/import right now for a product is limited to a list of id's. some of our customers complain about it and wish to have it with product_number and or product_name, at least for the export with name
-
Marc Cheng commented
we have "a lot" customers (translate that to almost every customer with more than a handful products in the store) that wish to export products filtered by category.
-
Tino Robeller commented
Please add the invoice number field so that you can download a csv in which the invoice numbers are also visible.
-
gigi balanel commented
I would like to have in SW6 import/export in JSON not only CSV.
to be: Select a CSV or JSON file to upload
-
User commented
Please enable product export for individual brands.
Provide a corresponding dropdown for this purpose.
If, for example, suppliers increase prices, this would enable targeted and therefore faster processing of relevant products. -
User commented
A reasonable error output is absolutely necessary. The line and field where the data import got stuck should be displayed.
Example: In a large import, I accidentally had a meta description for a product that was longer than 255 characters. However, the corresponding field in the database only allows 255 characters, which is correct from an SEO perspective, but it was simply an incorrect data record.
It took me hours to find it. With a reasonable error output, as I know it from other shop systems, the matter would have been resolved in a few minutes.In Shopware, unfortunately, the import simply hangs at line xy instead, but does not abort. The displayed line does not allow any conclusions to be drawn about the actual incorrect line, i.e. the error cannot even be localised.
-
Jonathan Klinnert commented
each attribute as a single column to fill values in clear names
-
Sergej Riewe commented
Support of dynamic product groups and rules for export
-
Markus Fischer commented
In Shopware 5 import / export there was an import of orders implemented. The import functionality of this was reduced to changing order states. Sometimes customers ask for this feature in Shopware 6, too.
-
Philip Schilling commented
The Settings > Import/Export feature in the Shopware backend does not fulfil my needs. Examples:
- I would like to export a list where I can see for which orders a promotion has been applied and what discount has been granted per order.
- I would like to export a list of promotional codes, how often they have been used and what the total discount value has been.
- I nwould like to export a list of all customers with registration date, number of orders and sum of order value. This list must also include customers that have not placed any order to understand our lost potential.This can be solved by updating the Import/Export module and / or add an export feature to any customizable data table in backend (46114087-more-fields-and-options-in-the-admin-grid).
-
Marcel Rector commented
It should be already great when the import/export is (functional) performing the same way as in Shopware 5. The Shopware 6 import-export module is a huge step back.
Skip the (required) UUID's or the need to buy a very expensive (and less user friendly) extension (€ 75 fee monthly) to establish something similar.
-
Raymond commented
Automatically export of the stock for all products and save as csv file to the webserver. We use the stock info as csv for importing to other ecommerce systems.
simply:
sku;stock
1234;5
5678;10 -
Marc de Jong commented
Add mapping to the order export so that it is possible to export the choosen payment method per order. In the back-end UI, in the order section you can filter on choosen payment method and you get your result (see screenshot).
It would be great this information can be included in a order export.
-
Robin Figuli commented
Select a period of time for the export of orders
-
Hans Tuscher commented
Error logging and handling would be nice.
There's no way to figure out, that a scheduled generation of a product export worked or not.