One of iDempiere’s strengths is that most of the application is data, not code. Windows, fields, validation rules, print formats, and messages all live in the Application Dictionary tables, which means your vibe-code agent can change them directly in the database, then restart the service so they take effect.

These ten customizations are the ones that make iDempiere feel like your system instead of a demo. Some take minutes; a couple take an afternoon. The effort is stated honestly.

1. Add a custom field to a window

Need a “Credit hold reason” on Business Partner or an “EORI number” for customs? The agent can add a column through the dictionary model, register it, and drop the field onto the right tab. Say: “Add a short text field called ‘VIP tier’ to the Customer window after the Group field, with a dropdown of Gold, Silver, Bronze, and show it read-only to anyone but the Sales Admin role.” It creates the AD_Column and AD_Field records, syncs the table, and restarts. Ten minutes, no plugin required. Just don’t rename the column later without telling the agent.

2. Build a new window for your own entity

Some businesses track things no ERP anticipates: loaner units, quality holds, insurance policies. iDempiere can generate a full CRUD window from a table definition. Ask: “Create a table for loaner equipment with serial number, customer link, out date, due date, and status, then generate a window and menu entry under Sales.” The agent builds the table, registers it in AD_Table, creates columns from your list, and generates the window and tab. Naming columns well up front matters; the agent will flag any names that collide with existing columns.

3. Rework the invoice printout

The standard invoice layout is functional, but your logo, bank details, and payment terms belong on it. Print formats and the Jasper report bundle control what customers see. Say: “Put our logo top-left, replace the payment terms paragraph with our late-fee text, and add a line for the customer’s PO number under their address.” The agent edits the print format items or the Jasper template and generates a sample PDF for you to check. Layout work is fiddly by nature, so expect a couple of review rounds before it’s perfect.

4. Fix document numbering per organization

Shared numbering across companies and document types gets messy fast. iDempiere numbers documents by document type, and each org can carry its own sequence with its own prefix. Ask: “Give sales invoices in Org West the prefix INV-W-, invoices in Org East INV-E-, restart both sequences at 1 next fiscal year, and never reuse a number.” The agent sets up the document types, sequences, and year-start rules, then completes one test document per org to prove the numbering works before you trust it.

5. Rename the vocabulary

“Business Partner” means client in one industry and account in another. Labels and messages are dictionary data, so renaming is cheap and safe. Say: “Rename Business Partner to Client everywhere in the UI, including window titles, field labels, and the help text, but leave internal table names alone.” The agent updates AD_Message and AD_Field entries for the language you use, keeping terminology consistent so search and training material still make sense. It takes minutes per window and makes the system noticeably friendlier for staff.

6. Add validation rules and display logic

Raw fields accept anything; validation rules make the UI enforce your process. A dropdown can pull from a reference list, and display logic can reveal a field only when it matters. Ask: “On sales orders, show the ‘Project’ field only when the order type is Standard, and make the Reason lost field mandatory before a quote can be marked Lost.” The agent writes AD_Val_Rule records and display-logic expressions on the fields, then walks you through the exact clicks to verify each behavior. This is where a good agent saves real training time.

7. Tighten roles and turn on MFA

Default roles accumulate rights over time, and iDempiere has no MFA out of the box. Both are fixable. Say: “Audit every role: list each one’s window, process, and report access, remove anything unused for 90 days, scope each role to its org, and enable the MFA plugin for anyone with accounting rights.” The agent diffs role access against actual usage, proposes the cuts, and applies them only after you approve. Don’t skip the export of the current setup first; rollback is your friend.

8. Package customizations as a plugin with 2Pack

Once you have several dictionary changes, moving them by hand from staging to production is where mistakes breed. 2Pack exports dictionary changes and custom code into an XML pack that installs like a plugin. Ask: “Take the Loaner Equipment window, the VIP tier field, and our invoice print changes, and package them as a 2Pack plugin we can install on the production server with a version number.” This is real development work, not a config toggle, so budget an afternoon. The payoff is repeatable staging-to-production moves and a rollback path.

9. Brand the login screen and UI

Staff and partners see the default iDempiere login page dozens of times a day. Swapping in your logo, a background image, and your company name is a small change with outsized effect. Say: “Replace the login logo and background with our brand images, change the browser tab title to our company name, and swap the favicon.” The agent drops the files into the web UI’s image directories and adjusts the theme files. Cache and browser quirks cause most of the confusion here; test from a private window before complaining.

10. Harden the server around the app

The ERP is only as healthy as the box it runs on. A maintenance pass keeps it that way. Ask: “Set up log rotation so the server log can’t fill the disk, schedule weekly vacuum and analyze on the database, alert me if disk usage crosses 80% or the email server stops answering, and run a test restore of last night’s backup into a scratch database every Sunday.” The agent wires cron jobs and health checks, then sends you the first status report. A backup you haven’t restored is a hope, not a plan, so the restore test is the part that matters most.

Start with the customizations people touch daily: labels, numbering, and the invoice printout. The deeper work like plugins and role audits can follow once you’ve seen the agent work carefully on the small stuff.

Every one of these runs against your own database, on your own server. iDempiere on OpenSysLab gives you the agent and the box, prewired.