Why a separate application
My earlier ERPNext work focused on Fabric Store stock, batch and gate-pass workflows. I started REVE ONE to bring related garment-manufacturing tasks into a focused application interface, while retaining ERPNext as the transactional foundation.
I started REVE ONE to build that application layer: an operator should be able to find a factory order, understand its next step and follow related materials or quality work without navigating unrelated ERP screens. It is distinct from the legacy ERPNext customization.
Architecture and ownership
A Vue 3 and TypeScript interface runs on a Frappe application backed by Python APIs and ERPNext. Vue Router separates the workspaces; Tailwind and Frappe UI support a consistent shell and reusable record interfaces. Frappe sessions, CSRF checks and server permissions remain the authority for access.
ERPNext owns native stock and accounting records. REVE ONE adds garment-specific interfaces and related workflow context. Keeping those responsibilities distinct avoids maintaining a competing inventory ledger.
Interface engineering
The application shell provides grouped navigation, dark and light themes, session-aware controls, search and notifications. Record pages share headers, list controls and clear loading, empty, error and permission states. The interface is designed around the next action and the relevant evidence, rather than a dashboard full of disconnected totals.
Order 360 gathers related activity and operational context in one place. Navigation visibility follows role capabilities, but hiding a button is never treated as a security boundary: the backend checks the action too.
Application workspaces
Factory orders, planning and production. Factory orders, planning and production are connected workspaces. The interface brings related order context and production progress together so users can follow the work across stages.
Materials and store operations. Material requirements, stock visibility, batches, physical rolls, scanning, issues, transfers and returns are organized as operator tasks. Stock postings use native ERPNext transactions.
Cutting consumption and remnants. Cutting interfaces connect issued fabric with returned remnants and related order context. The aim is to make consumption understandable while keeping the supporting stock transactions traceable.
Quality and corrective actions. Checks, defects and follow-up actions have explicit ownership and state. They connect to Order 360 and related production context so an unresolved quality issue can be followed through the workflow.
Shared workflows. Activity, notifications and search help users find related records. Workforce, packing and reporting workspaces extend the same application structure. Implemented modules are not a claim that every department has adopted them.
Gate passes, rolls and inventory review
Gate-pass and physical-roll interfaces connect material handling with inventory context. Stocktake and reconciliation work provide a separate place to review counted stock and differences. These are software capabilities and development areas; their inclusion here does not imply accepted physical balances or production adoption.
Engineering trade-offs and validation
Building on ERPNext preserves a shared transactional foundation, but it makes integration testing important. I separate interface feedback from server validation, keep loading and failure states explicit, and use role-aware controls without relying on navigation visibility for authorization.
Backend tests and Playwright interface tests support the development process. Testing software behavior is distinct from confirming deployment, data quality and day-to-day operational use. This portfolio does not present historical project tests as a fresh production acceptance run.
Current status
REVE ONE is application-development and staged-integration work. Production deployment and factory-wide adoption are not independently established, so I do not describe it as a fully operational factory system. The public overview intentionally omits internal rollout records and compatibility findings.
Both diagrams are illustrative. They show the engineering relationships without displaying company records, internal endpoints or production screenshots.