
Compare-at price monitoring on Shopify competitor catalogs
List price alone hides promotions. Track compare-at and variant-level moves, read Shopify's price fields correctly, and tie catalog deltas to Search Console demand.
Shopify merchants use compare-at price to signal discounts without changing product handles. Merchandising reviews that only snapshot price miss half the story—and Search Console will not tell you a competitor shifted compare-at on a bundle you share shelf space with.
How Shopify exposes price on the storefront
On live product pages, Shopify themes typically render:
- Price — current selling price (what checkout uses).
- Compare-at price — reference “was” price when set on the variant.
The Product variant object documents price and compare_at_price in Liquid; public JSON endpoints used for catalog monitoring should capture both when present.
List price-only monitors will miss:
- A competitor raising compare-at to make the same selling price look like a deeper deal.
- Promo weeks where selling price drops but compare-at stays high (or vice versa).
- Variant splits where only one size went on sale.
What to watch each month
| Signal | Why it matters |
|---|---|
| Compare-at increases with flat selling price | Perceived discount depth changed without a “price cut” headline |
| Selling price drop without compare-at change | True undercut vs cosmetic strikethrough |
| New variants (size/color bundles) | Apples-to-oranges comparisons if your roster maps SKUs loosely |
| Category-wide moves | Pillar repricing after launch—often precedes ad spend shifts |
Document which SKUs map 1:1 vs “directional comps” in your internal roster notes. See competitor roster for Shopify catalog tracking.
Tooling expectations
Your monitor should read live catalog JSON from storefronts you choose—not scraped marketplaces you do not compete with in checkout.
Minimum bar:
- Hand-picked competitor domains (3–5 per category is enough for monthly review).
- Monthly sync aligned with SEO reporting month.
- Export with prior-period delta for finance audit trails.
- Filters by competitor, category, or comparator pillar.
Alerts between syncs help when a hero SKU moves mid-cycle; avoid alert fatigue on long-tail variants nobody sells.
Reconcile catalog moves with organic demand
In the same sitting as catalog review, open Search Console filtered to the collection that maps to the category:
- Impressions up, clicks flat → SERP/CTR story may dominate.
- Clicks up, conversion down on PDP → pricing/merchandising story strengthens.
- Both flat while competitor cut price → margin risk without demand lift—prioritize response, not new blog posts.
GA4 and Search Console together explains how to compare direction without forcing click/session equality.
Compliance and ethics (practical, not legal advice)
- Monitor public storefront prices only—no logins, no cart abuse.
- Do not republish competitor prices on your site without permission.
- Use data for internal merchandising and positioning—not automated undercutting rules without human review.
DIY spreadsheet vs catalog tracker
Spreadsheets work for three competitors and ten SKUs. They break when:
- URLs change after theme migrations,
- Variant IDs multiply,
- Multiple teammates export different dates.
Competitive Product Tracker tracks published URLs with filters and deltas, exportable for leadership. Pair it with Search Console trends in Intelligence Hub to see whether a promo week matched organic demand.
Further reading
Ready to put this into practice?
Blue Carrot combines monthly SEO reporting with optional Shopify competitor catalog pricing in one workspace.





