Skip to content
Services
Service

ERPNext & Frappe Development

Custom DocTypes, server scripts, workflow automation and print formats on Frappe and ERPNext — including government-grade deployments with full audit trails.

At a glance
Starting at
₹59,999
Tiers
3 options
Deliverables
10 items
First milestone
Week 1–2
See pricing

ERPNext gets you eighty percent of the way for free. The last twenty percent — the module that matches how your business actually operates — is where implementations either succeed or quietly get abandoned for spreadsheets. That last twenty percent is what we build: custom DocTypes, permission rules, approval workflows, dashboards and print formats, on deployments serving 150-plus daily users.

What you get
  • Custom DocTypes with validation and naming series
  • Server and client scripts for business rules
  • Multi-stage approval workflows with role gating
  • Permission rules — role, user and document-level
  • Print formats in Jinja with bilingual and RTL support
  • Dashboards, report views and query reports
  • REST API integration with third-party systems
  • Bench deployment, Nginx, supervisor and backup schedule
  • Data migration from legacy systems
  • Version-upgrade path and staging environment
AHow it works

The parts that actually
decide the outcome.

01

Custom modules that feel native

Built with the framework rather than bolted beside it — proper DocTypes, naming series, links, child tables and dashboards. Your custom module behaves like core ERPNext, which means it survives version upgrades and your staff already know how to use it.

02

Workflow automation with real approval chains

Multi-stage approvals with role gating, conditional transitions, escalation on delay, and notifications that go to the right person. Approval hierarchies that would otherwise be a WhatsApp group become an auditable state machine.

03

Bilingual and RTL where it is required

Full English and Arabic support including right-to-left print formats and correct numeral handling — built for diplomatic and government operations where the document has to be correct in both languages on the same page.

04

Audit trail and zero-trust access

Every state change attributed and timestamped, document-level permissions, and where the deployment demands it, VPN-only access with IP allow-listing. Built for environments where 'who approved this and when' is the first question asked.

05

Print formats that match the paperwork

Jinja print formats reproducing the exact document your organisation issues — letterheads, seals, signature blocks, bilingual columns, GST-compliant invoices. The output is the thing people judge an ERP by.

06

Integration into what already exists

REST API work in both directions: pulling from legacy systems, pushing to accounting, syncing with a separate customer-facing app. We have run dual-backend architectures where ERPNext handles operations and a separate service handles the public surface.

BDelivery process

What the first
few weeks look like.

  1. 01Week 1–2

    Fit-gap analysis

    Map your process against stock ERPNext and document exactly which gaps justify custom code and which are better solved by changing the process. The cheapest customisation is the one you decide not to build.

  2. 02Weeks 3–8

    Build custom modules

    DocTypes, scripts, workflows and permissions developed on a staging bench, reviewed with your process owners as each module lands.

  3. 03Weeks 8–10

    Migrate & train

    Legacy data migrated with reconciliation, then role-specific training — the accounts team learns a different thing from the warehouse team.

  4. 04Ongoing

    Go-live & maintain

    Cut over with a rollback plan, then a maintenance retainer covering upgrades, backups and change requests.

Pricing

Turn the dial
to your situation.

Every tier lists what it excludes as plainly as what it includes. All figures are in INR, exclusive of GST, and fixed against a written scope — there is no hourly meter.

Tier 2 / 3
Full Implementation
Full ImplementationMost chosen8–12 weeks
One-off setup₹1,99,999Then monthly₹7,999/mo

ERPNext deployed, customised, migrated and staffed-up — from empty server to daily use.

Best forBusinesses moving off spreadsheets or legacy ERP
Included
  • Fit-gap analysis and implementation plan
  • Bench deployment with Nginx, supervisor, backups
  • Custom modules for your operational gaps
  • Approval workflows and permission matrix
  • Legacy data migration with reconciliation
  • Print formats and dashboards
  • Role-specific training for each team
  • Maintenance retainer with upgrade cover
ERPNext & Frappe Development — tier comparison with setup and monthly pricing in INR
TierSetupMonthlyBest forTurnaround
Customisation Sprint₹59,999Live ERPNext instances that need specific gaps closed2 weeks
Full Implementation₹1,99,999₹7,999/moBusinesses moving off spreadsheets or legacy ERP8–12 weeks
Government / EnterpriseOn requestOn requestGovernment bodies, diplomatic operations, regulated industriesScoped after audit

All prices in INR and exclusive of GST. Third-party costs — ad spend, hosting, SMS and WhatsApp API charges, paid directory listings — are billed at actuals and never marked up.

DClients on this service
Shift reconciliation used to happen the next morning on paper, so a shortage was nobody's. Now it closes with the attendant still on site. Thirty-odd reports were built from what we actually asked for each morning rather than what the software wanted to show us.
Station ManagerDehradun
The bilingual print formats were the requirement everyone else told us was a nice-to-have. Getting English and Arabic correct on the same document, right-to-left, with the audit trail intact, is why the deployment was accepted.
IT Coordinator
EFAQ

ERP / Frappe — the questions we actually get

Written as straight answers, including where the honest answer is 'no' or 'it depends'.

  • If your process is recognisably accounting, inventory, purchasing, HR or manufacturing, customise ERPNext — you inherit years of edge-case handling for free. If your core product is the software itself, or the workflow has nothing to do with standard business documents, build custom. We give a straight answer at fit-gap stage even when it means a smaller project.

  • Not if they are built as a proper custom app with fixtures and migration patches, which is how we build them. Monkey-patched core files break; app-scoped DocTypes and hooks survive. We keep a staging bench so upgrades are tested before they touch production.
  • Yes. We start with a two-day audit of the bench, custom apps, unmigrated patches and permission model, and give you a written state-of-play including anything that will cause trouble at the next upgrade. Takeovers are a large share of what we do.
  • Either. We deploy to your cloud account or on-premise server and hand over credentials, or we manage hosting as part of a retainer. For government and diplomatic deployments it is typically your infrastructure with VPN-only access, and we work inside that constraint.
Next available cycle

Send a business name
and a city.

We'll run the geo-grid scan on your current Maps position and send back the grid — the same artefact a paying client gets monthly. No call required, no obligation attached.

Direct lines