Guide

How to get Shopify and WooCommerce store data

Your own store exports for free. For someone else's, decide first whether you need every product row or an answer at store level.

Two platforms, two very different levels of openness

Shopify and WooCommerce both run enormous numbers of stores, and getting data out of them works nothing alike. That is worth knowing before you pick a tool.

Your own store is the easy case. Both platforms export your own catalogue natively. Shopify has a CSV export in the admin; WooCommerce ships a product exporter that handles variations and images. If the store is yours, use those. They are free, complete, and nothing beats them.

Someone else's store is the real question, and that is what most people are actually searching for: a competitor's assortment, a supplier's catalogue, or a segment of the market.

What the free routes give you

Chrome extensions. Plenty exist, they work per store, and the free tiers usually stop somewhere around the point the catalogue gets interesting. For one store, once, they are fine.

Public endpoints. Many Shopify storefronts expose a public products path that returns JSON, which is why every scraper tutorial starts there. It is paginated, it is rate limited, and a store can turn it off. Treat it as something that works today rather than an API you can build a business on.

WooCommerce is messier, because it is WordPress: the shape depends on the theme and the plugins, so there is no single reliable path across stores. Anything working across many WooCommerce stores is doing real parsing, not calling an endpoint.

The question before the catalogue

People ask for a full product export when what they need is a store-level answer: what platform is this, how big is the catalogue roughly, what does it sell, which apps or payment methods does it use, is it actually active. That is one row per store instead of thousands of product rows, it costs a fraction, and for research or qualifying a lead it is the better dataset.

Work out which of the two you need before you pay for either. Full catalogues are the right answer for price monitoring and assortment comparison. Store reports are the right answer for qualifying, segmenting and sizing.

What to watch out for

  • Variants explode the row count. One product with five sizes and four colours is twenty rows, and any per-row price applies to all of them.
  • Prices are currency and market specific. The same store can serve different prices by region. Pin it or your comparison is nonsense.
  • Images are links, not files. Exporting a catalogue gives you URLs. If you need the pictures themselves, that is a second job.
  • Terms. A store's own terms can forbid automated collection even when the data is publicly reachable. That is a separate question from whether it is technically possible, and the one that actually matters.

What a product row should carry

If you do go for the catalogue, these are the fields that decide whether the export is usable six months later.

  • A price range, not a price. A product with variants has a lowest and a highest one. For a single product both are the same number, and a table that stores only one of them quietly loses the spread.
  • The struck-through price separately. The was-price is a different field from the current price, and mixing them makes every discount analysis wrong.
  • Variant and image counts. Cheap to carry, and they tell you how much work a full variant export would be before you pay for it.
  • The store it came from on every row, so a multi-store pull stays one table.

What we charge for it

Store reports are billed per store reported at $3.50 per 1,000 for both platforms, so under half a cent per store. That is the dataset for sizing a market or qualifying a list of shops: a thousand webshops for three dollars and fifty cents, filterable on platform, catalogue size and payment setup.

Both platforms also have a product catalogue, billed per product listed at $1.00 per 1,000, with the price range, the struck-through price, variant and image counts and stock state on every row. A shop with two thousand products costs two dollars to pull.

One difference to know before you compare the two in one table. WooCommerce publishes its own on-sale flag and carries the sale price as its own field. Shopify does not: there the was-price sits in a compare-at field and the on-sale state is derived from it being higher than the asking price. Same answer, arrived at differently, and worth pinning down in your own schema before you merge the two.

The datasets behind this

›Shopify Products Catalog Scraper: prices, variants, stock, bulk

Product catalogue of any Shopify store from its public products feed, up to 200 stores a run and 5,000 products each: title, handle, URL, vendor, type, tags, dates, price range, sale and stock flags, every variant with SKU, price and options, images and description. Robots-aware. Pay per product.

$1.00 per 1,000 · Product listed

›WooCommerce Products Catalog Scraper: prices, stock, categories

Product catalogue of any WooCommerce store from its public Store API, up to 200 stores a run and 5,000 products each: name, URL, SKU, price, sale price, currency, stock and on-sale flags, rating, categories, tags, brands, attributes, images and description. Robots-aware. Pay per product.

$1.00 per 1,000 · Product listed

›Shopify Store Analyzer & Report: catalogue, prices, stock

One report per Shopify store, up to 200 stores per run: catalogue size, price range and average, currency, share in stock, share on sale, product types, brands, newest and oldest product, plus ranked signals such as a stale catalogue or heavy discounting. Pay per delivered report.

$3.50 per 1,000 · Store reported

›WooCommerce Store Report: catalogue, prices, stock, reviews

One report per WooCommerce store, up to 200 stores per run: the exact product count, price range and average, currency, share in stock, share on sale, categories, brands, average review rating, and ranked signals such as an empty catalogue or heavy discounting. Company data only, no personal data.

$3.50 per 1,000 · Store reported