Shopify Products Scraper — Any Store, No Auth | from $1.50/1K

Built for dropshippers tracking Shopify supplier catalogs, price intelligence tools monitoring competitor stores, and e-commerce analysts building cross-store product databases.

Pricing: Pay per product — $1.50/1K (per-product mode), $2.00/1K (per-variant mode). First 10 results free.

No login. No proxy. No API key. Works on any Shopify store.

Scrape any Shopify store's full product catalogue via the public /products.json endpoint. Works on both *.myshopify.com subdomains and custom store domains.

What you get

• One row per variant (default) or one row per product — your choice
• Clean, typed fields: price is a float, not a Shopify string
• Full variant data: variant_id, variant_title, price, compare_at_price, sku, available
• Product metadata: title, handle, vendor, product_type, tags, image_url, product_url
• ISO 8601 timestamps: created_at, updated_at, published_at
• parse_confidence score + warnings list per row (see below)

Use cases

• Competitive price monitoring — track prices and availability across stores
• Catalog indexing — build product databases from Shopify merchants
• Dropship research — find in-stock variants and supplier SKUs
• Market analysis — aggregate product types, vendors, tag taxonomies

How to use

1. Add Shopify store URLs to Store URLs — one per line:

   gymshark.myshopify.com
   www.allbirds.com
   mybrand.myshopify.com
   

2. Set Max products per store (0 = no limit, scrapes all pages)
3. Toggle One row per variant — ON for price/SKU tracking, OFF for catalog overview

Input fields

Field	Type	Default	Description
storeUrls	list	—	Shopify store URLs (myshopify.com or custom domain)
maxProducts	integer	100	Products per store; 0 = all
rowPerVariant	boolean	true	One row per variant (true) or per product (false)
includeBodyHtml	boolean	false	Include body_html product description
productHandleFilter	string	—	Substring filter on product handle
vendorFilter	string	—	Substring filter on vendor field

Output schema

Field	Type	Notes
store_domain	string	e.g. gymshark.myshopify.com
product_id	integer	Shopify product ID
title	string	Product title
handle	string	URL slug e.g. classic-tee
vendor	string	Brand/vendor name
product_type	string	Store-defined category
tags	array	Product tag list
variant_id	integer	Shopify variant ID (null if rowPerVariant=false)
variant_title	string	e.g. Small / Black
price	float	Listing price
compare_at_price	float or null	Struck-through / original price
sku	string	Stock-keeping unit
available	boolean	In-stock flag
image_url	string	First product image CDN URL
product_url	string	Canonical storefront URL
body_html	string or null	Product description (opt-in)
created_at	string	ISO 8601
updated_at	string	ISO 8601
published_at	string	ISO 8601
parse_confidence	float	0.0–1.0 quality score
warnings	array	Machine-readable quality codes

parse_confidence & warnings

Each row includes a parse_confidence score (1.0 = all expected fields present). Deductions:

• product_id_missing → −0.50
• title_missing → −0.25
• handle_missing → −0.10
• no_variants → −0.20
• created_at_missing → −0.05

Limitations

• /products.json is a public Shopify endpoint — no login, no proxy needed
• Some stores restrict it (401/403/404). The actor logs these and continues to the next store
• Shopify does not expose inventory_quantity in the public API — use available (boolean) instead
• Price is in the store's default currency (no currency code in the public API)

vs. competitors

Feature	This actor	epctex/shopify-scraper
Auth required	None	None
Per-variant mode	Yes	Partial
compare_at_price (sale detection)	Yes	No
parse_confidence drift signal	Yes	No
Price	$1.50/1K	$2–3/1K

Use with AI agents (MCP)

This actor is tagged MCP_SERVERS — compatible with Claude, GPT-4o, and other MCP-aware agents:

https://mcp.apify.com/?tools=bovi/shopify-products-scraper

Pricing example

Volume	Mode	Cost
100 products	Per-product	$0.15
1,000 products	Per-product	$1.50
1,000 variants	Per-variant	$2.00
10,000 variants	Per-variant	$20.00

First 10 results are free. You pay only for rows actually returned.

FAQ

Do I need a Shopify API key or login? No. This actor uses the public /products.json endpoint — available on every Shopify store without auth. No credentials, no proxy needed.

Does it work on custom domains (not myshopify.com)? Yes. Provide the full custom domain (e.g. www.allbirds.com) and the actor detects the Shopify backend automatically.

What output formats are available? JSON (default), CSV, and Excel — via the Apify dataset export or API.

What if a store returns empty or a 403 error? Some stores restrict /products.json via their Shopify settings (password-protected stores). The actor logs the error and continues to the next store — it does not crash. You are not charged for failed stores.

Notes

• This actor is not affiliated with Shopify Inc.
• Scraping is limited to publicly accessible product data — no account required

Integrations

Built for dropshippers and e-commerce analysts monitoring competitor catalogs, pricing, and variant availability — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Tiktok Shop Scraper
• Uber Eats Menu Scraper
• Vinted Marketplace
• Allegro Offers
• Amazon Products Scraper
• Autoscout24 Cars Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.