Retail inventory management comes down to three recurring problems, whatever the store sells: running out of the things customers actually want, losing stock to shrinkage nobody's tracking, and losing track of it all once the SKU count climbs past what one person can hold in their head. Get reorder points, shrinkage, and multi-SKU tracking right, and most other inventory headaches in a retail business solve themselves.
Retail inventory management centers on three priorities: setting reorder points so popular items don't stock out, controlling shrinkage from theft, damage, or errors through regular counts, and tracking stock accurately across potentially hundreds of SKUs. Getting these right keeps cash from being tied up in the wrong stock. If you are weighing lean ordering instead of holding safety stock, see just-in-time (JIT) inventory management: how it works and its risks.
Key takeaways
- A reorder point is the stock level that triggers a new purchase order, calculated from average daily sales, supplier lead time, and a safety buffer.
- Shrinkage isn't mainly a theft problem — damage, administrative errors, and unwritten-off expired stock are often the bigger, more fixable share of the gap.
- Not every SKU deserves the same attention. Group products by value and sales velocity, and put tighter reorder points and more frequent counts on the ones that matter most.
- Retail's central tension is stockouts versus tied-up cash — the same tools (reorder points, counts, accurate costing) exist to make that a calculated tradeoff, not a guess.
- A regular stock opname is what actually reveals shrinkage. It's invisible in a system that only tracks recorded sales and purchases.
Reorder points: the first pillar of retail inventory management
A reorder point is the stock level that triggers placing a new purchase order, set so the remaining stock lasts through your supplier's delivery lead time without running out. The formula:
Reorder point = (Average daily sales × Supplier lead time in days) + Safety stock
The reorder point formula
Safety stock is a buffer for the parts you can't predict exactly — a slightly slower delivery, a slightly busier week.
Harborview General Store sells a reusable tote bag that moves at a fairly steady pace.
| Input | Value |
|---|---|
| Average daily sales | 12 units |
| Supplier lead time | 7 days |
| Safety stock buffer | 20 units |
| Reorder point | 104 units |
Reorder point = (12 × 7) + 20 = 104 units. When stock on hand hits 104 totes, it's time to place the next order — not when the shelf is nearly empty, and not by gut feel.
Get the lead time or the daily-sales estimate wrong and the whole calculation drifts, so revisit both whenever a supplier's delivery pattern changes or a product's sales pace shifts meaningfully — a reorder point set once and never revisited slowly stops matching reality.
What actually causes shrinkage
Shrinkage is the gap between what your books say you should have and what's physically there, and it comes from more sources than most owners assume:
- Theft — by customers or, less comfortably, staff.
- Damage — breakage, spoilage, or handling loss that's never formally written off.
- Administrative errors — a miscounted delivery, a return logged against the wrong SKU, a sale rung up incorrectly.
- Expired or unsellable stock — still sitting in the books as good inventory long after it stopped being sellable.
It's tempting to treat every shrinkage number as evidence of theft, but administrative errors and unwritten-off damaged stock are frequently the larger, more fixable share of the gap. A miscounted delivery and a broken item nobody logged are both cheaper problems to fix than theft — but only if you separate them instead of writing every discrepancy off as "shrink" without asking why.
A regular stock opname is the only reliable way to find shrinkage, because it's invisible to a system that only records transactions someone actually entered. If Harborview's books show 500 units of a product and a count finds 480, that's a 4% shrinkage rate on that SKU — a number that means nothing on its own until you investigate what caused it rather than just adjusting the books and moving on. Unwritten-off shrinkage also inflates closing inventory, which quietly understates cost of goods sold until a count catches it — it's one of the common inventory and costing mistakes that compounds the longer it goes unchecked.
Managing stock across many SKUs
A shop with 30 products can track everything by memory. A shop with 800 can't, and treating every SKU with the same level of attention wastes effort on the ones that don't need it while under-watching the ones that do.
Group SKUs by value and movement speed instead:
| Group | Typical treatment |
|---|---|
| High-value or fast-moving | Tight reorder points, frequent cycle counts |
| Mid-range | Standard reorder points, count each full opname |
| Low-value, slow-moving | Looser reorder points, counted less often |
This is the same logic behind classic ABC inventory analysis: a small share of SKUs usually represents a disproportionate share of sales value, and that's where reorder-point accuracy and count frequency pay off most. A slow-moving, low-value item running out for a week barely registers; a top-selling item running out for a week is a real revenue loss and a customer who may not come back to check again. Retail's inventory profile also tends to differ meaningfully from food and beverage stock management, where perishability forces daily attention regardless of a SKU's value tier.
Turning this into a weekly routine
None of this works as a one-off project. A workable retail rhythm looks like:
- Check reorder-point alerts against actual stock levels a few times a week, not just when someone happens to notice an empty shelf.
- Run cycle counts on your highest-value or fastest-moving SKUs every week or two.
- Run a full stock opname monthly or quarterly, investigating variances rather than just adjusting them.
- Recalculate reorder points whenever a supplier's lead time or a product's sales pace changes noticeably.
Reyuko's Product record carries a minimum-stock threshold per SKU, and the app flags any product that falls below it — the practical version of a reorder point, without recalculating the formula by hand every day. If you sell from more than one place, Inventory → Locations tracks stock separately per location, with stock transferable between them, so a reorder alert reflects the right shop or warehouse.
When it's time to check for shrinkage, Inventory → Inventory Checking is Reyuko's guided stock opname screen: it shows book quantity next to what you actually count and the difference, and saving it automatically creates the adjustment — no separate spreadsheet reconciliation. Serial number, batch, and expiry tracking are also available, useful once a retailer carries high-value or perishable SKUs among its mix.
None of this is limited to a paid plan — inventory tracking, minimum-stock alerts, multi-location stock, and stock opname are all in Reyuko's free edition.
Work out your own reorder point
A shop sells a product at an average of 8 units a day. The supplier takes 10 days to deliver, and the owner wants a 15-unit safety buffer. What's the reorder point?
Answer: (8 × 10) + 15 = 95 units.
Reyuko