HomeServicesPortfolioAboutContactBlogCareers
Book a call
Retail

Computer Vision for Shelf Monitoring: What It Can Actually Detect

August 2026 · ISTRALLEN Team

What the camera can and can't tell you

Computer vision shelf monitoring gets sold as a store that watches itself. The useful version is narrower and more honest: a detector that flags likely gaps and misplacements from shelf photos, and is explicit about when it isn't sure. Knowing where that line sits is the difference between a system store teams act on and one they learn to ignore.

What it detects reliably

  • Shelf gaps and out-of-stocks. An empty facing is a strong, unambiguous visual signal. This is the core job, and it's where the value is — on our computer vision project catching gaps close to when they happen moved product availability by around 18%.
  • Misplaced items. A product sitting in the wrong slot relative to the expected layout — a common cause of "we have it but nobody can find it."
  • Facings and share of shelf. How many facings a product or brand occupies, useful for compliance checks against an agreed layout.
  • Coarse planogram deviation. Actual arrangement versus the plan, at the level of "this section doesn't match," not millimetre placement.

What it detects poorly or not at all

  • Exact SKU under bad conditions. Partial occlusion, glare, steep angles, and seasonal or promotional packaging the model was never trained on all degrade identification. The model may see "a product is here" clearly and still get which product wrong.
  • Small printed detail. The price on a shelf tag, dosage, best-before dates — resolution and shooting angle rarely support reading these.
  • Depth of stock. A photo sees the front row. One item in front of an empty shelf looks fully stocked.
  • Cause. It detects an empty gap. Whether that gap is a late delivery, a planogram change, or shrinkage is an operations question the image can't answer.

Why "confidence" is part of the spec

Real store photography is messy, and a detector confident enough to be useful on clean shots will sometimes be confidently wrong on the messy ones. A single fixed threshold forces a bad choice: set it low and store teams get flooded with false alerts until they stop trusting the feed; set it high and real stockouts slip through.

The pattern that holds up is confidence-based routing — auto-alert above a high-confidence bar, and send the ambiguous middle band to a quick human review queue before anything becomes a task on an associate's list. Alert fatigue is a well-documented failure mode across monitoring systems: once people learn alerts are often wrong, they ignore all of them, including the correct ones.

What makes or breaks accuracy in practice

  • Capture consistency. A fixed camera at a known angle and light level is far easier to work with than ad-hoc staff phone photos — though both can work with the right tolerances.
  • Keeping training data current. Packaging changes constantly. A model trained once and left alone drifts.
  • A feedback loop. Every alert a human marks wrong is a labelled example. Without that loop, accuracy plateaus and you never learn why.

The alerts are only worth the trust store teams put in them

The technical detection rate is half the story. The other half is whether an associate who gets a "gap in aisle 6" alert walks over and finds a real gap. Get that hit rate high enough and the feed becomes part of the routine; let it drop and the alerts get swiped away unread within a few weeks, at which point the detection accuracy is academic. This is why the confidence routing above isn't an optional refinement — it's the mechanism that keeps the human-facing hit rate high enough for the system to stay in use at all.

Where this isn't the right tool

  • You need true depth-of-stock, not front-facing availability. That's a job for shelf sensors or RFID, not photos.
  • Store connectivity can't support image upload. On-device inference that sends only a small structured result — SKU, confidence, shelf position — rather than the photo makes this workable on business broadband or 4G, but a design that ships full images off-site will struggle.
  • Very few stores. Manual audits may still be cheaper than the rollout and the hardware.
  • No capacity to staff the review queue for the ambiguous detections that routing depends on.

FAQ

Does it need special cameras? Fixed cameras give the most consistent input, but staff-phone photos work if the model is trained with enough tolerance for varied angles and lighting.

Can it tell me why something is out of stock? No. It detects the gap. Diagnosing the cause is an operations task.

How accurate is it? It depends heavily on capture conditions and how current the training data is. The practical answer is to design around confidence routing rather than chasing a single headline accuracy figure.

ISTRALLEN builds shelf-monitoring computer vision that runs in-store and routes uncertain detections to people; see AI for Retail.

See it in production
AI for Retail → Semantic search case study →
← All articles