Customer-Specific Requirements
In addition to the standard AIAG PPAP requirements, each customer may define customer-specific requirements (CSRs) that must be included as part of the PPAP submission.
These requirements vary by OEM and customer and may include additional documentation, approval steps, submission formats, or validation activities beyond the core PPAP elements.
Understanding customer expectations
It is considered best practice to confirm PPAP expectations with the customer before quoting or accepting work. Early clarification helps avoid:
- Unexpected documentation requirements
- Delayed approvals
- Additional costs or rework
Customer-specific requirements may affect:
- PPAP submission level
- Required studies or testing
- Approval authority and sign-off
- Ongoing reporting or audit expectations
OEM requirements and reference sources
Most North American automotive OEMs publish their customer-specific requirements through the International Automotive Task Force (IATF). These documents outline additional PPAP, APQP, and quality system expectations that suppliers must follow.
Suppliers should always refer to:
- OEM supplier portals
- IATF-published customer-specific requirement documents
- Contractual or purchase order requirements
Key considerations
- Customer-specific requirements override generic PPAP guidance where conflicts exist
- Requirements may differ between customers—even for similar parts
- Updates to CSRs must be monitored and implemented
- All CSRs must be clearly referenced within the PPAP package
Failure to comply with customer-specific requirements is a common cause of PPAP rejection or delayed approval, even when all standard PPAP elements are complete.
Why this matters
Customer-specific requirements ensure that PPAP submissions meet the unique needs of each OEM while maintaining consistent quality and compliance across the supply chain.
Understanding and managing these requirements is essential for successful PPAP approval and long-term customer relationships.