Warehouse root-cause analysis for recurring stock discrepancies

July 28, 2026

Recurring stock discrepancies are rarely about one “bad count”; they’re a symptom of deeper problems in your warehouse processes, systems or controls. Getting to the root cause is the difference between endlessly firefighting variances and running a stable, compliant, profitable operation. This guide shows UK warehouse and inventory managers how to do structured root-cause analysis that stands up to HMRC, UK GAAP and auditor scrutiny, with practical steps you can apply in any WMS or stock control environment.

Why stock discrepancies matter so much in the UK

In the UK, recurring inventory discrepancies are not just an operational headache – they have direct implications for tax, financial reporting and directors’ duties.

Under UK GAAP and IFRS, inventory must be recorded accurately at the lower of cost and net realisable value, with an auditable trail of movements and adjustments.[1] Material discrepancies that are not properly investigated and adjusted can lead to misstated cost of sales, profit and asset values.[1] HMRC expects businesses to maintain adequate records of stock and sales; poor inventory records can trigger questions on VAT, corporation tax and, in severe cases, investigations into potential evasion or fraud.[2]

Companies House filings for larger entities must reflect true and fair inventory values, and recurring unexplained variances will attract attention from auditors and potentially the board’s audit committee.[1] In practice, that means:

You need repeatable stock control procedures (cycle counting, year-end counts, adjustment authorisation).
You must be able to show your workings when you correct stock – who investigated, what they found, and how you’ve reduced the risk of recurrence.

A structured root-cause analysis (RCA) approach gives you that defensible story: not just “we wrote off 300 units”, but “we verified the variance, traced it to specific process failures, and changed controls to prevent it happening again”.[2][9]

The usual suspects: common causes of warehouse discrepancies

Before diving into the method, it helps to know the patterns you’re likely to find. Studies of warehouse operations show that most discrepancies cluster around a handful of process failures and human errors.[3][5][8][10]

Typical causes include:

Receiving errors – miscounts at the dock, wrong unit of measure, or incomplete paperwork when goods in are booked.[5][10]
Putaway and stowing mistakes – items put in the wrong location or different SKUs mixed in the same bin or pallet.[5][3]
Label and barcode issues – damaged, unclear or duplicate barcodes, or labels applied to the wrong pallet, causing incorrect scans.[5][8]
Transaction timing gaps – stock moved physically but the WMS or ERP updated later (or not at all), leaving phantom or double stock.[5][10]
Picking and packing errors – short picks, substitutions, or manual workarounds that aren’t recorded properly.[5][7][8]
Unrecorded damage, scrap and returns – damaged or returned items staying in saleable stock instead of being segregated and adjusted out.[5][8][10]
Data-entry mistakes – wrong SKU, location or quantity keyed in, often under time pressure.[7][10]
System and integration issues – poor links between WMS, ERP and e‑commerce platforms leading to diverging stock figures.[8][10]
Shrinkage – theft, misappropriation, or unrecorded losses in handling and transport.[3][10]

Root-cause analysis does not stop at “we miscounted”; it digs into why miscounts keep happening – for example, unclear SOPs, under-trained temps, poor lighting at the dock, or WMS workflows that encourage shortcuts.[9][12]

A practical root-cause analysis workflow for warehouse variances

For recurring stock discrepancies, you need a structured, repeatable playbook that your team can follow. The following workflow blends classic RCA tools (5 Whys, fishbone diagrams) with inventory-specific steps.[2][6][9][11][12]

1. Define the problem crisply

Start by writing a tight problem statement:

SKU/material number
Location(s) and storage type (bin, pallet, mezzanine)
Size of discrepancy (units and £ value)
First date it appeared and how often it recurs

For example: “SKU 12345 shows a negative variance of –180 units at pick face A-12, recurring weekly since early June, mainly on the late shift.”[9][12]

Clear definitions keep the investigation focused and help you later justify any write-off or adjustment to finance and auditors.[9]

2. Contain the impact

Before you investigate, stop the bleeding:

Mark the affected SKU/location as do not move in your WMS or on physical labels.[6][9]
Route orders temporarily to alternative stock (e.g. reserve locations) or trigger a second scan at pack-out for that SKU.[9]
If needed, introduce a short-term checker or supervisor sign-off for movements involving the problem item.[9]

Containment protects customers, prevents further variance, and shows HMRC/auditors you acted promptly once the issue was identified.[2][9]

3. Verify the variance with a structured recount

Never investigate on the back of a single count:

Conduct a blind count – do not show the expected quantity from the system to the counter.[2][6]
Use two independent counters where possible, record user IDs, timestamps and methods (manual, handheld, scale).[2][6]
If the variance is large or the area busy, break the count into sections (e.g. by bay or pallet) and recount each separately.[2]

Only once you’ve confirmed the discrepancy is real should you move on; false positives waste time and erode trust in the process.[2][11]

4. Map the end-to-end process

Sketch the full lifecycle of the problem SKU or location:

Supplier and inbound transport
Goods-in receiving and quality checks
Putaway, replenishment, slotting
Picking, packing, loading and despatch
Returns, damages, rework or kitting (if relevant)

Include systems touchpoints (WMS, ERP, e‑commerce) and handoffs between teams (goods-in to putaway, warehouse to transport, etc.).[9][10] A simple process map helps you see where transactions could be missed, duplicated or mis-coded.[9]

5. Pull the data and evidence

Next, assemble the facts:

WMS/ERP transaction logs for the SKU and location (receipts, picks, moves, adjustments) for at least 24–72 hours before the first variance and up to the present.[6][11]
Putaway and picking lists, exception codes, returns reasons, cycle-count history.[2][9][11]
Handheld scan logs for the relevant shifts, plus any photos of pallets, labels or damage reports.[6][9]
If available and proportionate, CCTV footage and interviews with the operators handling the item across different shifts.[4][9]

Keep this evidence attached to the case; it forms part of your audit trail, especially if the outcome is a material write-off or process change.[2][9][11]

6. Generate possible causes (blame-free)

Use a fishbone (Ishikawa) diagram or a simple brainstorm across categories:[4][9]

People (training, fatigue, supervision)
Process (SOPs, exception handling, sign‑off)
Equipment (scanners, scales, racking)
Environment (lighting, congestion, temperature)
Materials (packaging, labelling, mixed pallets)
Measurement (unit of measure, counting methods)

Capture every plausible cause without judging.[9] Mixed materials in pallets, human error and misalignment between physical transfer and recorded data often emerge as major contributors in case studies of warehouse RCA.[1][3][5]

7. Test causes with data and 5 Whys

Select the most likely causes, then:

Use 5 Whys: keep asking “Why?” until you reach a controllable underlying factor (usually 4–6 layers deep).[12]
Back each “why” with evidence – a log entry, an observed behaviour, a configuration setting.[9][12]
Cross‑check with unit-of-measure, label accuracy, WIP and unposted transactions, especially in manufacturing or kitting operations.[11]

For example, “wrong quantity picked” might trace to “pick face overfilled” → “no clear max bin quantity rule” → “slotting policy doesn’t consider case size, leading to mixed cartons and loose units in one bin”. That final step is the root cause you can fix.[5][9][12]

8. Confirm root causes and implement actions

Often there are multiple root causes – for instance, a flawed returns process plus poor labelling plus delayed system updates.[3][5][8][10] For each root cause:

Confirm it is systemic, not a one‑off exception.[9]
Design corrective actions (fix the current discrepancy) and preventive actions (change SOPs, WMS rules, training, layout).[9]
Assign owners, deadlines and success metrics (e.g. variance rate for the SKU, pick accuracy, cycle-count accuracy).[9]

Build changes into standard work, training plans, user permissions, barcoding schemes and cycle-count schedules so improvements survive beyond the next shift.[5][9][10]

UK practice vs EU, US and rest-of-world norms

The RCA mechanics are broadly similar worldwide, but the compliance and reporting context differs.

UK warehouses

Regulatory lens – HMRC focuses on the completeness and accuracy of records that underpin VAT and corporation tax calculations.[2] Frequent unexplained inventory adjustments may be challenged.
Accounting – Under UK GAAP/IFRS, inventory discrepancies must be investigated and material variances disclosed and adjusted with adequate evidence.[1]
Governance – Larger UK companies are expected to have robust internal controls over inventory; boards and audit committees will ask for RCA outputs on significant stock issues.[1]

As a UK manager, documenting your RCA – counts, logs, cause analysis, and actions – is essential not only for fixing the warehouse, but for demonstrating compliance to finance, auditors and regulators.

EU warehouses

EU operators working under national GAAP aligned to IFRS face similar requirements: accurate stock, traceable adjustments, and documented investigations.[1] However, labour and data‑privacy rules can affect how CCTV and staff interviews are used in RCA, requiring closer coordination with HR and works councils.[4]

US warehouses

In the US, the emphasis is often on:

Sarbanes‑Oxley (SOX) controls for public companies, where inventory accuracy is part of internal control over financial reporting.[1]
Shrinkage and loss‑prevention programmes, with strong focus on theft and fraud analysis.[3][10]

RCA work may be driven heavily by auditors and internal control teams, and US warehouses typically invest more in loss‑prevention analytics and exception reporting.[3]

Rest of world

Elsewhere, drivers vary: customs regimes, sector‑specific regulation (pharma, food, defence), or supply‑chain resilience pressures. The same RCA toolkit applies, but the reporting and documentation expectations differ. Multinational businesses should align RCA outputs with the most demanding jurisdiction they face, then scale down where appropriate.

Templates and checklists you can adapt

You can embed RCA into your daily warehouse routines with a few simple artefacts.

Root-cause analysis case form

For each recurring discrepancy:

Problem statement (SKU, location, date, variance, £ value)
Impact assessment (orders affected, service, compliance risk)
Containment steps taken
Recount results (counters, timestamps, quantities)
Transaction review summary (key anomalies found)
Fishbone diagram or cause list
5 Whys trail for each shortlisted cause
Confirmed root causes
Corrective actions (with owners and dates)
Preventive actions and control changes
Follow‑up metrics and review date

Investigation checklist for stock discrepancies

When a variance is flagged:

Isolate the SKU/location and stop movements.[6][9]
Blind recount by at least one independent counter; log details.[2][6]
Pull last 24–72 hours of transactions for the SKU and location.[6][11]
Check for unposted or duplicated transactions in WMS/ERP.[10][11]
Verify labels, barcodes and units of measure.[5][11]
Review receiving, putaway, picking, returns and damage processes.[5][8][10][11]
Interview operators across relevant shifts.[4][9]
Use fishbone and 5 Whys to identify root causes.[4][9][12]
Agree and document corrective/preventive actions.[9]
Update SOPs, training and system rules; monitor results.[5][9][10]

How RCA ties into WMS, barcoding, 3PLs and forecasting

Root-cause analysis is not a standalone exercise; it feeds improvements across your wider inventory ecosystem.

WMS and scanning – RCA often highlights configuration gaps: missing validation rules, weak permissions for adjustments, poor integration with ERP, or no alerts on negative stock.[8][10] Fixing these reduces error opportunities.
Barcoding and labelling – Many root causes trace back to poor barcode quality, inconsistent label formats or non‑scannable locations.[5][8] RCA findings should drive standardised labelling and regular print-quality checks.
Cycle counting – RCA outcomes help prioritise which SKUs and locations to count more frequently and which processes to observe during counts.[5][10]
3PL relationships – If your warehouse operations are outsourced, RCA gives you concrete evidence to discuss service failures, process changes and contract KPIs with your 3PL partner.
Demand forecasting and inventory accounting – Persistent discrepancies distort historical demand and margin analysis. Cleaning up the root causes improves the data feeding your forecasting models and the accuracy of your inventory valuation.[1][3][8]

Frequently asked questions

How often should we run root-cause analysis on stock discrepancies?
Reserve full RCA for recurring or high-impact variances – for example, discrepancies above a set £ threshold, or issues that have appeared more than twice in the same SKU/location in a month.[2][9] Smaller, one‑off variances can be resolved with a recount and simple transaction checks, but if a pattern emerges, switch to the full RCA workflow.

What tools do we need to do effective RCA in a warehouse?
You mainly need data visibility and discipline rather than fancy software: access to detailed WMS/ERP transaction logs, a structured case template, simple diagramming for process maps and fishbone diagrams, and the ability to pull scan logs and historical counts.[2][6][9][11] Many teams run effective RCA using spreadsheets and shared documents, then embed the resulting changes into their WMS rules and SOPs.

How do we stop RCA becoming a blame game with staff?
Make it explicit that RCA looks for process and system causes, not individuals to punish.[9] Use neutral language, focus on evidence, and involve operators in brainstorming causes and solutions. When findings point to training or staffing issues, frame changes around capability building and workload balancing, not personal fault.[9][12] A blame‑free culture encourages people to surface issues early, which is critical for long‑term inventory accuracy.

Conclusion

Recurring stock discrepancies are a warning light that something deeper is wrong in your warehouse processes, controls or systems. By applying structured root-cause analysis and documenting your findings, you can fix problems at their source, strengthen compliance with UK GAAP and HMRC expectations, and give your finance and audit colleagues confidence in the numbers. Start with one high‑impact SKU or location, run the full RCA workflow, and use the lessons to reshape your SOPs, WMS configuration and training – your accuracy, service levels and inventory ROI will all benefit.

References

Home » Information » Warehouse root-cause analysis for recurring stock discrepancies

Inventory Management, RCA, Route Cause Analysis, warehouse operations, WMS

Written by

AxioMedia