ScrapeWoo or WooCommerce’s built-in export: which one to use?
Both write a WooCommerce catalog to a file. What separates them is the access you need and where the products go next.
Use the built-in export if…
- The store is yours and you can log in to it.
- The products stay in WooCommerce.
- You need the drafts or the management fields.
Use ScrapeWoo if…
- The store address is all you have.
- The file goes to Shopify or another tool.
- You want to pick the categories and products before you export.
Point by point
| Criterion | WooCommerce’s built-in export | ScrapeWoo |
|---|---|---|
| What you need | A login to the store’s admin | The store address |
| Files you get | One CSV in the WooCommerce format | WooCommerce CSV, Shopify CSV, standard CSV or JSON |
| Products | All of them, drafts and private products included | The published products |
| Variations | One row per variation, tied to its parent by SKU | One row per variation, tied to its parent by SKU; nested in the JSON |
| Prices, stock, images, attributes | Yes | Yes, as the store publishes them |
| Cost of goods, purchase notes, custom fields | Yes | Not public |
| Best for | Editing the catalog and importing it back into the same store | Moving to Shopify or another tool, or working on a store you have no access to |
Measured on one WooCommerce 11.2.1 store, exported both ways.
Try it on a store.
Paste its address: the detected products appear before any export.