™
QUICK ANSWER
The short version
Start with one record per SKU and location, record every receipt, sale, return, transfer and adjustment, then verify the records with regular physical counts. Track quantity on hand, available quantity, unit cost, reorder inputs and the timestamp of the last verified count. The system matters more than the software: every stock change needs a source and an owner.
1. Create one inventory record for every SKU and location
A product name is not precise enough for inventory control. Each sellable variation should have a stable stock-keeping unit, or SKU. If a shirt comes in three sizes, each size needs its own record. If the same SKU is held at two stores, each location needs its own balance.
Keep the record small enough that staff will maintain it. A useful minimum is SKU, product name, location, quantity on hand, committed quantity, available quantity, unit cost, supplier, reorder point and last-counted time. Add lot or expiry fields only when the product and process actually require them.
| Field | What it tells you | Common mistake |
|---|---|---|
| SKU | Exactly which item or variation is being counted | Reusing one code for several sizes or flavours |
| Location | Where the units physically belong | Combining all stores into one balance |
| On hand | Units physically recorded at the location | Treating purchase orders as stock on hand |
| Committed | Units reserved for open orders | Ignoring units already promised |
| Available | On hand minus committed units | Using on hand as the sellable balance |
| Unit cost | Recorded acquisition cost used for analysis | Substituting retail price for cost |
2. Record every stock movement, not just the final balance
A balance tells you where inventory ended. A movement ledger explains how it got there. That explanation is what lets you investigate shrinkage, receiving errors and negative inventory instead of repeatedly overwriting the count.
For each movement, store the SKU, location, quantity change, movement type, timestamp, source document and person or system responsible. A sale might be linked to a receipt; a receipt to a purchase order; a transfer to both its sending and receiving locations; and an adjustment to a count or damage record.
- Receipts increase stock only when goods are actually received, not when a purchase order is created.
- Sales and write-offs decrease the relevant location balance.
- Returns need a condition decision before units become sellable again.
- Transfers should create linked outbound and inbound records so stock is not counted twice.
- Adjustments should require a reason such as count correction, damage, expiry or theft.
3. Reconcile the system with physical counts
Even a well-designed system drifts when a barcode is missed, a return is put back incorrectly or a receiving quantity is entered twice. A physical count is the control that tests the record against reality.
A full count checks everything at once but can interrupt operations. Cycle counting checks a manageable set of SKUs each day or week. Count high-value, high-volume and frequently adjusted items more often than stable low-risk items. Freeze or carefully control movements while a count is underway so the comparison uses the same point in time.
If 190 of 200 counted SKU-location records match the system within your approved tolerance, record accuracy is 95%.
4. Separate tracking from reorder planning
Inventory tracking answers how many units are available. Reorder planning asks whether more units should be purchased. The second decision needs more than a low-stock flag: demand rate, lead time, incoming stock, case packs, minimum order quantities, shelf life, storage space and available cash can all change the right order quantity.
Begin with a simple reorder point and review it whenever demand or supplier timing changes. If the inputs are uncertain, show the uncertainty rather than presenting a precise recommendation that the data cannot support.
At 4 units per day, a 7-day lead time and 10 units of safety stock, the basic reorder point is 38 units.
5. Use a simple operating rhythm
Assign each check to a role and define what requires approval. Inventory accuracy improves when the routine is visible and owned, not when everyone assumes someone else is watching it.
- Daily: investigate negative quantities, failed sales imports and unreceived transfers.
- Two or three times per week: review items below their reorder point and confirm incoming purchase orders.
- Weekly: cycle-count the highest-risk SKUs and review unexplained adjustments.
- Monthly: compare slow movers, stockouts, sell-through and inventory value by category.
- Quarterly: review SKU naming, duplicate records, obsolete items and supplier lead-time assumptions.
What inventory software should make easier
Choose software after defining the process. A useful system should preserve movement history, separate locations, connect counts to adjustments, export records, show source freshness and restrict sensitive actions. Integration does not automatically equal accuracy: imported data still needs mapping, duplicate controls and reconciliation.
Vanteloq currently supports tenant-separated operating records, purchase-order and receiving workflows, aggregate inventory visibility and a review-based reorder calculation. Automatic SKU recommendations still depend on verified SKU history and supplier inputs, so they should not be treated as live until those sources are connected and reconciled.
Sources and further reading
These sources support the accounting, platform or technical boundaries discussed in this guide. They are not endorsements of Vanteloq.
- Inventory and cost of goods soldCanada Revenue Agency
- IAS 2 InventoriesIFRS Foundation
- Managing inventoryLightspeed Retail Support
