Skip to content
Back to the timeline

Experience

Odoo Developer and Consultant — Work-Study

Development and maintenance of Odoo modules (Python, PostgreSQL). Design and development of a B2B e-commerce site with Symfony. Corporate website redesign with Next.js. Solo management of Odoo v16 → v19 migration. Database administration, CI/CD, and VPS server management (OVH, DigitalOcean).

Professional experience

1UP Distribution

Dec. 2024 — Present

Chambéry · Savoie

Step in detail

A step built through practice

A cross-functional role in ERP

At 1UP Distribution, I work on subjects ranging from business rules to interfaces used every day. Odoo modules require me to understand company processes, formalize exceptions with the people concerned, and turn those rules into maintainable Python models, XML views, and tests.

Connecting product, ERP, and infrastructure

This experience brings together several case studies: the migration from Odoo 16 to 19, internal business modules, the Symfony B2B site, and the Next.js corporate redesign. I also take responsibility for databases, CI/CD, and VPS servers. This scope forces me to reason in dependencies: a data, API, or interface change must remain compatible with users' work.

What this step is teaching me

Autonomy does not mean making decisions silently. It means moving forward, documenting choices, making risks visible, and seeking an arbitration before an assumption becomes an incident. The migration and business modules strengthened this method as much as they strengthened my technical practice.

Turning complexity into a work plan

The migration makes this change of scale especially visible: the ERP involved 20 direct internal users, 16 custom modules, third-party extensions, and numerous Studio customizations. It required three successive major-version migrations, checks on data and attachments, and stabilization after cutover. This experience taught me to break a broad responsibility into inventory, priorities, controlled trials, functional checks, and traceable decisions instead of confusing speed of execution with risk control.

Designing for the people who use the system

The related case studies are not isolated workstreams: business modules automate rules that may be known only by the teams, the B2B portal depends on ERP data, and the corporate site must make the offer understandable without degrading mobile access or published content. This continuity requires me to hold together the stated need, security and data constraints, daily use, and the ability to evolve the solution. The quality of a delivery is therefore measured as much by its behavior in real work as by its technical implementation.

In perspective

The case studies that make this step concrete

The case-study pages detail the situations, decisions, and outcomes mentioned in this journey entry. The markers below provide a concise reading: they connect this step to fuller evidence without confusing an assignment, a learning outcome, and an established result.

Enterprise ERP migration from Odoo 16 to Odoo 19

Context
In summer 2025, 1UP Distribution's Odoo 16 ERP, used by 20 internal users, needed to move beyond its support period with 16 custom modules and third-party extensions.
My contribution
I independently handled preparation, the three successive migrations, testing, production release, and post-cutover fixes.
Established outcome
The ERP and required modules were migrated to Odoo 19 while preserving data, useful business functions, and the intended service continuity.

Business module development for an ERP

Context
At 1UP Distribution, accounting, sales, sales administration, and logistics needs exceeded Odoo's no-code customization capabilities.
My contribution
I independently designed 16 Odoo modules, from requirements analysis through development, testing, deployment, and user support.
Established outcome
The modules automate business tasks, structure shared data, and make functions such as reminders, documents, and B2B synchronization manageable within the ERP.

Corporate website redesign with Next.js

Context
1UP Distribution's showcase website needed to move away from the Odoo builder to present the company more effectively to professional clients across screen sizes.
My contribution
I audited the existing site, formalized the requirements, analyzed the Figma mockups, then built the responsive integration and front-end architecture with Next.js.
Established outcome
The redesign replaces constrained blocks with a continuous responsive interface, reusable components, and interactions that remain accessible without blocking information.

Responsibilities

What I took responsibility for

  • Technical owner for internal Odoo business developments.
  • Autonomous management of the Odoo v16 → v19 ERP migration.
  • Full-stack development across ERP, B2B e-commerce, corporate website, and infrastructure.