WooCommerce Products Scraper – Store API Export avatar

WooCommerce Products Scraper – Store API Export

Pricing

from $0.56 / 1,000 products

Go to Apify Store
WooCommerce Products Scraper – Store API Export

WooCommerce Products Scraper – Store API Export

Export every product of a WooCommerce store through its public Store API: title, SKU, prices and sale prices, stock, categories, tags, attributes, ratings, images and links, one row per product. No login, no API keys, no proxies, no personal data; pay only for the rows delivered.

Pricing

from $0.56 / 1,000 products

Rating

0.0

(0)

Developer

Rowcraft

Rowcraft

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

17 hours ago

Last modified

Share

WooCommerce Products Scraper: Store API Catalog Export to JSON, CSV

Get the product catalogue of any WooCommerce store as clean, flat rows. This WooCommerce products scraper reads the Store API that every WooCommerce store serves to its own storefront without a login or an API key (/wp-json/wc/store/v1/products, documented by WooCommerce as an unauthenticated API), so it is fast, complete and does not break when a theme changes. Each product comes back as one row: title, SKU, brand, categories, tags, description, selling price and regular price, sale flag and discount, stock, variations, options and attributes, rating, images and the store's currency, as JSON, CSV or Excel.

List the stores you want (a domain, a store URL, a category URL or a product URL), add filters for stock, sale, brands, categories, tags, title words and price, and schedule it with Only new rows to get the new products of your market every morning for the price of the new rows. The robots.txt of each store is read first and obeyed; stores that block automated access are skipped and named, never bypassed.

Input form of WooCommerce Products Scraper – Store API Export

What you get

One row per product, the same columns for every store:

  • Product: ID, SKU, title, brand (where the store uses brands), product type (simple, variable, grouped), category path and category names, tags, link to the product page
  • Prices: lowest and highest selling price (variable products give a range), the regular price before a sale, discount in percent, on-sale flag, the store's currency as the store declares it
  • Stock: in stock, the low-stock count when the store shows one, number of variations
  • Options and attributes: the attributes that make variations (size, colour) with their values; every product attribute as name → values
  • Rating: average rating and number of ratings, as numbers only (the customers' comments themselves are never read)
  • Images: the first image URL in its own column, the full image list with thumbnails and alt texts when you want it
  • Description: as plain text, HTML removed and contact details masked
  • Store: host, store name, currency; the category the row was read from
  • Coverage: one line per store in the run summary with its product count, pages read, rows delivered and, when skipped, why

Why this actor

  • The documented public API, not HTML scraping: the Store API answers JSON for every visitor, 100 products per request, with the total in its headers, so a catalogue of 5,000 products takes 50 requests and nothing depends on the theme.
  • Category and product URLs: paste a category URL (/product-category/gifts/) or a product URL (/product/handle/) and only that part is read; the category is resolved on the store's public category list.
  • robots.txt first: each store's robots.txt is fetched and applied to the exact paths that will be read; disallowed stores are skipped and reported.
  • Honest about blocks: a store that disabled its Store API, answers 403, an anti-bot page or HTML instead of JSON, or asks for a password, is skipped at once with the reason in the run summary; nothing is retried through proxies.
  • Filters before you pay: stock, sale, brands, categories, tags, title words and price range are applied before any row is charged; duplicates (a product in two categories) are delivered once.
  • Count before you pay: Count only returns the number of products per store (the store's own total when no filter is set) and the cost; nothing is delivered.
  • Same columns as the Rowcraft Store Products Scraper, which reads Shopify, WooCommerce and VTEX stores together.

How to use it

  1. Open the Actor and fill in Stores (the other fields are optional filters).
  2. Set Maximum products to a small number for a first try (the default is a safe start).
  3. Optional: tick Count only and start once. You get the number of matching rows and the estimated cost, for free (only the start event is charged). Untick it to get the data.
  4. Click Start. The status line shows progress; the run stops cleanly at your limit or at the charge limit you set in the run options.
  5. Open the Dataset tab and download JSON, CSV, Excel, XML or HTML, or send the rows to Google Sheets, Slack, Make, n8n or Zapier with the Integrations tab.
  6. To run it on a schedule, use Schedules in Apify Console and turn on Only new rows since the last run below: every run then costs only the new rows, and a webhook URL tells you when something new came in.

Input

FieldWhat it does
storesStores to read, one per line: offermanwoodshop.com, https://store.com, a category URL (https://store.com/product-category/gifts/) or a product URL (https://store.com/product/handle/)
categories, brands, tags, titleContainsKeep products whose category or type contains a word, of these brands (exact, case ignored), with one of these tags, or with one of these words in the title
availableOnly, onSaleOnlyIn stock only; on sale only
minPrice, maxPriceSelling price range in the store's currency
includeDescription, includeImagesDescription as text (on), the full image list (on)
maxProductsPerStore, maxItemsStop each store after this many products; stop the run after this many rows
countOnly, onlyNew, stateName, notifyUrl, notifyWhenEmptyCount only (deliver nothing); see Automation below
requestIntervalMsPause between requests, one second by default, 500 ms at the lowest

The stores are read one after the other. A store entry that points to a category or a product reads only that part; a product that appears in two categories is delivered once.

Example: everything on sale from two stores, without images, as a daily feed of new rows.

{
"stores": ["offermanwoodshop.com", "https://auntfannies.com"],
"onSaleOnly": true,
"includeImages": false,
"onlyNew": true,
"maxItems": 2000
}

Output

41 fields per row. Empty values are null, never missing, so CSV and Excel columns are stable.

FieldTypeExample
idstringpipsnacks.com:6719287066696
platformstringshopify
urlstringhttps://www.pipsnacks.com/products/lime-corn-dippers
storestringpipsnacks.com
storeNamestringPipsnacks
storeCountrystringUS
currencystringUSD
productIdstring6719287066696
skustringLIME-DIP-6
skusarray["LIME-DIP-6"]
gtinstring5949084015911
titlestringLime Corn Dippers
brandstringPipsnacks
productTypestringDippers
categoryPathstringBacanie > Dulciuri > Croissante
categoriesarray["Bacanie", "Dulciuri"]
tagsarray["gluten-free", "vegan"]
descriptionstringCorn dippers with lime…
pricenumber4.99
priceMaxnumber6.99
listPricenumber5.99
discountPercentinteger17
onSalebooleanTrue
availablebooleanTrue
stockQuantityinteger99999
variantsCountinteger2
availableVariantsCountinteger2
optionsarray[{"name": "Size", "values": ["S", "M"]}]
attributesobject{"Material": ["Cotton"]}
ratingnumber4.8
ratingCountinteger12
imageUrlstringhttps://cdn.shopify.com/s/files/1/0/products/lime.jpg
imagesCountinteger3
imagesarray[{"id": "1", "src": "https://cdn.shopify.com/s/files/1/0/products/l…
publishedAtstring2024-03-05T14:00:00-05:00
createdAtstring2024-03-01T10:00:00-05:00
updatedAtstring2026-10-01T09:30:00-04:00
sellerstringAuchan Romania
collectionstringbest-sellers
sourcestringcatalog
scrapedAtstring2026-10-12T18:00:00.000Z

Example rows

Two real rows from a run (long texts shortened here, complete in the dataset):

[
{
"id": "auntfannies.com:120459",
"platform": "woocommerce",
"url": "https://auntfannies.com/product/laundry-detergent/",
"store": "auntfannies.com",
"storeName": "Aunt Fannie's",
"storeCountry": null,
"currency": "USD",
"productId": "120459",
"sku": "LDP",
"skus": [
"LDP"
],
"gtin": null,
"title": "Laundry Detergent",
"brand": null,
"productType": "variable",
"categoryPath": "Laundry",
"categories": [
"Laundry"
],
"tags": [],
"description": "The power of vinegar\n• Lifts grime – naturally breaks up tough stuff, including greasy kitchen spills.\n• Sparkling Finish – incredible on…",
"price": 11.99,
"priceMax": 11.99,
"listPrice": 11.99,
"discountPercent": null,
"onSale": false,
"available": true,
"stockQuantity": null,
"variantsCount": 2,
"availableVariantsCount": null,
"options": [
{
"name": "Scent",
"values": [
"Bright Lemon",
"Eucalyptus",
"Fragrance Free",
"… 1 more"
]
}
],
"attributes": {
"Scent": [
"Bright Lemon",
"Eucalyptus",
"Fragrance Free",
"… 1 more"
]
},
"rating": null,
"ratingCount": 0,
"imageUrl": "https://auntfannies.com/wp-content/uploads/2026/04/Group-124.png",
"imagesCount": 1,
"images": [
{
"id": 120466,
"src": "https://auntfannies.com/wp-content/uploads/2026/04/Group-124.png",
"thumbnail": "https://auntfannies.com/wp-content/uploads/2026/04/Group-124-300x300.png",
"alt": null
}
],
"publishedAt": null,
"createdAt": null,
"updatedAt": null,
"seller": null,
"collection": null,
"source": "catalog",
"scrapedAt": "2026-10-12T16:25:56.081Z"
},
{
"id": "auntfannies.com:120454",
"platform": "woocommerce",
"url": "https://auntfannies.com/product/extra-strength-laundry-detergent/",
"store": "auntfannies.com",
"storeName": "Aunt Fannie's",
"storeCountry": null,
"currency": "USD",
"productId": "120454",
"sku": "LDE",
"skus": [
"LDE"
],
"gtin": null,
"title": "Extra Strength Laundry Detergent",
"brand": null,
"productType": "variable",
"categoryPath": "Laundry",
"categories": [
"Laundry"
],
"tags": [],
"description": "The power of vinegar\n• Lifts grime – naturally breaks up tough stuff, including greasy kitchen spills.\n• Sparkling Finish – incredible on…",
"price": 11.99,
"priceMax": 11.99,
"listPrice": 11.99,
"discountPercent": null,
"onSale": false,
"available": true,
"stockQuantity": null,
"variantsCount": 2,
"availableVariantsCount": null,
"options": [
{
"name": "Scent",
"values": [
"Eucalyptus",
"Fragrance Free"
]
}
],
"attributes": {
"Scent": [
"Eucalyptus",
"Fragrance Free"
]
},
"rating": null,
"ratingCount": 0,
"imageUrl": "https://auntfannies.com/wp-content/uploads/2026/04/Group-140.png",
"imagesCount": 1,
"images": [
{
"id": 120464,
"src": "https://auntfannies.com/wp-content/uploads/2026/04/Group-140.png",
"thumbnail": "https://auntfannies.com/wp-content/uploads/2026/04/Group-140-300x300.png",
"alt": null
}
],
"publishedAt": null,
"createdAt": null,
"updatedAt": null,
"seller": null,
"collection": null,
"source": "catalog",
"scrapedAt": "2026-10-12T16:25:56.081Z"
}
]

Results can be downloaded as JSON, CSV, Excel, XML or HTML from the Dataset tab, or read through the Apify API.

Results of WooCommerce Products Scraper – Store API Export in the Apify dataset view

Pricing

Pay per result. You pay for each product delivered to your dataset, nothing else: no subscription, no minimum, no charge for rows your filters drop or for the requests behind them.

Your Apify planPrice per 1,000 rowsPrice per row
Free plan$0.80$0.0008
Starter plan$0.72$0.00072
Scale plan$0.64$0.00064
Business plan and above$0.56$0.00056

Example: 1,000 products cost $0.80 on the Free plan and $0.56 on the Business plan. The Apify platform usage of a run (compute, storage) is small for this actor — well under one cent per 1,000 rows — and is billed by Apify separately, as for every Actor. A start event of $0.00005 is charged once per run (Apify default). Cap your spend: set Maximum total charge in the run options. The actor stops cleanly when the cap is reached and you keep everything delivered until then. The run summary (RUN_SUMMARY in the key-value store) says why a run stopped. Check before you pay: turn on Count only to see how many rows match and what they would cost at your tier. That run delivers nothing and costs only the start event.

Automation: only new rows, notifications, schedules

Only new rows since the last run. Turn on onlyNew and the actor remembers every product it delivered to you (in a key-value store named rowcraft-woocommerce-products-scraper-state in your Apify account). The next run with the same stateName skips what you already have and you pay only for new rows. The first run delivers everything that matches. Use a different stateName for each schedule or search so they keep separate memories.

Notification when the run ends. Put a webhook address in notifyUrl and the actor sends one JSON POST with the number of new rows, links to the dataset (JSON and CSV) and the run. It works out of the box with Slack and Discord incoming webhooks (the message is in text and content), with Make, n8n and Zapier catch hooks, and with your own endpoint. By default it is sent only when there is at least one new row; notifyWhenEmpty sends it every time.

Schedules. Create a schedule in Apify Console (hourly, daily, weekly or cron) with onlyNew on. A daily schedule gives you a feed of new products for the price of the new rows only.

Integrations. Send the results to Make, n8n, Zapier, Google Sheets, Slack, Google Drive, Airtable or any webhooks from the Integrations tab of the Actor, with no code. Apify also offers native actions for Make, n8n and Zapier.

API, SDKs and AI agents. Every run is available through the Apify API and the official JavaScript and Python clients; the Actor can also be called by AI agents through the Apify MCP server. The example input in the API tab is a working call.

Count only. countOnly returns the number of matching products and the estimated cost without delivering anything, so you can size a job before paying for it.

Use cases

  • Price and sale monitoring: selling price, regular price, discount and stock per product, run daily; compare with yesterday's dataset or feed a sheet.
  • Competitor assortment: what a shop sells, in which categories and price bands, what is on sale, which attributes it offers.
  • Catalogue feeds and migrations: a clean product export with images, attributes and descriptions for a marketplace listing, a comparison site or a move to another platform (your own store or one that allows it).
  • Supplier and reseller checks: your products on resellers' WooCommerce shops: prices below the agreed minimum, outdated descriptions, missing variations.
  • Sourcing research: brands, categories and price ranges across many small shops, counted before anything is paid.

Ready-made examples, each with the input filled in (open one and press Start, or save it as your own task):

What this actor does not do

  • Read stores that disabled the public Store API or block automated access: a 404 on the Store API, a 403, an anti-bot page or HTML instead of JSON means the store is skipped and named in the run summary; the actor never uses proxies or disguises itself.
  • Read paths a store's robots.txt disallows.
  • Deliver dates, units in stock or stock per variation: the Store API gives no publication or update dates, only a low-stock count where the store shows one, and the variations' own prices and stock only through one request per variation, which the actor does not make.
  • Deliver customer data or customers' comments: the comments endpoint carries the writers' names and is never read; only the average rating and the number of ratings are delivered.
  • Deliver one row per variation, use a store's search, log in, or go through the REST API that needs keys.

Limits and fair use

  • One request per second by default, 500 ms at the lowest, and one store at a time. Each request returns up to 100 products, so a catalogue of 5,000 products takes 50 requests. A 429 from a store ends that store at once (not retried) and the run continues with the next one.
  • The Store API gives no dates, no units in stock (only a low-stock count) and no stock or price per variation; price and priceMax are the range the store shows for a variable product.
  • Many WooCommerce shops run behind a CDN that blocks automated access, or have the public Store API disabled; they are reported as such in the run summary and never charged.
  • Prices are in the store's currency as shown to a visitor; a store that sells in several currencies shows its default one here.
  • A listing is read up to 300 pages (30,000 products) per store or category; split a larger store by category URLs.

Data source

The data comes from the WooCommerce Store API of each store (/wp-json/wc/store/v1/products, /products/categories and the WordPress root for the store name), which WooCommerce documents at developer.woocommerce.com/docs/apis/store-api as an unauthenticated API that needs no keys or tokens. The actor fetches each store's robots.txt and follows it for the exact paths it reads. Each store publishes its own terms of service, and some forbid automated access; the actor cannot read those terms for you. By listing a store you confirm that you may read its catalogue under that store's terms and the law that applies to you. Stores that block automated access are skipped, never bypassed. Rowcraft is independent and not affiliated with or endorsed by Automattic Inc., WooCommerce, WordPress or any store; names and trademarks belong to their owners.

Privacy: no personal data

Rowcraft actors are built not to collect personal data:

  • The Store API's product endpoints carry product data only: no customers, no orders, no staff. The customers' comments endpoint, which carries the writers' names, is never read; only the average rating and the number of ratings are delivered. The fields delivered are listed above and nothing else is kept.
  • Descriptions and titles are passed through the same filter as every Rowcraft actor: e-mail addresses, phone numbers, mailto: and tel: links and contact-person names are removed before the row is saved.
  • The brand is the business name shown on the store, not a person's contact.

You are responsible for using the data in line with the law that applies to you and with the terms of the stores you list.

Other Rowcraft actors

All Rowcraft actors read official or public sources, deliver flat rows without personal data and support only-new runs and notifications:

FAQ

Which stores work? Any WooCommerce store whose Store API answers, which is the default since WooCommerce 5.6: in a test of seven shops from the official showcase, two answered at once, four had moved to Shopify (read by the Rowcraft Shopify or Store Products scrapers) and one was blocked by its CDN. The run summary names every store with its result.

Why was a store skipped? The reason is in the run summary and in the log: robots.txt disallows the path, HTTP 403 or an anti-bot page (the store blocks automated access), 404 (the Store API is disabled or the site is not WooCommerce), HTML instead of JSON, a password page, a 429 rate limit, or a host that does not exist. None of these is retried through proxies or with a disguised browser: the store has said no.

Do I need an API key or a login? No. The Store API is public; the actor sends a clear user agent and nothing else. The keyed REST API (wc/v3) is not used.

Can I read only one category or one product? Yes: paste the category URL (https://store.com/product-category/gifts/) or the product URL (https://store.com/product/handle/) into stores. To filter by category words across whole stores use categories.

Why are there no dates? The Store API does not publish creation or update dates, so publishedAt, createdAt and updatedAt are empty for WooCommerce rows. For a feed of new products use Only new rows, which remembers what was delivered.

What about variations? The row has the number of variations, the attributes that make them (size, colour) with their values, and the price range of the product. The variations' own prices and stock would need one request per variation and are not read.

Which currency are the prices in? The store's own currency, read from the store's price block (currency column). Prices are numbers, not strings, so you can sort and compare.

Are images included? The first image URL is always in the row; includeImages adds the full list with thumbnails and alt texts. Images stay on the store's server; the actor does not download files.

What does Count only do? It asks each store how many products it would deliver: the store's own total when the whole catalogue is read without filters, otherwise the listing is read and counted. The result, with the cost at your plan, goes into the run summary; nothing is delivered and only the start event is charged.

How do I get the results into Slack, Google Sheets, Make, n8n or Zapier? Use the Integrations tab of the Actor for the data, and the notifyUrl field for a message when a run ends (Slack and Discord webhooks work directly; catch hooks of Make, n8n and Zapier too).

Can I call it from code or from an AI agent? Yes: through the Apify API, the JavaScript and Python clients, and the Apify MCP server. The API tab shows a working example with the input of this Actor.

Is it legal to use this data? The actor reads the official API described in the Data source section and delivers product catalogue data without personal data. The licence of the source is described above. How you use the data is your responsibility under the law that applies to you.

Does it collect personal data? No. Contact persons, e-mails and phone numbers are removed and fields about people are never requested. See the Privacy section.

The run finished with 0 rows. Did I pay? No: with no rows delivered nothing is charged apart from the start event. Check the run summary (RUN_SUMMARY) for warnings, widen the filters, or run with Only new rows off if everything matching was already delivered to you.

Support and reviews

Problems, missing fields, questions: open an issue on the Issues tab of this Actor. We answer within one working day and fix confirmed bugs in the next release; the changelog lists every change.

If this Actor saved you time, a short review on its page helps other users find it and helps us keep improving it.