metasfresh is deliberately configurable: the app dictionary holds windows, fields and tables in the database, reports are Jasper templates you can change, and the whole stack runs in docker on your server. Your Vibe-code agent can make those changes for you and show its work. Here are ten customizations worth asking for.
1. Custom Fields Where You Need Them
Every business has data that does not fit the standard master data: an organic certificate number on the supplier, a dangerous-goods class on the product, a customer discount group for your own segmentation. In metasfresh these are columns in the app dictionary, and the agent can add the column, register it on the right table, place the field in the window layout where your users will find it, and make it filterable in the list view. Because the change lives in the database configuration, it survives updates. Try: “Add an organic certificate number field to business partners, show it in the customer window next to the GLN, and make it searchable in the list.”
2. Invoice and Picking List Layouts That Look Like Yours
The printed face of your company is a Jasper report: the sales invoice, the delivery note, the picking list. The agent can adjust the standard templates — your logo in the corner, a SEPA QR payment block, the discount column moved next to the unit price, terms in the footer — and build a picking list variant that shows the handling unit per line so the warehouse packs in the right boxes. Try: “Change the sales invoice report: logo top-right, SEPA QR payment block, discount column next to unit price — and make a picking list that shows the handling unit for each line.”
3. A Price Architecture Instead of One Long List
Most metasfresh setups start with a single price list and grow messy. The clean version is a price system with separate lists — a net list for wholesale customers, a gross list for occasional counter sales, maybe a webshop list — and price list versions that carry quantity-based discounts and UOM pricing, like sacks priced per kilogram. The agent can build the whole structure and migrate your existing prices into it. Try: “Build a price system for us: one B2B net list for wholesale customers, one gross list for counter sales, and a version starting next month with quantity discounts — price the 25 kg sacks per kilo.”
4. Credit Limits, Payment Terms and Dunning Rules per Group
Your retail outlets get 14 days, your key accounts get 30 with a real credit limit, and the dunning ladder should charge a fee from the second notice. All of this is business partner group configuration, and getting it right once saves arguments later. The agent sets the group defaults, the credit limit with a warning workflow, and three dunning levels with fees and polite texts in both German and English. Try: “Set 14-day payment terms as default for the Retail group, give Key Accounts 30 days with a 50,000 EUR credit limit, and set up three dunning levels with fees of 0, 10 and 25 EUR, texts in German and English.”
5. Multi-Org and Counter Documents for Two Legal Entities
If you trade through two GmbHs — one sells, the other owns the stock — metasfresh can run both in one system with separate orgs and counter documents: a sales order in one org automatically creates the matching purchase order in the other, keeping the intercompany books aligned without retyping. The agent sets up the second org, moves the customers and warehouses that belong to it, and turns the counter document rules on. Try: “Set up a second org for our sister company, move the three named customers to it, and enable counter documents so a sales order in one org creates the purchase order in the other.”
6. Handling Units and Empties for Beverage Wholesaling
metasfresh’s handling unit system tracks how products are packed — a case of 24 bottles, a pallet of 60 cases — and its empties management keeps the returnable crate balance per customer and bills what does not come back. This is real configuration work: packing instructions, TU and CU levels, empties products and balances. It is exactly the kind of fiddly setup the agent can do while you check the result on a test order. Try: “Set up our crate logic: beer packs 24 per crate, track empties per customer with a balance on the business partner, and credit returned crates against the empties invoice.”
7. Warehouse Layout That Matches the Building
Adding the new annex means a second warehouse with locators, a default receipt location per supplier, and picking flows that actually work on a scanner. The agent creates the warehouse structure, sets the routing defaults, and then walks the WebUI receiving and picking steps itself to confirm your USB scanners behave. Try: “Create a second warehouse for the annex with its locators, make it the default receipt location for supplier Natura, and verify the WebUI receiving and picking flows work with our scanners.”
8. Roles with Least Privilege
The five pickers do not need accounting, and ex-employees should not be loggable at all. The agent copies the standard role into a warehouse-only role with access to receipts, shipments and inventory but nothing in pricing or billing, assigns it, and disables the stale accounts. It can also show you who has admin access today, which is usually more people than you think. Try: “Make a warehouse-only role that can see receipts, shipments and inventory but nothing in accounting or pricing, assign it to the five pickers, and disable the three ex-employee accounts.”
9. Outbound Mail and Notifications That Actually Reach People
Order confirmations, shipment notes and invoices should go out from your own address, not sit in a print queue. The agent wires outbound mail through the server’s mail relay, sets the sender address, and configures WebUI notifications so the right users get pinged when stock drops below reorder point or a dunning candidate appears. Try: “Send outbound email through our mail relay so invoices and order confirmations go from the ERP address, and notify me in the WebUI when any product drops below its reorder point.”
10. Harden the Box It Runs On
The ERP holds your whole business, so the server deserves the same care. The agent can enforce HTTPS at the reverse proxy, restrict the firewall to 443 and SSH, confirm every container restarts on failure, and then prove your backups are real by restoring last night’s dump into a scratch database. That restore drill is the one step everyone skips and the one that matters most. Try: “Harden this server: HTTPS at the proxy, firewall open only on 443 and SSH, every container set to restart on failure, and walk me through a restore of last night’s backup into a scratch database to prove it works.”
None of these require touching metasfresh source code — they are configuration, reports and server work, which is why the agent can do them safely and show you a diff of what changed. Ask it to explain any step before it runs.
See metasfresh on OpenSysLab for the server that runs all of this out of the box.
