Custom tax data in CSV import

Much more a question for whoever has built/developed the CSV import tool you’re using, than us. It sounds like it’s just a matter of properly mapping the csv content to the appropriate taxonomy before performing the import itself. Unsure which or who’s CSV import tool you’re using for this, so I don’t have any immediate answers for next steps outside of reaching out to them.

REST API exposure isn’t sounding like a needed detail unless the import is occurring over POST requests to the REST API itself.

Thanks for prompt reply Michael. As I mentioned previously it default Woocommerce products export / import which is in the header of Woocommerce products admin section, no extra plugins used.
I just metioned API to illustrate why I was surprised of no custom taxonomies found in export. Now I checked — no custom taxonomies in Woocommerce API too, seems like Woo doesn’t have any data about it at all, and it exposes only in WordPress data.
For sure I’m not about to call it an issue, just sharing an experience and expectations thoughts.

Not quite sure how it’s showing/mapping for you with this WooCommerce based import, but I know they list their menu items as “Categories” but the taxonomy slug would need to be “product_cat” to successfully import as terms for that Woo Category. “Tags” would be “product_tag” and then “Attributes” are “product_attributes”, for what it’s worth.

If using WooCommerce to export first, then I assume they’re only exporting their own data.

I didn’t investigate indeed but I have another shop with premium theme which have taxonomy Brands included. And it’s exposed in CSV. It looks completely like CPT UI generated taxonomy, link in admin area edit-tags.php?taxonomy=brand&post_type=product — that’s why I expected to see custom taxonomies in export by default. Hope this information might be useful for you.

Not sure what to suggest exactly at the moment. It’s still up to WooCommerce to include as part of their export, etc. As is, it feels more like a case of having a block of content, that is being wanted to be imported as product_cat terms, correct? Or is this very explicitly a WooCommerce export from one site, that’s trying to be imported into a different WooCommerce site?

All that CPTUI is, at its heart, is a UI to collect arguments for register_post_type() and register_taxonomy() and then actually register them at the appropriate times. We stay pretty hands off when it comes to what is done with the content created afterwards, including migration details like we have here.

No doubt it’s case. But it’s not about transferring data between 2 sites, API is great for it.
Here’s my case: I’m making a shop for very old fashioned book stores. They have about 10K SKUs now, and about 200-400 new SKUs weekly. Their usual tool is Excel, and CSV is their best friend to bulk upload or edit products.
I’m not an experinced PHP developer, but I’m all-about-IT guy. I can run some queries, write my own functions for my own WC shop, but when I need to bulk turn off backorders I prefer CSV as a most visually reliable tool.
Sure CPT UI is fantastic, and what I’m talking about is not a feature request. Here’s my point: about 90% of WC shops I know use CPT UI, big part of them use CSV import on regular basis, and it’d be great to have some walkaround in CPT UI FAQ.

Understood and noted.