Guide / Excel stage
An inventory system in XLS — build it right, know the end
An .xls workbook can run small-scale stock honestly — if built as movements with derived quantities. The build, the ceiling, and the upgrade path when the workbook stops holding.
The key facts
- A workbook can genuinely run one-person stock — the build decides everything: products sheet, append-only movements sheet, derived quantities.
- The ceiling is structural: one file, one truth, no guardrails, no scan-to-record — and every management act is a human running a formula.
- The upgrade signs: two people needing the file, an unexplained quantity, reordering by memory. All three arrive together.
- The upgrade is an afternoon when built right — products export, one baseline stocktake, and systems like BSimple (paid, from $180/mo, trial) import them cleanly.
- Context: the full inventory system holds the wider system, this page one stop in it.
- 01The key facts
- 02The XLS build that works
- 03The ceiling, stated structurally
- 04The upgrade path, priced honestly
The XLS build that works
Sheet 1 — Products. SKU, description, supplier, cost, par level — one row per item, edited deliberately, never in passing. Sheet 2 — Movements. Date, SKU, direction, quantity, reason, who — append-only, the sheet everyone actually writes to. Derived quantities. On-hand equals the sum of movements, by formula — typed quantities are how records start lying. Protection on everything except the movements rows. A monthly count, variances investigated, corrections entered as adjustment rows.
Built that way, a workbook is a legitimate inventory system at one-person scale — the same architecture real software uses (the deeper Excel guide and the Sheets variant cover the family), and it exports cleanly to anything later.
The ceiling, stated structurally
One file, one truth. Sharing an .xls means emailing a copy — and every copy is a fork of the truth that will never fully merge. Cloud-shared workbooks solve visibility and create silent conflict resolution, which is worse.
No guardrails. Nothing stops selling below zero, logging to the wrong SKU, or "fixing" a formula. Data validation is a suggestion; the correction culture it produces is why workbooks drift.
No floor. The workbook lives on a laptop; the stock lives on shelves. Scanning needs a system at the shelf to scan into (the scanner gap) — batch entry from clipboards is where the day's truth decays.
No management. Reordering, order checking, supplier reconciliation — every act is a human running the right filter at the right time. The recording-versus-managing line is exactly where spreadsheets stop.
The upgrade path, priced honestly
The trigger is not size — it is the first unexplained quantity, the first day two people needed the file at once, the first stockout the reorder formula failed to prevent. When discipline becomes the bottleneck, the workbook has done its job.
The migration is an afternoon: export products, import into the system, run one baseline stocktake, record movements there from day one. We build BSimple, so weigh that: import is first-class, and the workbook gains what it could never hold — shared live truth, guardrails, scan-to-record, reorder drafts, invoices pushed to Xero or MYOB (US integrations rolling out) — from $180/$250/$399 per month AUD, with the trial free and full. Until then, stay free and stay disciplined: the free-options ledger covers that route honestly.
Frequently Asked Questions
Can I run an inventory system from an Excel file?
For one person at moderate volume, yes — movements-based, protected, counted monthly. The ceiling arrives with sharing, floor-level scanning or management automation; those are software, not spreadsheet, capabilities.
What is the biggest mistake in XLS inventory files?
Typing quantities into a totals cell. It feels efficient and destroys history, audit and concurrency in one habit. Movements in, quantities derived — the rule carries the whole build.
How do multiple people share one workbook safely?
They mostly cannot — copies fork, cloud syncs merge badly. One owner with one file works; two owners is the migration trigger. The Sheets variant is the sharing-aware middle step.
What should the XLS include for GST and EOFY?
Supplier cost columns and a stock value report (quantity × cost) are the honest basics — enough to inform the accountant, not to replace the books. Compliance stays with your accounting system; the boundary holds at every scale.
What does moving to BSimple involve?
Export, import, one baseline stocktake, movements recorded thereafter — the trial runs it beside your live workbook before any money moves.
BSimple