5.1 Inventory classification: ABC analysis

Applying the same level of physical control to a highly complex, expensive FPGA and a standard passive resistor is inefficient. It misallocates labor and exposes the operation to trackable financial variances. Inventory ABC Analysis provides a risk management framework for the warehouse. It dictates where to focus cycle counting efforts to ensure high accuracy on the critical items that represent the bulk of the inventory value.

Classification logic: financial value + operational criticality

Note that Inventory ABC Analysis focuses on physical security and cycle counting inside the warehouse, whereas Spend ABC (covered in Chapter 1.3) drives commercial negotiation.

The pareto baseline (annual usage value)

Every active SKU in the ERP must be ranked by its Annual Usage Value: (Unit Cost × Annual Velocity).

Class A: Top 80% of total Inventory Value (typically representing 10–20% of the physical SKU count).
Class B: Next 15% of total Inventory Value.
Class C: Bottom 5% of total Inventory Value (typically representing 50–60% of the physical SKU count).

The “strategic override” (criticality dependency)

Financial valuation alone is insufficient if a very inexpensive part can halt the SMT line. Manual overrides within the ERP must be used to upgrade a classification when operational risk demands it:

Pilferage Risk: Small, highly desirable items (e.g. SD cards, consumer SSDs) should often be flagged as Class A.
Long Lead Time / Single Source: Standard proprietary parts with extended lead times (e.g. 52 weeks) should be upgraded to Class B (at minimum) to ensure more frequent verification.

Control intensity matrix

The classification dictates the rigor of physical handling. The Warehouse Management System (WMS) must be configured to enforce these rules structurally.

ERP Class	Definition (Value)	Cycle Count Frequency	Accuracy Target	Access Control	Counting Method
A	Top 80%	Monthly (12x / yr)	> 99%	Restricted Access Cage	Physical Unit Count (1:1)
B	Next 15%	Quarterly (4x / yr)	~ 98%	Standard Aisle	Physical Unit Count
C	Bottom 5%	Annually (1x / yr)	~ 95%	Open Bin / Visual Kanban	Weigh Scale or Volume Estimate
D	Obsolete / Dead	Annual Audit	100%	Segregated / Quarantined	Visual Verification

Cycle counting & discrepancy logic

A transition away from massive “Annual Physical Inventories” that disrupt factory operations is required. Continuous Cycle Counting driven by the ABC classification must be implemented.

The schedule generator (the WMS engine)

The Logic: Divide the total SKUs in a class by the required count frequency to generate a daily cadence.
Example: If you have 500 ‘A’ items, the warehouse should count about 25 items per day to comfortably meet the monthly target.
The Execution: The ERP/WMS should automatically push daily “Count Tasks” to the warehouse staff’s barcode scanners.

Discrepancy escalation

When physical counts do not match the ERP record, a clear escalation path must be established based on variance value.

Variance < $$$100: Warehouse Shift Lead (Standard auto-adjustment via scanner).
Variance $$$100 - $$$1,000: Supply Chain Manager (Root Cause Analysis document is typically required).
Variance > $$$1,000: Operations Director + Site Controller (Requires a full investigation and formal sign-off).

Pro-Tip: It must be ensured that the person correcting a significant inventory variance in the system is not the same person who counted or mis-handled it. Segregation of duties is a standard requirement for audit compliance.

Common traps (the failure modes)

Structural issues that can undermine ABC analysis must be kept in mind.

Over-investing in C-Items: Spending excessive labor hours to track down minor discrepancies on standard fasteners is inefficient. It must be understood when to accept nominal Class C variances and redirect labor to critical items.
The “Static List” Fallacy: Running the ABC algorithm only once during system implementation. Changes in production volume can quickly alter the mathematical footprint of a part.
The “Ghost” A-Items: Items with zero digital stock on hand.
- The Trap: If ERP Qty = 0, the cycle counting scheduler might skip generating a task for that item.
- The Fix: “Zero Confirmation” counts must be ensured to be configured. The staff must still visit the physical location and confirm it is completely empty.

Refresh cadence

Inventory profiles change over time. The classification system must be ensured to be updated periodically.

Quarterly re-classification

The Action: The ABC algorithm must be run based on Projected MRP usage for the next 6 to 12 months, rather than relying solely on historical data.
The Output: The “ABC Code” in the Item Master must be updated via a system batch update.

Trigger-based updates

New Part Introduction (NPI): New parts must be assigned a default status (e.g. Class B) until empirical usage data enables an accurate ABC calculation.
Cost Fluctuations: If a component’s unit price shifts significantly, evaluating its ABC status manually should be considered.

Final Checkout: Inventory classification (abc analysis)

Control Point	Engineering Requirement	Target Goal
Data Integrity	ABC Codes are populated in the ERP.	100% of Active SKUs
Cycle Velocity	Class ‘A’ Items are counted per schedule.	E.g. Monthly completion
Blind Counts	Counter software hides expected system quantities.	Enforced by WMS configuration
Overrides	High-risk/highly pilferable items are flagged as A.	Verified periodically
Refresh Logic	Full MRP Classification is systematically updated.	Quarterly
Financial Auth	Discrepancies follow an approval hierarchy.	Escalate high-value variances