Scan Pokémon cards with a document scanner
Start with your scanner and a stack you know
Use a document scanner with a feeder. You can feed in a stack, while with a phone you position cards under the camera individually. Prepare individual image files in a folder, with the front of each card shown in colour.
For EasyCardTCG Scan, we tested with the Ricoh/Fujitsu fi-8170, scanning the fronts of the cards in colour at 300 dpi.
For your first session, choose a stack you already know. Pick cards you are actually planning to list and decide on their order beforehand. Keep the rest of your stock separate so you can tell which stack an image came from. If you have a different scanner, tell us the model when you apply for the closed test. We can look at how you would use it.
Make a trial scan
Set out a small trial stack. Look at the fronts before you begin and put any cards you want to keep separate to one side. Choose an empty folder on your computer for this trial and give it a name you will recognise. It can be something as simple as a label you can leave alongside the physical stack. That way, you have the same batch to return to during your review.
After the trial, look at the first and last images and a few in between. Ask yourself whether you can read the name and number, whether the whole card is in the frame and whether you can easily find it in the stack. If you are unsure about an image, fetch the physical card and make another scan if you need to. Note what you changed so you can try it again afterwards.
Check the folder before opening the images
Look through the folder in file order before you open it in EasyCardTCG Scan. Count the cards and compare that with the number of images you intend to add. If the counts differ, go back through your trial stack and look for a duplicate or a missing image. Keep repeat attempts in a separate folder and use the set of images you want to process for the session.
EasyCardTCG approves a card automatically only when the set, number, language and finish are certain. If the app is unsure, it sends the card to Needs review, where you can check the details.
Keep the stack close after you add the images. If a card needs a closer look, record what you compared on paper or in your own notes. This gives you something to refer to later when you explain where you had to look and whether you needed a better image.
Judge how the setup fits your work
Use the first stack as a trial for your own workspace. Think about where new cards come in, where you set your trial stack down and where the cards go after you check them. Give uncertain cards their own place. That makes it easier to find where you left off after a break. Then try the same routine with a stack that resembles your usual stock.
Write down which actions felt straightforward and when you had to go looking for cards or files. Note how you saved the images and which scanner you used. You can then talk about the trial without having to reconstruct your entire routine from memory.
Frequently asked questions
What images do I need?
Keep individual colour images of the card fronts together in a folder and check them before adding them.
Which resolution should I use?
Use 300 dpi, as in our test with the Ricoh/Fujitsu fi-8170.
Can I use another model?
Tell us which scanner you use and how you save images when you apply. We can look at your setup with you.
What should I do with a hard-to-read scan?
Find the physical card, capture it again if needed and compare the two files.