WooCommerce 3.1 CSV Import/Export

[Jon007]

This plugin doesn't do anything to break the new WooCommerce 3.1 CSV Import/Export but also doesn't do anything to help either.

What could be the issues/requirements to support it?

WooCommerce 3.1 CSV Import/Export:

• has no concept of Polylang language taxonomy: custom meta and Product Attributes are supported but not arbitrary additional taxonomies, so an additional hook would be needed for this.
• import would not update related attributes in translated versions of products: ie if you used import to update price, attributes etc of existing products, these would not be synchronised to the translated products so the data would become inconsistent.

[frottoli]

How to import a product with the standard csv importer ?
https://polylang.pro/doc/product-csv-importer-and-exporter/

I was thinking the link above was working but is not because the "language" field not exists

[Jon007]

language is a taxonomy not a field, check if the woocommerce importer supports taxonomies, a year ago when this was raised it did not, and this part was not implemented.

possible workarounds:
import products in base language only - they will be imported with no language set but you can use the polylang tool to assign them all to base language
or, use the polylang plugin which you have just linked to (which is not this plugin) and use their support channels
.. or, add the missing implementation

[frottoli]

yes but this plugin is not for free :) Ok now I try with taxonomies or with the workaround and I give you a feedback

[Jon007]

Import isn't synchronising meta on variations at the moment

[konstantinosftw]

First off, man you've done some amazing work with this plugin. It has saved me a ton of time and trouble.

On the issue, I am having the same problem, it's a bit of a fuzz to manually connect each translation of the same product. I personally don't care much about updating the products through CSV imports, but mostly when I have to upload some hundreds of new products and manually connect them with their translations. The best manual process I've found is this:

1. Create one CSV file for each language. For example English and Greek.
2. One of them, the Primary (let's say the English one) has all the necessary fields filled up.
3. The Secondary language CSV needs only the Name, Short Description and Description fiels, since it will inherit everything from the Default product once we connect them together (which will happen after upload).
4. Extra Step In the case of many products, it might help to add a "Language" taxonomy column on each CSV, in which the connected products will share the same, unique, value. This is so you will know which product goes with which, once you try to connect them later on.
5. Now set Polylang's Default Language to the Primary language (English) and Upload the Primary CSV from step 1. All uploaded products will inherit that language.
6. Set Polylang's Default Language the your Secondary language and import the second CSV. All these products will inherit the Secondary language (Greek) on upload. These ones will be pretty empty as they have only the basics, no SKUs, Images etc.
7. At this point you reset the Default Language to your Primary and you start connecting each product with its translated sibling.
   ALWAYS select the Primary language product and add the translated one to it, not vice versa! If you do it the opposite way, the Primary language product will inherit all fields from the Secondary one (which has mostly empty fields) so that specific product's data will be wiped clean. Always click on the Primary product and connect to it the Secondary.

That's about it. I hope there is a way to automate this through your plugin!

[guillermo259]

This plugin doesn't do anything to break the new WooCommerce 3.1 CSV Import/Export but also doesn't do anything to help either.

What could be the issues/requirements to support it?

WooCommerce 3.1 CSV Import/Export:

• has no concept of Polylang language taxonomy: custom meta and Product Attributes are supported but not arbitrary additional taxonomies, so an additional hook would be needed for this.
• import would not update related attributes in translated versions of products: ie if you used import to update price, attributes etc of existing products, these would not be synchronised to the translated products so the data would become inconsistent.

I added a custom taxonomy to my woocommercer exporter so when I have to load the products I have a column called language and it adds each product to each language

[Jon007]

@guillermo259 you are welcome to contribute

[guillermo259]

I use this example https://github.com/woocommerce/woocommerce/wiki/Product-CSV-Importer-&-Exporter#adding-custom-export-columns-developers with this I add a new column to my export file the taxonomy "language" and that show me in the export file which language has each product, and now I'm adding the taxonomy "post_translations" that show me the relationship between my products in each language