The sixty-second answer
Split the store into sections and count one or two a day. Walk the shelf and the matching backroom stock with a phone or earbud, and say each product and quantity out loud. Maple-AI turns that into a count sheet, you review it, and MapleInventory posts the difference as a variance. BDC calls this a cycle count [1].
Why do small stores struggle to keep inventory accurate?
Because every day adds a few small errors, and nobody has time to find them. A delivery gets received as 24 when 23 came in. A broken jar goes in the garbage without being written off. A customer walks out with something. The point of sale keeps selling from a number that is slowly moving away from what is on the shelf.
The fix is not complicated. BDC's advice is that to keep an inventory system accurate you need to regularly count actual inventory [2]. The problem is time. A full count in a convenience store with a few thousand products means closing, or staying up all night with a clipboard. So it happens once a year, if that, and the system is wrong for the other eleven months.
What is the difference between a cycle count and a full count?
BDC describes two common approaches. A cycle count means physically counting a small sample of your inventory, typically daily or weekly. A physical count means counting every item, typically annually or twice a year. Many businesses combine the two [1].
For a small store, cycle counting is the one that actually happens. Twenty minutes on a quiet Tuesday afternoon is realistic; eight hours on a Sunday night is not. And because each section is counted several times a year, errors are caught while someone still remembers the delivery that caused them.
How do you set up a cycle count plan for a small store?
- Divide the store into sections. Use the way the store is already laid out: aisle 1 left, aisle 1 right, the cooler, the cigarette cabinet, the backroom shelves. Each section should take ten to twenty minutes to count.
- Pair each shelf with its backroom stock. Count the chips on the shelf and the chips in the backroom in the same session. If you count them on different days, stock moved between them in the meantime looks like a gain in one place and a loss in the other.
- Rank by risk. High-value, small and fast-moving items get counted every week. Everyday grocery lines every few weeks. Slow, cheap items monthly or quarterly.
- Put it on a calendar. A rotating list, so Monday is always the cooler and Thursday is always aisle 3, is more likely to survive a busy month than good intentions.
What does a 20-minute voice count of one aisle sound like?
Here is a Tuesday afternoon count of the snack aisle and its backroom shelf in a convenience store.
- Check receiving (1 minute). Make sure this morning's snack delivery was received in the system. If it is still on the invoice clip, receive it first.
- Pick a quiet window. You will be counting products that are for sale, so do it when the till is not busy and ask whoever is on cash to call you if a customer buys something from the aisle mid-count.
- Top shelf, left to right (6 minutes). Phone in your pocket, one earbud in: "Doritos Nacho 235 gram, 7. Doritos Cool Ranch 235, 4. Lay's Classic large, 9. Ruffles All Dressed large, 11."
- Lower shelves (6 minutes). Same rhythm. When a product has a small size and a large size, always say the size, because "Lay's, 9" is ambiguous.
- Backroom shelf (4 minutes). Unopened cases are counted in the same unit the shelf is counted in: "Ruffles All Dressed large, 24" rather than "two cases." Do the case arithmetic in your head before you speak, or write the pack size on the shelf label so nobody has to guess.
- Review and post (3 minutes). The count sheet shows each product and the quantity you said. Fix anything that landed on the wrong product, then post. The variances against what the system expected come back as soon as it posts.
Shelf and backroom quantities for the same product add up, just as if you had written them on two lines of a paper sheet. What posts is the total for that product at that location.
How do variances turn into something useful?
A variance is the counted quantity minus the expected quantity. On its own, one variance tells you little. The pattern tells you a lot. BDC suggests tracking inventory count accuracy, which it defines as actual count divided by recorded count [2], as one of your regular inventory measures [1].
Look at variances by section and by product over several counts:
- The same product short every time points to theft or an unrecorded use, like staff taking drinks.
- A product over, and a similar product short by the same amount is almost always a receiving or scanning mix-up between two sizes or flavours.
- A whole delivery's worth off usually means the delivery was received twice, or not at all.
- A unit-sized error, like 11 counted where 132 was expected, is a case-versus-each problem. BDC specifically recommends consistent units of measure to avoid this [1].
Losses you find are an expense of the period in which they happen. IAS 2 recognises write-downs and all losses of inventories as an expense in the period the loss occurs [5], and frequent counting means the loss is recorded in the right month rather than piled onto year end.
Do cycle counts replace the year-end count?
They can support it, and in some cases may reduce it. At year end, inventory is valued at the lower of cost and fair market value under the Income Tax Act [4]. The CRA's archived interpretation bulletin on inventory valuation says that in the usual case a physical stocktaking should be carried out at year end, and that one is not required only where a reliable perpetual inventory system is in use and has been periodically verified against actual quantities on hand [3].
A store that cycle counts every section several times a year, with the count sheets and adjustments saved, has evidence of exactly that kind of periodic verification. Whether that is enough for your business is a question for your accountant. Many small stores still do a full count at year end and use cycle counts to make it quick and uneventful, because there are fewer surprises to chase.
The same bulletin also sets out conditions for the retail inventory method, which estimates cost from retail prices and is used where there are many different commodities for resale [3]. Counting still sits underneath that method: you need the quantity before you can apply any ratio to it.
What records should a voice count leave behind?
A voice count should leave the same trail as a paper one, and a better one if possible. The CRA describes an audit trail as the information needed to recreate the sequence of events related to a transaction, and notes it may link to front-end systems like point of sale and to stock inventories [6]. For a count, that means:
- Who counted, which section, and when.
- Each product and quantity counted, and what the system expected.
- The adjustment posted, and any note explaining it (a known breakage, a return to supplier).
Keep those records with the rest of your books, generally for six years from the end of the last tax year they relate to [7].
How does MapleInventory handle it?
MapleInventory keeps stock by product and location and posts each count difference as an adjustment in its stock ledger, so every variance is traceable to a count, a date and a person. Voice count is in preview: you speak the count, Maple-AI turns it into a count sheet, and nothing posts until you have reviewed it. See the related guides on the year-end count for a T2 and organising stock by bin location.