# Shopify Products Scraper for Catalogs & Variants (`fetch_cat/shopify-products-scraper`) Actor Export public Shopify product catalogs with variants, prices, images, vendors, tags, availability, and product URLs from one or more storefronts. - **URL**: https://apify.com/fetch_cat/shopify-products-scraper.md - **Developed by:** [Fetch Cat](https://apify.com/fetch_cat) (community) - **Categories:** E-commerce, Automation, Developer tools - **Features:** Limited permissions - **Stats:** 6 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.005 / start This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event ## What's an Apify Actor? An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md. ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run. For examples already wired to this Actor's own input schema, see the [API](#api) section below. Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`). # README Export public Shopify product catalogs with **Shopify Products Scraper**. Collect product titles, URLs, vendors, tags, prices, availability, variants and image details from one or more storefronts for catalog research, merchandising audits and your own comparison workflows. No Shopify API key is needed. Stores must expose a readable public catalog. Currency is always `null`, and inaccessible stores produce error rows rather than product records. ### Quick start 1. Open the Actor and enter a public Shopify storefront homepage. 2. Start with a small product limit and run the Actor. 3. Open the dataset to review product rows and any store-level errors. ```json { "storeUrls": [{ "url": "https://www.deathwishcoffee.com" }], "maxProductsPerStore": 20, "includeVariants": true, "includeImages": true, "includeRawProduct": false } ``` Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same. https://youtu.be/1OW8gOqlZbY?t=25 ### Ready-to-run examples Choose an example to start with a preconfigured input. - [Export Products from a Shopify Coffee Store](https://apify.com/fetch_cat/shopify-products-scraper/examples/shopify-coffee-store-products) — Collect up to 50 products with variants and images from a coffee storefront. - [Compare Product Catalogs Across Shopify Stores](https://apify.com/fetch_cat/shopify-products-scraper/examples/shopify-competitor-product-catalogs) — Collect up to 25 products per store from two storefronts for your own comparison. - [Build a Shopify Product Image Dataset](https://apify.com/fetch_cat/shopify-products-scraper/examples/shopify-product-image-dataset) — Collect up to 50 products with image URLs and dimensions, without detailed variants. ### What you get - **Product records:** Titles, handles, product URLs, vendors, product types and normalized tags. - **Prices and availability:** Variant price ranges, compare-at prices and whether any variant is marked available. - **Optional detail:** Variant SKUs and options, image URLs and dimensions, or the original product object. - **Multi-store results:** Successful products stay in the dataset alongside any store-level error rows. Run records help you inspect partial work and resume unfinished stores. ### Who is it for? | Team | Useful workflow | | --- | --- | | Ecommerce analysts | Compare product assortments across brands. | | Merchandising teams | Audit variant prices, tags, images and availability. | | Agencies and researchers | Prepare structured catalog exports. | | Automation teams | Feed product records into spreadsheets or databases. | ### Input settings Use storefront homepages or domains. A product or collection path is normalized to the storefront origin, not used as a filter. | Setting | JSON key | Purpose | | --- | --- | --- | | Store URLs | `storeUrls` | Storefronts to read, as URL objects or strings. | | Maximum products per store | `maxProductsPerStore` | Cap each store at 1–10,000 products. Form default: 20. Omitted API input: 100. | | Include variants | `includeVariants` | Include variant detail, enabled by default. | | Include images | `includeImages` | Include image detail, enabled by default. | | Include raw product JSON | `includeRawProduct` | Include the original object, disabled by default. | | Maximum run time | `maxRunSeconds` | Work budget up to 270 seconds. | | Resume store URLs | `resumeStoreUrls` | Add unfinished stores from an earlier run. | | Proxy configuration | `proxyConfiguration` | Keep the existing proxy settings or configure supported direct/custom access. See field help for defaults and costs. | To resume without adding stores, supply `storeUrls: []` and the saved list as `resumeStoreUrls`. A resumed store starts from its first page, so reconcile duplicate products in your own workflow. ### Output data The dataset contains one row per saved product, plus an error row when a store cannot be read. This illustrative shape is not a fresh extraction result: ```json { "status": "success", "storeUrl": "https://example.com", "storeDomain": "example.com", "productId": 123, "title": "Example product", "handle": "example-product", "url": "https://example.com/products/example-product", "vendor": "Example vendor", "priceMin": 19.99, "priceMax": 24.99, "currency": null, "available": true, "variantCount": 2, "imageCount": 1 } ``` | Fields | Meaning | | --- | --- | | `status`, `errorMessage` | Product success or store-level error and its reason. | | `storeUrl`, `storeDomain`, `sourceUrl`, `scrapedAt` | Store identity, source page and extraction time. | | `productId`, `title`, `handle`, `url` | Product identity and storefront link. | | `vendor`, `productType`, `tags` | Catalog labels when present. | | `publishedAt`, `createdAt`, `updatedAt` | Source timestamps when available. | | `priceMin`, `priceMax`, `compareAtPriceMin`, `compareAtPriceMax` | Numeric variant price ranges, or `null`. | | `currency` | Always `null`. No currency is inferred. | | `available`, `variantCount`, `imageCount` | Availability summary and detail counts. | | `variants` | Optional ID, title, SKU, price, compare-at price, availability and selected options. | | `images` | Optional image ID, URL, alt text, dimensions and position. | | `rawProduct` | Optional original product object. | `RUN_SUMMARY` in the run's key-value store records saved products, errors, failed stores, empty catalogs and unfinished stores. `PENDING_STORE_URLS` is saved when work remains. Blocked requests, invalid catalog responses and incomplete exports fail the run while preserving useful products and store-level errors. Customer spending or short time limits stop successfully with `LIMIT_STOP` and an explanation in the summary; raise the limit to collect more products. #### Download your results Open your run's dataset, choose **Export** and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet. See [Apify's download and export guide](https://docs.apify.com/storage/dataset#apify-console) for the available formats and field options. ### Pricing This Actor uses pay-per-event pricing. The `start` event is charged once when processing begins. A `result` event is charged for each successfully saved product. Store-level error rows do not incur a `result` event. A run without products can still incur the start charge. Input limits help bound the amount of work, and configured proxy traffic can have separate charges. See the [live Pricing tab](https://apify.com/fetch_cat/shopify-products-scraper/pricing) for current rates and discounts. ### Tips for best results - **Start with one store.** Use a small product limit to check its public catalog. - **Use the storefront domain.** Product and collection paths do not restrict the catalog. - **Keep exports small.** Disable detailed variants, images or raw product objects when you do not need them. Price ranges and counts are still returned. - **Inspect partial results.** Review error rows and `RUN_SUMMARY` before treating an export as complete. - **Compare your saved datasets.** Recurring runs collect new snapshots, not built-in change alerts. ### Limits and caveats Only publicly readable Shopify storefront catalogs are supported. The Actor does not log in, access private inventory or guarantee access to every store. There are no collection, search, bestseller or sorting filters. Capped exports retain the public catalog's returned selection. With the 10,000-product cap, images disabled and raw JSON disabled, an ID-only discovery can select a lower-bandwidth public Storefront export when the complete catalog fits. Complete Storefront exports use product-ID order; discovery overflow retains the original capped catalog route. Explicit proxy choices apply to both routes. Storefront rejection before any output can fall back to the original catalog route; errors after output fail rather than restart or silently mix selections. `sourceUrl` identifies the actual public endpoint. `updatedAt` is that endpoint's timestamp and may differ between the Storefront and catalog JSON surfaces; it is not a cross-source change-tracking guarantee. Counts include all fetched image and variant pages even when their details are omitted. Raw JSON and image-detail exports retain the original complete catalog route. Prices have no verified currency code, and availability is a summary of the source variants, not an inventory quantity. Empty public catalogs return no product rows. Unreadable stores produce error rows. A blocked response alone does not establish that a store is private or deleted. Large or slow catalogs can finish partially, and resuming repeats the unfinished store from its beginning. ### Automation and integrations #### Save your settings for next time Once you have an input that works for you, [save it as an Apify task](https://docs.apify.com/actors/running/tasks). This keeps your settings together so you can use them again without filling in the form from scratch. #### Run on a schedule Need fresh results regularly? You can [schedule the Actor or a saved task](https://docs.apify.com/actors/running/schedules) to run at a time that suits you. Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow. #### Send results to your other tools Use **n8n, Make or Zapier** to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the [Apify integration guides](https://docs.apify.com/integrations) for your chosen tool. For a custom connection, an [Apify webhook](https://docs.apify.com/integrations/webhooks) can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure. ### API usage Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results. The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its `defaultDatasetId` to fetch the results. For setup instructions, see Apify's [JavaScript client guide](https://docs.apify.com/api/client/js), [Python client guide](https://docs.apify.com/api/client/python) and [Actor runs API reference](https://docs.apify.com/api/v2/acts-runs-post). #### cURL ```bash curl --request POST \ --header "Authorization: Bearer $APIFY_TOKEN" \ --header "Content-Type: application/json" \ --data '{"storeUrls":[{"url":"https://www.deathwishcoffee.com"}],"maxProductsPerStore":20}' \ 'https://api.apify.com/v2/acts/fetch_cat~shopify-products-scraper/runs' ``` After the returned run completes, fetch `https://api.apify.com/v2/datasets/DATASET_ID/items` with the same authentication, replacing `DATASET_ID` with its `defaultDatasetId`. #### Node.js ```js import { ApifyClient } from 'apify-client'; const client = new ApifyClient({ token: process.env.APIFY_TOKEN }); const run = await client.actor('fetch_cat/shopify-products-scraper').call({ storeUrls: [{ url: 'https://www.deathwishcoffee.com' }], maxProductsPerStore: 20 }); const { items } = await client.dataset(run.defaultDatasetId).listItems(); console.log(items); ``` #### Python ```python import os from apify_client import ApifyClient client = ApifyClient(os.environ['APIFY_TOKEN']) run = client.actor('fetch_cat/shopify-products-scraper').call(run_input={ 'storeUrls': [{'url': 'https://www.deathwishcoffee.com'}], 'maxProductsPerStore': 20, }) items = client.dataset(run['defaultDatasetId']).list_items().items print(items) ``` ### MCP and AI agents You can ask your AI assistant to collect data with **Shopify Products Scraper** and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes. Connect your assistant through the [Apify MCP server](https://mcp.apify.com/). MCP gives your assistant a way to find this scraper, run it and read the results. Follow the [official setup and sign-in guide](https://docs.apify.com/mcp) for your app. #### Easier setup with an Apify plugin If you use a supported coding assistant, the [official Apify plugin](https://docs.apify.com/agents/plugins) can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app. #### Use Apify AI in Console Prefer to keep everything in Apify? Open [Apify AI in Console](https://docs.apify.com/account/apify-ai) and ask it to find Fetch Cat's **Shopify Products Scraper**. You can describe the data you want and ask questions about the results. Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply. #### Choose your assistant - **Claude and Claude Code (Anthropic):** [Apify setup guide](https://docs.apify.com/integrations/claude). - **ChatGPT and Codex (OpenAI):** [Apify setup guides](https://docs.apify.com/integrations/openai). - **Grok Bot (xAI):** [Apify plugin guide](https://docs.apify.com/integrations/grok-bot). - **Gemini CLI (Google):** [MCP server setup guide](https://geminicli.com/docs/tools/mcp-server/). Use the server URL below with the HTTP configuration supported by Gemini CLI. #### Connect just this scraper To keep your setup focused on this scraper, add this server configuration to a compatible MCP client: ```json { "mcpServers": { "apify": { "url": "https://mcp.apify.com?tools=fetch_cat/shopify-products-scraper" } } } ``` Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format. #### Use Apify's general server Already connected to the general Apify MCP server at `https://mcp.apify.com`? You can use it to find this scraper without adding another server. Ask your assistant to use **Shopify Products Scraper** by Fetch Cat, or give it the identifier `fetch_cat/shopify-products-scraper`. Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service. #### Example requests - “Get 20 products from deathwishcoffee.com and summarize their price ranges.” - “Collect up to 25 products each from deathwishcoffee.com and brooklinen.com, then compare their vendors and product types.” - “Get 30 products with images from brooklinen.com and prepare a spreadsheet of product names and image URLs.” Normal Apify charges apply. Check the [live Pricing tab](https://apify.com/fetch_cat/shopify-products-scraper/pricing) before asking your assistant to run a larger batch. ### Pay with x402 If your AI agent has a funded wallet, it can pay for Apify usage through [x402](https://docs.apify.com/integrations/x402). This experimental option lets an agent use Apify without a conventional account. [Apify AGI](https://agi.apify.com/) provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection. Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability. Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration. #### Other ways for agents to pay Apify also supports **MPP** for prepaid access through AGI and **Skyfire** for eligible Actors. If your agent already uses one of these, see the [agentic payment guide](https://docs.apify.com/agents/payments) to choose the right setup. ### FAQ #### Do I need a Shopify API key? No. This scraper reads public storefront catalogs without Shopify login credentials. It is not a replacement for authenticated Shopify Admin API access. #### Can I export variants and images? Yes. Enable the corresponding settings to include the detail arrays. Each dataset row remains a product, not an individual variant. #### Why is currency empty? `currency` is always `null` in this Actor. Check the storefront separately before comparing prices across currencies. #### Why did I get fewer products or error rows? The store may expose fewer public products, block access or fail during processing. Inspect the error rows and run summary. No response alone proves that a store is private or deleted. #### Can I monitor catalogs over time? You can save settings and arrange recurring runs through Apify. Store snapshots and compare them in your own workflow. The scraper itself does not detect changes or send alerts. ### Related Actors - [Google Shopping Results Scraper](https://apify.com/fetch_cat/google-shopping-results-scraper) — Research shopping listings across stores. - [AliExpress Products Scraper](https://apify.com/fetch_cat/aliexpress-products-scraper) — Collect marketplace product records. - [Walmart Products Scraper](https://apify.com/fetch_cat/walmart-products-scraper) — Export Walmart product data. - [Shopify App Reviews Scraper](https://apify.com/fetch_cat/shopify-app-reviews-scraper) — Research Shopify apps rather than storefront products. - [Website Contact Finder](https://apify.com/fetch_cat/website-contact-finder) — Find publicly listed website contact information. ### Support and feedback For custom additions or integrations, email . Found an error or have a feature request? [Open an issue](https://apify.com/fetch_cat/shopify-products-scraper/issues) with the run URL, a non-sensitive input example and what you expected. Need help sharing it? See [Apify’s guide to sharing a run when reporting an issue](https://docs.apify.com/account/collaboration/general-resource-access#automatically-sharing-runs-via-actor-issues). Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead. Tried this scraper? We'd love to hear how it worked for you. [Leave a review](https://apify.com/fetch_cat/shopify-products-scraper/reviews) to help others choose the right tool and help us improve it. If the review page is unavailable, open the Actor page and use its available review option. Your feedback means a lot to us. Made with care for curious people, AI agents and the possibilities in data. ♥ # Changelog This Actor's version history is a separate document: https://apify.com/fetch_cat/shopify-products-scraper/changelog.md # Actor input Schema ## `storeUrls` (type: `array`): Shopify storefront homepages to scrape, such as https://www.deathwishcoffee.com or https://kith.com. ## `maxProductsPerStore` (type: `integer`): Maximum products saved per storefront, from 1 to 10,000. The input form defaults to 20. API calls that omit this field use the existing runtime limit of 100. ## `includeVariants` (type: `boolean`): Include variant-level SKU, price, compare-at price, availability, and options. ## `includeImages` (type: `boolean`): Include product image URLs and dimensions. ## `maxRunSeconds` (type: `integer`): Stop cleanly before the platform timeout and save unfinished stores for a later run. ## `resumeStoreUrls` (type: `array`): Optional public store URLs from PENDING_STORE_URLS after a partial run. These are combined with Store URLs and duplicate origins are removed. When resuming without additional stores, supply storeUrls as an empty array. ## `includeRawProduct` (type: `boolean`): Attach the original Shopify product payload for advanced debugging or custom processing. This increases dataset size. ## `proxyConfiguration` (type: `object`): The input form defaults to Residential Apify Proxy from the first request because direct cloud requests have encountered storefront rate limits. Existing API calls that omit this object retain the SDK-managed Apify Proxy default without selecting a group. Explicit settings take precedence: managed proxy groups and country, custom proxy URLs, or useApifyProxy: false for direct access are preserved. There is no automatic direct-to-proxy fallback. Proxy traffic may incur separate charges. Use direct access only after confirming that it works for your target. Invalid configurations are handled by the existing SDK validation, not replaced with an automatic paid fallback. ## Actor input object example ```json { "storeUrls": [ { "url": "https://www.deathwishcoffee.com" }, { "url": "https://www.brooklinen.com" } ], "maxProductsPerStore": 20, "includeVariants": true, "includeImages": true, "maxRunSeconds": 270, "includeRawProduct": false, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } } ``` # Actor output Schema ## `overview` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "storeUrls": [ { "url": "https://www.deathwishcoffee.com" }, { "url": "https://www.brooklinen.com" } ], "maxProductsPerStore": 20, "includeVariants": true, "includeImages": true, "includeRawProduct": false, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } }; // Run the Actor and wait for it to finish const run = await client.actor("fetch_cat/shopify-products-scraper").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "storeUrls": [ { "url": "https://www.deathwishcoffee.com" }, { "url": "https://www.brooklinen.com" }, ], "maxProductsPerStore": 20, "includeVariants": True, "includeImages": True, "includeRawProduct": False, "proxyConfiguration": { "useApifyProxy": True, "apifyProxyGroups": ["RESIDENTIAL"], }, } # Run the Actor and wait for it to finish run = client.actor("fetch_cat/shopify-products-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}") for item in client.dataset(run.default_dataset_id).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "storeUrls": [ { "url": "https://www.deathwishcoffee.com" }, { "url": "https://www.brooklinen.com" } ], "maxProductsPerStore": 20, "includeVariants": true, "includeImages": true, "includeRawProduct": false, "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ] } }' | apify call fetch_cat/shopify-products-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,fetch_cat/shopify-products-scraper" } } } ``` The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer ` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations). ## OpenAPI specification Download the OpenAPI definition: https://api.apify.com/v2/actors/39DRVmgD1UQ14aBer/builds/gQWNybou6hebDR8F7/openapi.json