Enterprise systems · ERP customisation
Custom ERPNext & Frappe Applications
Custom doctypes, workflows, print formats and integrations built the Frappe way.
Publication draft: status, contribution and technical details require contributor approval. The architecture and implementation notes below are illustrative, not verified accounts of a client deployment.
Context & challenge
Standard ERP modules rarely match specialised operational processes, and external applications must post into the ERP reliably.
Objectives
- Fit the ERP to the process without forking core
- Reliable API integration for operational apps
Solution approach
- Custom apps with doctypes, hooks and server scripts
- Script reports and branded print formats
- Token-authenticated integration endpoints
Architecture
- Operational app
- REST API
- Custom Frappe app
- Doctypes & workflows
- Reports
Simplified and anonymised. No private infrastructure details are published.
Important technical decisions
- Customise through apps and hooks, never by editing core
- Upgrade-safe between ERPNext major versions
Operational considerations
- Version upgrades
- Permission design
- Background job queues
Results
Results pending verification. We only publish outcomes that have been confirmed.
Lessons learned
- Working with the framework is cheaper than working around it.
