Engineering/DEV
Built on the framework the ERP is built on.
The part that is genuinely yours, built on the same framework as the ERP so it does not become an integration problem.
Same framework as the ERP·Yours under an open licence·Survives an upgrade
Your record typeOpen licence
Field
Link to a customer
Permission rule
APIReportsAudit trail
ILLUSTRATIVE · YOUR RECORD, ON THE SAME FRAMEWORK
Does this sound like you/01
When a standard module will not do.
What you get for free/02
Model a record. See what comes with it.
- Appears in the APIEvery record type is an endpoint.
- Shows in reportsReportable like any standard record.
- Audit trailChanges are written to the record.
- Role and field accessAdd a permission rule to switch this on.
- Approval statesAdd a workflow to switch this on.
- Agents may act within limitsAgents get nothing until permissions are set.
- Survives an upgradeHeld as configuration, not edits to the source.
ILLUSTRATIVE · NOT A REAL BUILD
How the programme runs/03
Four phases. Pick one.
WHEN IT CLOSES YOU HOLD
- What the standard modules already do, demonstrated
- The genuine gap, stated precisely rather than broadly
- A build-or-configure recommendation in writing
- If build: the record types and relationships, sketched
What goes live, and when/04
A staircase, not a big bang.
Layer 1Record types and permissions
Layer 2Where it meets the core
Layer 3The interfaces
Layer 4Reporting and the API
What you are left with/05
Each one is something you can show.
Straight answers/06
The terms, in one line each.
First step
Establish whether you need a build at all
Framework
The same one the ERP runs on — not a bolted-on app
Ownership
Source in your repository from the first commit
Upgrades
Built as an app, so the platform upgrades underneath it
Cadence
Working software in your environment every two weeks
Maintenance
Any Frappe developer can take it on — by design
Where it shows up/07
The use cases it runs.
Next step