Sub-Total: £0.00
Why Your Spreadsheet Breaks at 500 Cards
(and What to Do Before It Does)
Nobody starts a card business with bad systems. You start with a clean spreadsheet: columns for card, cost, list price, sold price. It’s fast, free, and completely under your control. For your first hundred cards it might be the best inventory system ever built.
Then the business grows, and the spreadsheet grows with it — new tabs, new formulas, a second platform, a breaks section bolted on the side. Somewhere around a few hundred cards — call it 500, though the exact number varies — the tool that made you organised becomes the thing you’re scared to touch. Not because spreadsheets are bad, but because you’re now asking one file to be an inventory system, an accounting ledger, a comping tool and a reporting suite at once.
The frustrating part: it never announces it’s breaking. It breaks quietly, cell by cell, while the true profit and stock numbers you rely on drift further from reality.
Why it matters
Your spreadsheet isn’t a document — it’s the business’s memory. It’s where cost basis lives, what your stock is worth, what’s listed where. When it degrades, the loss isn’t hypothetical time; it’s real money in mispriced cards, forgotten stock and unreliable profit numbers, which is why inventory management makes or breaks sellers.
And spreadsheet failure has a particular shape: you find out at the worst moment. Tax return week. A dispute over whether a card sold. The day you finally sit down to work out if the business made money. The file that “mostly works” in daily use is precisely the file that fails an audit of any kind — by HMRC, by a buyer, or just by future you.
The common mistakes — the seven failure modes
Almost every broken card spreadsheet fails in the same seven ways:
- No audit trail. A number changes and nothing records who, when or why. Yesterday’s stock value disagrees with today’s and there is no way to find out which one was right.
- One owner. The file only makes sense to the person who built it. Holiday, illness or a growing team — everything stops, because the system is a person.
- Formula rot. A deleted row breaks a reference; the fix is typing the number in by hand. Every hardcoded patch is a little lie the file now tells with total confidence.
- No platform sync. The card sold on Whatnot on Sunday; the spreadsheet finds out on Thursday. In between, your stock list and your listings disagree — and sometimes the card sells twice.
- Manual comps. Values pasted in once, months ago, still presented as “what it’s worth”. A valuation column that never moves isn’t a valuation — it’s a memory.
- Version chaos. `inventory_FINAL_v3_ACTUAL(2).xlsx`, one on the laptop, one in email, one in the cloud. Two of them have been edited since they diverged, and merging them is nobody’s idea of a weekend.
- Fear. The clearest sign of all: you hesitate before opening it, and you’d never dare restructure it, because you’re not sure what would break.
None of these is carelessness. They’re what happens when a flat file is asked to do a database’s job.
A better approach: the staged path off
You don’t fix this in one heroic weekend, and you shouldn’t move systems in a panic either. The path off is staged:
Stage 0 — back up, today. Export the file, date-stamp the name, put a copy somewhere that isn’t the same laptop. Ten minutes. Do it before you change anything else (Friday’s post this week is exactly this).
Stage 1 — stabilise. Stop the bleeding: no new tabs, no new clever formulas. Lock the structure, and start a simple change log — even a “changes” tab with date/what/why beats nothing.
Stage 2 — consolidate. One master file, everything else archived as read-only. Separate data from working: one clean ledger of inventory facts (card, quantity, cost, location, status), and separate sheets for analysis that reference it but never overwrite it.
Stage 3 — get the ledger fields right. If the clean ledger records purchase date, source, allocated cost basis, platform and status per card, you have something a real system can import in one pass. This stage is what makes the eventual move easy instead of traumatic.
Stage 4 — move when the triggers say so. Reasonable triggers: admin hours you resent every week; a money number you caught being wrong; a second person needing access; more than one platform to keep in sync. When two or more are true, the spreadsheet has told you its answer.
The order matters. Sellers who jump straight to “new system” import their chaos and blame the system. Sellers who do stages 0–3 first migrate clean data — and half of them discover the discipline alone bought them another year of spreadsheet life. That’s a fine outcome too.
The OTA perspective
We’re building On Top Accounts for card businesses on exactly this path — and, honestly, OTA is being built now, in the open, not a finished product. The reason it exists as a system rather than a better template is that the seven failure modes above aren’t formula problems; they’re structural. Audit trails, multi-user access, platform sync and living valuations are what databases do and flat files don’t. Our job is to make Stage 4 feel like relief: your clean ledger imports, the history stays, and the spreadsheet retires with honour instead of dying in service.
Action steps
- Do Stage 0 now. Export, date-stamp, cloud copy. Ten minutes, and the worst-case scenario stops being existential.
- Count your failure modes. Score the file honestly against the seven above. Zero to two: carry on. Three or more: start the staged path this month.
- Freeze the structure. No new tabs or formulas while you consolidate — additions are how it got here.
- Build the clean ledger. The Stage 3 fields, one row per card or lot. Slow, unglamorous, and the single most valuable data task in the business.
- Write down your move triggers. Decide now what would make you switch systems, so the decision gets made by criteria instead of by crisis.
If your spreadsheet already scares you, it’s telling you something. Listen to it before it makes the decision for you.
