---
title: "Discussion on \"Frappe ERPNext Manufacturing: Compare Planned and Actual Material Use\" | Hashnode"
description: "Discussion on \"Frappe ERPNext Manufacturing: Compare Planned and Actual Material Use\". A production pilot that connects the BOM, extra issues, unused returns and remaining work in progress."
url: "https://hashnode.com/posts/frappe-erpnext-manufacturing-planned-actual-material-use/6afd60dab2fcb6d1098ba6f0"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Frappe ERPNext Manufacturing: Compare Planned and Actual Material Use](https://erpnova.hashnode.dev/frappe-erpnext-manufacturing-planned-actual-material-use?utm_source=hashnode&utm_medium=feed)

A production pilot that connects the BOM, extra issues, unused returns and remaining work in progress.

1d ago · 4 min read · erpnova.hashnode.dev  
Read the article

-   [#erpnext](https://hashnode.com/tag/erpnext)
-   [#manufacturing](https://hashnode.com/tag/manufacturing)
-   [#data-quality](https://hashnode.com/tag/data-quality)

## Written by

[Andy R](https://hashnode.com/@erpnova)

@erpnova · Chennai, India

  
[View profile](https://hashnode.com/@erpnova)

Founder at ERPNova.co. Company has expertise in the building the AI implemented ERP Solutions for our Manufacturing customers.

## Responses 2

Markdown supported · ⌘↵ to post

[Dov at HireDov](https://hashnode.com/@hiredov)

[1d ago](https://hashnode.com/posts/frappe-erpnext-manufacturing-planned-actual-material-use/6afd60dab2fcb6d1098ba6f0/comment/6afdd3b77a35787d0bbb411f)

The 220 kg issued vs 212 kg net example is the part most teams skip: an issue is movement, not consumption. One thing that helped me think about variance is tagging each extra issue with a reason code (scrap, rework, supplier material out of spec), because a 6% overage means something very different if it traces back to a bad lot from one vendor. It also gives you real data when you renegotiate yield assumptions or order more material, rather than guessing and cursing at the spreadsheet later. Have you seen teams actually log a reason on every extra issue, or does that fall apart on a busy shift?

[Andy R](https://hashnode.com/@erpnova)

[1d ago](https://hashnode.com/posts/frappe-erpnext-manufacturing-planned-actual-material-use/6afd60dab2fcb6d1098ba6f0/comment/6afdd3b77a35787d0bbb411f#reply-6afe15384a40aceeff85ab28)

I think it can work on a busy shift if it’s one tap. The operator should be able to pick ‘Unknown’ when the cause isn’t clear, and the shift lead can follow up at handover. If a bad lot is suspected, capture the lot number at the time of issue so it can be traced later.
