Should I put AQL defect limits directly in the purchase order?

Should I put AQL defect limits directly in the purchase order?

Direct answer: Yes. State explicit Critical (0), Major (e.g. 2.5) and Minor (e.g. 4.0) acceptance limits under ISO 2859-1 directly in the purchase order, and require a passed inspection report with timestamped photo logs before the balance payment is released. AQL left in a separate email is easy to ignore; written into the PO it becomes a contractual standard the factory must meet.

What AQL Actually Means

AQL (Acceptable Quality Limit) is the worst tolerable defect rate in a batch, defined by the ISO 2859-1 sampling standard. It is expressed as three limits: Critical (safety/functional zero-tolerance), Major (e.g. 2.5 — visible or functional defects), and Minor (e.g. 4.0 — cosmetic only). The inspector draws a sample size from the lot based on the AQL table and accepts or rejects the batch against those numbers.

An inspector applying an AQL sampling plan to a production lot.
An inspector applying an AQL sampling plan to a production lot.

Why It Belongs in the PO

If AQL limits live only in an email or a separate QC document, the factory can claim they were 'guidance'. Written into the purchase order, they are contract terms: the goods are not 'as ordered' unless they pass. This is what turns a vague expectation into an enforceable quality gate — and it is the backbone of preventing quality fade.

A purchase order page with quality terms — AQL belongs here, not in a side email.
A purchase order page with quality terms — AQL belongs here, not in a side email.

A Real-World Case

A buyer specified 'AQL 2.5' loosely in a message. The factory delivered a batch with a 6% major-defect rate and argued the limit was never formally agreed. Because the PO said only 'inspected before shipment', the buyer had weak leverage and accepted a discount instead of a rework. On the next order the buyer wrote 'AQL ISO 2859-1: Critical 0, Major 2.5, Minor 4.0; PSI required; balance paid only on passed report with photo logs' into the PO. The factory complied — the standard was now contractual.

The Limits to Write Down

Use the ISO 2859-1 convention and set them by risk.

ClassTypical AQLCovers
Critical0Safety, function, regulatory failure
Major1.5-2.5Visible/functional defects
Minor4.0Cosmetic only

How RND SOURCING Writes the PO

RND SOURCING bakes AQL and the payment gate into every PO we issue: explicit Critical/Major/Minor numbers, the inspection stage (DUPRO + PSI), the standard (ISO 2859-1), and a clause that the balance is released only on a passed report with timestamped photo logs. The factory signs the PO knowing exactly what 'pass' means — no room to redefine it later.

RND SOURCING supports importers on: Should I put AQL defect limits directly in the purchase orde…
RND SOURCING supports importers on: Should I put AQL defect limits directly in the purchase orde…

Step-by-Step: Embed AQL in the PO

  1. Choose AQL by defect class (Critical 0, Major 2.5, Minor 4.0 as a baseline).
  2. Write the numbers and 'ISO 2859-1' explicitly into the PO quality clause.
  3. Name the inspection stage (DUPRO and/or PSI) and who runs it.
  4. Add: balance paid only on passed report + timestamped photo logs.
  5. Keep the signed PO as the arbitration reference if the batch fails.

Common Mistakes to Avoid

  • Writing AQL only in email — make it a PO term.
  • Setting Major too high for a high-visibility product.
  • Skipping the photo-log requirement so failures are disputed.
  • Releasing balance before the inspection report exists.

Key Takeaways

  • AQL in the PO is a contract, not a suggestion.
  • Use Critical 0 / Major 2.5 / Minor 4.0 as a defensible baseline.
  • Gate the balance payment on a passed, photo-logged inspection.
  • The signed PO is your dispute reference.