Apache OFBiz is built to be customized: hot-deploy components, an entity engine you can extend, themes, and templates behind every screen and email. The catch is that the customization surface is spread across entitymodel.xml files, services.xml declarations, Groovy scripts, and Freemarker templates — each in its own corner of the directory tree. Your vibe-code agent reads all of it and edits it in place, showing you the diff. Here are ten customizations worth asking for.

1. A Custom Entity With CRUD Screens

Need to track something OFBiz doesn’t model — warranty registrations, asset loans, supplier certifications? The agent defines a new entity in your hot-deploy component’s entitymodel.xml with the right fields and relationships, adds seed data and form widgets, and wires list and create screens into the menu. Try: “Add a WarrantyRegistration entity tied to Product and Party, with list and create screens so support staff can register warranties.”

The entity engine then gives you querying, permissions, and data export for free, on the same footing as Order or Product. Extend an existing entity with new fields instead if a wholly new one feels heavy.

2. A Groovy Service Fired by an ECA

Logic that must run when something happens — an order completes, a shipment ships, an invoice is paid — belongs in a service wired to an event-condition-action rule. The agent writes the Groovy service inside your component, declares it in services.xml with its inputs and outputs, and hooks the ECA so it fires on the exact event you name. Try: “When an order completes, call an external webhook with the order id and total so my shipping tool picks it up.”

Because it runs inside the service engine, your hook inherits transactions, permissions, and logging for free. Keep the external call at the end so a slow API can’t roll back the order itself.

3. Your Own Hot-Deploy Component

Keep custom code out of the OFBiz core so upgrades stay painless — that is exactly what the hot-deploy directory is for. The agent scaffolds a clean component with ofbiz-component.xml, plus empty entitydef, servicedef, groovyScripts, data, and webapp folders, then verifies the framework loads it without errors. Try: “Scaffold a hot-deploy component called mycompany for our custom code, and verify OFBiz loads it cleanly.”

Everything else on this list should live in that component, which keeps your changes in one place you can diff and back up. It also means support questions start with a clean answer: “our custom component.”

4. Rebrand the Storefront Theme

The ecommerce app ships with a default theme that looks like a demo, and it should look like your business before customers see it. The agent swaps the logo, adjusts the color palette in the theme’s styles, and edits the header and footer Freemarker templates — while leaving the screen layouts themselves alone. Try: “Rebrand the shop theme with our logo, a navy and orange palette, and our company name and links in the footer.”

Working at the theme level means upgrades to the applications don’t wipe your look. Ask for a before-and-after screenshot check on the home and product pages so you see the result, not just the diff.

5. A Custom Invoice PDF Template

Invoices go out as PDFs rendered from templates, and the default layout is generic enough that customers notice. The agent edits the invoice template to add your logo, tax wording, bank details for transfers, and payment terms, then renders a real invoice from a recent order to prove the output. Try: “Update the invoice PDF so it shows our logo, VAT number, and payment terms of net 14, and generate one for order 10410 to check.”

Small wording differences here prevent real disputes — “net 14” on the invoice beats it living in an email nobody kept. Have the agent keep a copy of the original template so the change is reversible.

6. A Dashboard Screen With Your Numbers

The standard first screen is a generic menu; yours should answer your questions the moment you log in. The agent builds a small dashboard screen backed by a Groovy action that queries the entity engine on each load — open orders, today’s revenue, low-stock count, orders awaiting approval — and lays them out readably. Try: “Build me a dashboard showing today’s order count and revenue, orders pending approval, and products below minimum stock.”

Since it queries live entities, the numbers are always current rather than cached from last night. Add links from each figure to the corresponding list screen so the dashboard is a jumping-off point, not a dead end.

7. Rewrite the Order Confirmation Email

The order confirmation email is assembled from templates plus the order notice screen, and the default text reads like a system message. The agent updates the copy, tone, and layout — tracking link, support contact, maybe a cross-sell block — and sends a test copy to you before any customer sees it. Try: “Rewrite the order confirmation email to be shorter and friendlier, include our support email, and send me a test.”

Confirmation emails have the highest open rate of anything you send, so the wording is worth ten minutes of thought. Keep variables like order total and items intact — the agent will show you which parts are dynamic.

8. Harden Admin Access

Out of the box OFBiz includes powerful tools like webtools that no storefront user should ever reach. The agent audits every UserLogin and its security groups, confirms customers sit in least-privilege groups with no path to accounting or tools, and rotates the admin passwords. Try: “Audit our user logins and security groups — make sure no storefront customer can reach webtools or accounting, and force password resets on the two admin accounts.”

It can also confirm webtools is unreachable from the public host and document what each admin account is for. Knowing which logins exist is half of the security battle.

9. Get SMTP Sending Reliably

Email problems in OFBiz usually trace back to SMTP settings that were never finished, so confirmations silently never arrive. The agent configures the mail properties for your provider with authentication, sends test mail until delivery is proven, and then triggers a real order confirmation end to end. Try: “Configure OFBiz to send mail through our SMTP provider and send test order confirmations to me until they arrive.”

Test with the actual order flow, not just a bare sendMail call, because templates and from-addresses fail in ways raw tests don’t. Once it works, ask the agent to note the settings in your component so a rebuild doesn’t lose them.

10. Tune the Runtime for Your Server

Default memory, default ports, and unbounded logs are fine on a developer laptop and wrong on a real server. The agent reviews the JVM heap against your RAM, moves ports if something else needs them, and sets log retention so runtime/logs can’t fill the disk months from now. Try: “Check the JVM heap and log rotation for a 4 GB server, set logs to keep 14 days, and restart OFBiz to apply.”

It restarts the service and watches the startup log until the framework is healthy, so you know the change took effect. Keep the old settings in a comment — heap tuning is the kind of thing you revisit after the first busy season.

Customizing OFBiz used to mean hiring a framework specialist. With the agent, you describe the outcome and it finds the right files — entitymodel.xml, services.xml, theme templates — and shows you exactly what changed. Apache OFBiz on OpenSysLab.