Your Prices Are Being Scraped: What Resellers Do With Your Listing Data

The feed that undercuts you by a dollar

Competitive price monitoring is the most common use case for ecommerce scraping, and the data shape is simple: SKU, competitor, price, stock status, timestamp. A brand or marketplace seller tracks the same SKU across competitor sites and marketplaces multiple times a day, and the operational bar is high: hourly or sub-hourly frequency, near complete coverage, and 5 to 20 competitor sites at once. That is the machine pointed at your listings right now. It does not need to be sophisticated. It needs to be persistent.

The tell is timing. Your price moves on Tuesday morning, and by Tuesday afternoon a reseller you have never heard of is a dollar under you on the same ASIN. That is not a coincidence and it is not a human watching your page. It is a monitor that caught the change within the hour and repriced against it. Bots already scrape sold listings to price counterfeit goods; the same pipeline aims at legitimate resellers who want your margin, not your brand.

MAP is a contract, not a setting

Minimum Advertised Price only works if you enforce it, and enforcement is a scanning job. Brands check every authorized reseller and every marketplace listing for their SKUs several times a day and flag any advertised price below the floor. The established vendors in this space are Profitero, Stackline, CommerceIQ, NielsenIQ, and DataWeave, and they exist because the work is too repetitive for a human and too constant for a spreadsheet. A MAP violation caught on day one costs a warning. The same violation caught in week three, after the reseller has trained the Buy Box to expect the lower price, costs a month of margin.

The part sellers get wrong is treating MAP as a listing setting. It is a clause in a distribution agreement, and it only binds the resellers who signed it. An unauthorized seller who bought your product through a distributor in another country never agreed to your floor, which is why the reseller bot supply chain is hard to shut down with policy alone. You can report the listing, you can cut off the distributor who leaked the stock, but you cannot MAP a seller who never signed.

What the scrape tells them that your dashboard does not

Price is only the first field. Stock monitoring is the second, and it is the one that pays. When your listing goes out of stock, a scraper sees it within the hour, and the resellers who hold inventory raise their price the same day. When you come back in stock, they drop back under you. Your own dashboard shows units sold. Their feed shows the gap between your stock and theirs, and they price the gap.

Review velocity is the third field, and it is the one sellers ignore until it hurts. A listing gaining reviews fast looks like demand to a repricing bot, so it holds a higher price and buys more stock. A listing whose reviews stall gets discounted. The bots are not reading your reviews. They are counting them, and the count moves their price.

The three tells in your own listings

First, a price change on your side is matched within hours by a seller you do not recognize. Second, a new seller appears at fifty cents or a dollar under you, not ten dollars under, because the goal is to win the Buy Box, not to start a price war. Third, your stock status flips and the reseller price moves the same day. One of these is noise. Two at once is a feed pointed at you.

The response is not a better blocklist. Amazon, Walmart, and eBay run multi-layer anti-bot systems with CDN, WAF, application, and behavioral layers, and a scraping operation that survives them will survive yours. The response is watching your own position the way they do: a daily check of who holds the Buy Box on your top SKUs, a MAP report that actually gets read, and a distributor conversation the first time a leak shows up instead of the fifth. Price matching guarantees get abused the same way, and the fix is the same: know your price position before the feed does.