E-commerce Assortment Change Monitor

Convert recurring catalog snapshots into stable, event-level assortment intelligence. Use products pasted directly or read any compatible Apify dataset—such as the output of Product Data Extractor, a marketplace scraper, or an internal feed Actor.

Event taxonomy

• PRODUCT_ADDED / PRODUCT_REMOVED
• PRICE_INCREASED / PRICE_DECREASED
• OUT_OF_STOCK / BACK_IN_STOCK
• DISCOUNT_STARTED / DISCOUNT_ENDED
• VARIANT_ADDED / VARIANT_REMOVED

The first complete run creates a persistent baseline for monitorKey. Reusing the same key on a schedule compares the new catalog with that baseline, emits events, and saves the new state. If a charge limit interrupts the catalog, the Actor does not overwrite the last complete baseline.

Quick start

{
  "monitorKey": "demo-store-us",
  "products": [
    { "sku": "SKU-100", "name": "Trail Shoe", "price": 89.99, "listPrice": 109.99, "inStock": true, "variants": ["black-42"] }
  ]
}

On the next run, change the price, stock, variants, or product set while keeping the same monitorKey.

Pricing

The intended pricing is pay per product compared, with platform usage included. Change events, baseline rows, and the run summary are included. Current exact prices appear on the Store page. A full, unmodified baseline is preserved when the run's maximum charge is too low.

Limitations

This Actor compares structured product records; it does not scrape storefronts itself. Product identity is only as stable as the supplied monitorKey, ID, SKU, GTIN, URL, or name. Renamed products without a stable ID can look removed and re-added. Currency conversion is not performed. Availability and variant shapes vary by upstream Actor and should be checked during the first run.

No private/authenticated scraping, CAPTCHA bypass, personal-data profiling, outreach, or credentials are used.