ABC analysis for warehouse inventory is a classification method that ranks SKUs into three tiers, usually A, B, and C, based on how much value or movement they contribute, so you can count the highest-impact items more often and the low-impact ones less often. In Shipider, that ranking connects directly to pallet and SKU tracking, so the A-tier items you count weekly are the same ones with the tightest movement history and audit trail, and a counting schedule stops being a guess.
Most warehouses count the wrong things at the wrong frequency. A $4 packaging insert gets the same quarterly cycle count treatment as a $400 component that drives half your revenue. ABC analysis fixes that mismatch by forcing a simple question for every SKU: how much does this item matter, and how often does that justify checking on it?
What ABC analysis actually measures
ABC analysis is a form of the Pareto principle applied to inventory. In most warehouses, a small share of SKUs accounts for most of the value that moves through the building. The classic split looks like this:
- A items: roughly 10-20% of SKUs, responsible for 70-80% of inventory value or usage.
- B items: roughly 20-30% of SKUs, responsible for 15-25% of value.
- C items: the remaining 50-70% of SKUs, responsible for only 5-10% of value.
Those percentages are a starting point, not a law. [NEEDS VERIFICATION: confirm whether to cite a specific published Pareto/ABC split study or keep this as a general rule of thumb without attribution]. What matters operationally is the shape of the curve: a few SKUs carry outsized weight, and your counting effort should track that weight, not the raw SKU count.
Value is the usual basis for classification, but it is not the only one. Depending on your operation, you might classify by:
- Annual dollar usage (unit cost multiplied by annual volume moved), the most common approach
- Pick frequency, useful if you are optimizing slotting alongside counting
- Risk or shrinkage history, useful for high-theft or high-damage categories
- Shelf life or regulatory sensitivity, relevant for lot and batch tracked goods
Whichever basis you pick, the output is the same: a tier label on every SKU that tells your team how much attention it deserves.
Why count frequency should follow value, not alphabet order
Cycle counting exists to catch discrepancies before they become a stockout, a mis-ship, or a write-off. If you spread count effort evenly across every SKU, you are spending the same labor hour on a low-value accessory as you spend on your top revenue driver. That is backwards. A items deserve more frequent counts because an error there costs more, both in dollar terms and in the downstream disruption to orders and customer promises.
This is also where ABC analysis differs from the mechanics of cycle counting without shutting down the warehouse. Cycle counting is the method you use to count without halting operations. ABC analysis is the logic that decides which SKUs get pulled into that count rotation and how often. You need both: the classification tells you what to count, the cycle count process tells you how to count it on a live floor.
| Tier | Typical share of SKUs | Typical share of value | Suggested count frequency | Why |
|---|---|---|---|---|
| A | 10-20% | 70-80% | Weekly to monthly | Highest dollar exposure per error, usually your fastest movers |
| B | 20-30% | 15-25% | Monthly to quarterly | Moderate value, worth regular checks without weekly overhead |
| C | 50-70% | 5-10% | Quarterly to annually | Low value per unit, errors here rarely move the needle |
Some warehouses add a fourth tier for obsolete or dead stock that gets counted only during an annual physical, or flagged for liquidation review instead of regular cycle counts at all.
Building your ABC classification
Step 1: Pull usage and value data
You need, at minimum, unit cost and either annual usage volume or annual dollar movement per SKU. If your warehouse data currently lives in spreadsheets, this is often the first real test of whether that data is trustworthy. Gaps here usually point back to the same root causes covered in how to calculate the inventory accuracy formula: incomplete receiving records, untracked adjustments, or counts that never made it back into the system of record.
Step 2: Rank and assign tiers
Sort SKUs by annual dollar usage from highest to lowest, then calculate a running cumulative percentage of total value. Draw the cutoffs where the curve bends: the point where cumulative value crosses roughly 70-80% becomes your A/B boundary, and where it crosses roughly 95% becomes your B/C boundary. These cutoffs are judgment calls, not fixed formulas. A warehouse with 50 SKUs will draw different lines than one with 5,000.
Step 3: Attach the tier to a count cadence
Once every SKU has a tier, convert that into an actual schedule: which locations get counted on which day, by whom, and how discrepancies get resolved. This is where the classification stops being a spreadsheet exercise and becomes a floor routine.
Step 4: Re-run the classification on a schedule
SKU velocity shifts. A seasonal item can jump from C to A for two months and drop back down. A product that used to be a top seller can decline into B or C territory as it ages out. Re-running the classification quarterly, or after any major demand shift, keeps the tiers honest.
Where ABC classification breaks down without the right system
The idea is simple. The execution usually is not, for three reasons.
Tiering lives in one file, counting happens on the floor. If your ABC spreadsheet is disconnected from your actual count assignments, nobody on the floor knows which bin is an A item today versus last quarter. The tier has to be visible at the point of the count, tied to the warehouse location and SKU record, not buried in a separate document.
There is no record of whether the count actually happened. A schedule that says "count A items weekly" is worthless if you cannot confirm it happened, who did it, and what they found. Shipider's real audit trail logs every count event against the SKU and location, so a weekly A-tier cadence is something you can actually verify, not just something you hope is happening.
Discrepancies get fixed quietly instead of flagged. If a counter finds a mismatch and just types in a correction, you lose the chance to catch a pattern, like a bin that keeps drifting short every month. Shipider's maker-checker verification means a count adjustment gets logged by one person and confirmed by a second before it becomes the new system quantity, so the correction is visible and attributable rather than silent.
Running ABC-driven counts with camera-based scanning
A tiered count schedule only works if the counting itself is fast enough that staff actually stick to it. Shipider's barcode scanning runs in the browser on any phone, so a picker can scan an A-tier bin location, confirm the SKU and quantity, and move to the next assignment without checking out a dedicated scanner gun first. For a weekly A-tier rotation across a few hundred bins, that speed difference is the gap between a schedule that happens and one that quietly slips.
Because every scan ties back to the same pallet and SKU records used for receiving and putaway, a discrepancy found during an ABC-driven count links straight to its movement history instead of starting an investigation from zero. If you want the mechanics of counting a live floor without pausing picking or shipping, see cycle counting without shutting down the warehouse.
Tracking whether the classification is working
ABC analysis is only useful if it improves your accuracy numbers over time. After a few count cycles under the new tier structure, check whether A-tier items are showing fewer discrepancies than before, and whether C-tier items still behave predictably at a lower count frequency. The relevant KPIs to watch, including count accuracy rate and discrepancy frequency by tier, are covered in inventory accuracy KPIs every warehouse manager should track. If A-tier discrepancies are not dropping despite more frequent counts, the problem is usually upstream, at receiving or putaway, rather than in the counting cadence itself.
For multi-site operations or 3PLs running several client inventories, ABC tiers should be built per site or per customer rather than blended together. A SKU that is a top mover for one client can be a slow mover for another, and a shared classification hides that. Shipider's multi-site inventory structure and multi-tenant isolation keep each customer's classification and count schedule separate, which matters for the 3PL operations where commingled data creates real billing and accuracy problems.
Frequently asked questions
What is the difference between ABC analysis and cycle counting?
ABC analysis is a classification method that sorts SKUs into value tiers. Cycle counting is the counting process itself, done on a rolling basis without a full warehouse shutdown. ABC analysis decides which SKUs get counted more often; cycle counting is how those counts actually get done on a live floor.
How often should A-tier items be counted?
Most warehouses count A-tier items weekly to monthly, since they represent the largest share of inventory value and the highest cost of error. B items typically fall on a monthly to quarterly cadence, and C items are counted quarterly to annually since their lower value means errors there have less financial impact.
Can ABC analysis be based on something other than dollar value?
Yes. While dollar usage is the most common basis, warehouses also classify by pick frequency, shrinkage or theft risk, or shelf-life sensitivity. The right basis depends on what kind of error is most costly in your specific operation.
How often should an ABC classification be updated?
Most warehouses re-run the classification quarterly, or immediately after a major demand shift such as a new product launch or a seasonal spike, since a SKU's tier can move as its sales velocity changes.
Does ABC analysis work for a 3PL managing multiple customers?
Yes, but the classification needs to be built separately for each customer's inventory rather than blended across the whole warehouse. A SKU that is a top mover for one client may be a slow mover for another, so a shared ABC tier would misrepresent both.
Ready to turn SKU tiers into a count schedule your team actually follows, with scans, audit history, and maker-checker verification built in? Create a free Shipider account and set up your first ABC-based cycle count rotation today.
Related reading: Inbound Quality Control: Catching Damaged Inventory at Receiving Before It Reaches the Floor