Why Can't the App Find My Wine?

Usually because the bottle was never catalogued, not because your photo was bad. Scanning matches a picture of a label against a catalogue, so a wine nobody entered cannot be found however carefully you shoot it. The two failures look identical on screen, and there is a ten-second way to tell them apart.

Two failures that look the same

“Not found” is doing double duty, and that is the whole problem.

One failure is I could not read it — glare on the glass, a tilted angle, a torn label, an unusual typeface. The other is I read it fine and it is not in here. Both surface as the same shrug, so people retry the thing that only fixes the first one, get the same result, and conclude the app is broken. Collapsing “could not look” and “is not there” into one message is a small design sin with an outsized cost.

The ten-second test

Type the wine’s name into the app’s search box.

The scanner and the text search draw on the same catalogue. So if typing the producer and vintage finds the bottle, your photo was the problem and it is worth another scan in better light. If typing also comes up empty, the wine is genuinely absent and no amount of retaking the picture will change that. One test, two very different next steps, and it costs nothing.

Which wines are routinely missing

Catalogues are built from what is widely traded and widely reviewed, so absence follows a pattern.

Bottle	Odds it is catalogued	Why
A well-known estate, recent vintage	High	Traded and reviewed everywhere
Supermarket own-label	Low	One retailer, one market, producer often changes
Small grower, a few thousand bottles	Low	Little trade, few reviews to build a record from
This year’s release, just landed	Patchy	The wine exists before the entry does
Restaurant-exclusive bottling	Low	Deliberately outside normal retail

Own-label bottles are the ones people hit most, which is worth knowing before you blame yourself in the aisle — they are also the ones picking wine at the grocery store deals with directly.

What a good app does when it doesn’t know

The honest response to an unknown bottle is to say so.

• Name the failure. “I could not read the label” and “I do not have this wine” need different words, because they need different actions from you.
• Never guess a near-match. A different vintage or a similarly named estate returns notes for a wine you are not holding, with nothing on screen to warn you.
• Let you save it anyway. An unrecognised bottle you liked is still worth recording, which is the point of remembering wines you liked.
• Explain the mechanism. Knowing that scanner apps match label images makes the failure legible rather than arbitrary.

Not knowing is a normal outcome for a catalogue of a world that makes far more wine than anyone records. What separates apps is whether they tell you which kind of not-knowing you have hit.

Want a wine app that explains its reasoning instead of guessing? Download AboutWine free on the App Store.

Frequently asked questions

Will scanning in better light fix it?

Only if the photo was the problem. Better light, a straight-on angle and a steady hand genuinely raise the hit rate on a bottle that is already catalogued. None of it helps for a wine nobody has entered, because there is no record for a clearer picture to match against. Run the typing test first so you know which problem you have.

Why do supermarket own-label wines fail so often?

They are made for one retailer, sold in one country, and often change producer between vintages. That combination gives them few of the traces a catalogue is built from, so they sit in the thin part of the long tail. It is not a judgement on the wine, only on how visible it is.

Is a wrong match worse than no match?

Considerably. No match tells you the truth, which is that the app does not know. A confident near-match on a different vintage or a similarly named estate hands you notes and scores describing a wine you are not holding, and nothing on screen signals that. Prefer an app that admits the gap.