Why PullScope fits
- The scan can stay in the same context while you append another image.
- Candidate selection and rescan behavior are part of the product flow, not an afterthought.
- It is designed to prefer a cautious answer over a wrong final match.
Use case guide
Use PullScope when a single front image is not enough and you need a scan flow that can accept the back photo before finalizing the result.
This page covers one of the most practical card-scanning problems: you have a close match, but not enough certainty. PullScope is relevant because it can ask for another photo instead of pretending the first guess is final.
Why PullScope fits
What to photograph
Related reading
Read the scan workflow FAQUse the supporting guide if you need more context before you run the scan itself.
Workflow
Let the first scan produce an initial candidate set and confidence score before you decide whether another image is needed.
Use the back photo when the app signals low confidence or when you know the reverse side carries the missing signal.
After the second image, review the updated result or choose the best candidate manually if the app still stays cautious.
Questions behind this use case
Yes. The product is meant to handle low-confidence cases with another photo instead of treating every first scan as final.
Do it when the app offers a short candidate list and you can see the right card faster than another rescan would resolve it.
Yes. The corrected scan result can become the final saved record instead of leaving the weak first match behind.
Related categories
Use this page for sports cards when you need a clean first pass on player, set, year, rookie context, and price guidance from camera input.
Use this page for Pokemon cards when you need a first-pass match on set, collector number, rarity, language, and likely price direction.
Use this page for Yu-Gi-Oh! cards when you need quick help with set codes, rarity treatment, print language, and pricing context.