Case study
How a Spanish industrial company runs purchasing, sales and projects on Odoo — from v8 to Enterprise
A Spanish industrial company today runs purchasing, sales, quotes, tasks and projects on Odoo, with shop-floor staff clocking in from their phones. The system has come through several version migrations — from Odoo v8 to 16 + Enterprise — without losing a single custom development along the way.
The starting point
The project started on Odoo v8, with a clear goal: one system for purchasing, sales, quotes, and task and project management, with shop-floor time tracking from mobile phones instead of a fixed terminal. Odoo had already been evolving for years when we began, and the challenge wasn't just implementing it — it was making sure whatever was built on top would survive the versions still to come.
What was implemented
Purchasing
Supplier purchasing management integrated with sales and projects, in the same system.
Sales
Sales pipeline connected to quotes and real orders.
Quotes
Quotes that turn into orders without re-entering the data.
Tasks and projects
Task and project tracking tied to the same quotes and purchase orders.
Mobile clock-in
Shop-floor staff clock in from their phones, with no dependency on a fixed terminal.
The methodology: client-layer modules, zero core changes
Every custom development is always built in the client's customization layer — never by touching Odoo's core. The result is verifiable: version upgrades run clean, and the custom developments get reapplied and keep working after each upgrade. As we put it to this client: your Odoo updates; so do your developments.
This project is the real-world backing for that methodology: we've accompanied its data migrations across several versions, from Odoo v8 to 16 + Enterprise, with the client's own purchasing, sales, quotes and clock-in modules working on every new version — without getting stuck on v8 or rewriting anything from scratch.
Full CI/CD
Every change to the client's own modules goes through a continuous integration and deployment pipeline before reaching production — the same engineering rigor used to build software, applied here to Odoo customizations instead of deploying changes by hand.
And the project keeps its own AI trainer
uKodeIT and uKITAIz are the same company. As part of the implementation, the project is handed over with its own AI model trained as a special trainer: the client's team can ask, at any time, about the specifications and processes of their own project, in natural language. It's always a private AI — trained for this client and deployable on controlled infrastructure, with no dependency on third-party clouds. It's offered as part of the implementation service, not as a uKore feature.
Frequently asked questions
- For confidentiality we don't reveal the client's name: we describe it as a Spanish industrial company. The technical details of the case — modules, versions, methodology — are real.
- That no custom development touches Odoo's core code. So when Odoo ships a new version, the upgrade runs clean and the custom developments get reapplied and keep working — instead of getting stuck on an old version or having to be rewritten.
- That every change to the client's own modules is tested and deployed through an automated pipeline before reaching production, instead of being pushed by hand — the same control used to build software applied to Odoo customizations.
- A private AI model, trained on this specific project's specifications and processes, that the client's team can query in natural language. It's an implementation service from uKodeIT/uKITAIz, deployable on controlled infrastructure — not a feature included in uKore.