Skip to content
Menu
Services · Custom Frappe apps and extensions

Custom Frappe apps and extensions

What ERPNext does not do out of the box, built as a separate Frappe app: custom DocTypes, workflows, print formats, reports, scheduled jobs and integrations. Kept apart from core so upgrades stay clean, versioned in your repository, documented for the next developer.

Problems we are called in for

01ERPNext does most of what you need, but the one process that makes your business different does not fit.
02A previous partner changed core files, and now nobody dares to upgrade.
03Reports and print formats are rebuilt in Excel every month because the system cannot produce them.

How the work runs

The same six waypoints and three gates as every implementation.

  1. Survey · 2 weeks
  2. Chart · 2 to 4 weeks
  3. Build · 4 to 12 weeks by tier
  4. Rehearse · 3 to 5 weeks
  5. Cross over · 1 to 2 weeks, plus the parallel run
  6. Settle · 30 days
  7. Next leg · Optional add-on, as scoped
YOU SIGN ATBlueprint sign-offGo-live readiness reviewHandover sign-off
How we implement, waypoint by waypoint →

What we have built

  • Emperor Akbar Cardamombag-level traceability linked to batches and manufacturing orders, forward contract management and export documentation
  • Sheeltronscore-based QC grading from A to D, part compatibility checks and grade-based pricing for refurbished laptops
  • Living Liquidza 22-column vendor payout statement, bulk payment approvals and a rate-limited vendor portal API
  • NIDO Groupa unified BOM with revisions during production, and serial-number machine tracking with BOM-linked spare validation
  • Touchstone Foundationan event-based budget allocation and transfer engine for donations
  • Sonotech Medical Centerlab reports released only on a doctor's passcode, then sent by SMS, and gateway payments reconciled against invoices

How it works: configuration first

If ERPNext can do it with configuration, we configure it. Custom code is the last resort, and the BRD says so line by line. When we do build, it goes into a separate Frappe app with its own DocTypes, workflows, print formats, reports, scheduled jobs and integrations, never into ERPNext core. Upgrades then run on a copy first, with a checklist of what the app touches.

What you own

  • The app, in your GitHub organisation from the first commit
  • A README and documentation the next developer can work from
  • The requirement line that justified each piece of custom code
  • An MIT-licensed framework underneathWhich any Frappe developer can read

Technology

  • DGFT (licences, RoDTEP, drawback)

Where we have done it

All 16 case studies for this service →

Industries

FAQ

Not when it lives in its own app. We never patch ERPNext core, and every upgrade runs on a copy first with a checklist of custom code that needs attention.

The code in your repository, the requirements documents, a README and a user guide, and a list of open items. Another Frappe team can pick it up from there.

Start a conversation

Tell us what you need.

An engineer reads it and replies within one working day with questions, not a brochure.