Shelf recognition software for retail audits

Every shelf checked against the planogram on the day of the visit

A merchandiser photographs the shelf in the app, and the model recognises your products by their packaging, counts facings and finds empty spots, competitor products and wrong price tags. The merchandiser sees the issues while still in the store, and the supervisor gets a summary by store instead of a folder of photos.

What happens to the shelf between visits

  • A merchandiser sends 40 photos a day. The supervisor opens five, the rest stay buried in the chat.
  • The contract says four facings at eye level. In the store there are two on the bottom shelf, and a competitor has moved in next to them.
  • The product is in the store backroom, but the shelf has been empty since morning. You find out from the sales report at the end of the month.
  • A price tag from an old promotion is still up. Shoppers argue at the checkout, and the retailer files a claim.

What changes after launch

  • 01Every merchandiser visit is checked, not a random few
  • 02Empty spots and price tag errors are visible on the day of the visit
  • 03Talks with retailers about display rely on photos, not impressions

How the system works

  1. 01

    Load planograms and the range

    Planograms, packaging photos, rules for price tags and share of shelf. The model learns to recognise your products and the competitor products that matter for the report.

  2. 02

    The merchandiser takes a photo

    Following the app prompts: the whole shelf, no steep angle, price tags in frame. A blurry or cropped photo is flagged for a retake while the merchandiser is still at the shelf.

  3. 03

    The model reads the photo

    It finds products by packaging, counts facings and marks empty spots, competitor products and price tags.

  4. 04

    Check against the planogram

    It compares the actual display with the reference: what is out of place, what is missing, where the tag does not match the product or the price.

  5. 05

    Doubtful cases go to a person

    Look-alike packs, glare on film wrap, a hidden price tag. The model flags such photos, and a supervisor reviews them.

  6. 06

    Visit and network reports

    The merchandiser sees the issues before leaving the store and can fix them on the spot. Managers see a summary by retailer, region and supervisor.

Which scale is yours?

One task, three different projects. Pick the one that looks like you and press “I want this” — your request arrives tagged, and we send an estimate in 1–2 days.

Small business

One brand or distributor, a small merchandising team and a few dozen stores.

What we build

  • One product category and your own range
  • Capture app with a photo quality check
  • Empty spots, facings, price tag presence
  • Visit report and an Excel summary
Integrations
Excel, Telegram alerts to the supervisor
Where it runs
Cloud: no infrastructure needed on your side
Timeline
Guideline: 6–10 weeks to the first working version

Mid-size business

common start

Several categories and retail chains, each with its own planogram, and the sales team needs display reports every week.

What we build

  • Planogram checks by retailer and store format
  • Price on the tag checked against your price list
  • Integration with your visit tracking or merchandising CRM
  • Reports by retailer, region and supervisor
  • Support contract: we add new products and packaging changes
Integrations
Merchandising CRM, ERP (1C), BI tools
Where it runs
Cloud or your own server
Timeline
Guideline: 2–4 months to the first working version

Enterprise

common start

A retail chain or a large manufacturer: hundreds of stores, an in-house merchandising team and audits done by store staff.

What we build

  • One set of display rules across the network
  • Roles: store employee, store manager, category manager
  • Audit log: who took the photo, who confirmed it, what was fixed
  • Models on your servers, updated as the range changes
  • Service under an SLA
Integrations
Assortment and planogram management systems, ERP (1C), internal APIs
Where it runs
Your servers or a closed perimeter
Timeline
Guideline: 4+ months, starting with a pilot in a group of stores

Pilot from RUB 500,000. Beyond that we price by task and hours.

Questions

Can the model tell our products from similar ones?

If the packs look different on a photo, yes, once trained on your range. Near-identical packs in different flavours are the hardest case: we check them by the price tag or send them to a person to confirm.

What happens when the packaging changes?

The model will not recognise new packaging on its own. You send photos, we retrain. Under a support contract this is routine work, not a separate project.

Can we use the photos merchandisers already send?

We start with them: during the assessment we check how many are usable. Most often the capture rules need adjusting (angle, distance, lighting), plus a photo quality check built into the app.

Does it work without internet in the store?

Photos can be taken offline and sent once the connection is back. Running the model on the phone itself, with no server, is a separate task we discuss during the assessment.

A quote in 1–2 days

Name the process that eats time. You get a pilot range, not a 40-slide deck.

Or message us