Custom Frappe app development for the workflows ERPNext doesn't cover

Frappe is a full-stack web framework in Python and JavaScript with one unusual idea at its centre: the data model is metadata. A doctype defined in the framework produces the database table, the form and list views with filters and saved reports, a REST API with pagination and filters, role and field-level permissions, document versioning, comments, assignments, email and notification hooks, and a workflow engine — all without code. Around that sit background jobs on Redis Queue, real-time updates over socket.io, a report builder, print formats, a multi-tenant bench that runs many sites on one installation, and a mature upgrade path. For the kind of application most organisations actually need — records, rules, approvals, reports — that is roughly 80 % of the work already done.

That is also the honest boundary. Frappe is the right choice when the application is about business records and the people who act on them; it is the wrong choice for a high-throughput consumer product, a UI-first application where the interface is the product, or a domain that is not relational. In those cases we build on FastAPI or Django and say so during discovery. Compared with a low-code platform, Frappe is open source with no per-user licence, the customisation ceiling is 'anything Python can do', and the application is yours to host, read and hand to another team. Compared with a from-scratch framework, you skip months of building the parts every business application needs and inherit ERPNext's modules whenever accounting, HR or stock enters the picture.

The first design decision is whether the application lives inside ERPNext or beside it. When the domain is one ERPNext already models — accounting, stock, buying, selling, manufacturing, HR — the answer is ERPNext plus a custom app that extends it: Mohan Impex's import-export duty and landed-cost handling and channel-partner management are extensions on a full ERPNext. When the domain is a programme or platform of its own — training centres and examinations, field surveys, capacity-building batches — the answer is a standalone Frappe app that may install alongside ERPNext for accounting and HR but owns its own doctypes and workflows: RKCL, MOSPI and GRAAM.

Either way the rules are the same, and they exist because the alternative — patching core — is how Frappe systems become un-upgradeable within two years. Fields and property changes go through Customize Form and Property Setters, exported as fixtures in your app. Behaviour goes into hooks — doc_events, overrides, scheduler events — and whitelisted API methods, never into edited core files. Anything larger is its own doctype in your app's module. Data changes ship as patches so an upgrade of a site replays them in order. Every app has tests and runs in CI against the Frappe and ERPNext versions you target. Upgrading from v14 to v15 then means upgrading the platform and re-running your tests — which is what we do on the annual support retainer, not a rescue project.

A Frappe app is built from the data model outward. Discovery produces the doctypes — the nouns of the business, their fields, naming series, links and child tables — and the roles and permission rules that say who may see and do what. Workflows are drawn as state machines with the business before they are configured. From there the work divides into server-side Python (controllers on document events, validation, whitelisted APIs, scheduled jobs), client-side JavaScript (form behaviour, dashboards), portal pages in Vue.js or Frappe UI for external users, reports, print formats and notifications. Every piece lands in a versioned app repository and deploys through bench and CI to staging before production.

• Data model — doctypes, child tables, naming series, links, indexes; role and field-level permissions; permission query conditions for row-level access
• Workflows — states, transitions and the roles allowed to make them; notifications and escalations; assignment rules
• Server side — Python controllers on validate / on_submit / on_cancel, whitelisted REST methods, background and scheduled jobs on Redis Queue
• Client side — form scripts, list and dashboard views, number cards and charts; Vue.js or Frappe UI portals for external users
• Reports & documents — query and script reports, government-format exports, print formats, PDF certificates with QR verification
• Integrations — REST and webhooks to HR, GST, payment, SMS, email and device systems; OAuth2 or API-key authentication; retry and audit on every call
• Quality & delivery — unit and integration tests, fixtures, patches, CI on GitHub Actions, bench deployment to staging and production with backups and restore drills

RKCL — Rajasthan's state IT-literacy programme — runs training-centre lifecycle management, student registration and batches, digital examinations with result processing, tamper-proof certificate generation and state-government reporting on one custom Frappe application: 5,000+ centres and 500,000+ students, certificates in the same day instead of two weeks, 80 % of manual reporting eliminated, non-compliant centres flagged automatically. The pattern: a programme platform where the framework's permissions and workflows are the product, scaled with indexing, background jobs and careful query design.

UNO MINDA — a Tier-1 automotive manufacturer — needed a learning and certification platform for a 3,000-strong workforce. We built the SAP Champion LMS on Frappe with structured module libraries, automated pre- and post-assessments, QR-verified digital certificates and real-time completion dashboards by department, location and skill, with enrolment driven automatically from HR data by role and grade. 3,000+ employees trained in the first three months, HR administration down 60 %, training cost per employee down 45 %. The pattern: a departmental app integrated with the systems of record so nobody keys data twice.

MOSPI — the Ministry of Statistics — coordinates national surveys through a custom Frappe app: survey programme management, field-officer assignment, multi-level data validation and approval, geographic progress dashboards and automated ministry reports, deployed on government-compliant infrastructure with role hierarchies matching the ministry's. Data-quality errors fell 75 %; monthly reports went from five days to same-day. The pattern: government-grade workflow and residency requirements met on an open-source stack. GRAAM — a social-sector organisation — manages capacity-building programmes, batches, certification and CSR project milestones with custom doctypes for what standard ERPNext does not cover; donor report preparation fell 70 % across 50+ concurrent batches. The pattern: ERPNext for the common modules, a custom app for the mission.

Frappe applications scale further than their reputation suggests when they are built with the database in mind. RKCL's half-million students and MOSPI's national survey load are handled with indexes chosen from real query plans, list views and reports that filter server-side, heavy work moved to background jobs, caching in Redis for reference data and permission checks, and permission query conditions rather than post-filtering so a user only ever loads the rows they may see. Load testing at the expected concurrency — thousands of centres submitting results on the same afternoon — happens before go-live, not after the first complaint.

Security is role-based access down to the field, document-level permission rules, audit trails on every change, rate limiting and API keys or OAuth2 on integrations, encrypted backups with tested restores, and hosting that matches the data's regulator: MOSPI runs under Government of India data-residency and security requirements; a manufacturer's LMS runs on its own cloud account; a small NGO runs on Frappe Cloud. Multi-tenancy — many sites on one bench — is used where an organisation runs several programmes or companies with separate data and shared code.

As a guide from our own projects: a focused ERPNext extension — a few custom doctypes, a workflow, print formats and a report — takes one to three weeks and usually ships inside an implementation. A departmental application such as a learning platform, a partner portal or a compliance tracker, with its own doctypes, roles, portal pages, integrations and reports, is four to eight weeks to a first release. A platform application on the scale of RKCL or MOSPI — many roles, external users in the thousands, examinations or field workflows, government reporting — is a product build of four to nine months delivered in releases, with the first release live within the first quarter.

Five things set the cost: the number of doctypes and workflows and how much bespoke logic sits behind them; the portal and dashboard surface, especially for external users on phones; integrations and the maturity of the systems on the other end; data migration from registers, spreadsheets or a previous system; and hosting, security and residency requirements. User count matters little — there is no per-seat licence. Discovery is a fixed fee that produces the data model, workflow drawings and a costed release plan; builds are fixed price per release with change control; support is a monthly retainer that includes the annual Frappe and ERPNext version upgrade.

Our custom Frappe work clusters where a business or a programme has a process that no packaged product models well and a budget that a licensed platform would consume. Manufacturers extending ERPNext for training, quality or trade compliance, as at UNO MINDA, Jyoti CNC and Mohan Impex. State and central government programmes that need a system of record with reporting to match, as at RKCL and MOSPI. Social-sector and CSR organisations that must show impact to donors, as at GRAAM. Corporate learning and certification functions of any size. Teams that already run Frappe and want an app rescued, upgraded or extended by people who will not patch core.

If your application does not fit Frappe, the discovery phase says so and the same Python team proposes FastAPI or Django instead. The wider practice — collaboration models, industries, hosting and the full list of case studies — is on the Frappe & ERPNext services page.