# Bots Scraping Prices and Inventory: How to Spot the Pattern

Source: https://bottrafficindex.com/blog/2026-10-27-bots-scraping-prices-inventory-patterns.html

October 27, 2026

*Price scraping bots leave a distinctive trail through product pages, variants, and inventory endpoints. How to recognise scraping in your logs and respond proportionately.*

## Scraping looks different from shopping

A shopper browses unevenly: a few products, a pause, a size check, a cart. A scraper moves like a catalogue being copied, hitting product after product in a steady rhythm, often in catalogue order, requesting every variant and returning on a fixed cycle to catch price changes. In logs, look for complete category coverage, no images or assets loaded by older style scrapers, and repeat visits timed to your price update schedule. One fast visitor is a curiosity; the same full sweep daily is a program.

Start with a short written checklist for this specific case and work it in the same order every time. Consistency is what makes results comparable from one week to the next, and it stops the common pattern where a fix is applied to the page someone complained about while the same pattern survives on nine similar pages nearby.

## The endpoints give them away

Price and stock data often lives in predictable product JSON or variant endpoints, and scrapers go straight there, skipping the pages humans read. A high ratio of data endpoint hits to page views, from a narrow set of addresses, is a strong signal. So is systematic variant enumeration, where every size and colour combination is requested including ones the interface hides. Record which endpoints are hit and in what order; that sequence identifies the tool better than any single request.

Document what you found with a date, a screenshot or a saved copy, and the exact page where it appeared. That record turns a vague impression into work another person can pick up, and it gives you a baseline when you recheck after a fix, a redesign, or a tool update changes the setup again.

Related reading that pairs well with this guide: [Bot Traffic Index](https://bottrafficindex.com/index.md), [Answers](https://bottrafficindex.com/answers/index.md), and [Glossary](https://bottrafficindex.com/glossary/index.md).

## Decide who actually harms you

Not all scraping is equal. A search engine indexing prices is distribution. A competitor repricing against you hourly, a reseller hunting stock mistakes, or a scalper watching limited inventory is a business problem. Rank the response by harm: rate limiting and caching for the merely wasteful, challenges and access rules for the harmful, and legal routes for commercial scale copying of your content. Blocking every automated visitor usually breaks the legitimate services your store also depends on.

Bring the people who own the content into the fix early. Most of these problems are created by ordinary publishing, merchandising, or care habits rather than by a single technical fault, so a fix that only touches code or only swaps one product tends to fade. A shared short rule, written where the work happens, lasts longer.

## Respond in layers and watch the effect

Start with caching and rate limits on data endpoints, require normal request patterns for inventory checks, and protect limited release inventory with a queue or account rules rather than relying on secrecy. After each change, watch whether the sweep pattern adapts, slows, or moves addresses, and log the change with dates. Scraping is an ongoing measurement problem, which is why an index of patterns over time beats a single dramatic block that the next tool version walks around.

Recheck on a rhythm that matches how fast the underlying thing changes, and keep the check short enough that it actually happens. A brief review done monthly beats a perfect audit planned once a year and never run. When the recheck passes twice in a row, note that too, because knowing what is stable is part of the picture.

## Frequently asked questions

### What is the most important thing to understand about price and inventory scraping bots?

The key point is simple. Price scraping bots leave a distinctive trail through product pages, variants, and inventory endpoints. How to recognise scraping in your logs and respond proportionately. Most problems come from small details being skipped when the work is rushed, so a calm check of the basics usually finds the issue faster than a complicated new tool or a full replacement of what you already have.

### How do you check price and inventory scraping bots properly?

Work through it step by step in the order a real user or shopper meets it, using the same device, settings, or routine they would use. Note each failure where it happens, fix the pattern at its source rather than patching one example, and then repeat the same check to confirm the fix held.

### What is a common mistake people make here?

The common mistake is treating the visible symptom and stopping there. People fix one page, one product, or one bad day and assume the pattern is gone. It usually is not, because the template, habit, or setting that produced it is still in place. Checking two or three neighbouring examples reveals whether you fixed a case or a cause.

### How often should you revisit price and inventory scraping bots?

Revisit it whenever the underlying setup changes and on a regular short cycle in between. Templates, apps, products, and skin itself all change over time, so a result that was true last season may not be true now. A dated note from the last check makes the next one faster and more honest.