Context
A garment factory is a flow of material. Fabric and yarn arrive, move through inspection and external processing, enter cutting and stitching, and eventually become finished goods. When that flow is split across paper registers and spreadsheets, the central question, “where is this order?”, becomes slow and unreliable.
Reve Stitching uses ERPNext as the core platform. I did not build ERPNext itself. My work is implementation and customization: translating the factory’s real workflows into records, constraints, scripts, reports and screens that staff can use every day.
Why ERPNext
ERPNext provides a mature open-source base for stock and manufacturing, with the Frappe framework available for customization. That made it more practical than licensing a large enterprise suite or rebuilding common ERP foundations from scratch.
The standard system is deliberately general. The engineering work begins where a garment factory’s physical process stops matching the generic workflow.
What was customized
Stock movement. Material Receipt, Transfer, Issue and Return flows were configured so the digital record follows the physical movement of goods through the factory.
Batch and LOT traceability. Custom batch fields capture the operational details needed to identify and locate fabric, including party, order, pantone, received quantity, rolls, stock status and days in stock.
Gate passes. Dyeing and inward movement use digital gate-pass workflows instead of isolated handwritten records. This connects external processing to the same traceability model.
Scope boundary. The legacy system was used chiefly for Fabric Store stock, batches, gate passes and Stock Entries. Broader order, production and quality modules included prototypes and configuration; they are not evidence of factory-wide adoption. REVE ONE is the separate application built to develop those workflows.
Reports and workspaces. Custom reports such as the Fabric Stock Register expose live operational data. Frappe desk and workspace customization keeps the relevant tasks visible without forcing staff through unrelated ERP modules.
Automation. Client scripts set safe defaults and validate common Stock Entry paths. Server methods create and recalculate batches, maintain status through cancellation and enforce item-level constraints. Barcode-supported store workflows reduce manual lookup during receipts and returns.
Implementation constraints
The main constraint is adoption. A technically correct workflow fails if it adds friction on the factory floor. Screens and defaults are tested against the real task, then simplified until the digital path is at least as direct as the paper path it replaces.
Privacy is another constraint. Buyer names, suppliers, prices, internal orders and staff identities belong inside the system, not in a public case study. The workflow diagram describes the architecture without exposing operational records.
Result
The operational work established stock movement, batch traceability, gate-pass and reporting workflows. Historical ledger balances still require physical reconciliation and approved valuation before any new system cutover; internal consistency alone does not prove current stock accuracy.
Lesson
ERP implementation is modeling work: understand how material moves, encode it clearly, then make the resulting workflow easier to follow than the old one.