The inventory system template — structure before software

The key facts

• A template is a structure, not a file: the fields you track, the flows you record, the ritual you keep — portable across any medium.
• The core structure: product fields, movement fields, order fields, count fields — with quantities derived, never typed.
• The process map around it: intake, receiving, fulfilment, counting, reordering — who does what, in which order.
• The graduation path: the template's tables import directly into systems like BSimple ($180/mo AUD up, trial) when shared truth or scanning arrive.

The field lists — the template's heart

Product fields: SKU, description, supplier, unit of measure, unit cost, par level. Keep variants as their own rows; decide boxes-versus-singles once, in writing.

Movement fields: date, SKU, direction (in/out/transfer/adjust), quantity, location, reason, actor. Append-only — the field that matters most is reason, because variances without explanations are how records drift into fiction.

Order fields: order reference, customer, date promised, lines (SKU, quantity, price), state (placed/checked/picked/packed/invoiced/paid). The state field is what makes the order trackable — the life-cycle stages are the standard set.

Count fields: count date, SKU, counted quantity, variance, explanation, approver. The counting discipline is what keeps every other field honest.

Derived: on-hand quantities by formula over movements — the one rule that separates a template from a fiction generator. The database-design reasoning explains why this field list survives contact with real systems.

The process map around the template

A template without a process map is a form nobody fills in. Map the flows in one page: intake — every order enters the record the day it is confirmed, from every channel; receiving — every delivery is logged against the purchase before it touches the shelf; fulfilment — picked and packed quantities update the order's state; counting — monthly, with variances explained on the record; reordering — a weekly pass over par levels, or automation once software arrives. Assign each flow an owner by name. The small-business method is this map in its simplest form.

The template works in any medium that holds tables: spreadsheets (the Excel build, the Sheets one), Notion or Airtable databases, or as the configuration plan for real software — which is the graduation path below.

The graduation path, and our stake in it

The template earns its keep until shared truth, guardrails or scanning arrive — then its tables become the import file for real software, and the graduation is an afternoon rather than a project. We build BSimple, so weigh that: it is commercial software, not a downloadable template — the structure above implemented as a maintained product (live multi-location stock, batches, purchasing from demand, portals, invoices to Xero or MYOB with US integrations rolling out), from $180/$250/$399 per month AUD, with the trial as the full product. The template and the product share the structure — which is precisely why the migration is cheap and the comparison is fair.