Supplier Quality & Vendor Scorecard

ECOSIRE builds a proper Frappe app (supplier_quality) installed onto your bench, not a pile of custom fields. It ships new DocTypes — Incoming Inspection, Supplier Corrective Action Request, Vendor Scorecard Period, and Approved Vendor — linked to standard Supplier, Item, and Purchase Receipt records so nothing is duplicated. Inspection results captured against a receipt line write reject quantities and defect codes back through hooks.py doc events (on_submit, validate), and scheduled events (scheduler_events in hooks.py) aggregate rejects into defect PPM and reject-rate figures per supplier and per item on a nightly or period cadence. A failed inspection can auto-raise a SCAR and route it through a Frappe workflow (Open → Containment → Root Cause → Corrective Action → Verification → Closed) with due-date reminders and assignment.

Weighted scorecards are computed server-side: you configure the weights (e.g. quality 50%, delivery 30%, cost 20%) and the app rolls each supplier's period metrics into a graded score, surfaced on dashboards and a print-format scorecard PDF you can send to the vendor. Whitelisted methods exposed over the Frappe REST API let your other systems pull a supplier's current grade or push inspection data, and client scripts add in-form buttons (raise SCAR, view trend) on the Supplier and Purchase Receipt forms. Access is governed by permissions and a dedicated "Supplier Quality Engineer" role profile so procurement, quality, and management each see the right slice.

Because this is build-to-order, nothing ships until we agree on scope. We start with a short scoping call, confirm your defect taxonomy, scorecard weights, SCAR stages, and AVL rules, then build against Frappe/ERPNext v15 (and v16 where you are already migrated). Typical delivery is 2-4 weeks from confirmed scope. You get the installable app source, a UAT pass on your staging bench with a rollback plan, a documented handover, and a post-go-live support window — not a black box.