What shrinkage actually is
Shrinkage is the gap between the stock your system says you have and the stock you can actually sell. Industry estimates commonly put it at 2 to 4 percent of sales; in grocery margins, that can exceed the store's entire net profit. The uncomfortable part: in most shops the majority of it is process leakage, not dramatic theft.
The four places margin leaks
- Expiry and damage: short-dated stock discovered after it is unsellable, especially dairy, bakery and frozen.
- Receiving gaps: cartons signed for but never counted, supplier shortages absorbed silently.
- Counter leaks: unscanned items, wrong quantities, unauthorized discounts and voided bills that walk out the door.
- Paper inventory: stock adjusted in a notebook, transfers between branches that exist only in a phone call.
Control 1: batch and expiry tracking
Recording batches and expiry dates at receiving turns expiry from a discovery into a schedule. The system flags short-dated stock weeks ahead, while there is still time to discount, bundle or return it to the supplier. Stores that do this stop donating their dairy margin to the bin.
Control 2: disciplined receiving and transfers
Every carton gets counted against a purchase order; every branch movement is a recorded transfer, not a favor between managers. This sounds bureaucratic and takes about thirty extra seconds per delivery. It also removes the two largest unexplained variances most supermarkets carry.
Control 3: counter accountability
Role-based permissions, approval-gated discounts and a visible audit trail on voids change counter behavior on their own. Cashiers are not villains; ambiguity is. When every void has a name and a timestamp, disputes drop and patterns surface early.
Cycle counts close the loop: counting a small slice of the store daily keeps the system honest without ever shutting for a full stock-take.
Where the POS fits
None of these controls survive on paper. They work when the till, the inventory and the books share one database: the sale decrements the batch, the receiving posts against the PO, the void hits the audit log, and the variance report writes itself.
That is the design premise of MondayPOS: one system from the scanner to the ledger, so the shrinkage report is a number you act on, not a number you argue about.