A picker pulls up SKU 7842 on a handheld and the system says 120 units in aisle C. She walks to the bin and counts 104. That 16-unit gap is an inventory discrepancy, and it’s quietly costing the business money every day it stays unresolved.
Every company that holds stock runs into this problem. The question isn’t whether a discrepancy will show up this quarter. It’s how fast teams can spot it, how well they investigate the root cause, and how they stop the same mistake from happening next month.
This guide walks through the four types of discrepancies, the real business impact, the formula to measure the gap, seven common causes, and an 8-point prevention playbook. If teams have been treating discrepancies as a quarterly annoyance, there’s accuracy, customer trust, and cash being left on the table.
What Is an Inventory Discrepancy?
An inventory discrepancy is a mismatch between the quantity a system says is on hand and the quantity actually sitting on the shelf. Digital records and the physical count don’t agree, and that’s a problem.
The gap usually surfaces during a cycle count, a full physical audit, or at the moment a picker goes to fulfill an order and the item isn’t where the records said it would be. Sometimes finance flags it during inventory reconciliation at month-end close.
The gap can go in both directions. The system shows fewer units than actually exist (overage), or it shows more units than truly exist (shortage). Both cause problems. Shortage is more painful because it leads to stockouts and broken customer promises. Overage is quieter, but it still distorts cost of goods sold, tax reporting, and replenishment logic.
The core issue is data reliability. When inventory records can’t be trusted, every downstream decision suffers: purchasing, sales forecasts, warehouse layout, customer service. Inventory Record Accuracy (IRA) is the KPI that tracks this, and best-in-class operations hold IRA above 97%. Anything under 90% and the ops team is flying blind.
How to Calculate an Inventory Discrepancy (Formula and Example)
The math is simple:
Inventory discrepancy = System count − Physical count
A positive result means the system is overstating inventory. A negative result means more goods exist than the system knows about.
Here’s a concrete example. The inventory system shows 500 units of a moisturizer SKU. The team does a physical count and records 472 units. The discrepancy is 500 − 472 = 28 units.
To express it as a percentage:
Discrepancy % = (|System count − Physical count| / System count) × 100
So (28 / 500) × 100 = 5.6%. That’s a meaningful gap. In retail and eCommerce, anything above 2–3% at the SKU level is a red flag worth investigating the same day.
The percentage matters more than the raw number. A 10-unit gap on a 10,000-unit SKU is noise. A 10-unit gap on a 200-unit SKU is 5% of the shelf gone missing, and the team needs to know why.
The 4 Types of Inventory Discrepancies
Most articles lump all discrepancies together. In practice, there are four types, and each one has a different fix. Knowing which one a team is dealing with cuts investigation time in half.
| Type | What it looks like | Most common cause | Business impact |
|---|---|---|---|
| Shortage (system > physical) | System says 100, shelf has 85 | Theft, shrinkage, picking errors, unlogged sales | Stockouts, lost revenue, customer complaints |
| Overage (system < physical) | System says 100, shelf has 115 | Unposted receipts, missing return entries, data entry errors | Inflated inventory value, wrong reorder signals |
| System-only phantom | Item exists in the system but not physically anywhere | Wrong SKU creation, duplicate product records | Broken order fulfillment, wasted purchasing |
| Physical-only ghost | Item is on the shelf but doesn’t exist in records | Receiving skipped, sample/return not logged | Revenue leakage when sold off-system |
Shortage gets most of the attention because it’s the one customers feel. But overage and ghosts are just as damaging over time. A ghost SKU sold off the books is revenue that can’t be reported, and a phantom record clogs up the reorder system with purchases nobody needs.
Start every investigation by classifying the gap. The rest of the workflow flows from there.
7 Common Causes of Inventory Discrepancies
Every gap traces back to one of these causes. Most operations deal with a mix, which is why isolated fixes rarely work.
1. Human Error in Data Entry
Someone types 10 when they mean 100. A barcode gets scanned twice. A transfer between sites is logged in the origin but not the destination. Manual entry is the single biggest source of inventory errors, and it scales linearly with order volume.
2. Theft and Shrinkage
Shrinkage covers both external theft (shoplifting) and internal theft (employees pocketing items). It also includes damage, spoilage, and items vanishing in transit. The National Retail Federation pegs total shrinkage in US retail at roughly 1.6% of sales, which is a staggering number once applied to revenue.
3. Misplaced or Lost Items
An item gets put back on the wrong shelf after a physical count. A pallet gets moved to make room for a shipment and never logged into its new location. During the next count, the goods appear missing even though they’re technically in the building. Poor labeling and loose put-away rules make this worse.
4. Receiving and Shipping Errors
A supplier ships 48 units instead of 50 and receiving marks the PO complete. A packer sends out two units of the wrong variant in a customer order. Both create a discrepancy the moment they happen, and both compound if shipping and receiving aren’t cross-checked against the purchase order.
5. System Integration Issues
The point-of-sale system doesn’t sync with the inventory management system in real time. A sale on Shopify processes but the count on the wholesale channel doesn’t update for 6 hours. During that window, both channels sell from the same pool, and the retailer ends up oversold. This is one of the most common sources of stock problems for multi-channel sellers.
6. Damaged or Expired Items
Units get damaged on the receiving dock but still show as sellable. A batch hits its expiration date and nobody scraps it out of records. The recorded quantity looks healthy. Actual sellable quantity isn’t. This is where FIFO (First In, First Out) discipline saves the operation.
7. Returns Mishandling
A customer returns a product. The team inspects it, decides it’s fine, puts it back on the shelf, and forgets to mark the return processed in the system. Or the opposite: the return is logged but the item ends up in a reject bin without a transaction. Returns are a known weak spot in inventory processes, which is why dedicated return workflows matter.
The Real Business Impact of Inventory Discrepancies
It’s easy to treat discrepancies as a warehouse problem. They’re not. They ripple through the whole business.
Lost revenue. When the system says there’s stock that doesn’t exist, orders get accepted that can’t be fulfilled. Every canceled order is a refund plus a customer who probably won’t come back. Research on churn suggests that a single fulfillment failure raises the probability of losing a customer by 30–40%.
Inflated carrying costs. When the system underestimates actual goods on hand, purchasing reorders product that wasn’t needed. Cash gets tied up in extra units, warehouse space fills up, and holding costs climb. For most SMBs, carrying cost is between 20% and 30% of inventory value per year. Overordering by even 5% hurts.
Broken financial reporting. Inventory is an asset on the balance sheet. When stock records are wrong, cost of goods sold is wrong, gross margin is wrong, and tax liability is wrong. Auditors flag this fast, and variances over a certain threshold trigger mandatory write-offs.
Damaged supplier relationships. Frequent stock discrepancies lead to erratic reorder behavior: big rush orders one week, cancellations the next. Suppliers notice. Preferred terms disappear and lead times stretch out.
Slow operational decisions. When the team doesn’t trust the numbers, everything slows down. Every order gets double-checked. Every reorder needs a visual verification. That drag compounds until the ops team is spending 30% of its time working around bad data instead of fulfilling orders.
How to Investigate an Inventory Discrepancy: A 6-Step Playbook
Don’t just adjust the records and move on. Investigate. Otherwise the same gap reappears next quarter.
- Stop and isolate. Pause the operation where the gap surfaced (cycle count, order fulfillment, receiving). Don’t let more transactions touch that SKU until the cause is clear.
- Recount with a fresh pair of eyes. Have someone uninvolved in the first count do a second physical count. Rule out the possibility that the gap is a counting mistake, not an actual variance.
- Check units of measure. If the gap is a round multiple of the pack size, it’s probably a shipment received in the wrong unit of measure (cases logged as each, or vice versa). Classic ERP error.
- Review the transaction history. Pull every transaction for that SKU over the last 30 days: sales, receipts, transfers, adjustments, returns. Look for missing entries, duplicated transactions, or wrong quantities.
- Check nearby locations. Misplaced goods are the most common root cause. Search the adjacent bins, the receiving dock, the returns area, and any overflow storage.
- Document the root cause and fix the process. Once the cause is clear, adjust the records and write down the reason. If a picker made the same error three times, retrain. If a supplier shorted a PO twice, escalate with procurement.
Don’t expect to fix every variance at the root. Some will stay classified as “unknown.” But the team should trace at least 70% of discrepancies to a specific cause. Anything less means process tracking is too loose.
How to Prevent Inventory Discrepancies: 8 Best Practices
Investigation handles the symptoms. Prevention handles the cause. These eight practices, applied together, will push IRA above 98% within two quarters.
- Run cycle counts, not annual stocktakes. Count a slice of the operation every week instead of shutting down for a 3-day annual audit. ABC cycle counting (A-class SKUs monthly, B-class quarterly, C-class annually) is the most efficient rhythm for SMBs.
- Barcode or RFID everything. Manual data entry is the single biggest source of inventory errors. Barcode scanning cuts data entry mistakes by roughly 80% according to GS1 studies. RFID goes further for high-value goods.
- Write SOPs for every movement. Receiving, put-away, picking, packing, transfers, returns. Each one needs a documented process with checkpoints. Consistency is what keeps human error from compounding.
- Train staff on the why, not just the how. When a packer understands that one mis-scan costs the company a customer, they scan carefully. Training that starts with business impact sticks better than training that starts with button clicks.
- Reconcile receipts against purchase orders daily. Don’t let a supplier shortage slip through because receiving marked the PO complete without verifying. A 5-minute reconciliation at end-of-day catches most receiving errors.
- Integrate sales channels in real time. If Shopify, a wholesale portal, and the warehouse all pull from the same live source, the biggest category of multi-channel discrepancies disappears. This is table stakes for modern inventory management.
- Track IRA as a KPI. What gets measured gets managed. Report Inventory Record Accuracy weekly at the site level and monthly at the SKU level. Set a target (we recommend 98%) and hold the ops team accountable.
- Review the top 10 variances every month. A short monthly review of the biggest gaps, with the site lead, ops manager, and finance partner in the room, surfaces systemic issues before they become quarterly surprises.
Tools and Technology That Reduce Discrepancies
The tech stack matters. An operation running on spreadsheets will always have more variances than one running on a proper inventory management system, no matter how careful the staff is.
A modern cloud-based platform such as Qoblex centralizes goods across channels, syncs sales and receipts in real time, and fires alerts the moment a physical count diverges from the records. For businesses operating across Shopify, WooCommerce, Amazon, and wholesale portals, a single source of truth is what keeps IRA high.
Barcode scanning on mobile devices handles the operational layer. A warehouse management system (WMS) adds bin-level tracking and guided put-away. For high-value goods, RFID adds automatic, continuous counting without any manual scanning. The stack scales with the complexity of the operation, but the principle is the same: replace manual data entry with automation, and discrepancies drop.
We’ve seen SMB clients go from 88% IRA to 98% IRA in a single quarter after moving from spreadsheets to a connected stack. The ROI usually shows up first in fewer stockouts, then in lower carrying costs, then in cleaner month-end financials.
Inventory Discrepancy FAQ
What is a discrepancy in inventory?
A discrepancy in inventory is a gap between the quantity recorded in an inventory management system and the quantity physically present on the shelf. It can be a shortage (less than recorded) or an overage (more than recorded). Both point to a data reliability problem that needs investigation.
What are the four types of inventory discrepancies?
The four types are: shortage (system count higher than physical), overage (system count lower than physical), system-only phantoms (items in records but not physically present), and physical-only ghosts (items physically present but not in records). Each type has a different root cause and needs a different fix.
How do you handle inventory discrepancies?
Handle a variance in six steps: stop and isolate the SKU, recount with someone uninvolved, verify the unit of measure, review the last 30 days of transactions, check nearby locations for misplaced goods, then document the root cause and fix the process that caused it. Don’t just adjust the ledger and move on, or the same gap will reappear.
How do you calculate inventory discrepancy?
The formula is: Inventory discrepancy = System count − Physical count. To express it as a percentage, divide the absolute difference by the system count and multiply by 100. A value above 2–3% at the SKU level is typically worth investigating on the same day.
How often should a team run cycle counts?
Cycle counts should follow an ABC rhythm: count A-class SKUs (the 20% of items that drive 80% of revenue) monthly, B-class quarterly, and C-class annually. This keeps top-value goods accurate without shutting the operation down for a full physical count.
Ready to cut inventory discrepancies in half? Try Qoblex free for 14 days and see how real-time sync, multi-site tracking, and automated cycle counts change the operation. No credit card required.
![Inventory Discrepancy: Causes, Formula and 8 Fixes [2026]](https://qoblex.com/wp-content/uploads/2026/05/inventory-discrepancy-featured.png)
