Shopify Product Catalog Scraper — Prices & Variants
Pricing
$0.80 / 1,000 delivered products
Shopify Product Catalog Scraper — Prices & Variants
Export accessible public Shopify product catalogs with variants, prices, availability, images and product links. Bounded multi-store CSV/JSON exports. $0.80 per 1,000 delivered products, no start fee or API key.
Pricing
$0.80 / 1,000 delivered products
Rating
0.0
(0)
Developer
Datamule
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Shopify Product Catalog Scraper
Export product catalogs from accessible public Shopify stores into structured JSON, CSV or Excel. Supply several storefront URLs and receive one row per unique product, with every publicly returned variant kept inside that row. Use it for catalog research, price comparisons and product-feed analysis.
Quick start
{"storeUrls":["https://www.allbirds.com"],"maxProducts":25}
Use a store's final, canonical HTTPS hostname. Paths normalize to the shop origin; redirects are not followed. The example is an independent public storefront, not a demo dataset or an affiliation. Catalogs change over time.
What you receive
- Product ID, title, handle, description HTML, vendor, type, tags and product URL.
shopOriginso catalogs from multiple stores stay attributable.- All publicly returned variants, including IDs, titles, options, SKU, price, compare-at price and boolean availability.
- Images and product options as returned by the public catalog.
- Storefront creation, update and publication timestamps when present.
Prices remain source strings. Currency is null: this public products.json interface does not assert a reliable currency code alongside its prices. We do not infer currency from a domain, language, price symbol or a shopping-cart cookie. Verify the store's pricing currency separately before combining monetary values. available means at least one variant is marked available by the storefront; it is not an exact inventory quantity.
Inputs and limits
| Input | Default | Meaning |
|---|---|---|
storeUrls | Public example above | 1–20 HTTPS storefront URLs |
maxProducts | 25 | Global unique-product cap across all stores, 1–10,000 |
Stores are processed in input order. Identical normalized origins and product IDs within an origin are deduplicated. Products on different store origins remain separate, even if their titles match. Pagination uses at most 250 products per request. A changing live catalog can shift page boundaries; this is not an atomic shop snapshot.
Only public /products.json and /robots.txt are requested. No Admin API, login, cart operations, checkout, customer data, proxy bypass or anti-bot workarounds. Store robots rules and crawl delays are honored; inaccessible or disallowed catalogs are skipped. Follow applicable source terms and use only catalogs you are authorized to collect. Password-protected shops, blocked JSON endpoints and redirects are unsupported; use the final storefront hostname rather than expecting bypasses. Response size is capped at 12 MiB, individual HTTP calls time out after 25 seconds, and pagination has a safety ceiling. Unusually large or malformed products can be skipped. No full-catalog completeness guarantee is made.
The SUMMARY key-value record reports delivered products, malformed-product skips and source failures. If no current valid catalog is accessible, the run fails rather than returning invented products. An accessible empty catalog can succeed with zero products. With multiple stores, successful rows may accompany reported source errors.
Pricing and spending
$0.0008 per delivered product ($0.80 per 1,000), with no start fee. All variants and images inside a product row are included. One product costs $0.0008; 25 cost $0.02; 100 cost $0.08. These are Actor event charges; consult Apify for any separate platform charges.
Set a positive maximum run charge in Apify to bound billed results. A positive limit below one product's price produces no rows or product events. Do not use a run charge setting of zero as a zero-spend guarantee: Apify may interpret zero as unset. The global result cap and remaining budget both apply.
Output uses the Apify SDK's charged push, which clips delivery to affordability. Dataset and charged-event history are reconciled on restart; disagreement stops the run instead of silently rebilling. Dataset writes and billing are not transactional: a crash or billing failure can leave an unmatched output prefix requiring investigation. We do not promise exactly-once billing across an ambiguous failure.
This independent Actor is not endorsed by Shopify or any example storefront.