← All projects

In progress Oct 2026 — present

Odoo 19 — one database for a pharma group, with an AI agent on top

Replacing a home-grown BI system, spreadsheets and a FaceID vendor portal with one Odoo instance for three companies: custom modules, parity-tested migration, row-level-secured analytics and a Telegram agent that answers questions with each employee's own rights.

Role
Solo: architecture, modules, data migration, access model, AI agent
Stack
Odoo 19 Community · Python · PostgreSQL 16 (RLS) · OWL / JavaScript · Docker Compose · openpyxl · LLM tool use · scikit-learn
custom modules, ~17k lines (Python, XML, JS)
7
parity and integration test scripts — 0 differences vs the legacy system
21
read-only tools behind the Telegram agent
15
companies, one user model, uz/ru UI
3

The problem

A pharmaceutical group (a manufacturer with two brands, a distributor and an IT company) ran on five disconnected systems: a home-grown Node.js BI for sales, Excel files from distributors, a vendor portal for FaceID attendance, an order book in a legacy app, and 1C for accounting. Every report was assembled by hand, people existed under different names in each system (Cyrillic in one, Latin in another), and nobody could answer “who sold what last month” without opening three tools.

Leadership asked for one database. I chose Odoo 19 Community on Docker rather than writing another custom system: the HR, sales, inventory and access models already exist, and the work is in the domain logic, the migration and the guarantees.

What I built

How I know it is right

Decisions worth noting

Status

In daily use for sales reporting and attendance since mid-October 2026; order entry and SLA went live on 22 October. Telephony integration, pricelists and the 1C bridge are still open.