Shopify product scraper: price and stock monitor avatar

Shopify product scraper: price and stock monitor

Pricing

from $0.66 / 1,000 product records

Go to Apify Store
Shopify product scraper: price and stock monitor

Shopify product scraper: price and stock monitor

Monitor public Shopify catalogs for product and variant price, availability, new-product, restock, and removal changes. Export structured catalog events for competitor tracking, dropshipping research, and price intelligence in CSV or JSON. No store login or API key.

Pricing

from $0.66 / 1,000 product records

Rating

0.0

(0)

Developer

GetAScraper

GetAScraper

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

πŸ›οΈ Shopify product scraper

πŸ”Ž Turn public Shopify catalog movement into a usable feed. Collect current public catalog data, keep each row tied to the original listing, and turn manual checking into a repeatable market signal. Work only from pages that anyone can normally view.
🧭 Focused sourcesUse ordinary public catalog or seller pages.πŸ”” Meaningful changesSeparate new, updated, restocked, and removed items.πŸ”— Source contextKeep the original listing link beside every record.πŸ“… Ready to repeatRun once for research or on a schedule for monitoring.

🎯 Turn public catalog changes into a useful signal

Monitor public Shopify catalogs for products and variants, including new items, price and availability changes, restocks, updates, and confirmed removals. Each record stays connected to the public listing so an operator, analyst, or sourcing team can verify the context before acting.

Who gets value

  • I am a ecommerce intelligence lead looking to keep a competitor catalog watchlist current without building or maintaining custom collection tools.
  • I am a catalog operations lead looking to keep current public product data without opening every store by hand.
  • I am a market researcher looking to compare availability and pricing across a defined seller or store list.

⚑ Get results in three steps

Start with a small public source to confirm the output fits your workflow. Repeat the same setup on an Apify schedule when you need ongoing catalog visibility.

STEP 1Add sourcesPaste public Shopify store links or domains or select your filters.STEP 2Choose the viewCollect a current snapshot or focus on changes.STEP 3Use the feedSend source-linked records into your existing process.

🧩 Configure your run

The first setting identifies the public sources you want to follow. The remaining settings let you balance detail, scope, and the amount of history returned.

FieldTypeRequiredDescription
storeUrlsList of linksNoPublic Shopify store links or domains to monitor.
includeVariantsYes or noNoInclude public variant identifiers, options, prices, and availability.
maxProductsPerStoreNumberNoMaximum products retained from each store.
maxPagesNumberNoMaximum catalog pages checked for each store.
outputModeChoiceNoReturn every observed product or only lifecycle, price, availability, and variant events.
stateNameTextNoName the saved comparison history for this store set.
pageSizeNumberNoProducts requested in each result page.
requestDelayMsNumberNoDelay before each public catalog request.
requestTimeoutMsNumberNoMaximum wait for one public source response.
maxRetriesNumberNoRetries for temporary availability problems.

πŸ“¦ Use the data immediately

Every result is a structured record with the original public source retained for review. Choose a full view for a current snapshot or a change-focused view for downstream actions.

FieldTypeDescription
recordTypeTextWhether the row represents a product, variant, or change.
eventText or nullNew, updated, restocked, removed, price, availability, or variant event.
titleTextPublic product title.
productIdTextSource product identifier.
handleTextPublic product handle.
productUrlLinkOriginal public product page.
productTypeText or nullPublic product type.
vendorText or nullPublic vendor label.
tagsListPublic product tags.
createdAtDate and time or nullPublic product creation time when available.
updatedAtDate and time or nullPublic product update time when available.
publishedAtDate and time or nullPublic publishing time when available.
variantsList or nullPublic variant details when selected.
variantCountNumberNumber of public variants found.
availableVariantCountNumberNumber of publicly available variants.
changedVariantsListVariants that changed since the previous complete check.
firstSeenAtDate and timeFirst time this product appeared in this history.
lastSeenAtDate and timeMost recent observation time.
closedAtDate and time or nullTime a confirmed removal was recorded.
scanCompleteYes or noWhether the store check was complete enough for lifecycle comparison.

πŸ’³ Understand your run cost

Review the current pricing shown in the Apify Store before you scale a scheduled workflow. Begin with a small public source so you can confirm the records match your criteria.

⭐ Enjoying Shopify product scraper?

After a successful run, rate the Actor based on the usefulness and clarity of the records. Your feedback helps improve the next release for teams with the same workflow.

⭐ ⭐ ⭐ ⭐ ⭐ Rate this Actor if it helped you keep a public competitor catalog current. Your feedback helps ecommerce teams find a practical public catalog workflow.
β˜…Β Β Rate this Actor on Apify

❓ Frequently asked questions

These answers cover the safest way to get a reliable first result. Start with a small public source and confirm its scope before setting up recurring monitoring.

Yes. Paste the public source described in the input form, then use the available filters to narrow the collection.

Can I use this for recurring monitoring?

Yes. Run it on an Apify schedule and choose the change-focused output when you only need records that have meaningfully changed.

How are removed products handled?

A product is only treated as removed after complete checks confirm it is no longer present. This reduces false removal events caused by incomplete source results.

Do I need a seller or store account?

No. This Actor is designed for publicly available information and does not request seller, shopper, or owner account access.

πŸ›‘οΈ Use public information responsibly

Use the records for legitimate competitor research, catalog operations, and price intelligence. Respect the source’s terms and intended use, minimize retention, and do not use the data for deceptive or harmful practices.

πŸ”— Other actors

These adjacent Actors cover public marketplace and catalog sources that teams often track alongside this one. Choose the source that matches the store or seller platform you need to follow.