Shopify Products Scraper: Variants, Prices & Inventory avatar

Shopify Products Scraper: Variants, Prices & Inventory

Pricing

from $1.00 / 1,000 products

Go to Apify Store
Shopify Products Scraper: Variants, Prices & Inventory

Shopify Products Scraper: Variants, Prices & Inventory

Paste any Shopify store, collection or product URL and export every product with variants, SKUs, prices, sale prices, images, stock status and public inventory counts. CSV, Excel or JSON. No API key. $1 per 1,000 products.

Pricing

from $1.00 / 1,000 products

Rating

0.0

(0)

Developer

tingyou333 zhuang

tingyou333 zhuang

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

a day ago

Last modified

Categories

Features

Limited permissions

Share

Paste a Shopify store, collection or product URL and get every product as a spreadsheet row: title, vendor, type, tags, price and compare-at (sale) price, every variant with SKU and options, images, stock status, and (with inventory details on) barcode/GTIN and the inventory quantity wherever the store publishes it. Export to CSV, Excel or JSON. No Shopify login, app or API key needed.

Who uses it: e-commerce sellers and agencies tracking competitor prices and stock, dropshippers importing catalogs, and analysts building product datasets.

Try it in one click

Click Try for free. The form comes pre-filled with deathwishcoffee.com, 5 products, inventory details on. That run costs about half a cent and finishes in under a minute. To read a different store, replace the domain with any Shopify store, collection URL (/collections/sale) or product URL (/products/...).

{
"domains": ["deathwishcoffee.com"],
"maxProducts": 5,
"includeInventoryDetails": true
}

Set maxProducts to 0 to export the whole catalog. You can list up to 100 stores in one run.

What you get

Real rows from a test run on November 17, 2026 (default input). Prices and stock change constantly.

ProductSKUPriceIn stockInventory qtyVariants
Valhalla Java Dark Chocolate BarkLFVJBK04USD 15.00Yes1001
Yule Cat MugUMYULC26KUSD 38.00Yes1001
Nine Lives Pet BandanaUBYULEC26USD 10.00Yes1001
Gingerdead OrnamentUOGIND26USD 7.00Yes1001
Peppermint Mocha OrnamentUOPEPM26USD 7.00Yes1001

All 5 products in that run had an exact inventory count. One row = one product. Its variants list holds each size/color with its own SKU, price, availability and quantity. Use the Nested variants dataset view, or download JSON to keep the nesting.

Many stores hide quantities. You then still get prices, availability (in stock / sold out) and everything else, and inventoryQuantity is left empty rather than guessed.

Track changes every day (monitor mode)

Turn on Monitor changes and schedule the run daily. The first run saves a baseline and outputs every product once. Every later run outputs only what changed since the last run:

monitorStatusWhen
newA product appeared in the store
removedA product disappeared (only checked when the whole store or collection was read, i.e. maxProducts: 0)
changedPrice, sale price, in-stock status, inventory quantity or variants changed. changeTypes says which, and changes lists each field with before and after

Unchanged products are not output and not charged. A day with no changes costs only the small platform usage. Example input:

{
"domains": ["competitor-one.com", "competitor-two.com/collections/sale"],
"monitorChanges": true,
"maxProducts": 0,
"includeInventoryDetails": true
}

Set it to run daily: save the input as a task (Save as a new task), open Schedules → Create new, pick "Daily", and add the task. Each run's dataset then holds only that day's changes, and the Changes dataset view shows them as a table. Connect an integration (email, Slack, Google Sheets, webhook) to the task to get them delivered. Use Monitor name to keep separate watch lists, and Reset monitor baseline to start over.

Pricing

$1 per 1,000 products ($0.001 per product), plus a small Apify platform usage charge (typically well under $0.01 for a few hundred products). A product counts once no matter how many variants it has, and there is no start fee or extra fee for inventory details. 500 products cost $0.50 plus usage. Set a spending limit on the run if you want a hard cap.

Common inputs

You wantInput
A whole storedomains: ["store.com"], maxProducts: 0
One collectiondomains: ["https://store.com/collections/sale"]
One product with all variantsdomains: ["https://store.com/products/handle"]
Inventory counts, barcodes, SEO, metafieldsincludeInventoryDetails: true (about 3 extra requests per product, so slower)
A localized cataloglocale: "fr" or the store's regional domain
Daily price/stock trackingSave as a task and schedule it; compare runs on productId + variantId

API callers can also use the field names common to other Shopify scrapers (startUrls, maxResults, proxy). They are mapped automatically, and fields the Actor doesn't recognize are ignored with a warning instead of failing the run.

Good to know

  • Works on stores that expose Shopify's public product catalog, which is most of them. Password-protected stores and stores that block automated access are skipped, and the run's status message names them.
  • If one store in your list fails, the run still succeeds with the products from the other stores. The status message lists what was skipped and why. A run is marked failed only when no products at all could be collected.
  • This tool reads the stores you give it. It does not find stores for you or provide a database of Shopify merchants.
  • This is an independent tool, not affiliated with Shopify or any store it reads.

Reference

Inputs

FieldType and defaultActual behavior
domainsrequired string array; form example deathwishcoffee.com (API alias: startUrls)Up to 100 known public store domains. Accepts bare hosts and HTTP(S) URLs. Store, collection and product paths select the scope. An explicitly empty array uses deathwishcoffee.com. Duplicate targets are skipped. Overlapping URLs for the same store and locale share the product limit and are deduplicated by product ID.
maxProductsinteger, 0; form prefill 5 (API alias: maxResults)Stored-product limit per store; 0 continues to source exhaustion, subject to disclosed safety/time/budget stops.
includeInventoryDetailsboolean, false; form prefill trueReads matching product .json, Ajax .js, and HTML; merges actual public detail fields only.
proxyConfigurationobject, {"useApifyProxy":false}Apify Proxy groups/country or user-supplied proxyUrls participate in request routing. Custom URLs must use HTTP CONNECT. Direct mode remains the runtime default when this field is omitted; the form also prefills direct access; explicitly selected proxies can cost extra.
datasetIdoptional 17-character alphanumeric stringSelect an existing dataset in the resource picker or supply its ID in JSON. Verifies access, then copies each default-dataset product to it. Empty or omitted uses only the default dataset; the same ID as the default dataset is not written twice. Requires SDK execution, not the standalone local JSONL mode.
runIdoptional 17-character alphanumeric stringCopied as runId onto every row. No lookup or upstream run start. Empty means no field.
localestring, emptyExplicit locale route, for example fr or en-gb; the shop must support it. Regional store domains can be supplied directly. No translation or currency conversion.
pageSizeinteger, 250, range 1–250Request size on every page. When maxProducts is smaller, the smaller number is used.
maxPagesPerStoreinteger, 10000Emergency page ceiling. Reaching it means partial collection.
requestTimeoutSecsinteger, 25Timeout per request attempt; allowed 5–120.
maxRetriesinteger, 2Bounded retries for transient transport failures, 429 (waits 5, 15, then 30 s unless the store sends Retry-After) and selected 5xx; maximum 4. No retry on 401/403.
requestIntervalSecsnumber, 0.5Minimum delay between sequential source requests; allowed 0.2–10. No concurrent store requests.
maxRunSecondsinteger, 3300; form prefill 120Graceful collection deadline. Set below the platform run timeout so the summary can be saved.

Invalid types produce an input error. Common field names from other Shopify scrapers (startUrls, urls, maxResults, maxItems, proxy) are mapped to the fields above; other unknown fields are ignored and listed as warnings in the run log and OUTPUT. Use /collections/

Output

Standard fields include store, productId, handle, title, vendor, url, featuredImage, imageUrls, imageCount, imageAltTexts, images, currency, priceMin, priceMax, compareAtPrice, onSale, available, fullyOutOfStock, requiresShipping, weightAndUnit, variantCount, variants, options, productOptions, productType, tags, description, descriptionHtml, createdAt, publishedAt, and updatedAt.

Prices are decimal monetary values from the catalogue, or from the complete Storefront MoneyV2 set when recovering variants. priceMin and priceMax span the resulting verified variant set. compareAtPrice is the highest exposed compare-at price or null; onSale requires a compare-at price higher than that variant's actual price. Ajax integer price units never overwrite catalogue prices. Catalogue currency comes from public metadata, with a public cart fallback; a final response must match the store and locale context. A catalogue redirect to a different origin or locale triggers a fresh currency lookup. If neither confirms a code it is null. Recovery replaces the entire variant price family with MoneyV2 amounts and their consistent currencyCode, recorded as source.priceContext="storefront_default_market"; these are the API default market prices, which need not match a requested locale or customer-specific price. No personal cart is used or modified.

Variants preserve numeric IDs, SKU, option-name/value mapping, availability, shipping and taxable flags, prices, weight/grams, image metadata and timestamps. Images preserve IDs, dimensions, positions, linked variant IDs and alt text. weightAndUnit includes the first variant's explicitly exposed grams as {"grams":125,"value":125,"unit":"g"}. grams, value and unit describe the same exposed weight. During Storefront recovery, grams missing from the catalogue can be calculated from the same variant’s public weight and declared unit; that conversion is recorded in source.variantRecovery. If neither source provides a usable weight, the object is null. New variants have null lifecycle timestamps when the public recovery API does not expose them.

Detail mode can add:

  • Product: detailLevel, inventoryAccuracy, inventoryCount, sellingPlanGroups, sellingPlanCurrency, brand, seoTitle, seoDescription, metafields, and explicit source values for status, publishedScope or templateSuffix.
  • Variant: inventoryQuantity, inventoryManagement, inventoryPolicy, barcode, validated gtin, quantityRule, requiresSellingPlan, sellingPlanAllocations and metafields.

Enrichment-only fields are absent in standard mode. They also remain absent when no detail content was usable. inventoryAccuracy="exact" requires one matching public detail response to supply integer quantities for the entire resolved variant set. Quantities from separate partial responses are never combined into an exact total. Variant recovery alone does not recover private quantities. It describes source-reported values at observation time, not independently audited warehouse stock. Quantities may be zero or negative. inventoryCount is omitted when any quantity is missing; no partial sum is presented as a total. Barcode and GTIN are distinguished: only a valid numeric GTIN with a matching check digit becomes gtin.

Nonempty Ajax selling-plan groups and allocations are retained unchanged only after matching locale cart.js confirms the same currency as the product row. sellingPlanCurrency and source.sellingPlanMoney identify that context and unchanged Shopify Ajax amount format. Unverified or different-currency plans are omitted with a source diagnostic.

An enriched product with other useful details but no complete stock quantities has inventoryAccuracy="unavailable". Brand comes from identified structured Product metadata, never from an assumed vendor mapping. HTML metadata requires an exact matching final product URL and canonical or structured product identity. SEO title and description collapse runs of whitespace to one space and trim surrounding whitespace on both JSON and HTML extraction paths; the wording remains unchanged. Missing metafields, SEO or private publication data are not fabricated.

Added observedAt and source fields expose provenance, currency origin, exact quantity sources, optional HTML detail URL, requested locale and a possible variant-truncation warning. Use the Products and Nested variants dataset views to inspect these fields.

Pagination, failure and completeness

The primary route is /products.json. A 404, non-JSON response or incompatible shape can lead to /collections/all/products.json; this fallback is explicitly labelled because a merchant may curate that collection. Explicit access denials (401/403/430), password gates and identified challenges stop the current store immediately, including during variant recovery or optional detail enrichment; later handles or detail routes are not tried against that block. Existing rows remain in the dataset and the store is partial. Short pages are not assumed to mean the end: the reader requests the next page and stops on a real empty page. IDs are deduplicated within each store. Repeated pages, repeated next links, page ceilings, unavailable routes, invalid rows, published-count mismatches and runtime/budget stops are visible.

SUMMARY.status can be COMPLETED, EMPTY, PARTIAL, FAILED or UNCERTAIN; an individual store can also have LIMIT_REACHED or DUPLICATE_INPUT. fullCatalog=true is reserved for primary-route exhaustion without invalid rows or a known count mismatch. A run reaching an explicitly requested positive product limit is a successful bounded export, not a full catalogue. A collection fallback never claims full-catalogue coverage.

An uncertain default-dataset write or charge stops the whole run immediately. uncertainDefaultWrites identifies the product that may already have been persisted or charged; rowsStored then counts only acknowledged writes and rowsStoredCountIsExact=false. No blind write retry occurs. A copy-dataset failure also stops the run after preserving the acknowledged default row. Copy writes are not atomic with default writes, and an ambiguous copy may already exist: review before manually resuming.

Cloud status alone is not a data-completeness claim. A run that stored at least one product finishes as SUCCEEDED; its status message names any skipped store or stop reason (time limit, spending limit, blocked store) and SUMMARY.status stays PARTIAL or UNCERTAIN. A run that stored no products is marked FAILED. A platform hard kill may interrupt final summary persistence; choose a lower maxRunSeconds than the run timeout. Current code does not implement cross-run resume or migration checkpoint recovery.

Security and access

The optional datasetId resource picker declares READ and WRITE for the selected dataset under Apify limited permissions: metadata lookup requires read access and appending copied products requires write access. Apify expands the run token's scope for the dataset supplied in input; full-account permissions are not required. An omitted or empty datasetId triggers no external dataset access. runId is only a row label and requests no run access. A storage permission failure is a setup failure before source collection. See Apify's user-provided storage permissions.

Public GET requests and one fixed read-only tokenless Storefront GraphQL POST operation are used. The POST reads only one public product and its variants; it accepts no caller-supplied query, token, customer or admin fields. All POST redirects are rejected. The same verified IP/TLS/proxy transport is used for both methods. HTTP(S) URLs, redirect destinations and DNS answers are checked. Private, loopback, link-local, multicast, fake benchmark and transition addresses are rejected. Numeric-IP connections retain the original Host header and TLS SNI. The same policy also applies to configured proxy endpoints and destination IPs in CONNECT requests. Response bodies and redirect chains have limits. Tokens and cookies are not accepted as store input.

Custom HTTP proxies and Apify Proxy are implemented. HTTPS-scheme proxy servers and SOCKS proxies are an explicit limitation; TLS is not weakened to support them. Proxy setup errors are surfaced, and no implicit proxy purchase or automatic switching occurs. Paid proxy connectivity has only mock coverage in this delivery. Login, password pages and access denials remain boundaries. No cart-add requests, checkout automation, CAPTCHA solving, private Admin API, or authenticated storefront API are used.

Large variant sets and source limits

Shopify’s Ajax product API documents a maximum 250 variants per response. For catalogues exposing 100 or more variants (including the historical 100 boundary), or reporting a larger explicit count, this Actor verifies and recovers the product with tokenless Storefront API 2026-07 cursor pages of 100. Recovery requires matching product ID/handle and variant parents on every page, unique IDs/cursors, consistent MoneyV2 currencies, an EXACT total count and a terminal page. The hard ceiling is 25 variant pages per product, also subject to the run deadline and transport retries. A failed recovery skips the incomplete product and marks the run partial; it never stores the prefix as a complete price range or exact inventory. The tokenless query does not request quantityAvailable or private inventory. A local live check on September 26, 2026 recovered 280 variants in three pages after both JSON endpoints returned 250. Separate cloud acceptance covered six products, including one with 100 variants; it was not a cloud test of the 280-variant product. Private/draft/wholesale/password-protected inventory, location-level counts, unavailable metafields and headless catalogues without compatible public routes remain outside the accessible source. Source changes during pagination can still alter a snapshot; count matching alone cannot guarantee atomicity.

API and scheduled exports

Save your input as input.json, then start a run with your own Apify token:

curl --fail-with-body -X POST \
'https://api.apify.com/v2/acts/oQCaw1otYIwHhIYfm/runs' \
-H "Authorization: Bearer $APIFY_TOKEN" \
-H 'Content-Type: application/json' \
--data-binary @input.json

Read the returned run's default dataset for rows and its key-value store SUMMARY record for coverage. Export JSON, CSV or Excel in Apify Console. You can configure an Apify schedule for repeated snapshots; this Actor does not create schedules itself.

Use (store, productId) and variant IDs to compare snapshots. datasetId appends copies; it does not deduplicate across runs or replace earlier snapshots.

Support

Use this Actor's Issues tab for bugs. Include the run ID, a public store URL and the relevant SUMMARY error; never post your Apify token or store credentials. Availability is not an exact stock count. Private inventory and password-protected stores are outside this tool's scope.

Proxy connection compatibility

On Apify, the SDK can supply a private internal proxy gateway. Only its exact host and port from the platform configuration are accepted as a proxy connection when Apify Proxy is enabled. Store targets and user-supplied proxy URLs remain subject to public-address checks; product connections preserve pinned public IPs and verified TLS.