On a busy shop floor, the gap between what happened physically and what ERPNext knows is measured in hours. Operators move pallets, issue raw material to a work order, and finish operations — then someone keys it all into Stock Entries and Job Cards at the end of the shift, transposing digits and guessing at timestamps. Stock ERPNext gives you excellent Manufacturing and Stock DocTypes (Work Order, Job Card, Stock Entry, Serial No, Batch), but out of the box it assumes a person at a desk typing form fields. There is no first-class handheld capture flow, no RFID read-point concept, and no way to scan a GS1 label and have the right batch, serial, warehouse, and operation resolve automatically. That is exactly where teams fall back to spreadsheets and lose traceability.

We build a proper Frappe app — its own module, DocTypes, and permission set — that turns scanning into the primary way work is recorded. A lightweight mobile/handheld capture screen (a Frappe web form / desk page tuned for rugged scanners and phone cameras) lets an operator scan a job card barcode to clock in, scan material to issue it against the active work order, and scan the finished handling unit onto a pallet. Each scan hits a whitelisted @frappe.whitelist() method over the REST API that validates the code, resolves the linked Item, Batch, Serial No, and Warehouse, and writes the corresponding Stock Entry or Job Card Time Log transactionally — so ERPNext stock and WIP reflect reality within seconds, not hours. RFID reads (fixed portals or handheld UHF readers) post to the same endpoints, letting you track pallets and containers as Handling Unit records mapped to serial/batch contents. hooks.py doc events keep everything consistent (e.g. validating that a scanned serial belongs to the work order's BOM, blocking a clock-out with no matching clock-in), client scripts drive the scan-focus and beep/error UX, and scheduler events reconcile open job cards and flag stale WIP.

Labeling is treated as a real subsystem, not an afterthought: we build GS1-compliant label templates (Code128, GS1-128, QR, Data Matrix) generated from Print Formats or a ZPL pipeline, so every item, batch, serial, and handling unit carries a scannable identity from goods receipt onward. Role profiles and permission rules scope who can issue material versus who can only clock time, and every scan is auditable. The app is built and tested against Frappe/ERPNext v15 and v16, installs via bench get-app / bench install-app, and upgrades cleanly through standard migrations rather than untracked customizations that break on the next update.

Because this is build-to-order, nothing is a black-box download. It starts with a scoping call where we map your operations, hardware (scanner and RFID reader models, label printers), and the exact material/WIP/labor flows you want to digitize. We then build against that specification, stand it up on a staging copy of your ERPNext site for UAT, and only cut over to production once you have signed off — with a documented rollback. Typical delivery is one working week from confirmed scope, and you receive the full source in a git repository so the app is yours to run, audit, and extend.