Automotive and aerospace tier-1/2 suppliers live and die by their submission discipline. A customer PPAP request lands, and the quality team scrambles across shared drives, Excel trackers and email threads to assemble 18 elements, chase sign-offs on the control plan and PFMEA, and hand-fill a Part Submission Warrant before the deadline. ERPNext gives you strong item, BOM, quality-inspection and document-attachment foundations, but it has no native concept of a PPAP package, an APQP phase gate, a PSW, or customer-specific requirements (CSRs). Stock Quality Inspection and Quality Goal DocTypes were never designed to model an 18-element submission or a five-phase advanced-product-quality-planning timeline, so teams bolt this onto spreadsheets that auditors distrust and revisions silently drift out of sync.

We build a proper Frappe app — its own module, not a pile of customizations — that adds the missing domain model directly into ERPNext. New DocTypes (PPAP Package, PPAP Element, APQP Project, APQP Phase Gate, Control Plan, PFMEA, Part Submission Warrant, Customer Specific Requirement) link to your existing Item, Customer, Supplier and BOM records so a submission is always tied to the real part and program. Each of the 18 PPAP elements becomes a checklist row with owner, status, attached evidence and a required/waived flag driven by the customer's chosen submission level (1–5). APQP work is tracked through phase gates with entry/exit deliverables, and hooks.py doc events plus server scripts enforce the rules that matter: a package cannot move to Submitted until every required element is complete and the control plan and PFMEA are approved; a PSW print_format auto-populates from the linked package, part and dimensional data so nobody retypes it. Client scripts drive the in-form UX (dynamic element visibility by submission level, gate-readiness indicators), role profiles and permission rules separate Quality Engineer, Quality Manager and read-only Customer-auditor access, and scheduler events raise reminders on approaching gate and submission due dates. Everything is exposed over the Frappe REST API and whitelisted methods, so a customer portal or an external APQP dashboard can read package status without touching the database directly.

Because this is build-to-order, nothing ships as a blind download. We start with a scoping call to map your customer base (Ford, VW, Stellantis, a specific OEM CSR set), your typical submission levels, and how your control-plan and PFMEA process actually runs today. We then build the app against Frappe/ERPNext v15 or v16, validate it on a staging copy of your data through UAT, and install it on your bench with a rollback plan. You receive the full source in a Git repository you own, technical and user documentation, a training session for your quality team, and a post-go-live support window. The result is an auditable, single-source-of-truth PPAP/APQP system that lives inside the ERPNext your operations team already uses — not another spreadsheet the auditor flags.