ERPNext Customization
Every business has steps no standard ERP covers. We build them into ERPNext the supported way, with custom fields, workflows and scripts, so upgrades do not undo the work.
Why It Matters
Work done by editing core files disappears the moment you upgrade, which is why so many instances end up frozen on an old version. We keep every change in a separate custom app and attach it through the framework hooks, so upgrades stay a routine job.
A lot of requests turn out to be a setting, a permission rule or a report rather than development work. We check those first and tell you when a change does not need code at all, which keeps the bill down and the instance simple.
We look at the process behind the request, not just the screen you want changed.
We pick the lowest level that solves it and give you a fixed price and date.
Work is done in your custom app, versioned, reviewed and commented.
You run it on a staging instance with your own data before it goes anywhere near production.
We release to production, document the change and watch it through the first cycle.
All your changes live in a single versioned app, so it is always clear what is standard and what is yours.
We attach through framework hooks only, which is what keeps your instance upgradeable.
Nothing reaches production until it has been tested on a copy of your live data.
Each customization records what it does and why, so the next developer is not guessing.
Every release can be reverted, and we take a backup before we deploy.
The code sits in a repository you own, so you are never dependent on one vendor.
If a setting solves it, we say so. Less custom work means a simpler system for you.
We build on the Frappe framework itself, not just the ERPNext screens on top of it.
Each request is quoted before work starts, so there are no surprises on the invoice.
Our customers move between ERPNext versions without rebuilding their customizations.
We take over existing instances, review what is there and make them supportable again.
Custom fields and doctypes, workflows and approval chains, client and server scripts, print formats, dashboards, custom reports, role permissions, and full custom apps built on the Frappe framework underneath ERPNext.
Not when it is built the supported way. We keep changes in a separate custom app and use the framework hooks rather than editing core files, so an upgrade does not overwrite your work. Direct core edits are what break upgrades, and we do not do them.
We look for a configuration route first, because settings cost less and survive upgrades on their own. Custom code is proposed only when there is no standard option, and we tell you which route we are taking and why before we start.
It depends on the requirement. A custom field or print format is a small piece of work. A custom app with its own doctypes and integrations is a project. We scope each request and give a fixed price and date before any coding begins.
Yes. We start with a short review of the existing setup to see what was configured, what was customized and how, then work from there. If we find core edits, we tell you what it would take to move them into a supported custom app.
Yes. The custom app sits in your repository and on your instance, with documentation. You can maintain it in-house or with any other partner.
Related
The other services in this section, and related pages from TCB Infotech.
No commitment. A straight answer on what your change really needs.
