Tryton ships deliberately plain. Making it fit your business means modules, fields, print templates, permissions, and configuration — work that is mostly editing files, running administration commands, and restarting services. That is precisely what a vibe-code agent does well, and it explains every step while it works. Here are ten customizations to ask for.
1. Activate a New Module
Tryton’s functionality arrives as modules: dunning for overdue reminders, lot tracking for traceability, production for manufacturing, SEPA for bank payments. Installing one means installing a package, activating it on your database with the administration tool, and restarting the server. The agent can do the whole sequence, check the server log for import errors, and tell you which menu entries appeared. Try: “Install the account_dunning module, activate it on my database, and tell me which menu entries appeared.”
2. A Custom Field Where You Need One
If a party should carry a loyalty tier, or a product needs an internal SKU separate from the sale code, that’s a small custom module — a field definition, a view change, and a database upgrade. It is half an hour of work for the agent and it survives upgrades because it lives in its own module directory. Fields added this way also appear in searches and export like built-in ones. Try: “Create a custom module that adds an internal SKU field to products and shows it on the product form, then deploy it on my database.”
3. An Invoice Template That Looks Like You
Tryton prints its reports from OpenDocument templates, which means your invoice layout is a file the agent can copy and restyle. Add your logo, bank details for the payment reference, and the footer text your accountant expects, then set the custom report as the default for customer invoices. Print one test invoice before making it live. Try: “Make a custom invoice report with my logo, bank details, and a payment reference in the footer, and set it as the default invoice print.”
4. A Least-Privilege User for the Bookkeeper
Not everyone needs the keys. Tryton’s groups and model permissions let you shape exactly what a user can see and touch, so a bookkeeper can post invoices without being able to edit the chart of accounts, change taxes, or close periods. Describe the role in plain words on paper first; the agent will translate it into groups and test each rule against a sample login. Try: “Create a user for my bookkeeper who can read parties and products and post invoices, but can’t edit the chart of accounts, taxes, or close periods.”
5. Open the New Fiscal Year Properly
Year-end in Tryton is a sequence, not a button: close the final period, create the next fiscal year with its periods, and post the opening balance move so reports stay continuous. Doing it in the wrong order strands draft moves in a limbo nobody enjoys untangling. The agent can prepare the whole sequence and verify each step, and it can print the balance reports before and after so you can see the carry-over worked. Try: “Set up the 2027 fiscal year with monthly periods, then walk me through closing December 2026 and creating the opening balance move.”
6. Analytic Accounts for Real Cost Tracking
The analytic modules let you tag every move line with a project, department, or cost center, and then report on it — turning your general ledger into management accounts. Wiring it up is configuration, not code, but the terminology trips people up, which is why it stays unused. The agent can set the dimensions and prove them with a sample report split the way your board actually asks questions. Try: “Enable analytic accounting with a Department dimension so revenue and expense lines require a department, and show me a trial balance split by department.”
7. Nightly Maintenance on Autopilot
The database and log files grow silently until disk space becomes the emergency. A small scheduled job can dump the database, keep two weeks of backups, vacuum PostgreSQL, and rotate the server log — boring, reliable, and easy for the agent to wire into a timer entry. It reports the first run and the restored-size of the dump so you know the backup is real. Try: “Set up a nightly job that dumps the Tryton database, keeps 14 days of backups, runs a PostgreSQL vacuum, and rotates the server log — then report its first run.”
8. Harden the Web Client Without Locking Yourself Out
Tryton’s JSON-RPC endpoint and web client deserve the same treatment as any internet-facing service: HTTPS enforced, rate limits on the RPC path, and a shorter session timeout in the server configuration. The catch is testing from both the desktop client and the web client after each change, which is exactly what the agent is good at. Keep one old session open until the new rules are proven. Try: “Force HTTPS in the nginx config, rate-limit the RPC endpoint, and lower the session timeout in the server config — then verify I can still log in from both the desktop and web client.”
9. A Private KPI Dashboard
Tryton’s JSON-RPC interface can feed a small web page with today’s numbers — open sales, invoices posted, items below their reorder point — without buying a BI tool. The agent can build the page, read the data over the API, and put a simple password in front of it. It runs beside Tryton and reads only what you allow, so the ERP stays the single source of truth. Try: “Build a small internal dashboard that shows open sales, invoices posted today, and items below their reorder point, reading from Tryton over the API, and protect it with a password.”
10. One Screen for Data Cleanup
Recurring cleanup — parties with no email, products with no category — goes faster when the mess is gathered in one place instead of hunted through menus. The agent can add a custom view or menu entry that opens exactly those records, so a monthly ten-minute pass keeps the database honest. The same pattern works for any rule you care about: duplicate bank accounts, parties without a payment term, products without a unit of measure. Try: “Add a menu item that opens a list of all parties missing an email plus all products missing a category, so I can clean them in one sitting.”
Each change above is code or configuration on your own server. The agent shows its work as it goes, so you can review what changed and keep the system understandable long after the chat is closed.
