17Modules, order to dispatch
100+Doctype specification translated
REST-onlyBoundary with ERPNext
The problem
A foundry needed an ERP for its own operations, from sales order to dispatch, with heat-number traceability, while finance and payroll already lived in ERPNext.
What we built
A domain-specific ERP that owns all foundry data end to end: sales order to dispatch, production planning, melting and metallurgy, quality, inventory, maintenance and costing, with heat-number genealogy as the traceability key. It integrates with ERPNext only for finance and payroll.
What we delivered
- Translated a 100+ doctype functional specification into a NestJS, Prisma and PostgreSQL backend and a Next.js and React frontend
- Delivered the role-based access foundation with admin-configurable roles and segregation-of-duties rules, audit logging and 12+ master-data modules
- Short-lived JWT access tokens backed by rotating, hash-only-stored refresh tokens with replay protection
- ERPNext boundary over REST only, with idempotent correlation-ID calls, retry and backoff queues and a nightly reconciliation run for one-sided records
Tech stack
- Next.js
- React
- TypeScript
- NestJS
- Prisma
- PostgreSQL
- SWR
- Tailwind CSS
- JWT
- ERPNext
Related services
ERP IntegrationConnect your ERP to your other software, add the modules it's missing, and get dashboards your management can use.Technical Advice & Team LeadershipAdvice before you build, plans for big changes, and a senior engineer to lead your developers.
Same kind of problem?
Tell Us About Yours