The Math: Where Manual Price Checking Breaks Down by SKU Count

Nobody decides to stop price-checking by hand at a specific SKU count. It just quietly stops being possible, and by the time that's obvious, coverage has already shrunk without anyone deciding it should. This is a plain arithmetic model of where that breakdown happens — every number below is a stated assumption, not an industry statistic, and the whole point is that you should redo it with your own numbers rather than take these as fact.

The Model

Assumption 1 — time per competitor check: 45 seconds. Open the competitor's site or app, find the product, read the price, record it. This is a fast, focused pace with no interruptions — treat it as a best case, not a typical one.

Assumption 2 — competitors tracked per SKU: 5. Adjust to your actual competitor set.

Assumption 3 — check time per SKU: 45 seconds × 5 competitors = 225 seconds = 3.75 minutes.

Assumption 4 — productive hours per working day: 7.5 hours = 450 minutes. This assumes someone dedicated entirely to price-checking with no other duties, which is rarely how it actually happens — in practice this task is squeezed between other work, which is the gap covered in what manual price collection really costs.

Derived throughput: 450 minutes ÷ 3.75 minutes/SKU = 120 SKUs per person per day, at full dedication and best-case pace, for a daily refresh.

What That Throughput Means by Catalog Size

Read the table plainly: this is linear. There's no efficiency gained from scale in manual checking — checking SKU number 2,000 takes exactly as long as checking SKU number 1, every time, forever. A 10,000-SKU catalog needs roughly 83 full-time people checking prices all day, every day, for a daily refresh — which is obviously never going to happen, so what happens instead is what always happens: coverage shrinks to whatever headcount is actually available, silently.

Where Your Catalog Crosses the Line

Nobody staffs a dedicated price-checking team of more than one or two people. So set a realistic headcount ceiling — say, 0.5 to 1 FTE genuinely available for this task — and the table above tells you almost immediately where a daily-refresh catalog stops being feasible: somewhere between 100 and 300 SKUs, using these assumptions, is the ceiling for one dedicated, focused person running a full daily check.

Weekly refresh moves the line, but not far enough for most catalogs. If daily freshness isn't required and a weekly check is acceptable, one person's effective capacity multiplies roughly by the number of working days available to spread the work across — call it 5. That pushes the one-person ceiling to roughly 500–1,500 SKUs for a weekly refresh, still well short of what most mid-market retailers actually carry.

Notice the tradeoff those numbers force: the only way to make manual checking cover a real catalog is to check less often — which means pricing decisions get made on data that's weeks old by the time anyone acts on it, the exact problem this model doesn't even try to quantify, because staleness cost is a decision-quality problem, not a headcount one.

Why the Real Ceiling Is Lower Than This Model Says

Every assumption above was chosen to be generous to manual checking. Real-world conditions push the ceiling down further, for reasons this model deliberately excludes to keep the arithmetic clean:

• 45 seconds per check assumes zero errors and zero re-checks. A mistyped price, a wrong SKU match, or a site that's slow to load all cost time this model doesn't count.
• Zero context-switching cost. Moving between competitor sites, tabs, and a spreadsheet has real friction that a stopwatch test in isolation won't capture.
• Zero QA or reconciliation time. The moment a second person touches the same list — which happens constantly in practice — you're paying a reconciliation cost this table assumes away entirely, and which we walked through directly in the real cost of manual price collection.
• Full, uninterrupted dedication. In practice this task competes with email, meetings, and every other demand on the same person's day.

Treat every number in this model as a ceiling, not a realistic estimate — the true breakeven point for your team is very likely lower than the table shows, not higher.

Redo This With Your Own Numbers

The model only has four inputs. Plug in your real ones:

1. Your actual average check time (time yourself on 10 real SKUs, don't guess).
2. Your actual competitor count per SKU.
3. The realistic hours per week someone can actually dedicate to this, not the theoretical maximum.
4. Your target refresh cadence.

Run the same division — (SKUs × competitors × seconds per check) ÷ (available seconds) — and you'll have a defensible, redoable number instead of a hunch about whether your catalog has outgrown manual checking. For most retailers above a few hundred SKUs tracked against more than two or three competitors, the arithmetic answers the question on its own.

What Comes After the Math

Once a catalog crosses its manual ceiling, the choice isn't between "manual" and "nothing" — it's between shrinking scope (fewer SKUs, fewer competitors, less frequent checks) or changing the collection method entirely. We've laid out the real 12-month cost of the two automated paths — building in-house versus a managed feed — in in-house vs. managed price monitoring: the real 12-month cost, which is the natural next read once this model has told you where your ceiling sits.

How ScrapeWise Fits

ScrapeWise removes the linear-scaling problem this model describes: checking SKU 10,000 doesn't cost more per-unit than checking SKU 1, because the collection is automated and scheduled rather than staffed. Catalogs of any size get the same daily-refresh cadence the table above shows is impossible to staff manually past a few hundred SKUs.

Honest limitations: this model is about raw checking capacity, not decision quality — even with unlimited checking capacity, someone still has to act on the data, and matching accuracy on messy or private-label catalogs takes real setup work regardless of who's doing the collecting. Automating the collection step doesn't automate the judgment call that comes after it.

Conclusion

Manual price checking doesn't fail because people aren't working hard enough — it fails because it's a linear-time task applied to a catalog that doesn't grow linearly with the headcount available to check it. Run the model with your own numbers and you'll know, with arithmetic instead of a guess, exactly how far your current process can stretch before it silently starts dropping coverage.

Past your manual ceiling and want a refresh cadence that doesn't scale with headcount? Book a call →