Most manufacturers lose real money to scrap and rework without ever seeing it clearly. In stock ERPNext you can back-flush a Job Card, post a Stock Entry of type Material Transfer for Manufacture, or hand-key a scrap line into a BOM, but there is no structured place to capture why a part was scrapped, no reason-code taxonomy tied to the operation and workstation, and no way to route a defective unit through a rework loop and re-inspect it. Quality and continuous-improvement managers end up rebuilding the picture in spreadsheets after month-end — by which point the Pareto of top defect causes is stale and the cost attribution is guesswork. ERPNext's native Quality Inspection is pass/fail against parameters; it does not cost the failure, link it to a CI project, or drive corrective action.

This app closes that gap with a proper Frappe application (scrap_management) installed onto your bench as an ERPNext dependency. We add first-class DocTypes — Scrap Entry, Rework Order, Scrap Reason (a tree/link master), and Waste Cost Line (child table) — so scrap and rework become auditable transactions instead of free-text notes. Capture happens where the work happens: a client script injects a "Log Scrap / Rework" action into the Job Card form so an operator records quantity, reason code, workstation, operation, and disposition (scrap vs. rework) without leaving the shop-floor screen. A hooks.py doc_events handler on Job Card and Stock Entry validates the scrap quantity against produced quantity and writes the linked scrap transaction on submit, and a validate hook on Rework Order enforces the re-inspection gate before the reworked quantity can rejoin good stock.

Costing is derived, not typed. Server-side controller logic values each scrap line from the item's valuation rate plus the operating cost consumed up to the failing operation (pulled from the Job Card's time logs and workstation hourly rate), so a unit scrapped at the last operation is correctly costed higher than one caught at incoming inspection. Whitelisted methods (@frappe.whitelist()) expose scrap capture and rework routing to the Frappe REST API and to Client Scripts, so barcode scanners, tablets, or an external MES can post scrap events programmatically. A scheduler event (scheduler_events in hooks.py, hourly/daily) rolls up open scrap into a Scrap & Waste Analysis Query/Script Report with a built-in Pareto view of reason codes, scrap value by item group, and defect-to-cost trend — the numbers a CI team needs for a Kaizen or Six Sigma project. Role Profiles and permission rules (Quality Manager, Production User, CI Analyst) scope who can capture, who can approve rework, and who can only read the dashboards.

Because this is build-to-order, you are not downloading a fixed marketplace app and bending your process to it. After a short scoping call we confirm your reason-code taxonomy, disposition workflow, costing rules, and which reports and roles you need, then build the app against Frappe/ERPNext v15 or v16 to match your bench. We deliver on a staging site for UAT first, then install to production with a documented rollback, and hand over the full git repository so the code is yours to keep and extend. Typical delivery is 2–4 weeks from confirmed scope.