Final Quality Checks

A final check is the last gate before finished garments leave for boxing and shipping. It's the moment the factory confirms — to itself and to the brand — that a batch as a whole meets the spec everyone signed off on.

Where in-line checks catch problems early, final checks prevent problems from leaving. If anything has gone wrong upstream and slipped through, this is the catch. Once a batch ships, the cost of fixing a quality issue multiplies tenfold.

For most factories, the final check is also where AQL (Acceptable Quality Limit) sampling rules apply — the brand has agreed in advance on a sample size and accept/reject criteria, and the inspection must follow those rules to be defensible if the brand audits later.

How a final check is different from in-line

The same QC Inspection doctype handles both. What changes is the Inspection Stage (final = last operation) and the sample size convention.

Using it from the App

Final QC is the App's default landing tab. The flow on a tablet:

1. Open the App. It opens on Final by default.
2. Pick the Production Batch (or scan its packing carton). The Batch must have reached its last operation.
3. The app shows lot size from the Batch's completed quantity. Enter sample size based on your AQL table for that lot.
4. Walk the sample. Record parameter readings — measurements, visual checks, functional tests.
5. Log every defect found, with category, severity, and a photo if it's visual. The App makes it easy to walk one garment, log multiple defects, then move to the next.
6. At the end, the app computes the defect rate. If it's within the AQL accept threshold, mark Accepted (or Accepted with Deviation if there's a noted minor variance the brand has pre-approved).
7. If above the accept threshold, mark Rejected or Hold for Review.

The result locks the batch. A Rejected final check blocks the batch from posting as finished goods until the cause is addressed.

Image: The Quality App Final view mid-inspection, with sample garments inspected, multiple defects logged across categories, and the running defect rate visible.

Using it from the Desk

The Desk path is the same as in-line — create a QC Inspection, pick the final operation as the stage, fill in the parameter and defect tables.

Two reasons quality managers prefer the Desk for final checks:

• Side-by-side review. The form view shows all parameter readings, all defects, and the running totals on one screen, which is easier when you need to think about whether to Accept with Deviation or Reject.
• Adding context. Comments, attachments, and audit trail are easier to manage from the Desk than the App.

In practice: the inspector posts the inspection from the App, the manager reviews from the Desk and adds any commentary or final decision.

Accept with Deviation — when to use it

This result is for cases where the batch has some defects, but they're within a tolerance the brand has explicitly agreed to. Example: the brand accepts up to 2% minor color variance on naturally-dyed indigo; the batch came in at 1.5%. That's Accepted with Deviation.

Use it sparingly. Every Accept with Deviation should be backed by a documented brand agreement, and the comment field should reference where the agreement lives. Otherwise it becomes a way to silently lower the bar.

Hold for Review — when to use it

Use this when the inspector can't make the call alone — the defect rate is borderline, the defect type is one the brand hasn't seen before, or the cause needs investigation before deciding to ship. A Hold for Review stops the batch from moving to finished goods and flags it for a quality manager.

This is where final QC and the dashboards meet: a Hold for Review shows up on the QC Overview and the Unit Status dashboards, so a manager sees it without having to be told.

What to do next

Both inspection flows write to the same two child tables on the QC Inspection. Recording defects and readings covers those tables in detail.