Shrinkage
Shrinkage is the loss of inventory that shows up as a gap between what your records say you hold and what is physically there, with no recorded sale or movement to explain it. Causes include theft, damage, supplier short shipments, errors and expired stock never written off. It is usually expressed as a percentage of inventory value.
Free during open beta. No card. No sales call.
How to calculate shrinkage
Shrinkage rate = (recorded inventory value - counted inventory value) / recorded inventory value.
For example, your system values stock at 250,000 before a count. After counting, investigating and correcting explainable differences, the counted value is 246,500. Shrinkage is 3,500, or 1.4% of recorded value. You can calculate the same thing in units per SKU, which is more useful for finding the cause than a single warehouse-wide percentage.
Common causes of warehouse shrinkage
- Receiving errors: a short delivery accepted as complete, or cases keyed as single units.
- Picking errors: the wrong SKU shipped, which leaves one item short and another over.
- Unrecorded damage: broken units thrown away without an adjustment.
- Theft, internal or external.
- Samples, internal use and replacements given out without a transaction.
- Expired or spoiled stock discarded without a record.
Shrinkage vs count variance
A count variance is the signed difference found at a single count. It can be positive or negative, and many variances are not losses at all: stock was put in the wrong bin, or a receipt wasn't posted yet. Shrinkage is the net loss that remains after those differences are investigated and explained.
That distinction matters. If you post every variance straight to a loss, you inflate shrinkage and hide the process errors that caused the difference in the first place.
How to reduce shrinkage
- Scan every receipt against the purchase order or ASN and record receiving variances at the dock rather than discovering them later.
- Scan-verify picks and packs so wrong-item errors are caught before the parcel leaves.
- Use blind counts so counters record what they see, not what the system expects.
- Require a reason code on every stock adjustment, and review adjustments by reason, SKU and user.
- Limit who can adjust stock, and require approval above a threshold.
- Count high-value and high-theft items more often.
How NextStock handles shrinkage
In NextStock every quantity change is a movement with a reason and a reference, and balances always equal that ledger, so unexplained change can't hide in an edited number. Receiving records over, short and damage variances. Counts support blind counting, recounts and variance approval, adjustments require a reason, and damaged stock can be moved to its own status instead of being silently removed. Role permissions control who can adjust. See cycle counting for the count flow.
Part of the NextStock warehouse glossary. Browse the full glossary