How To Investigate And Resolve A Stock Discrepancy: A Step-By-Step Guide

Stock Discrepancy is a difference between the quantity or condition of stock recorded in a system and what is physically found. This operational guide lays out a step-by-step investigation and resolution workflow warehouse teams can apply the moment a discrepancy is reported.

Act fast: the longer a discrepancy remains unresolved, the harder it becomes to trace its origin. A repeatable process with clear roles reduces investigation time, limits customer impact, and prevents recurrence.

Step 1 — Triage And Confirm

Begin by confirming the report and preserving evidence. Identify whether the issue is a quantity shortage, overage, or condition mismatch and gather the relevant transaction IDs and timestamps.

• Immediate Action: Place the affected SKU/location in exception status in the WMS to prevent it from being inadvertently picked or shipped.
• Recount: Have a second person perform a blind recount at the location to rule out simple counting mistakes.

Step 2 — Trace Recent Transactions

Query the WMS/ERP for all transactions involving the SKU during the window around the discrepancy: last receipts, putaways, picks, stock transfers, and returns.

• Check Receipts: Confirm the inbound ASN and receiving scan records. Unscanned goods are a frequent source of mismatch.
• Check Picks/Shipments: Compare shipping confirmations and carrier manifests to the system pick records.

Step 3 — Review Physical Handling And Security

Look for physical evidence: damaged pallets, open cartons, or misplaced tote bins. If theft is suspected, review CCTV and access logs for the relevant times and personnel.

• Facilities Check: Inspect nearby zones for mislocated inventory and check staging areas where split pallets are handled.
• Security Review: Pull camera footage for the dock and putaway routes during the suspect window.

Step 4 — Audit Master Data And Labels

Verify SKU master data, pack quantities, and barcode labels. A wrong pack quantity on the item master or duplicate barcodes can create persistent, confusing discrepancies.

• Master Data Audit: Confirm SKU, UPC/GTIN, dimensions, and case quantities in the WMS match supplier documentation.
• Label Check: Ensure pallet and case labels are readable and match the WMS records; re-label if necessary and scan to update the system.

Step 5 — Reconcile And Document

When you can reconcile the difference, record the root cause and corrective action in an incident log. If you cannot reconcile, escalate according to the severity and value involved.

• Reconciliation Entry: Create a system adjustment with a clear reason code (e.g., "damaged during receiving," "mispick") for audit trails.
• Escalation: For high-value items or repeated discrepancies, involve security and finance and schedule a forensic inventory count.

Step 6 — Apply Preventive Controls

Use insights from the incident to strengthen processes. Small administrative changes often stop a class of discrepancies from recurring.

• Process Change: If the root cause was unscanned putaway, add a required scan step and a managerial check for split pallet moves.
• Training: Retrain teams on exception handling and make the correct workflow easy to follow at the workstation.
• Technology: If frequent SKUs are causing problems, consider RFID for hands-free counts or smarter WMS rules that prevent negative inventory.

KPIs To Track After Resolution

Track whether corrective steps are effective by monitoring leading and lagging indicators.

• Resolution Time: Average time from discrepancy report to reconciliation or adjustment.
• Repeat Rate: Percentage of SKUs that generate repeated discrepancies within a defined period.
• Count Accuracy: Percentage of cycle counts matching system records for prioritized SKUs.

Quick Checklist For First 24 Hours

• Secure: Put location on hold to prevent further movement.
• Confirm: Recount with a second person.
• Trace: Pull recent transactions and CCTV for the time window.
• Document: Record the incident, actions taken, and any system adjustments.

In short, the Stock Discrepancy investigation succeeds when teams act quickly, follow a consistent triage workflow, and capture root causes for prevention. A disciplined cycle-count program, strict scan-based steps, and a simple escalation matrix turn one-off incidents into opportunities for continuous improvement.