Odoo & Python Engineer · Systems Administrator
_{Chile 🇨🇱 · Available for consulting engagements and freelance projects}

6+ ERPs in production  ·  20+ custom modules shipped  ·  6 industries

_{🇪🇸 Leer esta página en español}

I build and maintain Odoo ERP systems that run day-to-day operations for companies in Chile, through Fitsoft. My work sits where backend development meets operations: I write the Python modules, integrate the external APIs, run the PostgreSQL migrations and keep the Docker infrastructure alive.

I come from a Windows/Linux systems administration background — Active Directory, GPO, WSUS, DNS/DHCP, VPS management — which means I ship code I also know how to deploy, debug and operate in production, not just code that passes on my laptop.

What I'm good at: turning manual, fragile business processes into versioned, tested, self-service software.

Custom modules on Odoo 17, 18 and 19 (Community and Enterprise) — data models, business logic, security rules, backend views, QWeb reports and customer portals. Everything through inheritance, so third-party and Enterprise modules stay upgradable.

Moving instances between Odoo versions and from SaaS to self-hosted, including data migrations written to be idempotent and safe to re-run, and re-implementing no-code customisations as proper versioned modules.

REST APIs and webhooks against payment providers, GPS/telematics platforms and messaging services — with signature verification, idempotent handlers and server-side validation, because a payment flow should never trust the browser.

Working with l10n_cl and electronic invoicing: certificates and signing, CAF folios, document references and statuses, extending the flow from a custom module without touching the base.

Dockerised Odoo deployments (doodba), PostgreSQL, Nginx, backups and VPS administration on Ubuntu, plus Windows Server / Active Directory environments.

Standalone services and tooling outside the ERP: web scraping, data processing with pandas, PDF generation, and small Flask services deployed behind gunicorn.

Field service · Fleet and vehicle rental · GPS telematics · Medical device distribution · Wholesale and retail · Transport and logistics

Core

Web & frontend

Infrastructure & operations

• Test before you touch it. On code that moves money, the regression test that pins the current expected output comes before the refactor, not after.
• Inheritance over patching. Third-party and Enterprise modules are read-only; changes live in my own module so the next upgrade doesn't erase them.
• Migrations are idempotent and gated. Anything that runs against real data must be safe to run twice, and must stop rather than destroy.
• Decisions get written down. Conventions, architecture decisions and their reasoning are documented, so a choice made months ago is still explainable today.
• AI as leverage, not as an oracle. I use AI tooling built around my own documented conventions, and I review everything that comes out of it.

_{Most of my work lives in private client repositories — I'm happy to walk through real code and architecture on a call.}

If any of this sounds familiar, I can probably help:

• You're migrating Odoo versions, or leaving SaaS for a self-hosted setup you actually own.
• Your customisations break with every upgrade — or nobody documented how they work.
• You need payments, Chilean e-invoicing or an external platform wired into your ERP, reliably.

Sound familiar? Email me and let's talk it through — remote or on-site in Chile.

_{⚡ Software that survives the next upgrade.}