An inventory audit tells you whether your Shopify numbers match reality. Here is the exact process to run one — whether you have 50 SKUs or 5,000.
Your Shopify inventory numbers are a record of what your system thinks you have. A physical count is a record of what you actually have. An inventory audit is the process of comparing the two — and reconciling every gap.
Most merchants avoid audits because they sound painful. The reality is that a well-structured audit takes less time than you think, and the information it produces is irreplaceable. You cannot make good buying decisions on inaccurate inventory data.
There are three main approaches, and which you choose depends on your catalogue size and how much operational disruption you can absorb.
Count every single SKU in your warehouse in one session. Usually done annually, often at year-end for accounting purposes. Requires shutting down receiving and shipping for the duration.
Best for: Stores under 300 SKUs, year-end accounting requirements, first-time audits.
Count a subset of your inventory on a rolling basis — a few SKUs every day or week — so that every product gets counted several times per year without a full shutdown.
Best for: Stores over 300 SKUs, operations that cannot pause for a full count, ongoing accuracy maintenance.
Count specific high-risk products — your highest-value SKUs, items with recent anomalies, or products approaching reorder point. Not comprehensive, but fast and targeted.
Best for: Investigating specific discrepancies, pre-reorder verification, quick accuracy checks.
A poorly prepared audit wastes everyone's time. Spend 30 minutes on this before you touch a single product.
1. Freeze inventory movements No receiving, no shipping, no inter-location transfers during the count. If you cannot fully freeze operations, do the count at the lowest-activity time (early morning, overnight, weekend).
2. Organise your warehouse Everything should be in its assigned location. Products scattered across multiple bins, on receiving docks, or in the wrong sections will cause undercounts and recount sessions.
3. Print or export your current Shopify inventory list This is your baseline — what the system says you have. Export it from Shopify admin: Products → Export → All products with inventory.
4. Assign counting teams For stores over 200 SKUs, assign two people to each zone: one counts, one records. Counting solo leads to errors. If budget allows, have a second team recount a 10–20% sample to catch first-pass mistakes.
5. Prepare count sheets List each SKU, product name, and location. Leave the expected quantity blank — counters should record actual counts independently, without anchoring to the Shopify number.
Go location by location, bin by bin. For each SKU:
For barcode-enabled operations, scan each unit rather than counting visually — it is faster and eliminates counting errors on large quantities.
Do not show counters the expected Shopify quantities before they count. Anchoring to the system number is the most common source of audit error — counters unconsciously round to match what the system says rather than what they actually counted.
Once counting is complete, compare physical counts against Shopify quantities for every SKU.
Calculate the variance for each:
Variance = Physical Count − Shopify Quantity
| Result | Meaning |
|---|---|
| Variance = 0 | Perfect match |
| Variance > 0 | System under-reports (phantom deficit) |
| Variance < 0 | System over-reports (phantom stock) |
Create a discrepancy list: every SKU where variance ≠ 0, sorted by absolute variance value descending.
Do not update Shopify immediately. First, investigate the discrepancies.
Common causes of positive variance (more physical than system): - Unprocessed returns that were restocked but not recorded - Receiving errors where more units were checked in than recorded - Mis-scanned products during fulfilment
Common causes of negative variance (less physical than system): - Theft (internal or external) - Damage or spoilage that was not recorded - Fulfilment errors (sold but not decremented) - Sync failures between Shopify and a 3PL or marketplace
For discrepancies above a threshold you define (e.g., more than 5 units or more than £50 in value), investigate before writing off. Sometimes the physical count is wrong — the unit is in a different bin, or a pallet is misplaced. A second count of flagged items catches these before you adjust.
Once you have investigated and are confident in your physical counts, update Shopify to match reality.
In Shopify admin: Products → [Product] → Inventory → Adjust quantity.
For each adjustment, record: - The reason (theft, damage, receiving error, fulfilment error, unknown) - The reference (your audit date and session ID) - Any supporting notes
This audit trail matters for accounting, insurance claims, and identifying recurring patterns.
After updating Shopify, calculate your overall audit results:
| Metric | Formula |
|---|---|
| Inventory accuracy rate | SKUs with zero variance / total SKUs × 100 |
| Shrinkage value | Sum of all negative variances × unit cost |
| Shrinkage % | Shrinkage value / total inventory value × 100 |
| Positive adjustments | Sum of all positive variance units |
| Net adjustment | Total positive adjustments − total negative adjustments |
Industry benchmark: an inventory accuracy rate above 95% is considered good. Below 90% indicates a systemic process problem that needs addressing.
Rather than one painful annual audit, a cycle count programme spreads the work throughout the year.
ABC-based cycle count frequency:
| Category | Definition | Count frequency |
|---|---|---|
| A items | Top 80% of revenue | Every 30 days |
| B items | Next 15% of revenue | Every 90 days |
| C items | Bottom 5% of revenue | Every 180 days |
This means your most valuable SKUs — the ones where a discrepancy is most expensive — are verified monthly. Your slowest-moving items are checked twice a year.
A store with 500 SKUs might have 50 A items, 150 B items, and 300 C items. That is roughly 50 + 50 + 50 = 150 SKU counts per month, or about 7–8 per business day — a manageable 20–30 minutes daily.
The problem with periodic audits is the gap between counts. If phantom stock appears on day 2 after your audit, it will not be caught until day 30. In a high-velocity store, that is a lot of damage.
CoreCaptain monitors your inventory movements continuously and flags statistical anomalies in real time — unexpected drops, spikes, or patterns that suggest a discrepancy is forming. Rather than discovering problems at audit time, you see them within hours of occurrence.
The Inventory Counting module also supports barcode scanning for cycle counts, making the physical count process faster and less error-prone.
An inventory audit is not a one-time event — it is a practice. The merchants with the most accurate inventory are not the ones who do the longest annual counts; they are the ones who have built continuous accuracy into their daily operations through cycle counting and real-time monitoring.
Run your first full audit to establish a baseline. Then build a cycle count schedule to maintain it.
CoreCaptain detects phantom stock, sync errors, and inventory discrepancies automatically. 14-day free trial, no credit card required.
Start Free Trial