QM in Sales and Delivery: Customer Quality Requirements and Outbound Inspection
Understand how quality requirements can extend into sales and delivery so customer-specific inspection, certificates and release controls are completed before goods leave the business.
Explanation
📌 KEY POINTS
✅ Sales/delivery execution can trigger a quality-relevant check instead of relying only on production or procurement inspection.
⚠️ Passing production inspection does NOT automatically satisfy every customer contract.
💡 Outbound quality must be coordinated with ATP, picking, and goods issue — release too late wastes completed warehouse work.
━━━━━━━━━━━━━━━━━━━━
▶ 1. WHY QM PARTICIPATES IN OUTBOUND
- Verifies product quality before customer delivery
- Exact design depends on material, customer, and inspection settings in the release
━━━━━━━━━━━━━━━━━━━━
▶ 2. CUSTOMER-SPECIFIC REQUIREMENTS
- Additional characteristics, tighter limits, inspection certificates, or batch documentation
- Preserve the link from sales/delivery document to material, batch, and inspection evidence — proof of which result supported shipment
━━━━━━━━━━━━━━━━━━━━
⚠️ 3. THE ASSUMPTION TO AVOID
- Passing production inspection does not automatically satisfy every customer contract — a customer can require extra testing, a specific certificate, or a release rule
━━━━━━━━━━━━━━━━━━━━
▶ 4. TIMING COORDINATION
- Outbound quality must be coordinated with ATP, picking, and goods issue
- Releasing too late means completed warehouse work for stock that still can't ship
━━━━━━━━━━━━━━━━━━━━
▶ 5. DEFINE THE FAILURE PATH UPFRONT
- Does failed outbound inspection block delivery, trigger rework, create a notification, or require customer waiver?
━━━━━━━━━━━━━━━━━━━━
▶ 6. ACROSS RELEASES
- Concept unchanged; certificate and complaint data increasingly flow through embedded analytics for sales/account visibility
✅ CHECKPOINT: why can a shipment fail a customer's quality bar even after passing production inspection?
Real project scenario
A customer contract required an additional certificate and tighter moisture specification. Production inspection passed, but the delivery could not be released until the customer-specific outbound quality check was completed.
Common mistakes
- Assuming production quality automatically satisfies customer requirements.
- Losing batch-to-customer traceability.
- Generating certificates from uncontrolled data.
- Performing outbound inspection after warehouse loading.
- Allowing shipment override without approval.
Best practices
- Define customer-specific requirements explicitly.
- Link quality evidence to delivery and batch.
- Coordinate release with warehouse timing.
- Govern waivers.
- Keep certificate data traceable.
Interview angle
Explain why QM in sales can require additional quality evidence beyond manufacturing inspection.
Practice this lesson
Quick check
1. In the lesson "QM in Sales and Delivery: Customer Quality Requirements and Outbound Inspection", consider this project situation: A customer contract required an additional certificate and tighter moisture specification. Which statement is correct?
2. A company wants to ensure that certain customers automatically receive a quality certificate with every delivery of a specific material. Which QM functionality supports this requirement?
3. What is the typical consequence of an active quality-inspection-related delivery block on a sales order item?
Interview questions
1. A project team is working on QM in Sales. Using the QM in Sales and Delivery: Customer Quality Requirements and Outbound Inspection scenario, how would you approach the requirement from design through validation?
Answer it in your own words first, then compare.
2. What design decisions and trade-offs matter most when implementing QM in Sales, particularly for QM in Sales and Delivery: Customer Quality Requirements and Outbound Inspection?
Answer it in your own words first, then compare.
Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.
More lessons in this topic
Interview questions on this topic
Related SAP topics
- Advanced Quality, Certificates, SPC, Calibration and Compliance
- Quality Management Foundation, Master Data and Planning
- Quality Notifications, Nonconformance, CAPA and Complaints
- Quality Inspection in Procurement, Production, Inventory and Sales
- S/4HANA Quality Management, Migration, Public Cloud and Architecture
- Inspection Lot Processing, Results Recording and Usage Decision