Garment Quality Inspection & Reporting for Indian Units

A shirt with a skipped stitch costs a few rupees to fix at the sewing table. The same shirt found after packing costs the repair, the re-packing, and sometimes the shipment date. Found by the buyer, it costs a chargeback or a returned lot.

This guide is for a garment owner or QA head who wants a simple, repeatable way to inspect, record and report quality. It does not need a big system to start. It needs the same few columns, filled the same way, every day.

Why defects found at final inspection cost the most

The later a defect is found, the more work has already been done on top of it.

• Rework. At final inspection the garment may need unpicking, re-stitching, re-pressing, re-folding and re-packing. A fix at the sewing table is one step. A fix after packing is five.
• Shipment delays. If the fixing happens in the last stretch before dispatch, the lorry or the booking date does not move, but your work does. Overtime, split shipments and air freight are common ways of paying for late defects.
• Buyer chargebacks. When a buyer finds the defect, the usual outcome is a claim against the invoice. The amount and terms depend on your buyer agreement, so check what yours says.
• Repeat defects. If you only count at the end, the same operation keeps making the same fault for a whole order before anyone notices.

None of this needs a number to be true. The direction is simple: find it early, fix it early, and write down where it came from.

Inline, end-line and final inspection: what each should record

Inline is the cheapest stage and the one most units under-use. A checker who looks at the first few pieces from each operator, and again later in the shift, will catch a bad setup before it becomes a bundle.

End-line tells you how well the line is doing. Its defect rate by line is the number an owner should look at first every morning.

Final is the buyer's view. It decides whether the lot ships. By then it should be confirming good work, not discovering bad work.

AQL in plain words

AQL stands for Acceptable Quality Limit. Buyers use it to decide how many garments to pull from a lot and how many defects they will accept before the lot fails.

For a small unit, the practical rules are short:

1. Follow the buyer's stated AQL level. It is usually in the purchase order, the quality manual or the buyer's inspection checklist. Different buyers use different levels, and the level can differ by defect class.
2. Use the buyer's sampling plan. Do not make up your own sample size. Ask the buyer or merchandiser for the plan if it is not written down.
3. Keep the inspection record. If a buyer or their third-party inspector questions a lot, a clean record of what you checked and what you found is your best answer.
4. Do your own checking before theirs. Inspecting to the buyer's level yourself, before the lot is offered, is the point of final inspection.

This post does not give sampling tables. They come from the buyer or the standard the buyer refers to, and they change with lot size and level.

A simple defect log

The log is one row per check. It does not need to be fancy. It needs the same columns every time.

Example (hypothetical numbers, for illustration only):

Defect percentage is rejected pieces divided by checked pieces, for the same line and period. Fix the definition once so everyone calculates it the same way. Count rework and reject separately, because they cost differently. The wider habit of recording reasons is covered in tracking rejection and rework on the shop floor.

The daily QA report an owner should see

You do not need twenty charts. One page, every morning, with three things:

1. Defect % by line. Pieces rejected divided by pieces checked, for each line, for yesterday and the running order.
2. Top 3 defects. The three defect types with the highest count, and the line each one comes from.
3. Rework pending. How many pieces are waiting to be fixed, and for which style and size. This is the number that decides whether you can pack on time.

With those three, the owner can make a call by 9 a.m.: move a checker, stop a line, hold a lot, or tell the buyer early.

Why Excel and WhatsApp photos break down

Both work when one person watches one line. They stop working when there are several.

• Each line or checker keeps a different sheet, and columns drift. Totals do not add up the same way twice.
• Photos show a defect but do not give a quantity, a size or a line. Someone has to type them in later, and often does not.
• The daily number depends on who has time to collect and add it up, so it arrives late or not at all.
• Rework pending lives in someone's head until packing day.
• When a buyer asks for the record of a lot from two weeks ago, it has to be rebuilt from chats.

The fix is the same few fields entered once, at the point of inspection, in one place. That is a discipline first and a tool second. Excel can do it for a while if one person owns the format. Past a few lines and a few styles, it usually needs something built for it.

Where software helps

Software helps when the same defect record has to be read by people in different places: the checker on the floor, the line supervisor, the merchandiser and the owner.

In FactoStack, quality management records inward, in-process and final checks with rejection reasons and rework against the record they belong to. For apparel, the garments solution records inline and end-line checks, measurement failures and rework against the style order and the stage where they happened, with finished quantities kept by style and size. That puts quality on the same order that production and billing already use.

Stock and size-wise inventory sit alongside this. If you are also fixing how you track cut pieces and finished goods, see how to manage garment factory inventory in India. For the wider picture of what Tiruppur units struggle with when they pick software, read garment cluster software challenges in Tiruppur.

Factory OS is ₹2,999/month. Start Free Trial and put one running style through inline, end-line and final checks.

A one-week start

You can begin without buying anything.

1. Fix a short defect list with your QA head. Ten to fifteen types is enough.
2. Use the log columns above for one line and one style.
3. Add one end-line checker per line, filling the log every hour.
4. Build the morning page: defect % by line, top 3 defects, rework pending.
5. After a week, review which defect keeps returning and from which operation. Fix that first.

Related guides

• Rejection and rework: how to track quality issues on the shop floor
• How to manage garment factory inventory in India
• Software challenges in the Tiruppur garment cluster
• Quality management
• Garment manufacturing software