Data9 min readOct 11, 2026• By Amit Singh

Building a Marketplace Price Tracker for Amazon, Flipkart, Myntra & Nykaa (What Actually Works in 2026)

A brand with 1,800+ running listings across five marketplaces had no idea which ones were selling below its own base price. We built a twice-daily tracker that now checks every listing — here's the method, the traps, and the number that surprised everyone.

Ask any multi-marketplace brand in India what their product costs on Flipkart right now and you'll get a confident answer — and it will often be wrong. Marketplaces run their own discounts, sellers' price rules drift, and a listing that was ₹699 last week is ₹449 today because a coupon stacked on top of a sale event. For an eyewear and accessories brand we work with, selling on Amazon, Flipkart, Myntra, Nykaa and Nykaa Fashion, nobody could say how many of their listings were live at a price below the brand's own base price. So we built a tracker that answers that question twice a day.

Step 1: start from the brand's own list, not from search

Our first version searched each marketplace for the brand name and recorded whatever came back. It looked complete — around a thousand listings — until we compared it with the client's own pricing sheets. Search was covering only about a third of the SKUs the brand marked as 'Running'. Two reasons: the brand sells under three names (two sub-brands never showed up when searching the main brand), and marketplace search for broad terms quietly drops whole categories. The fix was to treat the brand's own sheets — one per marketplace, with the panel ID of every listing — as the source of truth.

Step 2: search first, then fetch every missing listing by ID

The final method does both. It searches each marketplace for all three brand names and keeps every listing it finds (which also catches listings missing from the client's sheet). Then, for every 'Running' listing the search didn't find, it fetches that product page directly by its panel ID — ASIN on Amazon, FSN on Flipkart, style ID on Myntra, product ID on Nykaa. Coverage of running listings went from about 35% to over 90% overnight, with roughly 2,400 listings priced in a single run.

Step 3: don't trust the first rupee on the page

Product pages are full of other products' prices — ad carousels, 'similar items', bank offers. On some marketplaces the first ₹ figure in the page text belongs to an advertisement. We read the price from the page's own structured data or the specific price element, never from the first number we can find, and we check the result against the MRP and discount before keeping it.

Step 4: tell a blocked scraper from a dead listing

When fifty listings in a row return nothing, is the marketplace blocking you, or are those listings simply gone? Our first rule — stop after several misses in a row — was abandoning hundreds of good listings, because dead listings come in clusters (a whole discontinued collection sits next to each other in the client's sheet). The fix is a canary: after a run of misses, re-fetch a listing that priced fine earlier in the same run. If the canary still works, the misses are genuinely not live and the run carries on; only if the canary fails too is it treated as a block. That one change recovered more than 150 listings in the next run — and produced a clean list of 'Running in your sheet, but not live on the marketplace' for the brand to check.

Step 5: compare against what the brand expects

The most useful output isn't the price list — it's the exceptions. Every run writes a 'Below Base Price' tab: every listing whose live price is under the brand's own base price, biggest gap first, with a direct link. The first full run found several hundred listings below base — some 40–65% under. That raised the right business question immediately: is 'base price' the price the customer pays, or the seller's price before marketplace-funded discounts? The tracker didn't answer that, but it made sure someone asked it.

Step 6: make the dashboard formulas, not a picture

The script only appends raw rows to a Google Sheet. The dashboard on top — summary per marketplace, the same SKU across marketplaces sorted by price variance, and the price changes since the last run — is built entirely from live sheet formulas. The team can sort, filter or change it without touching code, and nothing breaks when a new marketplace column appears.

What it runs on

A small Linux server, twice a day, using a real Chrome browser where a marketplace insists on one and plain HTTP requests everywhere else. Each run emails a summary: listings per marketplace, coverage of running SKUs, the biggest price changes and the below-base count. One marketplace (a quick-commerce app) blocks data-centre traffic entirely — we'd rather report that honestly than pretend it's covered.

If you're thinking about price tracking for your own brand

start from your own listing IDs, report coverage as a number, and spend your effort on the exceptions rather than the full list. At HowAutomate we build this kind of marketplace monitoring alongside order automation for Indian sellers — if you'd like to know how many of your listings are live below your price today, we're happy to scope it.

Want this done for your business? See how we implement it end-to-end.

E-Commerce Automation

Frequently Asked Questions

How do you track your own product prices on Amazon, Flipkart and Myntra?

Start from your own listing IDs (ASIN, FSN, Myntra style ID, Nykaa product ID), search each marketplace for your brand names, then fetch every listing the search missed directly by ID. Record the live price from the page's structured data, not the first price on the page, and report coverage of your running listings as a number.

Why does brand search miss so many listings?

Marketplace search drops categories for broad queries, and sub-brands don't appear when you search the main brand. In our case search alone covered only about a third of the brand's running SKUs; adding by-ID fetches took coverage above 90%.

How often should marketplace prices be checked?

Twice a day catches most changes from sale events and coupons for a typical brand. Higher frequency is possible but increases the load on the marketplaces and the chance of being blocked, so it should be justified by how quickly you can act on the data.

What is a 'below base price' alert?

A list of every listing whose live marketplace price is lower than the brand's own base price, sorted by the size of the gap. It turns thousands of prices into a short list of listings someone should check today.

Amit Singh

Founder, HowAutomate — Data Engineering, AI Automation & Cloud Infrastructure

Amit has 6+ years of experience building data pipelines, AI agents, and automation systems for businesses across India and globally. He founded HowAutomate to make enterprise-grade automation accessible to growing businesses.

Get Weekly Automation Tips

Real scripts, workflows, and AI tips — straight to your inbox.

Want us to implement this for you?

Book a free 30-minute discovery call and we'll map out exactly how to apply this to your business.

Book a Free Call Send an Inquiry

Automation

Automating Amazon Vendor Central Direct Fulfillment: Invoices, Labels, Handover & Ship Confirmation