{"id":2426,"date":"2026-08-18T14:32:43","date_gmt":"2026-08-18T06:32:43","guid":{"rendered":"https:\/\/sourcingall.com\/sourcing-basics\/how-to-define-critical-major-minor-defects\/"},"modified":"2026-08-21T15:45:56","modified_gmt":"2026-08-21T07:45:56","slug":"how-to-define-critical-major-minor-defects","status":"publish","type":"post","link":"https:\/\/sourcingall.com\/es\/sourcing-basics\/how-to-define-critical-major-minor-defects\/","title":{"rendered":"How to Define Critical, Major, and Minor Defects"},"content":{"rendered":"

\u201cMinor,\u201d \u201cmajor,\u201d and \u201ccritical\u201d sound clear until the supplier, inspector, and buyer give the same scratch three different labels.<\/p>\n

Defect severity is not a universal dictionary. It is a decision system for a particular product, customer promise, market, and production context. A loose thread on a basic garment may be a small cosmetic issue. The same visible issue on a premium retail product may be unacceptable. The label only works when everyone can see the condition, compare it to the released requirement, and apply the same written rule.<\/p>\n

InTouch Quality makes this point with a garment example: untrimmed threads may be minor for one buyer and major for another buyer serving a high-end retailer. 1<\/a> ISO 2859-1 similarly states that nonconformities may be classified by seriousness and that the classes, assignments, and related AQL choices must fit the specific quality requirements of the situation. 2<\/a><\/p>\n

Start with the difference between a requirement and a defect class<\/h2>\n

A requirement<\/strong> says what the product must be. A defect classification<\/strong> says how serious it is when the product does not meet that requirement.<\/p>\n\n\n\n\n\n\n\n\n
Requisito<\/th>\nDefect condition<\/th>\nClassification decision<\/th>\n<\/tr>\n<\/thead>\n
Carton must carry the released shipping mark<\/td>\nMark is absent, incorrect, or unreadable<\/td>\nDepends on destination, traceability need, and whether the issue blocks the order\u2019s intended use<\/td>\n<\/tr>\n
Product must meet the approved color reference<\/td>\nFinish is visibly outside the approved range<\/td>\nDepends on the product, customer expectation, visibility, and agreed tolerance<\/td>\n<\/tr>\n
Electrical component must have intact insulation<\/td>\nInsulation is damaged or conductor exposed<\/td>\nMay be treated as a high-severity safety concern under the applicable product rules<\/td>\n<\/tr>\n
Garment seam must be continuous in a stated area<\/td>\nStitches are missing<\/td>\nDepends on whether strength, fit, durability, or customer acceptance is affected<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Do not start by writing \u201cscratch = minor.\u201d Start with the product requirement, the condition found, and the consequence of that condition for this order.<\/p>\n

Use severity labels as working definitions, not shortcuts<\/h2>\n

The following descriptions are a practical starting point. Your product-specific defect library must make them more precise.<\/p>\n\n\n\n\n\n\n\n
Common label<\/th>\nPlain-English working definition<\/th>\nWhat the written standard should add<\/th>\n<\/tr>\n<\/thead>\n
Cr\u00edtico<\/td>\nA condition the buyer treats as unacceptable because it may create a serious safety, legal, mandatory-requirement, or severe-use risk<\/td>\nThe specific requirement, hazard or mandatory rule, evidence needed, and immediate escalation instruction<\/td>\n<\/tr>\n
Importante<\/td>\nA condition that prevents intended use, materially weakens function, creates a serious visible\/customer problem, or significantly departs from the approved standard<\/td>\nThe exact product feature, test\/inspection method, product\/customer impact, and classification examples<\/td>\n<\/tr>\n
Menor<\/td>\nA limited departure from the approved standard that does not prevent intended use but still needs to be recorded and controlled<\/td>\nThe permitted visual or physical range, reference image\/sample, location\/visibility criteria, and count\/action rule<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

InTouch Quality describes minor defects as commonly cosmetic, major defects as potentially affecting intended function or customer acceptance, and critical defects as potentially hazardous. 1<\/a> HQTS uses a similar severity framework and recommends that a custom checklist define the product-specific classifications and inspection criteria. 3<\/a><\/p>\n

These are descriptions, not legal conclusions. For regulated, high-consequence, medical, electrical, child-use, food-contact, or safety-sensitive products, identify the applicable technical and regulatory requirements separately and involve qualified specialists where needed.<\/p>\n

Build a defect library before production, not after a failed inspection<\/h2>\n

A defect library is a controlled list of conditions that the supplier and inspector can use. It does not need to predict every possible problem. It needs to cover the likely, important, and previously seen problems well enough that the inspection team is not improvising under time pressure.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Defect-library field<\/th>\nWhat to enter<\/th>\n<\/tr>\n<\/thead>\n
Defect ID<\/td>\nA stable identifier, such as FIN-07<\/code> o PKG-03<\/code><\/td>\n<\/tr>\n
Product\/version<\/td>\nSKU, style, model, material, color, size, or revision to which the rule applies<\/td>\n<\/tr>\n
Requirement\/reference<\/td>\nSpecification clause, drawing, approved sample, image, or packaging file<\/td>\n<\/tr>\n
Condition<\/td>\nA plain description of what is wrong, without vague labels such as \u201cpoor quality\u201d<\/td>\n<\/tr>\n
Location\/visibility<\/td>\nWhere it appears and how a user, retailer, or assembler would encounter it<\/td>\n<\/tr>\n
Severity class<\/td>\nCritical, major, minor, or another buyer-defined class if the system uses one<\/td>\n<\/tr>\n
Why it matters<\/td>\nFunction, safety, mandatory requirement, fit, finish, presentation, traceability, or customer impact<\/td>\n<\/tr>\n
Inspection method<\/td>\nVisual comparison, measurement, function check, document review, or specialist test path<\/td>\n<\/tr>\n
Evidence required<\/td>\nPhoto angle, measurement record, sample ID, document copy, or test record<\/td>\n<\/tr>\n
Action trigger<\/td>\nRecord only, segregate, hold for review, or escalate to the named decision owner<\/td>\n<\/tr>\n
Owner and revision date<\/td>\nWho maintains the rule and when it last changed<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

HQTS recommends that a custom quality checklist include product specifications, defect classifications, inspection points, on-site testing requirements, and applicable compliance checks. 3<\/a> InTouch Quality says a more complete quality-control checklist helps the supplier and inspector apply the buyer\u2019s tolerances consistently. 1<\/a><\/p>\n

Describe the condition so two people can find the same thing<\/h2>\n

\u201cBad finish\u201d does not help an inspector. A useful condition statement answers what, where, compared with which reference, and how it will be recognized.<\/p>\n\n\n\n\n\n\n\n\n\n
Weak statement<\/th>\nBetter defect-library entry<\/th>\n<\/tr>\n<\/thead>\n
Scratch on product<\/td>\nVisible scratch longer than the approved reference limit on the customer-facing front panel under the agreed viewing condition<\/code><\/td>\n<\/tr>\n
Wrong color<\/td>\nSurface color visibly differs from approved sample PS-04 under the agreed comparison condition<\/code><\/td>\n<\/tr>\n
Bad sewing<\/td>\nMissing stitches along the left side seam between points A and B; compare to approved sample and seam requirement<\/code><\/td>\n<\/tr>\n
Bad packaging<\/td>\nRetail box uses artwork revision PKG-12 instead of released revision PKG-14<\/code><\/td>\n<\/tr>\n
Missing part<\/td>\nPower adapter listed in BOM revision B-7 is absent from the sealed retail unit<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The better entries do not set a classification yet. First, they make the observed condition repeatable.<\/p>\n

Classify with a consequence check<\/h2>\n

Before you choose minor, major, or critical, ask the same questions every time.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
Question<\/th>\nWhy it helps classify the condition<\/th>\n<\/tr>\n<\/thead>\n
Does the issue create a safety or mandatory-requirement concern for this product and market?<\/td>\nMay require a high-severity escalation and a separate specialist\/compliance path<\/td>\n<\/tr>\n
Does it stop the product from doing its intended job?<\/td>\nPoints toward a more serious functional consequence<\/td>\n<\/tr>\n
Does it affect fit, assembly, durability, performance, or a downstream process?<\/td>\nShows whether the issue reaches beyond appearance<\/td>\n<\/tr>\n
Would a typical customer or retailer notice it under normal conditions?<\/td>\nHelps assess presentation and customer-acceptance impact<\/td>\n<\/tr>\n
Is the variance permitted by the released specification or approved reference?<\/td>\nPrevents treating an allowed variation as a defect<\/td>\n<\/tr>\n
Can the condition be corrected without changing the product requirement or hiding affected stock?<\/td>\nHelps plan containment but does not reduce severity by itself<\/td>\n<\/tr>\n
Is the same issue recurring across units, cartons, lines, or batches?<\/td>\nReveals a potential process problem beyond the individual item<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The answer can vary by product. InTouch Quality notes that the same condition can be treated differently according to the buyer\u2019s customer expectations and tolerance. 1<\/a> Do not upgrade or downgrade a classification because a current order is inconvenient to rework.<\/p>\n

Add real examples\u2014but label them as product-specific<\/h2>\n

Examples are powerful because they reduce interpretation. They can also mislead if they are copied across products without context.<\/p>\n\n\n\n\n\n\n\n\n\n\n
Product context<\/th>\nExample condition<\/th>\nPossible classification logic<\/th>\n<\/tr>\n<\/thead>\n
Softline garment<\/td>\nLoose thread at a hidden seam end<\/td>\nMay be limited cosmetic variance if the stated brand\/retailer standard allows it; classify from the written rule<\/td>\n<\/tr>\n
Softline garment<\/td>\nNeedle found inside the finished item<\/td>\nTypically triggers an immediate high-severity safety escalation<\/td>\n<\/tr>\n
Hardline product<\/td>\nDeep scratch across a customer-facing logo<\/td>\nMay materially affect presentation and retailer acceptance; classify using the approved appearance standard<\/td>\n<\/tr>\n
Tool or component<\/td>\nDimension outside the stated tolerance<\/td>\nSeverity depends on assembly, function, safety, and downstream effect\u2014not the word \u201cdimension\u201d alone<\/td>\n<\/tr>\n
Electrical product<\/td>\nDamaged insulation or exposed conductor<\/td>\nTreat as a potential safety concern; follow the product\u2019s safety\/compliance escalation path<\/td>\n<\/tr>\n
Retail packaging<\/td>\nBarcode from an obsolete artwork revision<\/td>\nSeverity depends on the operating consequence, destination requirement, and traceability\/retail process impact<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

InTouch Quality provides category examples including a needle in a garment, sharp points on hard goods, and damaged electrical wiring, while stressing that defect classification depends on severity and product context. 1<\/a> Use supplier-approved photos and your own released documents as the governing examples for your order.<\/p>\n

Separate defect classification from AQL settings<\/h2>\n

Severity class and AQL are related, but they are not the same thing.<\/p>\n