Shopify & WooCommerce Store Products Scraper avatar

Shopify & WooCommerce Store Products Scraper

Pricing

from $0.35 / 1,000 product scrapeds

Go to Apify Store
Shopify & WooCommerce Store Products Scraper

Shopify & WooCommerce Store Products Scraper

Export any Shopify or WooCommerce store catalogue as JSON: products, variants, prices, compare-at prices, stock, tags and images. Auto-detects the platform, plain HTTP, residential proxy included. From $0.50 per 1,000 products.

Pricing

from $0.35 / 1,000 product scrapeds

Rating

0.0

(0)

Developer

subimpact network

subimpact network

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

an hour ago

Last modified

Features

Limited permissions

Share

Export the whole product catalogue of any Shopify or WooCommerce store as clean JSON — title, price, compare-at price, currency, stock, tags, images, variants — from the store's own public catalogue JSON. No browser, no login, no API key.

Paste one store URL or a hundred. The actor detects the platform for each store by itself and reads whichever public endpoint that platform serves:

PlatformEndpoint read
Shopifyhttps://<store>/products.json?limit=250&page=N, https://<store>/collections/<handle>/products.json
WooCommercehttps://<store>/wp-json/wc/store/v1/products?per_page=100&page=N (the public Store API)

Pricing: $0.50 per 1,000 products ($0.0005 per delivered product row). Store error rows and empty catalogues are free.

What you get

One dataset row per product: store URL, platform, product id, handle, title, vendor, product type, tags, product URL, lowest variant price, compare-at price, currency, availability, variant count, the variants themselves, image URLs, a plain-text description, Shopify created/updated timestamps, scrape timestamp and a status.

  • Variants: id, title, SKU, price, compare-at price and stock per variant (includeVariants, on by default).
  • Price is the cheapest variant price — the "from" price a storefront shows — so it always describes something you can actually buy. compareAtPrice is the compare-at price of that same variant.
  • available is true when any variant is buyable.
  • description is HTML-stripped, entity-decoded and capped at 20,000 characters.
  • text fields (title, vendor, product type, tags, variant titles) are entity-decoded too, so Dropshipfy &#8211; Easy Dropshipping arrives as Dropshipfy – Easy Dropshipping.
  • Currency: Shopify stores are asked for it once per store (/meta.json, falling back to /cart.js); WooCommerce returns prices.currency_code on every product. Unknown currencies are null, never guessed.
  • Nothing is invented: a missing upstream value (no SKU, no sale price, no image) stays null.

Quick start

Input:

{
"storeUrls": ["https://www.allbirds.com"],
"maxProductsPerStore": 250,
"maxItems": 1000,
"includeVariants": true
}

That is one product request plus a currency lookup: a couple of seconds and $0.125 for 250 products.

Scrape only some Shopify collections

{
"storeUrls": ["https://www.allbirds.com"],
"collectionHandles": ["mens", "womens-shoes"],
"maxItems": 500
}

collectionHandles accepts bare handles (mens) or pasted URLs (https://store.com/collections/mens); a collection title is converted to its handle ("Men's Shoes" -> mens-shoes), and the exact handle is the part after /collections/ in the collection URL. It is ignored for WooCommerce stores, which are scraped whole. A product that appears in two collections is delivered once.

Scrape a set of stores

{
"storeUrls": [
"https://www.allbirds.com",
"https://woocommerce.com",
"https://www.advancedcustomfields.com"
],
"maxProductsPerStore": 100,
"maxItems": 300
}

Output example

A real row from a live run (formatted for readability):

{
"storeUrl": "https://www.mvmt.com",
"platform": "shopify",
"productId": "10221706969336",
"handle": "odyssey-ii-carnation-gold-25mm-28000352",
"title": "Odyssey II Carnation Gold 25mm",
"vendor": "MVMT",
"productType": "Watches",
"tags": ["BOGO_50", "BOGO_Y", "Womens", "YGroup_odyssey-ii-25"],
"url": "https://www.mvmt.com/products/odyssey-ii-carnation-gold-25mm-28000352",
"price": 153.95,
"compareAtPrice": 192.95,
"currency": "USD",
"available": true,
"variantCount": 1,
"variants": [
{
"id": "49993854943480",
"title": "Carnation Gold",
"sku": "28000352",
"price": 153.95,
"compareAtPrice": 192.95,
"available": true
}
],
"images": [
"https://cdn.shopify.com/s/files/1/0834/8654/0024/files/28000352_fr.jpg?v=1784141353",
"https://cdn.shopify.com/s/files/1/0834/8654/0024/files/28000352_b.jpg?v=1784147241"
],
"description": "A West Coast approach to an iconic 1970's silhouette. Reimagined from the distinct 70’s shape that’s defied the ordinary for decades, the Odyssey II features hand-polished steel contrasts, faceted hour markers that glint in motion, and a sleek profile.",
"createdAt": "2026-07-15T14:49:09-04:00",
"updatedAt": "2026-11-15T04:16:38-05:00",
"scrapedAt": "2026-11-15T09:16:16.257Z",
"status": "ok",
"error": null
}

A WooCommerce row carries the same fields; createdAt/updatedAt are null because the public Store API does not publish creation or modification dates, and WooCommerce variations carry their option values (title: "License Type: Bundling") without per-variation prices or stock.

Status values

statusmeaningcharged
okproduct rowyes
errorthe store could not be read — invalid URL, or its catalogue endpoint is disabled, blocked or returned something that is not JSON. error names the HTTP status of each endpoint triedno
emptythe store answered, but published no products (empty catalogue, or a collection handle with no products)no

A run never fails because one store in the list is broken: you get a free error row for that store and the other stores are still scraped.

Input

FieldTypeDefaultMeaning
storeUrlsarray— (required)Shopify or WooCommerce store URLs. Pasted /products.json, /collections/... or /wp-json/... URLs are reduced to the store root.
collectionHandlesarray[]Shopify only: scrape just these collections instead of the whole catalogue.
maxProductsPerStoreinteger250Stop paging a store after this many products.
maxItemsinteger1000Hard cap on product rows for the whole run (max 100,000).
includeVariantsbooleantrueAdd the variants array to each row.
proxyConfigurationobjectApify residential proxyResidential proxy is on by default and its cost is included in the price (see rate limits below).

A run also stops cleanly when the account's paid-event / max-dataset-items limit is reached; rows already delivered are kept and charged, and the run status message says how many rows were delivered.

Rate limits and politeness

The actor makes at most one request per second per store, sends no cookies and keeps no session, and honours HTTP 429 Retry-After before retrying (two retries, then the store gets a free error row instead of a hammering loop).

Shopify rate-limits its public products.json per client IP, shared across stores, and answers HTTP 429 with Retry-After when the budget is exhausted, and datacenter IP ranges are limited almost at once (measured 2026-11-15 from Apify: 5 of 6 Shopify stores answered 429 or 403 without a proxy or through datacenter proxy, 5 of 6 answered 200 through residential proxy). The actor therefore uses Apify residential proxy by default, without a pinned session, so each request leaves from a rotating IP; the proxy cost is included in the price. A few large brands block storefront JSON altogether (403); those stores get a free error row.

The actor also stays on HTTP/1.1 for these endpoints: measured on 2026-11-15, identical requests over HTTP/2 got 429 where HTTP/1.1 got 200 (Shopify's limiter is sensitive to the HTTP/2 client fingerprint).

Notes and limits

  • Public catalogue data only: password-protected stores, draft/unpublished products and stores that have disabled products.json / the Store API cannot be scraped. They produce a free error row that names both endpoints' HTTP status.
  • Product ids are delivered as strings so long ids stay exact.
  • Prices are in the store's own currency (a Shopify store selling in EUR gives EUR prices). No FX conversion.
  • One row per product, not per variant; use variants for variant-level data. To get one row per variant, expand the array downstream.
  • WooCommerce exposes at most 100 products per request and Shopify 250, so very large catalogues take products / page size requests at one request per second.

Development

npm ci && npm test # offline: node:test against saved fixtures, no network
node test/live.mjs 5 # live smoke run of the real fetch+parse path (not part of npm test)

src/http.js owns pacing/retries, src/shopify.js and src/woo.js are the pure parsers, src/scrape.js owns detection and paging, src/main.js owns delivery and charging (a row is pushed first, then charged).

Run monitoring and privacy

If a run fails or times out, this Actor tells its developer the run ID and status, so we can fix problems fast. It never sends your input, your results or your account data.