How to Do an Inventory Count in a Coin Shop

To do an inventory count in a coin shop, pick what you are counting (the whole shop, one safe, or one category), record what the system says should be there when you start, then scan or tick off every coin you physically find. Compare the two lists, look into every difference, and only then change your records. Count first, compare second, fix last.

That order is the whole method. Most bad counts go wrong because someone fixed records while counting, or because sales during the count turned into "missing" coins. The rest of this post walks through a count that you can trust.

Why coin shops count inventory

A coin shop holds small, valuable objects that look alike. A count tells you:

• Whether anything is missing. Theft, a coin left in a show case, a coin returned to the wrong box.
• Whether records match the shelves. Wrong quantities on rolls, coins in the wrong place, coins that were sold but never marked sold.
• What your stock is worth. Your accountant and your insurer will both ask. Ask each of them what records they want from a count, since needs differ.

Full count or cycle count

	Full count	Cycle count
What	Every coin in the shop	One safe, zone, or category
When	Once or twice a year, often year-end	On a schedule, such as one safe a week
Cost	A closed day or a long evening	An hour here and there
Best for	Year-end figures, insurance	Catching problems early in high-value areas

Many shops do both: a full count at year-end and cycle counts of the gold and the key dates during the year.

Before the count

1. Pick the scope. Write it down: "Main store, Vault zone" or "all certified gold". A count without a clear scope ends with an argument about whether a coin should have been there.
2. Freeze the expected list. Record the coins the system expects in that scope at the moment you start. That is the list you compare against.
3. Settle open moves. Put away coins from the last show. Finish putting away the last purchase. A count during a half-done move creates differences that are not real.
4. Make every coin scannable. A barcode or QR label on each 2x2 or slab sleeve turns a count from reading numbers into scanning. For slabs, the cert number is already a barcode.
5. Split the work by place. Give each counter a safe or a shelf. Two people counting the same box is how coins get counted twice.

During the count

Count by place

Work one place at a time: safe, shelf, box. Before you scan a box, set where you are. That way a coin found in the wrong box is caught as misplaced, not just counted.

Scan, do not type

Typing SKUs by hand is slow and error-prone. A USB or Bluetooth barcode scanner types the code for you. A phone camera works too. Scan every coin, including the ones you are sure about.

Count quantities for rolls and lots

For a roll or a lot recorded as one line with a quantity, count the coins and enter the number. A roll recorded as 20 that holds 19 is a real difference.

Do not count a coin twice

When a coin is scanned again, it should be flagged as a repeat, not added. With several people counting, this matters more.

Do not fix anything yet

If a coin is in the wrong box, scan it where it is. If a coin is missing, leave it missing. You will decide what to do in review.

Compare the count with the records

When counting is done, every line falls into one of a few outcomes:

Outcome	Meaning	Usual action
Matched	Found where the record says, quantity right	None
Missing	Expected, not found	Search, then mark missing if it stays lost
Unexpected	Found, but the record has it somewhere else	Move the record to where it was found
Unknown code	A scan that matches no coin	Find out what it is; often an old label
Quantity difference	Found, but the count differs from the record	Set the record to the counted quantity after a recount
Changed during the count	Sold or moved after the count started	Leave it alone

Worked example

You count the Vault zone. The system expected 486 records there. Your team scanned 483 records.

• 479 matched.
• 4 are missing.
• 1 roll recorded as 20 coins holds 19 (quantity difference).
• 2 coins sold online during the count, after it started (changed).
• 3 coins turned up in the Vault that the records place in the back room (unexpected).

You search for the 4 missing coins. Two turn up in the show case from last weekend. Scan them in. Two stay missing; those get marked missing. The 3 unexpected coins get moved to where they were found. The roll is recounted, still 19, and set to 19. The 2 sold coins are left alone, because the sale is real.

Notice what would have happened if you had fixed records while counting: the 2 sold coins would look missing, and someone might have put them back into stock.

Approve the changes

Have someone other than the counter review the differences and approve the changes, at least for high-value coins. Separating counting and approving is a basic control. It also means a counter cannot hide a missing coin by marking it found.

When you approve:

• Missing coins should come off every place you sell them, so you do not sell a coin you cannot ship.
• Each change should land in the coin's history, with who approved it and when.
• Keep the count report. Your insurer or accountant may want it.

Common mistakes

• No fixed scope. "Count the vault" means different things to different people.
• Counting during a busy sales day without recording the start time. Sales become false missing coins.
• Fixing records during the count. You lose the record of what was actually wrong.
• One person counts and approves. No second set of eyes on the differences.
• Skipping the search. Most "missing" coins are in a show case, a grading box, or the wrong safe. Search before you write them off.
• Not counting coins that are out. Coins on memo or at grading are not on the shelf. Treat them as away, not missing, and track them where they are.

How CoinManagerPro runs a count

CoinManagerPro stock counts follow this method. You start a count of a warehouse, some zones, or a category, and the count records the coins expected at that moment. On the scan screen you set the zone, safe, shelf, and box, then scan. A scan reads a CoinManagerPro label, an RFID tag, or a slab cert number, from a USB or Bluetooth scanner or a phone camera. Each scan gives a sound and a color, and a repeat scan does not count twice. If the connection drops in the vault, scans wait on the device and send when it returns.

When you finish counting, the app compares the scans with the records and lists each line as matched, missing, unexpected, unknown code, quantity difference, away, or changed during the count. No coin changes until a member with the approve permission chooses the changes and approves. A missing coin then comes off every sales channel, and each change goes into the coin's history. You can print a report or download a CSV. The details are in the stock counts help article, and the places you count come from the storage map.

The short version

Pick a scope. Freeze the expected list. Count by place, scanning every coin, without fixing anything. Compare, search for the missing coins, and decide each difference. Have someone else approve. Keep the report.