ERPNext manufacturing visibility: status is not consequence

Short answer. ERPNext records manufacturing very well: every sales order, work order, job card, BOM, stock movement and purchase order is there. Its dashboards and reports are built around status — how many work orders are open, which purchase orders are overdue, how much stock sits in a warehouse. The question a production manager asks at 8 AM is about consequence: which customer promise is about to break, because of what, and what to fix first. Answering it means joining several documents in time order. ERPNext holds the data for that join; it does not do the join for you.

What ERPNext already shows you

Out of the box, the Manufacturing workspace and the standard reports answer many “what is the state of X?” questions. Names vary slightly between ERPNext versions.

Where	What it answers
Manufacturing dashboard — number cards and charts such as Work Order Analysis, Pending Work Orders, Produced Quantity, Job Card Analysis, Downtime Analysis	How many work orders are in each status, how old the pending ones are, how much was produced, where machines were down
Open Work Orders, Work in Progress Report, Work Order Summary, Job Card Summary	Which work orders have not started, which are running, how far each has got
Production Planning Report, BOM Stock Report	Whether raw material on hand covers a BOM or a set of orders
Stock Projected Qty, Stock Balance	Actual, ordered, planned and reserved quantity per item and warehouse
Purchase Order Analysis	Which purchase order lines are still to be received
Sales Order Analysis	Which sales orders are still to deliver, and against which date

All of these are useful, and an implementer can add Script Reports or Frappe Insights dashboards on top. They share one property: each looks at one kind of document at a time and reports its state.

The five questions at 8 AM

From hands-on ERPNext manufacturing work, the questions a production or operations manager needs answered every morning are usually these:

1. Which customer orders are at risk this week?
2. Which shortage matters first?
3. Which work order is waiting on another one?
4. Which work center is the bottleneck this week?
5. Can I trust the stock number I am looking at?

Question	ERPNext has the data in…	What the person still has to do
Which orders are at risk?	Sales Order, Work Order, BOM, Bin, Purchase Order	Walk each order down to its materials and supply, and compare dates
Which shortage first?	Production Planning Report, Stock Projected Qty	Decide which shortage hits the earliest or most important promise
Which work order waits on another?	Work Orders for sub-assemblies, BOM structure	Connect the internal supply chain by hand
Which work center is overloaded?	Job Cards, Workstation, Work Order operations	Add up planned hours per day against available hours
Can I trust the stock?	Stock Ledger, Stock Reconciliation	Notice when postings lag the floor

None of these answers is a single field. Each is a chain across documents, and the chain only means something when you add time: when is the material needed, and when can it credibly arrive?

Status versus consequence, in one example

Synthetic demo scenario: a fictional apparel plant used to test TaktSignal. Not customer data. Monday 10:00.

Record	Status on its own screen
Sales Order SO-2108	60 jackets, promised Friday 17:00 — open, not late
Work Order WO-2307	Submitted; Cutting planned Tuesday 08:00
BOM	2 m black cotton fabric per jacket — 120 m for the order
Stock	20 m usable
Purchase Order PO-917	100 m ordered, 50 m received, 50 m open; due last Thursday, no revised date

Every status is correct, and nothing is late yet. Read as a chain, Friday's shipment is already in doubt: Cutting needs 120 m tomorrow, 20 m is usable, and the only supply is overdue with no new date. Even if it arrived today, the order would still be 50 m short. The full walk-through, with the ERPNext reports to use at each step, is in Every ERPNext document is correct. So why is the delivery at risk?.

That is the difference this site keeps returning to:

• Status says what a document is: open, overdue, 20 m.
• Consequence says what it does to a promise: SO-2108 cannot be confirmed for Friday unless 100 m of fabric is found, and here is the evidence.

What a consequence view needs

Whether you build it with a disciplined morning routine, a custom report or a separate tool, seeing consequence takes the same four ingredients.

1. Start from the promise. Begin at the sales order's delivery date, not at a list of shortages. A shortage that touches no order due this month is not this morning's problem.
2. Walk the dependencies in time. Sales order → work order → the operation that consumes the material → the material → its supply. Compare when it is needed with when it can credibly arrive.
3. Count only what is really usable. Stock in the right warehouse, not already reserved for another work order; supply with a credible date before the need. See “Material available” doesn't mean production can start.
4. Know how much to trust the data. If stock postings lag the floor, every conclusion inherits that doubt. See Stale ERP data creates false confidence.

Three ways to get there

A morning routine. Free and immediately useful: start from orders due in the next 7–14 days and walk each chain with standard reports. It depends on one person doing the joins every day, and shared materials make it hard to see which promise breaks first.

A custom report or dashboard. A Script Report, Query Report or Frappe Insights dashboard can join sales orders, work orders, BOM items, stock and purchase order lines. The hard parts are not the joins but the rules: timing, allocating shared material across orders, deciding when an overdue purchase order still counts as supply, and keeping it all maintained as processes change.

A read-only layer next to ERPNext. This is the category called manufacturing operational intelligence: software that reads the records continuously, walks the chains and ranks the consequences with their evidence. It does not replace ERPNext, an MES or a scheduler.

Where TaktSignal fits

TaktSignal is a read-only operational intelligence layer for ERPNext. It reads sales orders, work orders, BOMs, stock and purchase orders with a dedicated ERPNext account that can only read, and it is designed to show consequence: which delivery a problem threatens, why, the time at stake and how sure it is. Every alert shows its evidence; the rules are deterministic, not AI. How alerts work.

It is a Community Alpha: tested with synthetic factories and against ERPNext 15 and 16, but not yet validated in real factories. Start with a staging or test copy of ERPNext.

FAQ

Does ERPNext have a manufacturing dashboard? Yes. The Manufacturing workspace has number cards and charts for work order status, pending work orders, produced quantity, job cards and downtime. They describe status; they do not link a problem to the customer order it threatens.

Is Frappe Insights enough? Insights can chart any query you write, and it is a good tool for status dashboards. For consequence you still have to design the joins, the timing rules and the priority yourself.

Is this the same as an MES? No. An MES runs and records shop-floor execution. A consequence view reads what ERPNext already knows and points people at what to check first.

Do I need perfect ERPNext data first? No, but you need to know how good it is. A view that flags stale or doubtful data is safer than one that presents every number with the same confidence.