Price-tag scan troubleshooting on iPhone

Stage one: make the image readable

Live scanning requires camera permission and a configured camera session. If permission is denied, the app shows a camera-access message rather than OCR results. Permission can be changed in iOS Settings. Photo import remains a separate system-picker path, but the selected image still needs readable pixels. A permissions fix cannot repair blur, reflection, tiny type, or a tag outside the viewfinder.

Start with one label. Hold the phone parallel to the tag, reduce glare, and include the currency symbol plus the words that identify tax, sale, membership, or unit pricing. Wait for a stable result. If live text flickers, use Freeze. If you have a sharper close-up, crop it and use Photo. Do not fill the frame with only the digits; the surrounding term often determines which amount is meaningful.

1. Confirm camera permission for live mode.
2. Clean the lens and use bright, even light.
3. Frame one complete price card rather than a shelf full of labels.
4. Keep the currency mark and explanatory words visible.
5. Retry with Freeze or a cropped photo.

• A large blurry number is less useful than a smaller sharp number with its label.
• Plastic shelf rails can create glare exactly over the tax-included total.
• Perspective distortion can separate a term from the amount it describes.

Source: Apple Vision: Recognizing Text in Images

Stage two: correct market and parsing context

The source market constrains the expected currency and selects the local price-term dictionary. A Japanese tag with the wrong market can lose Japanese term matches or have yen evidence treated cautiously. The optional current-location action only suggests a country and currency; it does not continuously follow you or identify the store. Correct a poor suggestion manually.

The parser prefers explicit currency evidence because retail images contain many unrelated numbers. If OCR sees only 149 without ¥, 円, JPY, or a nearby source-currency clue, it may decline to treat it as a price. Barcodes and long digit runs are intentionally rejected in common scanner-noise cases. When the wrong amount wins, narrow the frame but preserve the term tied to the intended price.

1. Open Source Market and confirm the country, currency, and implied language.
2. Confirm the target currency is different from the scanner source.
3. Look for an explicit currency mark or code in the original tag.
4. Exclude barcodes, dates, package weights, and unrelated shelf labels.
5. Read any low-confidence or multiple-price warning before retrying.

• Tax included, sale, and likely final roles normally outrank regular or unit references.
• Member-price warnings indicate a condition, not a parser failure.
• Multibuy and points wording can be recognized without producing a complete deal calculation.

Stage three: separate translation, access, and rate failures

A missing product title is not the same as failed price OCR. Product-title translation appears only after the app extracts a plausible short title and confirms that Apple’s exact source-target Translation pair is installed. Local price-term labels can still appear when that optional title is absent. Do not repeatedly refresh FX rates to solve a translation problem. Product-title translation requires iOS 26 or later.

A visible upgrade message means OCR may have detected a price while the scanner access decision prevents presentation. Free users begin with 10 counted starter scans and later receive one daily live scan. Imported photos are excluded from counting, but result presentation still follows that access decision. A rate-unavailable message is different again: the app has a parsed amount but no cached snapshot that can convert the pair.

1. If only the title is missing, check the installed Apple language pair. Product-title translation requires iOS 26 or later.
2. If the result is locked, inspect free-scan or Pro status rather than changing the image.
3. If the original price appears without conversion, inspect rate status and pair coverage.
4. If nothing is recognized, return to image quality and market selection.

• Translation availability does not control local price-role labels.
• Photo import does not create a separate unlimited free entitlement.
• Manual conversion is available without Pro, but manual refresh has tier-specific cooldowns.
• There is no supported inbound pricetagfx scan deep link to test as a workaround.

Source: Apple Translation framework, Frankfurter exchange-rate API

Stage four: decide when to stop troubleshooting

Some tags remain ambiguous after a technically successful scan. Handwriting, unusual abbreviations, electronic labels mid-refresh, damaged shelf cards, and overlapping promotions can defeat a general OCR and parser workflow. A medium- or high-confidence card still reflects model and rule confidence, not access to the retailer’s pricing system.

When the app and store disagree, trust the seller’s current checkout disclosure and ask for clarification. Capture the full tag and receipt if you need to compare later. For travel budgeting, inspect rate age and payment fees. Repeatedly rescanning until one result matches an expectation is not validation; it is selection bias. The safer endpoint is a documented uncertainty and a verified register amount.

1. Compare the full tag, not just the selected number.
2. Ask the store which tax, member, sale, or quantity condition applies.
3. Confirm the register total in the local currency.
4. Review the card or merchant conversion terms separately.
5. Report a reproducible app issue without including unnecessary private content.

Troubleshooting

Frequently asked questions