Document the classification convention and keep business criticality separate.
Beginner-friendly animated guide
Learn ABC–XYZ without misleading boundaries from the beginning
Document the classification convention and keep business criticality separate. Use the controls to study one section at a time. No previous warehouse knowledge is required.
Paste a SKU, unit cost and at least three matching periods of demand per row. A blank demand cell is missing information; a zero is measured no demand. Do not mix three periods for one item and twelve for another.
Worked example
Two items have period consumption values ₹9,900 and ₹100. The first accounts for 99% of value. Under the start-of-item convention, it starts at 0% cumulative value and remains A. The second starts at 99% and is C. There may be no B item in a small set.
Understand XYZ
Coefficient of variation is sample standard deviation divided by mean. This implementation labels CV below 0.5 as X, 0.5 through 1 as Y, and above 1 as Z. These are configurable policy choices in concept, not universal standards. Short histories and seasonality limit interpretation.
Add a policy review
Tie the class to a proposed review frequency, then adjust for criticality, expiry, supplier risk and customer commitments. High variability is not itself a reason to discontinue a necessary item.
A spare-parts team finds that high annual-value items are being managed with the same rule as intermittent items. The useful response is not a generic target or a tick-box answer. Start by defining the exact event, location, item, time period and decision owner so that another reviewer can reproduce what happened.
Decision path
Classify value and demand variability separately, then test boundary changes before changing stock policy. Record assumptions before changing the process. Compare the proposed control with the current condition, test it on a limited scope where appropriate, and define the condition that would require work to stop or management to escalate.
Evidence pack
Twelve months of clean demand, class calculation, exceptions, policy owner and review date. Keep the source record with the action rather than copying only a summary into a presentation. A complete pack should show who reviewed the information, what was excluded, the date of the decision and proof that the action was later checked.
Supervisor walkthrough
Observe the work at the location and ask the operator to explain the normal sequence.
Compare the observed sequence with the written standard and system record.
Separate an isolated exception from a repeated condition by checking recent history.
Agree one immediate control and one corrective action with a named owner and realistic date.
Return after implementation and verify the result with evidence, not verbal confirmation.
Common failure to avoid
Do not close the review with “team advised” or “monitor closely.” Those statements do not identify a changed control, accountable owner or effectiveness check. A useful closure states what changed, where it changed, when it was checked and what result would reopen the issue.
Method and verification
This lesson is an operational decision aid. Reconcile definitions to your contracts, system fields and approved local procedure. See the calculation and evidence method.
