Inventory is a lifecycle, not a row

A useful inventory system answers what you own, where it is, what it cost, what state it is in, and what happened over time. A single editable status cell cannot explain a partial sale, return, damaged unit, or correction.

Give each item or lot an identity

Use a stable SKU or internal label. Record a storage location that someone can understand later. For multi-quantity buys, decide whether the units are economically identical enough to share one lot cost.

Useful fields include:

• item or lot identity

• quantity purchased and quantity available

• purchase and landed cost

• acquisition date

• listing marketplace and asking price

• sale price and known selling costs

• storage location

• notes based on observed facts

Do not require information you do not know. Unknown is a valid state.

Track events that change truth

Purchasing, receiving, listing, selling, returning, restocking, damaging, losing, and adjusting inventory are different events. They should change current state without erasing meaningful history.

For example, selling two units from a five-unit lot should reduce available quantity by two, attach the correct share of COGS to the sale, and leave three units with their remaining cost. A retry should not sell them twice.

Prevent impossible quantity

Canonical quantity integrity belongs in the database or trusted application logic, not only in a form. Two simultaneous attempts to sell the final unit must not create negative stock.

Reconcile inventory and profit

Inventory and profit should not become separate stories. A sale event should produce exactly one intended financial consequence. Returns, partial refunds, fees, and reversals should adjust history in an auditable way.

Review the operating signals

Scan available, listed, sold, returned, damaged, and stale inventory. Review aging with cost and realistic profit. Low stock matters only when the item is worth restocking; a low quantity alone is not a purchase recommendation.

Read spreadsheet vs software for the system tradeoff, or see how Flee OS approaches inventory.