How rung1 changes your ERP
ERP software rarely fits a business out of the box. Someone has to change it: a field, a rule, an approval, a report. In India that usually means a partner project of 4 to 16 weeks. rung1 does the same work with governed agents, and a person approves every change. This page follows one change from sentence to live system.
The business in this story: Kaveri Pumps, a fictional ₹30 crore pump manufacturer in Coimbatore, on ERPNext, with an in-house accountant and an external CA.
Block sales orders above a customer's credit limit
- ✔ G1 Ledger
- ✔ G2 Stock
- ✔ G3 Permissions
- ✔ G4 Tax
The same change, two ways.
| Aspect | Partner project today | With rung1 |
|---|---|---|
| Typical timeline | 4–16 weeks | Measured hours-to-go-live, published once our design partners are live |
| Who is involved | Partner consultant, your accountant, your CA | You, and your approver |
| How you see the change | A demo, then go-live | A side-by-side diff before anything goes live |
| How you undo it | Raise a new project | One click, for 30 days |
One sentence, logged properly.
The accountant at Kaveri Pumps types what they need. rung1 logs who asked, for which company, and why, as required for DPDP. Before any AI work starts, it reserves a budget for the request, so there are no surprise costs.
Block sales orders above a customer's credit limit.
Planned against your site, not a generic one.
Every ERPNext site is different. rung1 reads your site's structure (your fields, scripts, workflows and roles) into a fingerprinted snapshot, and plans against that, not against a generic ERP.
- Doctypes readCustomer · Sales Order · Credit Limit
- Custom fields on Sales Order7
- Server scripts3
- WorkflowsSales Order Approval
- RolesSales User · Sales Manager · Accounts Manager
What it may touch is fixed first.
The plan lists every object the change will create, and the only tools the agent is allowed to use for it. Nothing outside that list is reachable.
- Custom field1
- Server script1
- Validation1
- Report column1
Allowed tools
The plan fixes what the agent is allowed to touch before it reads any customer data.
A fresh copy. The only place it can write.
The change is applied to a fresh copy of your site. It is the only place the agent can write. Your live ERP is not reachable from here.
- Copy of live site created✔ Done
- Field
credit_check_statusadded✔ Done - Script
so_credit_limit_guardcreated✔ Done - Validation on Sales Order submit✔ Done
- Report column “Credit headroom”✔ Done
7 golden gates. 3 of them cannot be argued with.
The sandbox is checked against your own ledger, stock and permissions, then your tax, payroll, regression and performance.
| Gate | What it checks | Result |
|---|---|---|
| G1 LedgerBlocks if red | Trial balance balances; no orphaned GL entries | ✔ Pass |
| G2 StockBlocks if red | Stock ledger reconciles to bins; valuation unchanged | ✔ Pass |
| G3 PermissionsBlocks if red | No role gains access it was not asked for | ✔ Pass |
| G4 TaxWarns | GSTR-1 and 3B generate; e-invoice payload validates | ✔ Pass |
| G5 PayrollWarns | PF, ESI, PT, LWF unchanged | ✔ Pass |
| G6 RegressionWarns | Nothing else broke | ✔ Pass |
| G7 PerformanceWarns | Nothing slowed down | ✔ Pass |
Exactly what changes, before it changes.
You see exactly what changes, in plain words and side by side, before anything touches your live system.
A named person. A recorded reason.
A named person approves, with a reason. That approval is a signed record, not a checkbox. The model may propose a change. It may never approve one.
The same tested bundle goes live.
One service, the Promoter, applies the same tested bundle to your live ERP. It takes a snapshot first, then re-runs the ledger, stock and permission checks on live. If anything fails, it restores the snapshot automatically.
- Approval signature verified✔ Done
- Snapshot of live taken✔ Done
- Bundle applied (identical to sandbox)✔ Done
- G1–G3 re-run on live✔ Pass
- Status✔ Live
One record your CA can read. One click to undo.
The change, the approval, the tests and the cost go into an append-only record your CA can read. For 30 days, one click reverses it. The undo is assembled from what was recorded, with no AI model involved.
- Who asked, and why
- The plan and the tools it allowed
- Every gate result
- Who approved, and their reason
- The cost in ₹
- Rollback available until day 30
Your second change is faster than your first.
rung1 keeps what it learned about your ERP (your fields, your approvals, your vocabulary), so each new change starts from your setup, not from zero.
Questions about how a change runs.
Still have a question? Book a working session and ask us directly.
How do I customise ERPNext without writing code?
With rung1 you describe the change in a sentence, such as "Block sales orders above a customer's credit limit". rung1 plans it against your own ERPNext setup, builds it in a sandbox, tests it, and shows you the difference. You approve it, and the same tested change goes live. No code, no developer tickets.
What are rung1's golden gates?
The golden gates are 7 automatic checks run on every change. G1 Ledger, G2 Stock and G3 Permissions block a change that fails and cannot be overridden. G4 Tax, G5 Payroll, G6 Regression and G7 Performance warn, and can only be overridden with a written reason that goes on the record.
Can I undo a change made to ERPNext?
Yes. Every rung1 change can be rolled back in one click for 30 days. The undo is assembled from the recorded change itself, with no AI model involved, so it behaves the same way every time.
Does rung1 work with my existing ERPNext customisations?
Yes. Before planning, rung1 reads your site's structure (custom fields, scripts, workflows and roles) into a fingerprinted snapshot. It plans against your setup, not a generic ERPNext, and G6 checks that nothing you already had stops working.
How long does an ERPNext change take with rung1?
Much of the time is your own review and approval. We are measuring median hours-to-go-live with our design partners and will publish the real figure once it is measured, rather than quote an estimate. A comparable partner project in India typically takes 4 to 16 weeks.
Bring one change. We'll walk it through the path with you.
A 30-minute working session maps the change you need first and runs it through rung1.