Coin Collection Inventory Checklist: What to Record for Each Coin

Start with a useful minimum record

For every coin, record a clear name, denomination, issuing country, year, mint mark when present, quantity, and a plain-language condition note. Add the collection or album where it belongs and a general storage label.

If a detail is uncertain, say so. Do not turn a guess into a fact merely to complete a row.

Add identification and certification details

Choose Coins & Bullion under Collectible template for the current specialist form. Its optional details appear according to Item Type, grading status, and authentication status; expand Show More Collectible Details for the rest. A coin record may include series, variety, composition, weight, fineness, grade, grading service, certification number, and holder notes. Transcribe identifiers carefully and photograph the label or holder.

A certification entry records what appears on the holder; it does not mean Item Legacy has verified the holder, grade, attribution, authenticity, or certification status. Use the issuing service’s official resources when verification matters.

Preserve acquisition and cost context

Record acquisition date, source, purchase price, fees if useful to your own records, and the receipt or invoice when you have the right to retain it. Note whether a group purchase price was allocated across several coins and how you made that allocation.

These records can support personal organization, but they are not tax calculations. Ask a qualified tax professional what basis documentation a particular situation requires.

Separate collector value from metal calculations

If you enter an estimated collector value, add its source and date. Market listings, dealer offers, auction results, and professional appraisals are not interchangeable.

For eligible legacy precious-metal items using the existing category workflow, a Melt calculation depends on recorded metal, weight, purity, quantity, and a saved USD spot price. Automatic Value uses the higher of Melt and entered collector value after recalculation. Coins & Bullion v1 uses manual Value for the whole recorded quantity; its physical-weight summary does not perform spot-price valuation. It is a calculation from entered inputs, not a guaranteed sale price or professional valuation. Collector value may differ materially from metal content.

Photograph the coin and its identifiers

Use an overall image of each side, even lighting, neutral background, and a separate view of relevant edge, holder, label, or distinguishing feature. Avoid editing that disguises color or condition. Keep original files independently when they matter.

Photos help connect the record to an object. They do not prove authenticity, ownership, condition, or value by themselves.

Attach the evidence that explains the entry

Receipts, invoices, certificates, prior appraisals, and relevant provenance can remain connected to the item they describe. Use clear filenames and dates. Avoid uploading payment-card numbers, account credentials, safe combinations, or unnecessary information about other people.

Fictional example: keep four different numbers distinct

The following is fabricated teaching data, not a real coin, certification, customer, quote, or recommendation.

Example teaching record: acquisition cost $48.00 (2024-04-12); owner estimate $72.00 based on fictional notes dated 2026-08-01; professional appraisal $65.00 in a fictional appraisal dated 2025-06-15; melt calculation 0.7734 troy oz × 0.900 purity × a fictional saved spot price of $30.00 = $20.88. These figures are separate: melt arithmetic excludes collectible premium, fees, spreads, taxes, and transaction costs.

• ✓Universal fields: collection, item name, category, quantity, condition notes, acquisition context, cost, owner-estimate source/date, general location, evidence, and notes.
• ✓Coin/bullion fields: denomination, mint, year, grade transcription, certification number, metal, weight, purity, saved spot price, and melt calculation.
• ✓A grade is owner-entered or transcribed from a holder label; Item Legacy does not verify it.

Use Sets without duplicating the coin

An album or series checklist can be useful alongside the inventory. In Item Legacy, a Set references Items in its parent Collection; it does not require a second copy of the same coin record. Missing slots can remain planning entries until an Item exists.

Review three records before scaling up

Check whether another collector could distinguish the items, whether each number has a source, and whether your naming pattern is consistent. Revise the fields now, then continue through the collection in manageable groups.

Use current item numbers and private QR labels

Item Legacy assigns a displayed number within your account. Ordinary edits preserve it, but deletion may allow reuse. The underlying UUID remains the item identity. With Collector or higher, open the saved Item and choose Print Label: 1 × 1 inch sticker (25.4 × 25.4 mm), 1.5 × 1.5 inch sticker (38.1 × 38.1 mm), 2 × 2 inch sticker (50.8 × 50.8 mm), or 3.5 × 2 inch cardstock (88.9 × 50.8 mm). Choose Paper layout to match your stock: Spartan Industrial S001 uses 63 pre-cut 1-inch labels on US Letter; full-sheet cut-to-size layouts use cutting guides instead. Print a plain-paper test at Actual Size / 100% with Fit to Page off. For S001, compare placement with an unused sheet; for cut-to-size, measure the 50 mm ruler and cut on the corner marks. Test a scan before printing more.

A QR opens the existing private UUID item page. The owner can open it when signed in; a signed-out user must sign in; another account cannot access it. A deleted item's old QR does not open a replacement if the displayed number is reused. A label grants no access.

Keep copies and identity separate

Exported source_item_number is informational. CSV import creates fresh UUIDs and account-local numbers; it does not reserve the old number or restore the old QR destination. Keep the complete custom_fields JSON archive for specialist and retained details. CSV does not include photo or document files. Native snapshots preserve populated numbers subject to restore safety checks; older snapshots can receive new numbers. Check Backup & Data for actual snapshot status and reviewed restore-request access.