Guide
Spreadsheet or software for supplement compliance documents?
By Jake, founder · Published · Updated
A spreadsheet works with roughly a handful of SKUs and one manufacturer: one tab, one glance. It breaks once you're tracking multiple manufacturers, multiple lots per SKU, and each lot's own expiry, because "what's missing" stops being a cell you can see is empty and becomes a comparison against a requirements list the spreadsheet doesn't contain.
Where a spreadsheet genuinely suffices
A spreadsheet is the right tool for a specific, small shape of business: one contract manufacturer, a handful of SKUs, and lots that don't turn over often. If that's you, say four or five SKUs from a single manufacturer, a tab with a row per SKU, a COA date, and an expiry date is not a compromise. It's the correctly sized tool. Anyone who has built a compliance spreadsheet for a business that size and found it annoying wasn't wrong about the annoyance, but the annoyance is not evidence that the spreadsheet is failing at its job.
The reason it holds up at this scale is that a single person can hold the whole catalogue in their head. There's one manufacturer relationship to remember, one set of lot numbers to track, and few enough expiry dates that a monthly glance catches what's coming due.
Where it breaks
The spreadsheet doesn't fail gradually; it fails multiplicatively. The number of things that can silently go stale is roughly SKUs × manufacturers × lots-per-SKU × expiry dates per lot, and each of those axes grows independently. A brand that adds a second manufacturer doesn't just add rows; it adds an entire second set of relationships, request threads, and document formats to track in parallel. A brand that reformulates or re-sources a SKU doesn't replace a row. It adds a new lot with its own COA and its own clock, while the old lot's row often stays in the sheet looking current.
- Multiple manufacturers: each has its own cadence for sending documents, its own contact, its own way of naming lots, none of which a spreadsheet enforces or reconciles.
- Multiple lots per SKU: the newest lot's COA is the one that counts for a review, and a spreadsheet has no rule that stops someone from checking the wrong lot's date.
- Independent expiry clocks: every lot has its own document-age window running from its own certificate date, not the SKU's original launch date.
- No cross-check against what should exist: a spreadsheet only ever shows the rows someone created. A manufacturer that never sent a COA at all produces no row, no blank cell, no signal.
That last point is the real failure mode, and it's easy to miss because it doesn't look like a mistake. The spreadsheet looks complete. It just isn't complete relative to what Amazon's verification, Prop 65, or your own product's requirements actually call for, because the spreadsheet was never told what to expect.
What "knowing what's missing" actually requires
"What's missing" is a comparison, not a lookup. To know a SKU is missing a document, you need two things: your catalogue of what you have, and an independent list of what a product of that type is supposed to have, by product category and by authority. A spreadsheet only ever holds the first half. The second half is what a requirements library is for: a maintained, cited list of what each product type needs to show for Amazon, Prop 65, USP, and 21 CFR Part 111, so a gap can be detected instead of discovered.
Once that comparison exists, expiry tracking becomes a smaller problem too, not because the 182-day document-age window changes, but because a system that already knows what a SKU needs can also know when the document it has stops counting as current.
The honest comparison
| Spreadsheet | Software | |
|---|---|---|
| Setup cost | None: a blank sheet | None to start (14-day free trial, first product free forever); plans scale with product count |
| Good at | A small, stable catalogue one person can hold in memory | Catching what a spreadsheet can't see: missing documents, not just aging ones |
| Tracks dates | Only if someone remembers to check them | Reads certificate dates off uploaded documents and warns before expiry |
| Knows what should exist | No: only reflects what was typed in | Compares the catalogue against a cited requirements list |
| Scales across manufacturers | Manually, with growing risk of drift | Each manufacturer's documents land in one place regardless of count |
| Cost of getting it wrong | A retest at roughly $500 to $1,000 per product instead of a review at $80 to $120 | The same cost gap. Software's job is catching the gap before it costs anything |
The dollar figures in that last row aren't a software-versus-spreadsheet cost. They're what a missed document costs regardless of what tracked it. Compliant Always's free trial reads your catalogue and shows a readiness score without a spreadsheet, and the plans that follow it carry the expiry warnings and the chase.
How to tell which one you need
- Count your active manufacturers. One means a spreadsheet is plausible; two or more means reconciling formats and cadences by hand.
- Count active lots per SKU, not just SKUs. Three SKUs with rotating lots is closer to nine things to track than three.
- Ask whether anyone could currently produce a complete list of what's missing, not what's expiring but what's absent, without opening every manufacturer's email thread. If the honest answer is no, the spreadsheet has already stopped doing that job.
- Run the free check: it reads whatever COAs you drop in, checks them against the requirements library, and shows what a review would flag today, spreadsheet or not.
Related: what Amazon requires for supplement listings, how long a COA is valid for Amazon, and what your contract manufacturer is responsible for.
Sources
- Plans and product pricing accessed 2026-08-17
- Document-age window and TIC/retest cost figures, operational configuration, verified 2026-07-24 accessed 2026-08-17
Frequently asked questions
- At what point does a spreadsheet stop being enough?
- There's no single SKU count. It's when the number of active lots (SKUs, times manufacturers, times how often you reformulate or re-source) exceeds what one person can hold in their head. For a single-manufacturer brand with a handful of SKUs, a spreadsheet is often genuinely fine.
- What can't a spreadsheet do that software can?
- Tell you what's missing. A spreadsheet shows you what you typed into it. It can't compare your catalogue against a requirements list and flag a document you never had, because it has no independent knowledge of what should exist.
- Is the problem the spreadsheet or the person maintaining it?
- Both, structurally. A spreadsheet has no memory of what should be there, no alert when a date passes, and no way to know a manufacturer changed lots without someone re-entering it. The person maintaining it is doing the software's job by hand, unpaid, until a deadline proves it.
- Can a spreadsheet track certificate of analysis (COA) expiry dates?
- Yes: a date column and a manual glance work at small scale. What it can't do is warn you before the fact or know that a document-age window applies at all; someone still has to remember to check it. See how long a COA stays usable for Amazon's verification for the window itself.
- Does software replace the spreadsheet entirely?
- It replaces the tracking, not the judgment. Whether a claim is supportable or a spec is right for a formulation is still a human call, usually a consultant's. Software's job is knowing what documents exist, what's missing, and what's about to age out.