Shopify Catalogue Scraper

Guide

Competitor price monitoring for Shopify stores, with just a spreadsheet

7 min read, published 16 November 2026

Knowing how competitors price, and how often they discount, is some of the most useful information a retailer can have. When those competitors run on Shopify, you can collect it from their public catalogues with nothing more than a spreadsheet. This guide sets out a simple, repeatable workflow.

1. Decide what you are comparing

Price monitoring only works when like is compared with like. Before collecting anything, write down:

  • The stores. Three to ten direct competitors is plenty to start with.
  • The categories. If a store sells far more than you do, scrape only the relevant collection, such as store.com/collections/running-shoes.
  • The question. “Where do we sit in the price range?”, “How deep are their sales?” and “What did they launch this month?” need different reports.

2. Take a snapshot

Run each store or collection through the scraper and download the CSV. Add a column called snapshot_date with today’s date, and a store column if you are combining several stores in one sheet. Paste each snapshot under the previous one so you build a single long table over time.

Weekly snapshots suit most categories. Fashion and electronics, where prices move during sale events, may justify more frequent checks around those periods.

3. Compare prices on a fair basis

For a quick view of where each store sits, build a pivot table:

  • Rows: store; optionally product_type beneath it.
  • Values: MEDIAN (or AVERAGE) of price, MIN and MAX of price.
  • Filter: available = TRUE, so sold-out items do not skew the picture.

Medians are more honest than averages here: a handful of premium items can drag an average a long way. If stores sell in different currencies, convert first.

For product-level matching, such as the same branded item sold by several retailers, match on a normalised title or on the vendor plus model name. SKUs are rarely shared between stores, because each merchant invents its own.

4. Measure discounting

The discount_pct column is filled only when a variant’s compare-at price is genuinely above its price, so it is a clean signal of markdowns. Useful measures per store:

  • Share of variants on sale: count of rows with a discount_pct divided by all rows.
  • Typical depth: the median discount_pct of discounted rows.
  • Deepest cuts: sort by discount_pct descending to see which lines are being cleared.

Tracked week by week, these show you when a competitor’s promotions start and how aggressive they are.

5. Spot changes between snapshots

Use variant_id as the key to match a variant across two snapshots, because it never changes. In Google Sheets or Excel, an XLOOKUP (or VLOOKUP) of each variant ID from this week into last week returns the old price, and a simple subtraction shows the change. Then:

  • IDs present this week but not last week are new launches.
  • IDs that have disappeared were discontinued or unpublished.
  • Variants whose available went from TRUE to FALSE sold out, which is often the best demand signal public data offers.

6. Keep it in proportion

Public catalogue data shows list prices, not what shoppers actually paid after discount codes, bundles or loyalty rewards, and it says nothing about sales volumes. Treat it as a strong guide to positioning, not as a full picture of a competitor’s business.

It is also worth being a considerate visitor: scrape at a sensible frequency, and use the data for analysis rather than copying descriptions or photographs. Our guide to using catalogue data responsibly covers this in more detail.