Service
ERP customisation on the Frappe framework
Every business has a handful of things it does differently, and those are usually the things that matter. We build them into ERPNext rather than leaving them in a spreadsheet beside it.
At a glance
- Typical duration
- 2–8 weeks per module
- Engagement
- Fixed scope or retainer
- Platform
- Frappe framework
- Delivered as
- A versioned custom app
When customisation is the right answer
The honest default is to use ERPNext as it ships. Standard features get upgraded, tested and documented by a large community; custom code becomes your responsibility forever. We push hard on configuration before we write anything.
But some gaps are real. A pricing model nobody else uses, an approval chain tied to your licence conditions, a report your regulator wants in a specific shape — these are worth building, and the Frappe framework is built for exactly that.
We deliver customisation as a separate versioned app, never as edits to the core. That keeps your ERPNext upgradeable: when a new version lands, your custom app moves with it instead of blocking the upgrade for three years.
Scope
What we build
Custom doctypes
New record types with their own fields, permissions, naming series and links into standard documents.
Workflows and approvals
Multi-stage approval chains with role-based transitions, conditions and notifications.
Server and client scripts
Validation, calculated fields and automation that fires on the right lifecycle hook.
Reports and dashboards
Query and script reports, chart dashboards and scheduled email digests.
Print formats
Invoices, delivery notes and certificates that match your statutory and brand requirements.
Integrations
REST and webhook connections to payment gateways, logistics providers and legacy systems.
Method
How a customisation runs
Gap review
We confirm the requirement cannot be met by configuration, because the cheapest custom app is the one not built.
Specification
A written spec with the data model, the screens and the acceptance criteria, agreed before coding.
Build
Developed in a versioned custom app, reviewed on a staging site you can log into.
Test and sign-off
You test against the acceptance criteria on real data before anything reaches production.
Release
Deployed with a migration path, and carried forward on every future ERPNext upgrade.
Industries
We work with
FAQ
Questions we are asked before signing
Will customisation stop us upgrading ERPNext?
Not if it is done properly. We ship customisation as a separate app that hooks into core rather than editing it, which is what keeps upgrades possible. Direct core edits are the reason many ERP installations are frozen on an old version.
Do we own the code you write?
Yes. Custom work is delivered to your repository and your site. ERPNext and Frappe themselves are GNU GPLv3, and anything we build for you is yours to keep, read and change.
Can you customise an ERPNext someone else implemented?
Yes, and we do it often. We start with a short review of the existing configuration and custom code, because what looks like a missing feature is sometimes a misconfiguration that is cheaper to correct.
How do you price customisation?
Small, well-specified items are fixed price. Longer programmes of work run on a monthly retainer with an agreed backlog, which suits businesses that keep finding improvements after go-live.
Related services