ERPNext runs on the Frappe Framework, and Frappe was built for customization: add fields to any form, create new document types, restyle printouts, attach scripts. Traditionally that meant a Frappe developer or a consulting partner. On your OpenSysLab server the vibe-code agent can do most of it in chat, reading the app’s code and configuration as it works and testing each change before it lands. Here are ten customizations worth asking for.

1. Custom fields where you need them

Every form in ERPNext can carry extra fields without touching code; the framework stores them as metadata. The agent adds the field, sets its type and permissions, and decides whether it should travel to related documents like invoices and delivery notes.

Say “Add a Customer PO Number field to Sales Order, make it mandatory, and carry it through to the delivery note and sales invoice.” A change like this is minutes of chat, not a change request, and it survives upgrades because it lives in the database, not the codebase.

2. A custom DocType for your domain

Sometimes a whole new document belongs in the system: machine calibrations, rental contracts, site visits. The agent creates a custom DocType, and Frappe generates the list view, forms, permissions, and search integration around it for free.

Ask “Create a Machine Calibration doctype with machine, date, technician, pass or fail, and notes, and give maintenance a list view they can filter by due date.” It behaves like a native part of ERPNext because it is one, and its data can be reported on like any other document.

3. Naming series that read like your business

Document names default to plain numbers. The naming series tool can produce SAL-ORD-2026-00042 or branch-specific prefixes, and the agent can migrate existing documents so history stays consistent.

Try “Rename sales invoices to INV-2026-#####, start purchase orders at PO-1000, and check nothing breaks in old reports.” A small thing, but invoices look professional from the first one, and customers can quote a reference you both understand.

4. Print formats that carry your brand

The default invoice printout is functional, not yours. Print formats are HTML templates with your logo, fonts, and footer, and the agent can build one and show a PDF preview against a real invoice before you adopt it.

Say “Make a clean one-page invoice with our logo, bank details and payment terms in the footer, and a paid stamp when the invoice is settled.” Every document that leaves the building represents you, and consistent printouts are cheaper than letterhead debates.

5. Client scripts for form behavior

When you need the form itself to enforce rules, client scripts run in the browser on events like save. The agent writes and tests them: hide fields by role, auto-fill defaults, calculate values, block saves that break policy.

Ask “On Sales Invoice, require a purchase order reference before saving whenever the customer group is Government.” Rules like this stop bad data at the door instead of in the audit, and they are visible to staff as helpful messages rather than mystery refusals.

6. Reports that live in the menu

Standard reports cover common questions; your margin-by-customer-group question is yours alone. The agent writes a query report in SQL or a script report, adds it to the module menu with filters and a chart, and it is there every Monday morning instead of living in someone’s downloads folder.

Say “Add a Gross Margin by Customer Group report for this fiscal year under Selling, based on sales invoices minus item valuation, with a monthly chart.” Built once, used forever, and it exports to the same spreadsheet your accountant already expects.

7. A workspace per role

ERPNext desktops are customizable per role: number cards, charts, shortcuts. The agent builds focused desktops so a warehouse login opens to pending deliveries and low stock, while a sales login opens to open quotes and today’s orders.

Try “Give the warehouse team a desktop with number cards for pending deliveries, items below safety stock, and open stock entries.” People stop hunting through menus for their three daily numbers, and new hires learn the job from the screen they land on.

8. The customer-facing side

ERPNext ships with a website module, a customer portal, and a shopping cart, but out of the box it looks generic. The agent sets your logo and colors, publishes the pages you want, and decides what portal customers can see: orders, invoices, outstanding amounts.

Say “Put our logo and brand colors on the site, turn on the cart for the Retail item group, and let portal customers see their orders and invoices.” Customers self-serve the questions that otherwise flood your inbox, and invoices arrive in their hands without you sending them.

9. Event logic without a custom app

For server-side behavior, Frappe offers server scripts that run on document events and on a schedule, plus webhooks that call external URLs — no app deployment required. The agent writes, enables, and tests them against real documents, and shows you where each one logs its activity.

Ask “Write a scheduled script that assigns each new lead round-robin to a salesperson by territory every night, and log what it changed.” When you eventually outgrow scripts, the same logic moves into a proper app cleanly.

10. Harden the server itself

The customization that matters most is invisible: nightly backups uploaded off-site, SSL enforced, fail2ban watching SSH, updates on a schedule, disk-space alerts before the database fills. The agent configures ERPNext’s own S3 backup settings plus the system layer underneath, then proves a backup restores.

Say “Set up nightly backups to my S3 bucket keeping 30 days, email me the result, and walk me through a test restore into a scratch site.” A backup you have never restored is a hope, not a plan, and this is the one item on the list you should never skip.

See it in action

Official walkthroughs from the ERPNext team:

Worth a watch next:

• ERPNext – Workflow — the official guide to building approval workflows, a no-code customization covered in this article.
• What is ERPNext? — a quick official overview of the product before you start shaping it to your business.

Customization has one failure mode: too much of it, poorly documented. Ask the agent to keep a changelog of every field, script, and format it adds, and review it monthly. ERPNext on OpenSysLab