How to Track a Competitor's New Product Launches on Shopify

Every public Shopify store publishes new product launches in a structured JSON feed with an exact timestamp for when each product went live. With a 5 to 15 minute polling interval, you can detect a competitor's new product within one check cycle of it appearing. No scraping, no special access, no manual checking. The published_at field is the entire mechanism - and almost nobody uses it for launch detection.

The signal hiding in products.json

Append /products.jsonto any Shopify domain and you get the store's full product catalog as structured data. Most people who know about this endpoint use it for price monitoring. Few use it for launch detection, which is the more valuable signal.

Every product object in the feed contains a published_at field: the ISO timestamp when the merchant first published that product. Compare two snapshots of the same feed taken at different times and any product with a published_at timestamp newer than your last snapshot is a new launch.

What you miss by finding out late

Catching a competitor launch two weeks after it goes live means you are responding to momentum, not to a launch. By then they have reviews, ranking signals, and conversion data. Catching it within 15 minutes means you are evaluating a fresh product with no moat yet - and you can decide whether to respond before any of that compounds.

A competitor launches a new product line. Within 48 hours, customers who searched for your top SKU are now landing on their page instead. You find out two weeks later when your conversion rate report looks wrong. By then the competitor has reviews, rankings, and momentum you cannot reverse.

Three launch patterns worth distinguishing

Not all product launches carry the same urgency. Three patterns repeat across Shopify competitors: stealth (product live but not promoted, meaning the brand is testing), collection-first (category expansion without homepage commitment), and hero (full marketing launch with budget behind it). Knowing which type you are looking at tells you exactly how quickly you need to respond.

The stealth launch

A product appears in products.json but is not featured on the homepage, not linked from the main navigation, and not in any promoted collection. The product exists and is purchasable but the merchant has not announced it. This is common for:

• Testing a new product with organic traffic before committing to a campaign
• B-stock or clearance items added without fanfare
• Soft launches targeting a specific customer segment via direct link

The stealth launch tells you more about competitor testing behavior than about immediate market threat. Watch whether the product gets promoted in the next 1 to 2 weeks. If it does, it validated in the soft launch.

The collection-first launch

A new product appears simultaneously in products.json and in a specific collection, but the homepage stays unchanged. The competitor is signaling category intent without leading with it. This pattern often appears when a brand is expanding into an adjacent category without wanting to dilute their main brand message.

For your purposes: check which collection they added it to. A coffee brand adding a product to a "Brewing Equipment" collection they did not have before is a larger strategic signal than adding a new bag of beans to an existing roast collection.

The hero launch

A new product appears in products.json and the homepage hero image changes on the same day or within 24 hours. This is a full launch with marketing commitment. The competitor is betting margin on this product. It gets their best placement, their email list, and their ad budget.

Hero launches warrant immediate action. Evaluate the product, its price point, and whether it overlaps with your catalog. If it does, you have a narrow window before the SEO and review velocity compounds.

What a new product actually reveals

A product launch carries positioning data. The metadata in products.json tells you how the competitor thought about it.

A product tagged subscription or bundle tells you the competitor is testing a retention or AOV play, not just adding inventory. A product with six size variants and a compare_at_price on all of them launched at a promotional price, meaning they expect to compete on price at least initially.

The product title and handle also tell you about their SEO intent. A product titled "Dark Roast Coffee Beans 1kg" is going after search volume. A product titled "The Midnight Blend" is building brand equity. Both are legitimate strategies. Knowing which one your competitor is pursuing tells you whether you need to respond in search or in brand.

Setting up launch detection on Beaconmon

Beaconmon checks the full products.json feed for every Shopify competitor you add. New product detection is automatic. You do not configure a separate monitor for launches.

1. Add a competitor monitor. Paste the competitor's Shopify domain. Beaconmon auto-detects the platform and attaches to the products.json feed.
2. Set check frequency. For primary competitors in fast-moving categories, 5 minutes is appropriate. For secondary competitors or stable catalogs, 15 minutes is enough.
3. Enable new product alerts. In the monitor settings, toggle "New product launch" under alert types. You will receive an alert with the product name, price, variants, and tags the moment a new published_at timestamp is detected.
4. Route to Slack. New product alerts are time-sensitive. Route them to a dedicated #competitor-intel Slack channel so your team sees them immediately, not buried in email.
5. Review the Intelligence Digest each morning for a summary of all catalog changes across your competitor set, including new launches from the previous 24 hours.

What to do in the hour after a launch alert fires

The alert is information, not an instruction to react. Most new product launches by competitors do not require an immediate response. Run through this checklist before deciding what to do.

• Does it overlap with my catalog? If the competitor launched a product you also sell, evaluate the pricing. If it does not overlap, file it as market intelligence and watch whether it gets traction.
• What collection did it land in? A new collection signals a category expansion. A product added to an existing collection signals catalog depth. Category expansions warrant more attention.
• What is the launch price?Check compare_at_price. If it is set, the competitor is using a promotional price to acquire early buyers. The "real" price is the compare_at figure. Do not match the promotional price; wait to see what price they hold after the launch window.
• Is this a stealth or hero launch? Check their homepage. If the hero has not changed, you have time. If it has, start evaluating your response.

For launches that do require a strategic response, the ignore, match, counter, leapfrog framework applies as well to product launches as it does to price drops. The question is the same: does this move require a response, and if so, what kind?

Watching the full catalog over time

Individual alerts surface events. Catalog patterns reveal strategy.

A competitor who adds three products in the same subcategory over six weeks is building a category strategy, not filling inventory gaps. A competitor who launches and then quietly removes products after 60 days is testing and pruning. A competitor who launches with six size variants and then drops to two over time is rationalizing a catalog that got too wide.

Beaconmon's competitor catalog history shows you the full lifecycle: when products were added, when prices changed, and when products were removed. Most monitoring tools show you the current state. Beaconmon shows you the arc.