Shopify Products Scraper & API: Any Store, Prices, Stock
Pricing
from $0.70 / 1,000 product rows
Go to Apify Store
Shopify Products Scraper & API: Any Store, Prices, Stock
Any Shopify store's products as JSON: prices as numbers, variants, SKUs, stock. Monitor mode returns only price and stock changes. $1 per 1,000 rows.
Pricing
from $0.70 / 1,000 product rows
Rating
0.0
(0)
Developer
Dodo Data
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
7 days ago
Last modified
Categories
Share
Get every product of any Shopify store as clean JSON. 36 fields per product (48 per variant row), 439 products from two stores in 9 seconds: prices as numbers, sale and stock flags, every variant with its SKU, images, and the store's own currency. One row per product, or one row per variant for SKU-level price and stock monitoring.
Paste store URLs (or collection URLs). The Actor reads the public product feed every Shopify storefront serves, so it is fast, light on the store, and returns exactly what the shop shows.
What you get
Ten real rows from the run of 2026-09-17 (shortened here: descriptions to 120 characters, two variants, one image and five tags per product; the dataset carries everything):
In that run 23 of 439 products were on sale (priced below their compare-at price) and 246 were in stock.
What people use it for
- Monitor competitor prices and stock. For example, "every morning, which of my rival's SKUs changed price or sold out". Use One row per: Variant, schedule it daily, and compare on the stable
id. - Find what is on sale. For example, "all discounted products across these 50 streetwear stores, with the discount in percent". Turn on Only on sale.
- Build a catalogue or a product feed. For example, "titles, images, variants and prices from my suppliers' stores into my own database or an AI agent".
Why not build it yourself
Building this yourself: pagination, collections, variant maths, sale logic, currency per store, HTML descriptions, stores that answer differently: about 8 hours, then upkeep. This Actor: $1.00 per 1,000 rows, and when something changes we fix it within 48 hours. Every Apify account includes $5 of free usage a month, so your first 5,000 rows cost nothing.
Founding price: $1.00 per 1,000 rows for the first 100 users. It then rises to $1.50. Users who joined at the founding price keep it.
Proof
| Success rate (staging runs on Apify, 17 to 18 Sept 2026) | 100% from 4 runs, 20 requests, 0 failed attempts |
| Last verified against live stores | 2026-09-18 |
| Typical run | 439 products from 2 stores in 5 to 9 seconds |
| Issues answered within | 6 hours |
| Changes fixed within | 48 hours |
Changelog at the bottom of this page, and every fix is dated.
What we deliberately do not collect
- No personal data. This Actor reads products, not people: no store-owner contacts, no e-mails, no phone numbers, no customer reviews. E-mail addresses and phone numbers inside product descriptions are replaced with
[email removed]/[phone removed]. - Public storefront feed only. No logins, no admin API, no checkout.
- Light on the store: 250 products per request, pages of one store read one after another, at most 5 requests a second overall.
- This Actor declares limited permissions: it can only write to its own dataset.
How to run it
- Click Run. The defaults read two sample stores (Allbirds and Death Wish Coffee, about 440 products).
- Replace them with your own Store or collection URLs, for example
https://www.allbirds.com,allbirds.com, orhttps://www.allbirds.com/collections/mens. Hundreds of stores per run are fine. - Choose One row per product or variant, and narrow with Keywords, Only in stock, Only on sale. Turn on Include stock and barcodes for stock counts, barcodes and inventory policy per variant (details below). Products that do not match are never saved and never charged.
- Set Max rows to cap the run. That is also your spend cap.
- Download as JSON, CSV or Excel, or call it from the API or from an AI agent through the Apify MCP server.
Price and stock monitor: only what changed
A price monitor is this Actor on a schedule with one extra field. Give the run a Monitor name:
- every row comes back with
change_status(new,updated,unchanged),previous_price,price_change_percent(negative for a price drop) andprevious_available, so "back in stock" and "sold out" are one filter away updatedmeans the price, the crossed-out price, the availability, the stock count where it was read, or the set of variants and their prices changed. A product that gains or loses a variant counts as updated- with Only changes on, unchanged rows are left out and not billed. Measured on a real store (Death Wish Coffee, 145 products): the first run returned 145 rows, the next run returned only the rows whose price, crossed-out price, availability or stock had moved. A daily watch on a 2,000-product shop usually costs cents, not dollars
- removed products are reported too: a product or variant that was in the previous run and is gone from the feed comes back once with
change_status: "removed", its last known price and the dates it was first and last seen - works per product or per variant. In variant mode each SKU is tracked on its own price and stock; with Stock counts on, a change in
inventory_quantitycounts as a change too
A removal is only claimed when the feed was read to its end in that run, measured against the unfiltered feed, so a filter or a row cap cannot produce a false alarm, and never at all for a run the platform moved to another server mid-way. Before a product is reported removed the shop is asked about it directly, one request per candidate: the feed is paged, so a product deleted while we page shifts the window and can leave a still-live product unlisted, and that product must not be reported as gone. A removed row carries only what the monitor remembered about it: id, store, title, URL, previous_price, previous_available and the two dates. Every other field is null, because the product is no longer in the feed to read. State is kept in a key-value store on your own Apify account, one per Actor (the same name in another Dodo Data Actor tracks that Actor's sources separately) under the name you chose, one record per store and mode. Nothing is written until the run ends. The first run under a new name marks everything new; switching Stock counts on or off marks rows updated once, because the stock count joins or leaves the comparison.
Stock counts and barcodes
The catalogue feed carries prices and an in-stock flag, but not quantities or barcodes. Those live on a second public
endpoint, one request per product, which Include stock and barcodes reads for you. It adds inventory_quantity,
barcode, inventory_tracked and inventory_policy to every variant, plus total_inventory per product.
Three things we are careful about, because each of them silently corrupts a dataset:
- Shopify reports
999999for variants whose stock it does not track (digital add-ons, made-to-order). That is a placeholder, not a quantity. Those variants getinventory_quantity: nulland are left out oftotal_inventory. - A missing figure is
null, never0. Zero means sold out, which is a real signal; "this shop publishes no numbers" is not the same thing, and the two must not be mixed. - Whether a shop publishes any of this is the merchant's choice, so some stores return barcodes without quantities, or an internal code where you expected a GTIN. Quantities can also be negative when a shop has oversold.
It costs one extra request per product, so leave it off when you only need prices.
In variant mode each row is one variant: the product fields are repeated, the nested variants list is replaced by top-level variant_id, variant_title, sku, price, compare_at_price, option1 to option3 and grams, id and url point at the variant, and Only in stock / Only on sale apply to the variant itself.
Good to know: a small number of stores switch their product feed off or protect it; those are reported in the log and skipped, and you are not charged for them. A site that is not on Shopify is reported the same way.
Use it from an AI agent (MCP)
Add this Actor as a tool in Claude, Cursor, VS Code or any other MCP client through the hosted Apify MCP server:
The input is small and typed, and every field in the output is documented in the dataset schema, so an agent can call it without reading this page. The Actor is enabled for Apify's agentic payments (x402, experimental on Apify's side): an agent can pay per run without an Apify account. With a Monitor name, an agent that checks a competitor's shop every morning pays only for what changed.
Related Actors
- Career Page Jobs Scraper: jobs from Greenhouse, Lever, Ashby, Workday and eight more career-page systems
- France Travail Jobs Scraper: French public-service job offers with salary as numbers
Input reference
| Field | Default | Meaning |
|---|---|---|
startUrls | two sample stores | Store or collection URLs |
rowPer | product | product (variants nested) or variant (one row per SKU) |
includeInventory | false | Add stock, barcode and inventory policy per variant (one extra request per product) |
keywords | none | Keep products whose title, vendor, type or tags contain one of these |
onlyAvailable | false | Keep only products in stock |
onlyOnSale | false | Keep only discounted products |
monitorName | none | Turns on price and stock tracking between runs; use the same name every run |
onlyChanges | false | With a monitor name: leave out, and do not bill, unchanged rows |
includeRemoved | true | With a monitor name: report products that are gone since the previous run |
maxItems | 500 | Stop after this many rows |
maxConcurrency | 5 | Parallel requests |
useProxy | true | Use Apify proxy (recommended) |
FAQ
Does Shopify have a public API for a store's products?
Every Shopify storefront serves its own catalogue as JSON at /products.json, 250 products per page, the same data the shop renders for any visitor. This Actor reads that feed plus /meta.json for the store's currency, and turns prices into numbers and variants into rows.
How do I track a competitor's prices on Shopify? Schedule this Actor daily with a Monitor name and Only changes. Each run returns the products whose price or availability moved, with the previous price and the change in percent, plus new and removed products.
How do I get alerted when a product is back in stock?
Monitor in variant mode and filter the results on available = true and previous_available = false.
Do I need proxies, an API key or the store's permission? No key and no login: the feed is public. Some merchants switch it off or put it behind a bot check; that is reported in the log and the store is skipped, never worked around.
How fresh is the data? Every run is live. There is no database in between.
Changelog
- 2026-09-21, v0.1: price and stock monitor. A monitor name adds
change_status,previous_price,price_change_percent,previous_available,first_seen_at,last_seen_at; Only changes returns and bills only what moved. - 2026-09-17, v0.1: first release. Verified against live stores on 17 and 18 September 2026.
