Apache OFBiz on your private server is a full business automation stack: an entity engine for your data, a service engine for your logic, and ready-made apps for orders, catalog, parties, and accounting. Day to day, most of that power hides behind admin screens that take clicks to learn and more clicks to operate. Your vibe-code agent in the Open WebUI chat works with OFBiz directly — editing data files, running services and Groovy scripts, querying the database, and restarting services when needed. Here are ten ordinary jobs you can simply type.
1. Add a New Product With Categories and Pricing
Instead of clicking through Catalog Manager, describe the product once and let the agent create the whole chain of records: the Product entity, a ProductCategoryMember tying it to the right category, ProductPrice rows for the list price and default price, and an InventoryItem so it shows stock. It writes the entity XML and loads it through the data loader, then opens the product to confirm it renders. Try typing: “Add a new product ‘Organic Cotton Tote Bag’ at $24.50 into the Apparel category, with list price and default price set, and 100 units in stock at the main warehouse.”
This is the kind of job that involves five screens by hand and about a minute of typing with the agent. If the category doesn’t exist yet, the agent will create it first and say so.
2. Process Yesterday’s Orders
Orders pile up in statuses like ORDER_CREATED and ORDER_APPROVED, and someone has to move them along before the warehouse notices. The agent can query OrderHeader for the last 24 hours, check which ones are paid, approve the eligible batch, and trigger the pick and pack steps in sequence. It can also total the batch by sales channel so you see web versus phone versus marketplace at a glance. Try: “List all orders from yesterday still in ORDER_CREATED, approve the paid ones, and tell me the total value by sales channel.”
Ask it to show the list before it acts if you want a human gate — the agent reads the data first and can present a summary for your confirmation.
3. Unstick a Broken Order
Every store has that one order stuck in the wrong status because a payment callback failed or an item went out of stock mid-checkout. The agent can open the OrderHeader and its OrderItems, cross-check the Payment records to see whether money actually arrived, and then either re-trigger approval or cancel it cleanly so inventory and the customer both get the right answer. Try: “Order 10432 looks stuck — check its payments and items and either approve it or cancel it, then explain what went wrong.”
You get a plain-language postmortem with the order, which is usually more useful than the log line alone. It will also flag the same failure pattern on other orders if it sees one.
4. Clean Up Duplicate Customer Records
OFBiz stores customers as Party records with Person or PartyGroup extensions plus ContactMechanisms, so merging duplicates by hand is genuinely fiddly. The agent finds likely duplicates by matching email or phone, compares their order history and roles, re-points the newer party’s orders at the account you keep, and disables the loser. Try: “Find parties with the same email address, merge their orders into the older account, and disable the newer one.”
Done carefully this stops support from quoting one customer two different order histories. The agent should report exactly which parties it touched before it archives anything.
5. Bulk-Update Prices From a CSV
Supplier sent a new price list with two hundred lines? Paste or upload the CSV and let the agent turn it into ProductPrice updates with from-dates, keeping the old prices in history because OFBiz pricing is effective-dated. It stages the changes as an entity XML file, loads it, and then spot-checks three SKUs against your sheet. Try: “Here’s a CSV of 200 SKUs with new list prices — load it so the new prices take effect today, and show me the three biggest increases.”
If a SKU in the CSV doesn’t exist in the catalog, the agent lists the misses instead of guessing. That single behavior saves you from silent partial imports.
6. Create a Promotion Without the Admin Screens
Promotions in OFBiz are ProductPromo records with conditions and actions, and the admin UI for building them is tedious enough that most owners avoid it. Describe the deal in plain language and the agent constructs the rules, generates the promo code, sets the date window, and activates it. Try: “Create a promo code SAVE15 that gives 15% off everything in the Accessories category, active until the end of this month, one use per customer email.”
Afterwards it can test the promo against a sample order so you know the discount actually applies before you announce it. That two-minute check prevents the classic “code doesn’t work” support ticket.
7. Rebuild the Product Search Index
Storefront search runs on keyword tables (ProductKeyword) that go stale whenever products change outside the screens — imports, direct edits, scripts. The agent can run the rebuildProductKeywords service and then test-search a few products to prove the index is healthy. Try: “I added 40 products by import and they don’t show up in store search — rebuild the keyword index and test-search for ‘denim jacket’.”
If results still look wrong after a rebuild, the agent can inspect the ProductKeyword rows for a specific SKU and tell you whether the problem is the index or the product data itself.
8. Create an Employee Login With Sensible Permissions
New hire needs OFBiz access? The agent creates the Party and UserLogin, assigns the right UserLoginSecurityGroup so warehouse staff can pick and pack but never touch accounting, and verifies the login works. Try: “Create a login for sam@mycompany.com who should pick and pack orders and see inventory but not touch invoices or admin settings.”
Getting the security group right matters more than the account itself — a login in the wrong group is either useless or dangerous. The agent shows which group it chose and what that group can do.
9. Run a Sales Report Whenever You Want One
The built-in reports cover standard questions, but ad-hoc ones — this month versus last month, one channel versus another — are where the agent earns its keep. It runs a Groovy script through the entity engine over OrderHeader and OrderItem, computes the totals, and can drop a CSV into your files for the spreadsheet people. Try: “What was our revenue this month versus last month, split by web versus phone orders, and export the detail to a CSV.”
Because it queries the same entity engine the application uses, the numbers always match what the screens would show you. Ask it to explain the query if you want to learn how it got them.
10. Back Up Your Business Data On Demand
Your entire business state lives in entity data — parties, orders, invoices, inventory — so an export you can restore is worth having before you need it. The agent can export entity XML through the data export tooling or dump the database named in entityengine.xml, compress it with a timestamp, and keep a rolling set in a backups folder. Try: “Take a full entity-data export now, zip it with today’s date, keep the last 14 daily backups, and show me the backup folder listing.”
Ask it to run a restore test into a scratch location once, so you know the backup is real and not just a file that looks plausible. A backup you haven’t restored is a hope, not a plan.
These ten cover the daily rhythm of running an OFBiz store: products, orders, customers, prices, and data safety. The agent does the clicking and the file editing while you review what it proposes. Apache OFBiz on OpenSysLab.
