Odoo ERP Platform
2025—2026ERP · Backend
Custom Odoo 18 modules running production, sales, logistics and billing for an ice and cold-chain manufacturer.
- Odoo 18
- Python
- PostgreSQL
- OWL
- n8n
- WhatsApp Business
AI & Automation Engineer
Integrations · AI Agents · ERP
Mechatronics Engineer focused on AI, automation and system integration. I turn manual processes and ambiguous requirements into reliable solutions, connected to the platforms a business already runs on.
3+
years building production systems
90+
custom ERP modules in the codebase
285
commits as 2nd contributor on the ERP monorepo
10
shipped projects documented as case studies
Source code for employer and client projects is proprietary and not published. These are write-ups: the problem, what I built, the stack, and my actual role — with commit counts where they are verifiable.
ERP · Backend
Custom Odoo 18 modules running production, sales, logistics and billing for an ice and cold-chain manufacturer.
IoT · Data Architecture
Plant telemetry ingested into the ERP, reconciled against human capture, and surfaced by role.
PWA · Full-stack
A React PWA to run and record plant, sales and delivery operations live against the ERP.
E-commerce · Payments
Consumer storefront with passwordless login and card payment resolved through the ERP.
E-commerce · Frontend
Self-service ordering for retailers, against a catalog derived live from the ERP category tree.
Microsoft 365 · Low-code
A Power Apps canvas app, SharePoint data model and Power Automate flows that turn field inspections into signed PDF reports.
AI Agents · Commerce
A chatbot that takes an order through WhatsApp and drives it all the way to a warehouse pick — writing to the ERP, not just answering questions.
AI · Automation
AI agents and chatbots wired into the systems where the business actually runs.
Own product
An API that runs a WhatsApp promotions and referrals channel. Built from scratch.
Integration · Automation
Listing and catalog data kept current across marketplaces, without manual checks.
The same three ideas show up in almost everything above. They are what separate a demo from a system that survives contact with an operation.
Machine data never becomes a business number in one hop. It lands as evidence, gets reconciled against human capture, and only then drives a decision.
01
Field devices retry on bad connectivity. Every write path I build — packing capture, WhatsApp sends, webhook intake — is guarded against double-submission, because in the field a retry is the normal case, not the edge case.
02
An operator, a plant manager and finance need different detail and different permissions over the same data. I build one logic and one truth, then present it per role — rather than letting a dashboard quietly become the system of record.
03
Timezones, tax rounding, company scoping. A daily close that computes 'today' in UTC will be wrong every single day until it is fixed where the data is written, not patched in the report.
What I reach for. Depth varies — the ERP and automation side is where I have the most production mileage.
Open to AI engineering, automation and integration roles — remote or in Guadalajara.