Defect Dictionary for Bags: Photographic Guide to Major and Minor Defects
A defect dictionary lists every fault your programme recognises, with its location, how it is found and which class it belongs to. With one, inspection findings are consistent across inspectors and orders. Without one, every report reflects whoever happened to be holding the tape measure.

Write the list before the first lot, and version it. Every fault gets a name, a location, a way of finding it and a class. Then an inspector is reading your definitions rather than inventing theirs.
The most useful quality document in most programmes is not the sampling plan — it is one nobody writes. The plan tells you how many units to draw; the dictionary tells you what counts once you have drawn them. Get the second one wrong and the first stops mattering, because two inspectors looking at the same fifty units will produce genuinely different reports.
This is not theoretical. Pull any three reports for the same style from three different visits and compare how the same condition is described. "Thread ends", "loose threads" and "untrimmed threads" may or may not be the same finding; "colour deviation" might be anything from invisible to unacceptable. The reports are not comparable, which means nothing is being tracked even though everything is being recorded.
What Is a Defect Dictionary Actually For?
Three jobs, in order of importance. It makes findings comparable across visits, so a rising count means something. It makes the sampling plan meaningful, because an acceptance number is meaningless without agreement about what is being counted. And it makes conversations short, because most disputes are about definitions rather than about the goods.
It also has a quiet effect on production. When the line supervisor can see the thirty faults that will be counted, with photographs, those thirty get addressed before anything else does. A dictionary is a specification that everyone on the floor can actually read.
And it changes the economics of delay. Without a dictionary, a failed lot sets off a conversation about definitions before anybody gets to the corrections; with one, the conversation starts at "sort or remake". Against a 35-50 day bulk window, the days spent agreeing what a fault is called are days that could have gone into fixing it.
How Do You Write an Entry an Inspector Can Actually Use?
Write it as instruction rather than as description. "Stitch density below eight per inch measured over three inches at any load-bearing seam" can be executed by anybody on any floor. "Poor stitching" cannot be executed by anybody, and inspectors will each quietly invent their own version of it.
Avoid adjectives wherever a measurement exists. "Lightly soiled", "slightly out of line" and "noticeably darker" all shift with who is reading them. Replace each with a limit — a stated length, distance or grade — and the entry becomes enforceable. Where a measurement genuinely does not exist, keep the adjective but attach a reference image and say so.
Finally, write each entry in the language the inspector works in, or provide both versions side by side. An entry translated badly at the point of use is the same as an unclear entry, and it is a common failure in programmes sourced across languages.
How Should Each Entry Be Structured?
Five fields, consistently filled: the name, where it occurs, how it is detected, what counts as one occurrence, and the class. The fourth is the one people forget and it resolves a surprising amount — is a seam fault counted once per unit or once per occurrence along the seam? Agreeing this removes an argument the inspector currently resolves alone.
| Field | What it carries | Why it matters |
|---|---|---|
| Name | The fault as it will appear in the report | Reports become comparable across visits and inspectors |
| Location | Component, position and orientation | Tells the line where to look, and separates two faults that look alike |
| Detection method | Tool, distance, light and duration for finding it | A fault with a stated method is found consistently; one without is not |
| Counting rule | Per unit, per occurrence or per area | Removes the difference between one finding and twelve |
| Class | Critical, major or minor, with the plan each applies to | Determines whether the finding affects the release decision at all |
How Do You Decide Which Class an Entry Belongs To?
Ask what the customer does when they notice it. If they return the bag, it is a major. If they notice and keep it, it is a minor. If it creates a hazard or breaks a rule, it is critical, whatever anybody notices. That is the whole test, and applying it consistently to every entry is what makes a dictionary coherent rather than arbitrary.
The interesting cases sit where "the customer" is ambiguous. A fault visible at the point of sale behaves differently from one visible at home; a fault on the outer face differs from one inside a lining. Write down which customer and which moment the dictionary assumes, then apply it consistently. Most inconsistency in real dictionaries comes from answering that question differently for different entries.
Which Defects Belong in the Critical Class?
A short list, deliberately. Everything that could make the product unsafe or unlawful, plus anything the destination market specifically controls. Critical findings carry zero acceptance: one occurrence is enough to fail the lot regardless of how good the rest of the sampling looks.
| Critical finding | Why it carries zero tolerance | How it is found |
|---|---|---|
| Sharp edge or point reachable by the user | Injury risk, and one unit is enough to generate the claim | Running along every reachable edge, empty and loaded |
| Needle or broken blade fragment inside the unit | Injury risk, and it travels with the product | Needle-control record plus metal detection where the programme requires it |
| Detachable small part in a children's product | The hazard the ruling exists to prevent | Pull and twist to the stated force, then laboratory confirmation where the market demands |
| Restricted substance above the limit | Unlawful to place on the market | Accredited laboratory report, valid at the date relied on |
| Required marking missing or wrong | May block customs entry or retail acceptance | Reading the label against the approved file for the destination |
| Cord length over the limit drawn by young users | A specific strangulation hazard | Measured to the method the controlling ruling specifies |
What Does the Major List Contain?
Everything that loses the sale or loses the function. It is the longest list in most dictionaries and it is the one that actually moves the accept and reject numbers, because majors are what AQL 2.5 is set against.
| Major defect | Where it appears | How it is detected |
|---|---|---|
| Seam opened or partially opened | Any seam carrying load | Visual examination with gentle opposing pull |
| Stitch count below the stated minimum at a load seam | Strap anchors, handle joins, base seams | Counting over a stated length |
| Zipper will not close or opens under load | Any closure | Cycled, then loaded laterally |
| Buckle releases under load | Closure and strap hardware | Engaged, loaded to the stated value |
| Handle or strap attachment pulled out | Stress points | Loaded by hand or to the stated value |
| Colour outside the approved tolerance | Shell, trim, print | Compared against the reference under the named light source |
| Shell colour different between two pieces of one unit | Panel to gusset, flap to body | Side by side in the same light |
| Print illegible, incomplete or misplaced beyond tolerance | Any printed area | Measured against the approved artwork and position marks |
| Print not adhering at the stated test | Printed panels and webbing | Stated tape or rub method after full cure |
| Hole or cut through the shell fabric | Anywhere on the outer surface | Visual examination inside and out |
| Lining torn or not secured | Interior | Visual examination with the unit turned |
| Missing component or hardware | Anywhere | Cross-check against the bill of materials |
| Capacity below the stated minimum | Compartment claimed to fit an article | Reference article inserted, or dimensions read |
| Metal component showing corrosion | Hardware | Visual examination after the stated conditioning where relevant |
| Odour above the agreed threshold | Interior of closed units | Opened and assessed after a stated interval |
Two refinements make the list behave better in practice. First, decide how several majors on one unit are counted — per unit or per occurrence. Most programmes count the unit once in the major column and note the occurrences, because counting every occurrence would make a single bad unit look like a lot-wide problem. Second, decide what happens when one fault could be recorded under two entries; give one of them precedence and say which.

What Belongs on the Minor List?
Departures from specification that a customer could see and would keep the bag anyway. Minors are counted at AQL 4.0 under this programme, which means they accumulate more tolerance than majors by design — but only if the list is honestly maintained.
| Minor defect | Where it appears | Note on counting |
|---|---|---|
| Untrimmed thread end | Seam terminations and inside corners | Counted per unit rather than per thread, once above the stated length |
| Stitch density varying within tolerance | Long seams | Only recorded where it exceeds the stated variation |
| Small mark or soil likely to be removed | Any surface | Size limit stated, otherwise every mark becomes a finding |
| Creasing from packing that recovers | Panels and webbing | Assessed after a stated recovery period |
| Uneven topstitching within tolerance | Visible seams | Measured against the stated evenness requirement |
| Care label out of position within tolerance | Interior | Position stated on the drawing, not left to judgement |
| Light scratch on hardware within tolerance | Any fitting | Against the approved reference, and only where reachable |
| Print registration out by less than the stated amount | Printed areas | Measured, not estimated |
How Do You Keep the Dictionary From Growing?
It grows for the wrong reason: somebody sees a problem, adds an entry, and the list accumulates exceptions nobody revisits. Three hundred entries later, nobody applies them consistently and the document has quietly stopped being useful.
Two habits prevent this. Review the list at the end of each programme rather than continuously during it, adding only what actually occurred. And retire entries — if a named fault has never been recorded in four lots, ask whether it is being looked for or whether it simply does not arise. Retiring is healthy; nobody should treat the dictionary as permanent.
How Should the Photographs Be Managed?
One image per named fault, taken as deliberately as any other reference: consistent background, consistent scale, a stated light source, and the location marked in the frame where position matters. These are reference images rather than report images, so clarity beats convenience — a phone picture under the right conditions serves perfectly well.

Version everything. Put a number, a date and the order reference on each page, and send the current version with every booking. Half of the value of a dictionary comes from both sides being able to prove which version applied when the goods were inspected.
What Happens When a Fault Is Not in the Dictionary?
It happens constantly and needs a route. The sensible one is to record the finding as observed, without a class, photograph it, and refer it for classification rather than letting the inspector assign one. Add it to the next revision with the class everybody agreed.
What does not work is silence — the fault not being written down because it is not in the list. A dictionary exists to describe the product, not to limit what can be noticed. Say this explicitly when you hand it over, because inspectors are trained to work to lists.
Set a turnaround for that referral. A finding awaiting classification should not sit unresolved while the packing continues around it, and naming who answers and within how long keeps the exception from becoming a delay.
Store the record with the lot information rather than in a folder of photographs. A finding attaches to a lot, a line and a date, and that is how it will need to be found two years later.
How Does the Dictionary Reach the Inspection Company?
As an attachment to the booking, in the same file every time, referenced by version. Do not paste extracts into an email body; it guarantees that two people are working from different versions within a fortnight.
Ask for confirmation that the checker working your programme has read it, and ask what happens when the named inspector is unavailable. Substitute inspectors working from a list they have not read are one of the quietest sources of inconsistency there is.
Where Does This Fit Alongside the Sampling Plan?
Beside it, not after it. The plan sets how many units are drawn and what counts end the discussion; the dictionary sets what those counted things are. A programme can quote AQL 2.5 with complete precision and still not have defined a single defect — which is roughly where a great many programmes sit.
Read together they close the loop. The plan says reject at four majors in fifty units; the dictionary says what a major is. Neither document means much on its own, and the pair of them is what makes a report enforceable rather than merely informative.
Eleven rules for writing a dictionary that gets used
- Name each fault exactly as it will appear in the report.
- State the location: component, position, orientation.
- State the detection method — tool, distance, light, duration.
- State the counting rule: per unit, per occurrence, per area.
- Assign one class per entry, and never two.
- Put a limit on every minor — size, position or count.
- Keep the critical list short, hazards and compliance only.
- Illustrate each entry with one deliberate reference image.
- Version every page with number, date and order reference.
- Send the current version with every single booking.
- Review and retire entries at the end of each programme.
Have the dictionary drafted for your programme
Send the construction and its components — every fault worth counting comes back named, located, classed and illustrated.
Frequently Asked Questions
How many entries should a bag defect dictionary have?
Enough to cover observed faults and no more. Programmes typically run between thirty and eighty entries; beyond that, consistency starts to suffer.
Should I use my own defect list or the inspection company's?
Yours, attached to every booking. A provider's generic list is a starting point, not a specification of your product.
Who writes the dictionary?
Whoever understands what the customer would return a bag for. The inspection company can format and illustrate it; the programme owner supplies the judgements.
How often should it be revised?
At the end of each programme rather than continuously during one. Constant editing means nobody knows which version applies.
Is thread ends a major or a minor?
Almost always minor, with a stated length and a per-unit counting rule. Untrimmed threads inside a sealed lining can be argued either way — decide in advance.
Should the critical list include<|hy_place▁holder▁no▁813|> quality faults?
No. Hazards and compliance only. Adding serious quality faults dilutes the one class that must remain unambiguous.
What if two faults look identical but have different causes?
Give them separate names and separate locations. Keeping them apart is how you later know which station to visit.
Do pictures need professional photography?
No. Clear, consistent, well-lit and labelled beats beautiful. A reference image only has to be unambiguous.
How do I handle a fault nobody anticipated?
Record it unclassed, photograph it, refer it for a decision, then add it to the next revision with the agreed class.
Can the same fault be both major and minor?
Only if your entry splits it by size or position and you have written that split explicitly. One entry gets one class.
Does the dictionary replace the sampling plan?
No. The plan sets how many units and what receives_; the dictionary sets what a finding is. You need both.
Should trim colour be a major?
Where the difference is visible to a customer considering purchase, yes. Where it is only visible on close inspection, usually a minor.
Do all programmes need one?
Any programme expecting more than one lot does. Without it, reports across visits cannot be compared, so nothing can be tracked.
People Also Ask
What is a defect dictionary in quality inspection?
A list of every fault a programme recognises, each with its location, how it is detected, how it is counted and which class it belongs to.
What is the difference between a major and a minor defect on a bag?
A major is something the customer notices and returns the product for, or that reduces function. A minor is a visible departure nobody would return it for.
What defects are critical in bag inspection?
Sharp reachable edges, needle fragments, detachable small parts in children's products, restricted substances over the limit and missing or wrong required markings.
How do inspection companies classify defects?
Against the defect list supplied with the booking. Where none is supplied, the inspector applies the provider's generic classification.
Should every defect be photographed?
Every entry in the dictionary needs one reference image. Every failing finding in a report should be photographed as evidence.
Sources and further reading
Every figure on this page is either our own programme data or attributed below. Open the originals before you write them into a specification.
- ISO 2859-1:1999 Sampling procedures for inspection by attributesInternational Organization for Standardization
- Acceptance sampling — quality resource indexAmerican Society for Quality
- ASTM International — standards indexASTM International