Your customer sends you a purchase order. You read the part number, the quantity, the delivery date, and the price. You confirm you can deliver it on time and at the price quoted. You place production, you manufacture, you deliver, everyone is happy. Then you receive an email: your customer is rejecting the shipment because you didn’t meet a quality requirement that was buried in Section 7.3 of the PO, a clause you skimmed or didn’t read carefully. You’ve now got a problem: the customer is demanding a replacement shipment, and the original PO that you bid on didn’t explicitly call out that requirement. This scenario repeats constantly in contract manufacturing, and most of the time it’s preventable—you just need to actually read and understand the quality clauses in customer purchase orders before you commit to delivery.
Where Quality Requirements Hide in a Purchase Order
POs from large customers are rarely simple. Beyond the basic line items and delivery terms, there are terms and conditions pages that reference standards, specifications, quality expectations, and contractual obligations. A customer might reference “per customer quality specification Q1847, revision 3,” which you don’t have. Or they might state “all inspection shall be to industry standard ASTM D-something,” and if you’re not measuring with that standard, you’re out of compliance. Or they might require “full traceability to raw material supplier batch number,” which means you need to track not just your production lot, but where you sourced each batch of material. These requirements are often stated once, in the terms and conditions, and then assumed to apply to all orders from that customer unless specifically waived.
Some quality requirements are spelled out explicitly: “First article inspection required” or “100 percent dimensional inspection” or “Certs of Analysis required on all raw material.” Others are implicit: a reference to “per customer specification” assumes you know which specification, or “as per quality agreement dated 2019” assumes you have a copy of that agreement and have read it. Many POs reference international or industry standards without clearly stating which revision you should follow. If the PO says “per ISO 13849-1 safety control,” are they expecting certification to that standard, or just compliance? If they say “per API Q1 requirements,” do they mean the full API Q1 audit, or just compliance with specific elements?
Creating a PO Review Process
The only way to avoid surprises is to make PO review a formal step before you commit to production. When a customer PO arrives, send it through quality review before sending it to production. Your quality person should check: Does the PO reference any specifications or standards? Are there any requirements in the terms and conditions that affect how you’ll make or inspect the part? Are there any nonstandard inspection methods, documentation requirements, or traceability needs? Do you have copies of all referenced documents? If you don’t understand a requirement, ask the customer to clarify before you proceed. This takes 20 minutes per PO, and it catches 80 percent of the surprises before they become problems.
Maintaining Current Documentation
Customers often say “per quality agreement” or “per customer specification,” but they don’t always provide the current document. Sometimes they provide an outdated version. You need to know which version of each customer’s quality specification you’re currently bound to. Maintain a file of customer quality agreements, specifications, and any amendments or revisions. When a new PO comes in that references a specification, verify that you have the current version. If the customer has updated the specification since your last order, understand what changed before you bid on the job. Some changes are minor; some are substantial. A customer might add a new inspection requirement, a new certification requirement, or a tighter tolerance. You need to know this before you quote.
Common Quality Clause Traps
Several types of quality clauses cause consistent problems. First-article inspection (FAI) is often required but not always specified clearly. Does the customer want FAI on every new part number, or only on initial orders? Do they want it on all production, or just on tooling changes? Unwritten assumptions lead to conflicts. Certification and material documentation is another common trap. A customer might require “certified material” without specifying what certification they want. Do they want a mill certificate? A third-party testing certification? Compliance with a specific standard? Unless you clarify, you might receive material that’s certified to the wrong standard. Traceability requirements are also frequently misunderstood. “Full traceability” can mean different things: traceability to the raw material supplier, traceability to a specific production shift, traceability to the operator. Each requires different record-keeping, and you need to know which level the customer expects.
Communicating Constraints to Customers
Sometimes a customer’s quality requirements are impossible for you to meet with your current process or equipment. An FAI requirement that involves destructive testing, for example, requires that you have access to destructive testing capability—either on-site or through a subcontractor. A requirement for specific equipment or methods that you don’t have means you need to either acquire the capability or subcontract. A traceability requirement that goes beyond what your system can track means you need new software or a new process. If a customer requirement conflicts with your capability, surface that in the PO review step, not after production. Tell the customer: “this requirement would require X, which we don’t currently have capability for. Can we discuss an alternative?” Sometimes the customer will waive the requirement, sometimes they’ll accept a different approach, and sometimes they’ll accept increased cost to cover the additional work. But all of these conversations are better to have upfront.
Building Quality Clause Review into Quoting
The best time to identify and resolve issues with customer quality clauses is before you quote. When you receive an RFQ with terms and conditions, your quoting process should include quality review. If the job requires a capability you don’t have, your quote should call out the cost or the lead time impact. If you’re unsure how to meet a requirement, your quote should include a note asking for clarification. Customers would rather know upfront that a requirement is nonstandard or needs refinement than discover it after production starts and the part doesn’t meet expectations.
The relationship between quality requirements and production success is direct: you can’t deliver what you don’t understand, and you can’t understand a requirement if you don’t read it. Taking time to thoroughly review and clarify quality clauses before production is an investment in your first-time-pass rate and in customer satisfaction. QMS2GO’s audit preparation material includes templates for tracking customer requirements and for building quality clause review into your standard quoting and order-entry process.
