Systems integration · Delivery engineering · Security & compliance

Odoo at the centre of commerce and workforce operations

At Zyntrix Technologies Limited, for Celebrations Nigeria

Focus: Systems integration · Delivery engineering · Security & compliance
Evidence: 3 documented proof points
Decision record: Firsthand trade-off included

The brief

What was built

Two production-grade systems around Odoo 19: event-driven Glovo inventory and order middleware for three stores, and a secure employee self-service portal spanning HR, payroll, attendance and multi-stage requests.

Evidence

Recorded outcomes

Encoded five inventory rules — including Glovo ≤ floor(Odoo / 2) — across initial sync, Glovo orders, walk-in POS sales, receipts, transfers, adjustments and returns for AA, AK and Lekki
Built a Next.js BFF and versioned Odoo module for account activation, leave, payslips, attendance, expenses, appraisals, learning and branch-aware approval workflows
Designed failure-safe operations with OAuth2 adapters, signed replay-protected webhooks, idempotency, queues, retry and DLQ handling, recovery sweeps, audit trails, rate limits, Prometheus alerts and runbooks

Decision record

Odoo owns business state; every edge gets a narrow contract

I kept Odoo 19 authoritative for both commerce and employee records. Glovo is only a sales channel, so the middleware enforces five explicit inventory rules and never lets mirrored stock exceed floor(Odoo / 2). The employee browser follows the same boundary: it talks to a Next.js BFF, which calls a narrow versioned Odoo API. Its PostgreSQL database stores sessions, OTP challenges, rate-limit buckets, audit events and webhook idempotency records — never a second copy of HR or payroll data. That boundary keeps ownership clear while giving each integration its own retry, security and recovery controls.

Return to all work