1 June 2026

How to Monitor Competitor Prices on Shopify

Learn a practical workflow for monitoring Shopify competitor prices and stock without maintaining browsers, proxies, schedulers, and alerting yourself.

Ecommerce Monitoring

Shopify stores are common targets for competitor price monitoring because they are structured, fast-moving, and often similar enough that teams assume they will be easy to track.

Sometimes they are. Sometimes they are not.

A simple Shopify product page might expose the price in the first HTML response. Another store might render price after JavaScript, change it by selected variant, hide it behind a region selector, or show a sale price only after a client-side app finishes loading.

The job is not just "scrape a price". The job is to build a monitor that keeps returning the right price and stock value next week.

Start With a Small Product Set

Do not begin with a thousand URLs. Start with 10 to 20 representative products:

  • A simple product
  • A product with variants
  • A sale product
  • An out-of-stock product
  • A product with region-specific pricing
  • A product from a competitor that has blocked simple scrapers before

This gives you a useful test set without creating too much traffic or debugging noise.

If you are new to the workflow, start with the ScrAPI ecommerce tutorial. It uses ScrAPI-owned training pages, lets you run requests inline, and turns the final result into a scheduled monitor.

Find the Price and Stock Selectors

A monitor needs selectors that return stable values. For Shopify pages, you might see useful elements around:

  • Product title
  • Current price
  • Compare-at price
  • Sale badge
  • Variant availability
  • Add-to-cart button state
  • JSON-LD product data

Do not choose the longest selector copied from DevTools. Prefer the smallest stable selector that points at the value you need.

In ScrAPI, use the Playground to test:

{
  "url": "https://example-store.com/products/example-product",
  "useBrowser": true,
  "responseSelector": ".price-item--sale"
}

If the selector returns only the expected price text, you have a good candidate for the monitor.

Decide Whether Browser Rendering Is Required

For simple stores, raw HTML may be enough. For stores with apps, variant pricing, deferred scripts, or region-specific content, browser rendering is safer.

Use browser rendering when:

  • The price is missing from raw HTML
  • The page depends on JavaScript apps
  • Variant selection changes the price
  • Cookie or region state affects the visible price
  • You need to wait for a dynamic stock component

Avoid browser rendering when raw HTML is reliable. It is faster and cheaper.

Track Stock Separately From Price

Price and stock are different signals. Treat them separately.

A stock selector might read:

  • In stock
  • Sold out
  • Only 3 left
  • Pre-order
  • Add to cart
  • Unavailable

Do not assume a missing price means out of stock. Do not assume an enabled button means the product can be shipped to every region. Store the text you observed and convert it into a simple in-stock state for alerts.

ScrAPI's ecommerce monitor stores both the raw observed stock text and the parsed in-stock value.

Create the Monitor

Once the selectors work, create a hosted monitor with:

  • Product URL
  • Price selector
  • Stock selector
  • Currency
  • Proxy type
  • Proxy country if needed
  • Check frequency
  • Alert email

Start daily. Move to 4x daily only when price movement matters enough to justify the extra cost.

The first run should establish a baseline. Later runs should alert only when price or stock changes.

Export and Review History

Monitoring is easier when you can see patterns. CSV history helps answer questions like:

  • Did a selector break on one product or many?
  • Are failures clustered around one competitor?
  • Did a region-specific route start returning different content?
  • Are browser runs slower but more reliable?
  • Are residential proxies worth the extra cost for this target?

ScrAPI's hosted monitor stores run history and exposes CSV export so you can review the data outside the dashboard.

Test Safely First

Before testing real competitor stores, use explicit training sites:

These targets are useful for learning selectors, monitor creation, CSV export, and alert behaviour. They are not a substitute for testing your actual target set, but they keep the first learning loop clean.

A Practical Shopify Workflow

  1. Pick 10 to 20 representative product URLs.
  2. Test each page in the Playground.
  3. Use raw HTML first, then browser rendering only when needed.
  4. Confirm price and stock selectors return useful text.
  5. Create daily monitors.
  6. Let the first run establish baselines.
  7. Review CSV history before increasing frequency.
  8. Move difficult or region-specific pages to residential proxies.

This is deliberately boring. Boring is good for monitoring. The fewer moving parts you need per product URL, the easier it is to keep the system reliable.

Where ScrAPI Fits

ScrAPI gives you the lower-level scraping API, hosted ecommerce monitors, MCP access, and a training path in one place. That means you can start with an interactive scrape, copy working code if you need it, and turn the same tested selectors into a scheduled price and stock monitor.

The result is less scraper maintenance and more time using the data.