A Pokémon card collection tracker should answer a simple question later: which exact cards do I own, and what did I record about them? A list of names is not enough. Useful records distinguish the printing, handle duplicates, and keep observed price context separate from guaranteed value.
The right tracker depends on whether you prioritize quick phone capture, flexible spreadsheets, multi-device sync, local storage, or physical binder order. Every approach has a tradeoff.
The fields worth recording
Start with fields that help identify the card again:
| Field | Why keep it |
|---|---|
| Name | Makes the record recognizable |
| Set and collector number | Separates releases and numbered cards |
| Language and finish | Prevents visually similar variants being combined |
| Edition or variant | Captures stamps, early printings, promos, or other differences |
| Quantity | Handles duplicates without duplicate rows |
| Condition note | Records your own observation without claiming a professional grade |
| Photo | Preserves the particular copy you cataloged |
| Date added | Gives the record useful history |
| Price-source date and currency | Keeps a snapshot from looking permanently current |
The exact-printing fields matter most. If you record only “Charizard,” your collection may later combine cards from different sets, languages, finishes, and editions. Follow the exact identification workflow before saving a record.
Four common tracking approaches
Local phone app
Good for photographing and recording cards where you find them. Local storage can avoid creating a service account, but it may not provide cloud backup, browser access, or automatic multi-device sync. Deleting the app or losing the phone can matter unless the app documents a backup path.
Cloud collection app
Useful when you want sync, a web view, sharing, or access across devices. In exchange, the service needs an account or another identifier and stores some collection data remotely. Check export options before committing years of records.
Spreadsheet
Flexible, searchable, and easy to export. A spreadsheet works well when you already know the printing and are willing to enter fields manually. Photos and fast capture are less natural, and a free-form sheet can drift into inconsistent naming.
Paper or binder checklist
Durable, simple, and independent of a service. It mirrors physical organization well but cannot search photos, calculate quantities easily, or update marketplace context automatically.
The no-account collection guide compares these approaches in more detail.
Decide how to handle duplicates
Two copies of the same documented printing can share one record with quantity two. Keep separate records when condition, language, finish, edition, grading state, or another meaningful attribute differs.
Do not merge cards only because they use the same artwork. Reprints can look nearly identical while belonging to different sets or products.
Treat prices as dated observations
A collection total is tempting, but the underlying numbers need context. Record whether a figure came from active asking prices, completed sales, a marketplace estimate, or your own purchase. Also keep the date and currency.
A saved price does not refresh itself merely because the tracker is open. If the tool does update prices, learn how often, from which market, and whether it matches the exact printing and grading state. Do not treat a calculated total as an appraisal, insurance valuation, or guaranteed sale result.
Understand where photos and records go
“No account” and “nothing leaves the phone” are different claims. An app can store your finished collection locally while sending a selected image online for card recognition. It can also use separate services for purchases, diagnostics, or analytics.
Apple’s App Privacy framework distinguishes information processed only on the device from data transmitted off-device. Before scanning, check the app’s privacy disclosure, network requirements, deletion controls, and backup behavior. The guide to what happens to a scanner photo gives a practical checklist.
A repeatable cataloging workflow
- Sort a small stack by broad set or era if you can.
- Photograph one complete card with the lower identifiers visible.
- Verify the proposed set, number, language, finish, and edition.
- Choose an honest condition label without presenting it as professional grading.
- Enter quantity and keep a photo of the actual copy.
- Record any marketplace figure with its source, date, and currency.
- Put uncertain matches aside rather than forcing a record.
Consistency beats speed. Ten carefully verified cards are more useful than one hundred names attached to uncertain printings.
How Foily fits
Foily is a phone-based, Pokémon-first tracker built around photographing one physical card at a time. It proposes a likely printing and alternatives, lets you choose condition and quantity, can attach a current general market-value snapshot, and saves the card details and photo to a local collection on your device.
There is no Foily account or cloud collection sync. A selected scan photo is still sent online for identification, and purchase status is handled through the app-store subscription system. Foily does not currently offer import, export, manual entry, collection search or filtering, batch scanning, or automatic price refresh.
That makes it best understood as a focused photo-to-local-collection workflow—not a universal inventory platform.