“Minor,” “major,” and “critical” sound clear until the supplier, inspector, and buyer give the same scratch three different labels.
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.
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 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
Start with the difference between a requirement and a defect class
A requirement says what the product must be. A defect classification says how serious it is when the product does not meet that requirement.
| Requisito | Defect condition | Classification decision |
|---|---|---|
| Carton must carry the released shipping mark | Mark is absent, incorrect, or unreadable | Depends on destination, traceability need, and whether the issue blocks the order’s intended use |
| Product must meet the approved color reference | Finish is visibly outside the approved range | Depends on the product, customer expectation, visibility, and agreed tolerance |
| Electrical component must have intact insulation | Insulation is damaged or conductor exposed | May be treated as a high-severity safety concern under the applicable product rules |
| Garment seam must be continuous in a stated area | Stitches are missing | Depends on whether strength, fit, durability, or customer acceptance is affected |
Do not start by writing “scratch = minor.” Start with the product requirement, the condition found, and the consequence of that condition for this order.
Use severity labels as working definitions, not shortcuts
The following descriptions are a practical starting point. Your product-specific defect library must make them more precise.
| Common label | Plain-English working definition | What the written standard should add |
|---|---|---|
| Crítico | A condition the buyer treats as unacceptable because it may create a serious safety, legal, mandatory-requirement, or severe-use risk | The specific requirement, hazard or mandatory rule, evidence needed, and immediate escalation instruction |
| Importante | A condition that prevents intended use, materially weakens function, creates a serious visible/customer problem, or significantly departs from the approved standard | The exact product feature, test/inspection method, product/customer impact, and classification examples |
| Menor | A limited departure from the approved standard that does not prevent intended use but still needs to be recorded and controlled | The permitted visual or physical range, reference image/sample, location/visibility criteria, and count/action rule |
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 HQTS uses a similar severity framework and recommends that a custom checklist define the product-specific classifications and inspection criteria. 3
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.
Build a defect library before production, not after a failed inspection
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.
| Defect-library field | What to enter |
|---|---|
| Defect ID | A stable identifier, such as FIN-07 o PKG-03 |
| Product/version | SKU, style, model, material, color, size, or revision to which the rule applies |
| Requirement/reference | Specification clause, drawing, approved sample, image, or packaging file |
| Condition | A plain description of what is wrong, without vague labels such as “poor quality” |
| Location/visibility | Where it appears and how a user, retailer, or assembler would encounter it |
| Severity class | Critical, major, minor, or another buyer-defined class if the system uses one |
| Why it matters | Function, safety, mandatory requirement, fit, finish, presentation, traceability, or customer impact |
| Inspection method | Visual comparison, measurement, function check, document review, or specialist test path |
| Evidence required | Photo angle, measurement record, sample ID, document copy, or test record |
| Action trigger | Record only, segregate, hold for review, or escalate to the named decision owner |
| Owner and revision date | Who maintains the rule and when it last changed |
HQTS recommends that a custom quality checklist include product specifications, defect classifications, inspection points, on-site testing requirements, and applicable compliance checks. 3 InTouch Quality says a more complete quality-control checklist helps the supplier and inspector apply the buyer’s tolerances consistently. 1
Describe the condition so two people can find the same thing
“Bad finish” does not help an inspector. A useful condition statement answers what, where, compared with which reference, and how it will be recognized.
| Weak statement | Better defect-library entry |
|---|---|
| Scratch on product | Visible scratch longer than the approved reference limit on the customer-facing front panel under the agreed viewing condition |
| Wrong color | Surface color visibly differs from approved sample PS-04 under the agreed comparison condition |
| Bad sewing | Missing stitches along the left side seam between points A and B; compare to approved sample and seam requirement |
| Bad packaging | Retail box uses artwork revision PKG-12 instead of released revision PKG-14 |
| Missing part | Power adapter listed in BOM revision B-7 is absent from the sealed retail unit |
The better entries do not set a classification yet. First, they make the observed condition repeatable.
Classify with a consequence check
Before you choose minor, major, or critical, ask the same questions every time.
| Question | Why it helps classify the condition |
|---|---|
| Does the issue create a safety or mandatory-requirement concern for this product and market? | May require a high-severity escalation and a separate specialist/compliance path |
| Does it stop the product from doing its intended job? | Points toward a more serious functional consequence |
| Does it affect fit, assembly, durability, performance, or a downstream process? | Shows whether the issue reaches beyond appearance |
| Would a typical customer or retailer notice it under normal conditions? | Helps assess presentation and customer-acceptance impact |
| Is the variance permitted by the released specification or approved reference? | Prevents treating an allowed variation as a defect |
| Can the condition be corrected without changing the product requirement or hiding affected stock? | Helps plan containment but does not reduce severity by itself |
| Is the same issue recurring across units, cartons, lines, or batches? | Reveals a potential process problem beyond the individual item |
The answer can vary by product. InTouch Quality notes that the same condition can be treated differently according to the buyer’s customer expectations and tolerance. 1 Do not upgrade or downgrade a classification because a current order is inconvenient to rework.
Add real examples—but label them as product-specific
Examples are powerful because they reduce interpretation. They can also mislead if they are copied across products without context.
| Product context | Example condition | Possible classification logic |
|---|---|---|
| Softline garment | Loose thread at a hidden seam end | May be limited cosmetic variance if the stated brand/retailer standard allows it; classify from the written rule |
| Softline garment | Needle found inside the finished item | Typically triggers an immediate high-severity safety escalation |
| Hardline product | Deep scratch across a customer-facing logo | May materially affect presentation and retailer acceptance; classify using the approved appearance standard |
| Tool or component | Dimension outside the stated tolerance | Severity depends on assembly, function, safety, and downstream effect—not the word “dimension” alone |
| Electrical product | Damaged insulation or exposed conductor | Treat as a potential safety concern; follow the product’s safety/compliance escalation path |
| Retail packaging | Barcode from an obsolete artwork revision | Severity depends on the operating consequence, destination requirement, and traceability/retail process impact |
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 Use supplier-approved photos and your own released documents as the governing examples for your order.
Separate defect classification from AQL settings
Severity class and AQL are related, but they are not the same thing.
- Clasificación de defectos explains what kind of nonconformity was found and why it matters.
- AQL or acceptance sampling applies a pre-agreed sampling rule to the reported classes.
- Product requirements state the dimensions, materials, function, marking, packaging, and other features being assessed.
- The inspection report records what was observed, what could not be checked, and the plan applied.
QIMA says AQL settings can be separate for minor, major, and critical categories and should reflect actual risk tolerance, product category, defect profile, and batch context. 4 That is why copying generic AQL settings without a defect library creates arguments: people may agree on a number but disagree about what goes into the count.
Read AQL Explained for Importers Without the Jargon before setting sampling rules. This article is about the preceding step: deciding what the categories mean for your product.
Give the inspector a clear escalation instruction
An inspector should not be left to negotiate a serious finding on the factory floor. Your checklist should state who receives the alert, which evidence is required, and what work status needs to be identified.
| Finding type | Inspection record should capture | Escalation instruction to define |
|---|---|---|
| Potential critical condition | Product/SKU/revision, exact location, photos, available quantity, applicable reference, and immediate isolation status | Notify named contacts immediately; do not make a legal/compliance conclusion beyond the agreed scope; preserve evidence and identify affected goods |
| Major condition | Description, photos, count/occurrence, affected scope, reference comparison, and supplier explanation | Record a proposed containment/correction and the buyer’s named review path |
| Minor condition | Description, photos when useful, count/occurrence, location, and reference comparison | Record against the agreed rule and flag if the pattern exceeds the accepted threshold or repeats |
| Unclear condition | What was seen, what reference is missing, and why classification cannot be confirmed | Mark as open; obtain the correct controlled requirement rather than guessing |
This does not tell the buyer what commercial action to take. It makes the evidence clear enough for the buyer’s own approved process.
Keep a decision log when classifications change
A defect library should improve after each production round. Do not silently edit a class after a dispute. Record what changed and why.
| Change-log field | Example purpose |
|---|---|
| Date and owner | Shows who issued the interpretation |
| Product/revision affected | Prevents an old decision from being applied to a changed design |
| Original rule | Keeps the previous expectation traceable |
| New rule | States the new classification or definition exactly |
| Reason/evidence | Links the change to a product sample, customer requirement, test result, or repeated finding |
| Supplier/inspector acknowledgement | Confirms the working parties received the current rule |
| Effective order or sample round | Stops a mid-run standard change from becoming invisible |
A controlled update is especially important when an approved sample, material, packaging, or customer requirement changes. Use How to Manage Product Revisions Without Losing Control of the Quote to keep the product version and commercial record aligned.
A supplier-ready defect-standard checklist
Before you release the inspection checklist, confirm that it includes:
- The product, SKU, revision, and reference sample or visual standard.
- A plain description of each known or high-risk defect condition.
- The product location, viewing/inspection condition, and comparison method.
- A product-specific critical, major, or minor classification with a stated reason.
- Evidence requirements: photos, measurements, documents, or test records.
- The AQL/acceptance rule only after classifications are clear.
- Named escalation contacts and an open-item rule for unclear conditions.
- A version-controlled change log shared with supplier and inspector.
A defect class is not a label you attach after the fact. It is a shared instruction written before production so the right people can spot, record, and respond to the same problem consistently.