Community Alpha · early public testingManufacturing Operational Intelligence for ERPNext
TaktSignal reads your ERPNext operational data — sales orders, work orders, stock and purchase orders — and helps your team see material, production, capacity and data-trust risks earlier, with the reason, the evidence and how sure it is.
SO-1042 · Harbor & Pine Outfitters
Projected 4.3 h late for the Thu 12:00 ship date
Suggested investigation
Ask the supplier about a split shipment for PO-773; review whether WO-2241 cutting can start with the 477 m on hand.
Tested thoroughly with automated and synthetic factory labs, not yet across enough real factories. Start with a staging copy of ERPNext and check alerts against it. What that means for you.
01/The problem
Most factories don't lack data. They find out too late. Each record looks healthy on its own screen; the delay only exists in the relationship between them — and someone has to discover it by opening five reports, a spreadsheet and a chat with purchasing.
SO-1042
400 tees, ships Thu 12:00
WO-2241
Released, cutting starts Mon 08:00
FG-TEE-BLK-M
1.55 m jersey per unit → 620 m
RM-COTTON-BLK
477 m in the fabric store
PO-773
Confirmed, arrives Tue 14:00
Read together
Cutting needs 620 m on Monday at 08:00. Only 477 m exists until Tuesday 14:00. WO-2241 waits 30 hours, and SO-1042 misses Thursday — unless someone acts today.
TaktSignal reads these records together, continuously, and raises the collision while there is still time to act.
02/What we optimise for
TaktSignal has one goal: minimise avoidable factory time loss. Much of it comes from a handful of patterns that are often visible in ERP data before they hit the floor — if someone connects the records in time.
Waiting for material
Cutting is ready, fabric isn't. The line idles or is re-planned in a hurry.
Blocked downstream work
One held operation stops every step behind it, and the orders that depend on them.
Late starts
A work order that should have started this morning quietly hasn't.
Work-center congestion
Sewing Line 2 is planned at 137% on Wednesday. Something will wait.
Stalled WIP
No progress reported for 19 working hours. Nobody noticed yet.
Numbers you can't trust
Stock that isn't really there turns a safe plan into a stoppage — and hours of reconciling.
Needs attention
ranked by time at stake
Material wait at Cutting
CriticalRM-COTTON-BLK · WO-2241 · SO-1042
Queue at Sewing Line 2
Critical137% planned on Wed · 3 orders
Minor overload at Printing
Lowered to lowNo customer order affected
Not another wall of red KPIs. Issues are ordered by severity and by the factory time each one can cost. Small issues that touch no customer order are shown one level lower, so the list stays short enough to act on before 9 a.m.
03/Operational risk
Every alert answers the same five questions, in the factory's own terms — order numbers, work centers, materials and hours, not abstract scores.
Examples from TaktSignal's synthetic demo plant — no customer data. Impact and confidence are rule-based estimates.
04/Root-cause trace
A delivery risk is always downstream of something physical: a roll of fabric, a machine, a person, a supplier. TaktSignal walks the chain from the customer order through the work order and its operations to every material and work center involved — and shows which link is the critical one.
Customer order
SO-1042
Harbor & Pine Outfitters · ships Thu 12:00
Finished item
FG-TEE-BLK-M
400 units · black tee, M
Work order
WO-2241
Routing: Cutting → … → Sewing → … → Packing
Operation 10
Cutting
Planned Mon 08:00
Material
RM-COTTON-BLK
620 m needed · 477 m available
Constraint
143 m short
Until PO-773, Tue 14:00 (+30 h)
Operation 30
Sewing
Planned Wed
Work center
Sewing Line 2
137% planned on Wed
Constraint
≈ 5.6 h queue
Bottleneck of the week
Customer delivery risk
CriticalSO-1042 projected 4.3 h late
Critical chain: the material wait at Cutting, then the Sewing Line 2 queue.
05/Explainable by design
TaktSignal's engine is deterministic and rule-based. The same data always produces the same answer, the rules are documented and versioned, and every alert shows its working — so a planner can check it before acting on it.
What most tools show
82
Risk score. Model v3.
A number nobody on the floor can verify, argue with or act on. Is 82 bad? Compared to what? Because of which order?
What TaktSignal shows
Critical delivery risk · SO-1042Projected 4.3 h late because:
Suggestions are phrased as investigations, and every person's action — acknowledge, assign, note, resolve, record what actually happened — is kept in an audit trail. Recorded outcomes are how the alerts are held to account.
TaktSignal never, on its own:
06/Operational reconciliation
After a few months, ERP stock and physical stock drift apart: scrap nobody booked, offcuts back on the shelf, a supplier who shipped 3.5% extra, a count that was never entered. A risk engine that blindly trusts the ERP makes confident mistakes. TaktSignal checks the numbers first.
Work-order material variance · black cotton jersey
Variance +28 m, split into what is known and what isn't:
Supplier receipt · white cotton jersey
+35 m physically on hand that the ERP doesn't know about — and wasn't invoiced.
Receipt GRN-0770 · PO-770
Not verifiedPhysical quantity: unknown.
TaktSignal never invents physical quantities. If nobody counted, it says so — and says what that means for the alerts that depend on it.
Known vs unexplained
Scrap, rework, returns, offcuts and people's explanations are separated from variance nobody can account for — in quantity, % and money.
Trust feeds risk
A shortage computed from a material with drifting stock is flagged with lower confidence, with the reason on the alert.
Patterns, not one-offs
5 of 5 grey-hoodie orders used 4.5% more fleece than the BOM. That's a BOM to investigate — TaktSignal never changes it.
07/What-if
Try +20% demand, a line losing a shift, or a supplier slipping three days. TaktSignal re-runs the same analysis on a copy of today's data and shows which orders tip into risk. Live data is never touched. It is not a scheduler — it tells you what breaks, you decide what to change.
Scenario: demand +20%
computed on a copy
| Measure | Today | Scenario |
|---|---|---|
| Customer orders at risk | 3 | 5 |
| Sewing Line 2 peak load | 137% | 161% |
| Material shortages | 2 | 6 |
08/How it works
TaktSignal is not an ERP, MES or scheduler. It reads what ERPNext already knows, connects it, and tells people where to look first.
ERPNext
Your system of record. Nothing changes in how you use it.
Read-only connection
A dedicated API user with read permission only. Incremental sync every 5–60 min.
Operational model
Orders, work orders, operations, BOMs, stock, receipts — normalised, units converted, cancellations applied.
Risk + reconciliation
Deterministic engines project timing, capacity and material, and check whether the numbers hold up.
Attention
A short, ranked list: what will cost time, when, why, how sure — with data freshness shown.
People act
Planners, purchasing and production decide. TaktSignal records the outcome.
ERPNext-first
TaktSignal is designed to integrate with ERPNext through its standard REST API and understands how manufacturing actually runs there: submitted vs cancelled documents, stock vs purchase units, work-in-progress warehouses, split job cards, transfers for manufacture and returns.
Document types read
Exercised with ERPNext 15.121.4 and 16.36.0 using synthetic factory data; real-factory validation is what the Community Alpha is for. ERPNext and Frappe are trademarks of Frappe Technologies. TaktSignal is independent and not affiliated with or endorsed by Frappe.
09/Privacy & data boundaries
Your ERPNext. Your machine. Your database. Your factory data. TaktSignal reads operational information from ERPNext to help surface risk. It does not need to watch you.
Your ERPNext
System of record
Never written to
Your computer
TaktSignal + its local database
The operational copy, backups and logs live here — only here.
Read-only ERPNext connection
TaktSignal uses a dedicated ERPNext account that can only read. TaktSignal only sends read requests — it never creates, changes, submits or deletes anything in ERPNext — and setup stops if ERPNext reports write permissions for the account.
Your data is stored locally — on purpose
TaktSignal keeps an operational copy of the ERPNext data it reads in its own PostgreSQL database on your computer. It needs that copy to work. It is yours, and it stays there.
No central collection of factory data
There is no TaktSignal cloud receiving your data. Factory data is never uploaded to us, never sold, never shared with advertisers and never used to train AI models.
No telemetry, no product analytics
The installed product does not track how you use it. No usage analytics, no crash-reporting service, no installation ID, no device fingerprinting.
LLM data sharing is off by default
Alerts come from documented rules, not AI. The desktop Community Alpha has no AI data sharing at all; server installations can switch on an optional AI wording of the daily brief, which is off by default.
Diagnostics only when you ask
A support file is created only when you click Export diagnostics, and you decide whether to send it. It contains no passwords, API keys, ERPNext address or company, customer, supplier or user names.
Being precise about what we don't have yet: the Community Alpha builds are not code-signed, and TaktSignal has no external security audit or certification (no SOC 2, no ISO 27001). Every promise above is checked by automated privacy tests in our release process.
10/The product
The demo runs the real product on a synthetic apparel plant: 18 active work orders, 7 work centers, 15 customer orders and six weeks of history. Start on the morning dashboard, open the black-jersey shortage, and trace it through WO-2241 to SO-1042.
Screenshots and all examples on this page use TaktSignal's synthetic demo plant. No customer data.
11/Design partners
Beyond the open download, we are looking for a few design partners — manufacturers on ERPNext willing to run the Community Alpha alongside their operations and tell us, honestly, whether it catches problems earlier than they do today. It is early software; this is how it gets better.
Design partnership (optional)
Free during Community Alpha. Scope and timing are agreed per factory; the timeline is a typical example, not a promise.
Install and connect
Install the Community Alpha, create the read-only ERPNext Reader and run the first sync. We help over a call if you want.
Check the data
Walk through stock, work orders and orders with your planner until TaktSignal's view matches ERPNext and the floor — or tell us where it doesn't.
Run alongside operations
Your team looks at the dashboard and records, on each alert, what actually happened and whether it was right.
Review together
What was caught, how early, what was noise, what TaktSignal misread — from the outcome counts you choose to share.
We don't have customer results to quote yet, so we won't invent any. These are the measures each design partnership is judged on, computed from the outcomes your team records in TaktSignal.
Tell us a little about your plant and the problem that costs you the most time. We'll reply personally — no sales sequence. What you send is used only to answer you (see the privacy policy).
Please don't send ERPNext credentials, API keys or production data through this form. TaktSignal runs on your side; we never need access to your ERPNext.
Prefer email? work.manhcang@gmail.com
12/Questions
Manufacturing Operational Intelligence for ERPNext. It reads your ERPNext production data and shows where the factory is about to lose time — material shortages, stalled or late work, overloaded work centers, customer orders at risk — with the reason, the evidence and a confidence label, and it checks whether the numbers behind them can be trusted.
No. ERPNext remains your system of record. TaktSignal is not an ERP, not an MES and not a scheduler; it reads what ERPNext knows and tells people where to look first. People decide what to change, in ERPNext.
No. It uses a dedicated read-only ERPNext account, only sends read requests and never creates, submits, amends, cancels or deletes documents. Setup stops if ERPNext reports write permissions for the account. Create the read-only Reader.
No. TaktSignal is in Community Alpha — early public testing. Use it alongside ERPNext and your own checks, starting with a staging or test copy of ERPNext, and do not rely on it alone for critical production decisions.
TaktSignal has been through substantial automated, synthetic and internal validation, but it has not yet been validated across enough real factories, ERPNext configurations and desktop environments. Community Alpha exists to gather that evidence.
Because real ERPNext users telling us where TaktSignal is right, wrong or confusing is what it needs most right now. The exchange is your feedback — not your data: TaktSignal does not collect factory data, show ads or sell anything about you.
On your computer. TaktSignal keeps an operational copy of the ERPNext data it reads in its own local PostgreSQL database — it needs that copy to work — together with backups and logs. What exactly is stored.
No. There is no TaktSignal cloud receiving factory data. The installed product talks to your ERPNext and, only when you click Check for updates, to the TaktSignal release server — which receives no factory data or identifiers.
No. No telemetry, no usage analytics, no crash-reporting service, no installation ID, no device fingerprinting — and an automated check in our release process fails if any of that is added.
No analytics, no advertising or tracking scripts, no cookies. Your browser loads nothing from third parties on this site. The web host sees normal request information (such as your IP address) like any website and may keep access logs; we don't use them to profile anyone. Privacy policy.
The core does not use AI: risk, time impact, confidence and reconciliation come from documented, versioned rules, so every result can be traced. The desktop Community Alpha sends no factory data to any AI provider. (The server edition has an optional AI wording of the daily brief; it is off by default.)
ERPNext 15.121.4 and 16.36.0, with synthetic factory data. Older versions connect with a warning and are not validated. Heavily customised sites may be read incompletely — the Data Trust screen shows where.
macOS on Apple Silicon and Linux x64 (Ubuntu / Debian .deb) are tested Community Alpha platforms. Windows x64 is experimental. Intel Macs are pending. Details per platform.
The Community Alpha for Mac is an unsigned test build — not yet signed with an Apple Developer ID or notarized. macOS says “Apple could not verify TaktSignal is free of malware” for such apps. It is not a malware finding, and not a guarantee either. How to approve only this app, safely.
The Windows installer has been built, but it has not completed the same install testing on real Windows PCs as the macOS and Linux builds, and it is not code-signed yet. It is offered for community testing only when an experimental build is published.
Uninstalling keeps your data by default. To delete everything TaktSignal stored on your computer, choose Remove all TaktSignal data and type DELETE — this never touches ERPNext. Uninstall and delete your data.
Export the redacted diagnostics file from the Control Center and follow the support page. Never post API keys, passwords, backups or customer data. Security issues: report privately.