ScrapeWoo or the WooCommerce REST API: which one to use?
Both read a WooCommerce catalog without the export screen. One returns JSON to a program you write, the other hands you a file that is ready to import.
Use the REST API if…
- You can create API keys in the store.
- A program has to read the catalog on a schedule.
- You need the drafts or the management fields.
Use ScrapeWoo if…
- The store address is all you have.
- You want a file that is ready to import, with no code.
- The file goes to Shopify or another tool.
Point by point
| Criterion | WooCommerce REST API | ScrapeWoo |
|---|---|---|
| What you need | A pair of API keys with Read permission, created in the store’s admin | The store address |
| What you get | JSON, for a program to read | WooCommerce CSV, Shopify CSV, standard CSV or JSON |
| Products | All of them, drafts and private products included | The published products |
| Variations | One more request for each variable product | Included in every file, tied to their product |
| Prices, stock, images, attributes | Yes | Yes, as the store publishes them |
| Cost of goods, purchase notes, custom fields | Yes | Not public |
| Work on your side | A script that pages through the results and converts the JSON | None: the file is ready to import |
| Best for | Keeping a catalog in sync with a program you write | Getting an import-ready file without code, or without access to the store |
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.