How to Stop Stock Shrinkage in Kenyan Retail
Shrinkage is not one problem but five — theft, miscounts, damage, supplier short-delivery, and paper sales — and each hides in a different gap. Here is how Kenyan retailers close them.
Every retailer knows the feeling: the shelves moved, the till collected, and yet the month's numbers say you are poorer than the sales suggest. That gap has a name — shrinkage — and in Kenyan retail it routinely eats 2–5% of turnover, which for many shops is the entire net margin. The mistake is treating it as one problem. It is five, and each lives in a different gap in your process.
The five faces of shrinkage
| Type | Where it hides | The closing move |
|---|---|---|
| Theft at the counter | Sales made outside the system; drawer "errors" | Per-shift reconciliation with named attribution |
| Theft from the floor/store | Gaps between deliveries and shelf | Receiving against POs; cycle counts by section |
| Supplier short-delivery | Signed delivery notes nobody verified | Count at receiving, against the order, before signing |
| Damage & expiry | Write-offs that never got recorded | Damage log with reasons; expiry-dated stock rotation |
| Paper sales & informal credit | "I'll enter it later"; goods on trust to regulars | Every sale through the till — no exceptions culture |
The instrument: a live stock card
None of the closing moves work without one precondition: the system's stock number must be trustworthy. That means every movement — sale, receipt, transfer, damage, return — hits the record in real time. When POS and inventory are one system, the stock card is always current, and shrinkage shows up as a specific variance in a specific week, not a mystery at year-end.
Cycle counts beat annual counts
- Count a section weekly instead of the whole shop yearly — twenty minutes at opening, rotating so everything is counted monthly.
- Investigate variances the same day, while the CCTV footage and the memory both exist.
- Track variance by section and by shift over time — patterns identify causes better than any single count.
- Record every adjustment with a reason from a fixed list; free-text "correction" is where losses launder themselves.
The honest baseline
Your first verified full count will hurt — it always does. Take the loss, set the baseline, and measure from there. Retailers who avoid the first honest count to avoid the bad news simply pay the same bill monthly, invisibly.
People and incentives
- Named responsibility: every drawer, every section, every shift belongs to someone.
- Share the variance numbers with the team — measured openly, shrinkage becomes a shared score instead of a suspicion game.
- Reward accuracy, not just sales: a bonus tied to variance-under-threshold changes behavior faster than cameras.
- Make the compliant path fast: if entering a sale takes eight taps, staff will batch them "later". Two taps, no later.
Multi-branch retailers: shrinkage concentrates wherever head office cannot see. The visibility playbook is in running multi-branch retail without losing control, and the daily-close discipline that catches counter-level leaks is in the daily close done right.
What AWRA OpsHub does today
- Blind cycle counting that is genuinely enforced, with a separate permission required to reveal expected quantity.
- Variance rules on absolute quantity, percentage and value, which auto-adjust within tolerance and force approval beyond it.
- Adjustments with a reason from a configured catalogue, a named submitter and a separately-permissioned approver.
- Items locked while being counted, so a sale mid-count cannot invalidate the result.
- Per-location counting, so a section can be counted without closing the shop.
- Full audit logging of every movement.
More we can add to your workspace
- A supplier-invoice leg on the match. Delivered against ordered is now checked at receiving — an over-receipt is refused, a shortage flagged — but the invoice side of that entry point is not covered, because supplier invoice lines are not captured.
- Shift scoping on stock counts. Counts belong to a session, not a shift, so per-shift stock variance is not produced.
- Anomaly detection, flagging a user whose adjustments are unusual or a reason code suddenly spiking.
- A CCTV, EAS or POS-exception integration.
The counting half of shrinkage control is genuinely well built — enforced blind counts with tolerance-based approval is more than most retail systems give you. The receiving half used to be the weak point on this page and is now largely closed: deliveries are checked against the order at the door, over-receipts refused, shortages flagged. What remains is the invoice side — reconciling what a supplier charged against what they delivered — so a padded invoice against an accurate receipt is caught by a person today rather than by the system.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped additions, which are the ones readers ask for most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsGive shrinkage nowhere to hide
Enforced blind counts, tolerance-based variance approval, reason-coded adjustments and per-section counting — the counting half of shrinkage control, done properly.
See shrinkage control in AWRAFrequently asked questions
What is a "normal" shrinkage rate?
Well-run retail globally sits around 1–1.5% of turnover; Kenyan shops with weak controls commonly run 3–5% without knowing it. The target is not zero — damage and honest error exist — it is measured, explained, and trending down.
Cameras or systems — which first?
Systems. Cameras show you what happened after you already know something is wrong; the system tells you something is wrong in the first place, and narrows where to look. CCTV without variance data is hours of footage and no questions.
How do we handle informal credit to regular customers?
Formalize it — a customer account in the system with a credit limit, every issue recorded as a credit sale. The goodwill survives; the black hole does not. Informal credit is shrinkage with a friendly face.
Our staff say the system is too slow during rush hour. Now what?
Treat it as a real constraint: measure taps-per-sale and fix the workflow, add a second till, or pre-configure fast keys for top sellers. If the compliant path cannot keep up with the queue, staff will build a faster informal one.
