Inventory Audit Checklist: Step-by-Step (2026)
A good audit is the difference between numbers you can trust and numbers you merely hope are right. This inventory audit checklist gives you the full sequence — before, during and after the count — as a copyable checklist you can use straight away, plus a worked reconciliation example and the mistakes that quietly wreck audits. Copy the tables below into your own document or spreadsheet and adapt the rows to your operation.
What an inventory audit actually checks
An inventory audit verifies that the stock recorded in your system matches the stock physically on your shelves, and that its recorded value is correct. It is broader than a stocktake: a stocktake counts units, while an audit also tests your processes — how receiving, picking, adjustments and write-offs are recorded — to explain why any discrepancy exists. The goal is not only an accurate count today, but a system you can trust between counts.
The copyable inventory audit checklist
Work through these phases in order. Tick each item as you complete it and assign an owner so nothing falls between roles.
Phase 1 — Before the audit (preparation)
| Done | Task | Owner |
|---|---|---|
| ☐ | Decide the audit scope: full count, cycle count, or a specific category/warehouse | Ops manager |
| ☐ | Choose a date with low or paused movement (after close, or a scheduled freeze) | Ops manager |
| ☐ | Freeze stock movements, or record the exact cut-off time for in-flight orders | Ops manager |
| ☐ | Print or export a system stock report as the baseline (SKU, description, location, system qty) | Inventory lead |
| ☐ | Confirm every item has a scannable barcode or clear label | Inventory lead |
| ☐ | Tidy and organise the count area; group like items; segregate damaged/quarantine stock | Warehouse team |
| ☐ | Assign counters in pairs and split zones so no zone is counted twice or missed | Ops manager |
| ☐ | Brief counters on count units (each vs case vs pallet) and how to log discrepancies | Inventory lead |
| ☐ | Charge scanners/devices and test the counting sheet or app | Inventory lead |
Phase 2 — During the count
| Done | Task | Owner |
|---|---|---|
| ☐ | Count zone by zone, top to bottom, left to right — a fixed path prevents skipped shelves | Counter A |
| ☐ | Scan the barcode and enter the physical quantity; do not read the system figure first | Counter A |
| ☐ | Blind-count where possible: counters should not see the expected number | Counter A |
| ☐ | Have a second person recount any line that differs materially from the system | Counter B |
| ☐ | Record damaged, expired or unsellable stock separately, not in sellable quantity | Counter B |
| ☐ | Note items found in the wrong location or without a label | Counter B |
| ☐ | Mark counted shelves with a tag or tape so nothing is double-counted | Counter A |
Phase 3 — After the count (reconciliation and sign-off)
| Done | Task | Owner |
|---|---|---|
| ☐ | Compare physical counts to the system baseline; calculate variance per SKU | Inventory lead |
| ☐ | Investigate any variance above your threshold (for example ±2% or ±5 units) | Inventory lead |
| ☐ | Trace root causes: mis-receipts, unrecorded sales, theft, damage, unit-of-measure errors | Ops manager |
| ☐ | Post approved adjustments with a reason code and a note for the audit trail | Ops manager |
| ☐ | Recalculate inventory accuracy: (SKUs matched ÷ SKUs counted) × 100 | Inventory lead |
| ☐ | Value the stock and reconcile to the general ledger with finance | Finance |
| ☐ | Document findings, corrective actions and the next audit date; get sign-off | Ops manager |
Worked example: reconciling a variance
These figures are illustrative. Suppose you count SKU BOT-500 and record 182 sellable units, but the system shows 190. That is a variance of −8 units, or −4.2%, which is above a ±2% threshold, so it needs investigation. A second counter confirms 182 physical units. Checking the audit trail, you find two units logged as damaged last week but never written off, and a case of six sold in a manual counter sale that was recorded against the wrong SKU. Correcting the mis-keyed sale (−6) and posting the damage write-off (−2) fully explains the gap. You post the adjustments with reason codes, and BOT-500 now reconciles. The lesson: a variance is a question, not a verdict — the trail usually holds the answer.
How to calculate inventory accuracy
Two simple measures matter. SKU accuracy is the share of counted SKUs whose physical quantity matches the system: if 470 of 500 SKUs match, that is 94%. Unit accuracy weights by quantity and is stricter. Track both over successive audits; a rising trend tells you your processes are improving, while repeat offenders point to a specific step — often receiving or manual adjustments — that needs tightening.
How often should you audit?
A full annual count satisfies most accounting needs, but it is a poor way to keep numbers accurate day to day. Layer in cycle counting: count a small, rotating subset of SKUs each week, prioritising high-value or fast-moving lines (an ABC approach). This spreads the workload, catches errors within weeks rather than a year, and usually removes the need to shut down for a single dreaded stocktake.
Common mistakes to avoid
- Counting while stock is still moving. Without a freeze or a clear cut-off, in-flight orders guarantee false variances.
- Letting counters see the expected number. Non-blind counts invite people to “confirm” the system rather than count reality.
- Mixing sellable and damaged stock. If unsellable units are counted as sellable, your available figure overstates what you can actually ship.
- Adjusting without a reason code. Unexplained adjustments hide the root cause and make the next audit just as painful.
- Unit-of-measure errors. Counting a case as one “each”, or vice versa, is one of the most common and largest sources of variance.
- Only auditing once a year. Annual-only counts let errors compound for months before anyone notices.
How WhiteBox helps
WhiteBox keeps a real-time source of truth for stock across every channel and warehouse, so your audit baseline is accurate before you start and every adjustment carries a reason code and an audit trail. Barcode picking and packing, multi-warehouse counts and reporting make cycle counting routine rather than a once-a-year ordeal, and stock stays synced across Shopify, Lazada, Shopee, Amazon and TikTok Shop so counts are not undermined by overselling. See how it works on our inventory features page or start a free trial.
Frequently asked questions
What is an inventory audit checklist? It is a structured list of tasks covering preparation, counting and reconciliation, used to verify that physical stock matches system records and that the process behind the numbers is sound.
What is the difference between a stocktake and an inventory audit? A stocktake counts units; an audit also tests why any discrepancy exists by tracing receiving, sales, adjustments and write-offs, and reconciles the value to your accounts.
What is a good inventory accuracy percentage? Many well-run operations target 97% or higher on SKU accuracy. The more useful goal is a steady upward trend and shrinking repeat variances.
Should I stop operations to audit? For a full count you usually freeze movement briefly, ideally after hours. Cycle counting avoids shutdowns by counting a small rotating subset while the business runs.
What variance threshold should trigger an investigation? Set a threshold that fits your value and volume — for example ±2% of quantity or a fixed unit count — and investigate anything above it rather than every tiny difference.
Related reading: Inventory Management Guide, Stocktake Checklist and Free Template, SKU Naming Conventions and Examples, Best Inventory Management Software in Singapore.
