Shopify New Arrivals Scraper

Watch one or more Shopify stores for new arrivals and get back every product created in the days you choose as clean rows: titles, prices, variants, availability and images. Built for anyone who tracks launches: trend forecasters, buyers watching competitor drops, affiliates catching new products early, and analysts measuring launch cadence.

What you can do with it

• Catch new drops — paste allbirds.com with a 7-day window and get everything the store created this week.
• Track launch cadence — schedule a weekly run and count how many products each competitor launches.
• Price new launches at birth — launch prices plus compare-at discounts from day one.
• Feed a trend radar — titles, tags, types and images of fresh products across stores in one dataset.
• Tune the window — from the last day to the last year, per run.

What you get

One row per new arrival. Abridged sample of a single record:

{
  "storeDomain": "allbirds.com",
  "productId": "7392464955000",
  "handle": "womens-glider-sage",
  "url": "https://allbirds.com/products/womens-glider-sage",
  "title": "Women's Glider - Sage",
  "vendor": "Allbirds",
  "productType": "Shoes",
  "currency": "USD",
  "price": { "amount": 135, "currency": "USD" },
  "compareAtPrice": null,
  "variantsCount": 8,
  "availableCount": 8,
  "createdAt": "2026-09-05T10:00:00-07:00",
  "publishedAt": "2026-09-06T09:00:00-07:00",
  "imageUrl": "https://cdn.shopify.com/s/files/1/0034/example.webp?v=1784902793"
}

Input reference

Setting	Type	Default	What it does
Store domains	list of text	—	Shopify store domains to watch, e.g. allbirds.com. One batch of new-arrival rows is collected per store. Required.
Days back	whole number	30	Only products created within the last N days are collected. The catalog reads newest-first, so small windows finish fast. Maximum 365.
Max products	whole number	500	Maximum new arrivals to collect per store. The actor stops when this number is reached or the window runs out. Maximum 25,000.
Currency	text	empty	Three-letter currency code for prices, e.g. USD. Leave empty to use each store's own currency.

Output fields

Field	Type	Description
storeDomain	text	Store the product was read from.
productId	text	Stable product ID.
handle	text	URL slug of the product page.
url	text	Direct link to the product page.
title	text	Product name.
vendor	text	Brand or supplier when shown.
productType	text	Store's own product grouping when shown.
tags	list of text	Merchandising tags when shown.
status	text	Publication status when shown.
publishedAt	text	When the product went live on the storefront.
createdAt	text	When the product record was created — the new-arrival date.
updatedAt	text	Last edit timestamp.
currency	text	Currency code all price pairs in the row use.
price	price pair	Lowest variant price as { amount, currency }.
compareAtPrice	price pair	Strike-through price when on sale, otherwise empty.
minPrice	price pair	Lowest variant price.
maxPrice	price pair	Highest variant price.
variantsCount	number	How many variants the product has.
availableCount	number	How many variants are currently in stock.
options	list	Variant axes such as Size and Color with their values.
description	text	Plain-text product description when shown.
imageUrl	text	Main product image.
imageUrls	list of text	Every product image.
variants	list	Per-variant rows: ID, title, SKU, price pair, stock flag, options, weight and image.

Pricing

You pay per new-arrival row, with no monthly minimum.

What you are charged for	Price
New-arrival row — one row added to your dataset	$1.5 per 1,000

Limits & what this actor cannot do

• Each store walk covers up to 25,000 products; the window filter then keeps only products created in your window.
• Records are a snapshot at the moment of collection; prices, discounts and stock flags keep changing afterwards.
• Fields a store does not show come back empty rather than guessed — a product with no listed vendor has no vendor in its row.
• Stock is reported as a simple in/out flag per variant; exact quantities are not published by stores.
• Non-store domains and password-protected stores are skipped, not charged.
• Speed depends on the size of the job and on each store's own response times; no fixed throughput is promised.
• The source site's terms govern automated access. You are responsible for using the data lawfully and in line with the source site's terms, and for handling any personal data in line with applicable privacy law.

FAQ

Do I need a store account? No. The actor reads only what stores show publicly in their catalogs.

Does it need my login or password? No. There is nothing to connect and nothing to configure — paste store domains, pick a window, and press start.

How is "new" defined? A product counts when its creation date falls inside your window — e.g. the last 30 days. The run summary also reports how many catalog rows were scanned.

How many arrivals can I collect per run? Up to 25,000 per store in one run.

Can I schedule it? Yes. Schedule it daily or weekly from the Apify console — a 7-day window on a weekly schedule gives you every launch with no gaps and no duplicates.

Is the data complete? It is complete for everything the store shows openly in its catalog. Where a store omits a field, the actor leaves it empty rather than guessing.